Skip to content
Framework agnostic accessibility reporter, powered by axe-core
Branch: master
Clone or download
Juliette Pretot and juliettepretot 2.0.1
Latest commit c641728 Dec 10, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
src Fix the disconnect method not working Dec 11, 2019
.gitignore add microbundle Nov 19, 2019
LICENSE Initial commit Nov 19, 2019
README.MD improve readme Nov 30, 2019
WEBPACK_EXAMPLE.MD improve readme Nov 30, 2019
package-lock.json 2.0.1 Dec 11, 2019
package.json 2.0.1 Dec 11, 2019


Agnostic Axe

Agnostic axe logs accessibility issues to the browser console, as you develop your app. Its audits are powered by axe-core.

Basic Usage

Install the module from NPM (npm install --save-dev agnostic-axe) or directly import it from the URL:

  ({ AxeObserver, logViolations }) => {
    const MyAxeObserver = new AxeObserver(logViolations)

Be sure to only run the module in your development environment. Else your application will use more resources than necessary when in production. (Webpack-Example)

Advanced Configuration

The AxeObserver constructor takes two parameters:

  • violationsCallback (required). A function that is invoked with an array of violations, as reported by axe-core. To log violations to the console, simply pass the logViolations function exported by this module.
  • options (optional). An object with that supports the following configuration keys:
    • axeCoreConfiguration (optional). A configuration object for axe-core. Overwrites the default configuration used by agnostic axe.
    • axeCoreInstanceCallback (optional). A callback that is invoked with the axe-core instance.

The AxeObserver.observe method takes one parameter:

  • targetNode (required). AxeObserver performs an audit of this node, and continously monitors it for changes. If a change has been detected, AxeObserver audits the parts that have changed, and reports any new accessibility defects.

To observe multiple nodes, simply call the AxeObserver.observe method multiple times. There should never be more than one instance of AxeObserver running in the same enviroment.


To stop observing changes, call the disconnect method.



Unlike framework specific implementations of axe-core, such as react-axe, agnostic axe uses a MutationObserver to listen for changes directly in the DOM. This has two advantages:

  1. It always works with the newest version of your framework (and even if you switch technologies). For example, at the time of writing, react-axe does not work with React function components or fragments, while agnostic axe does.
  2. It only runs audits if the actual DOM changes. This means it uses less resources than react-axe, which runs audits when components rerender, even if their output does not change.

Agnostic axe is optimized for performance. Its audits are small chunks of work, that are run in the browser's idle periods.

You can’t perform that action at this time.