axe-tools

Appearance

Frequently Asked Questions ​

Please review this list of frequently asked questions for answers to common problems. If you don't see your particular question answered, please contact Ross Miller or Denny Crall.

Campus Data Report ​

How do I test my application's axe-tools configuration? ​

There is currently no reporting data for axe-tools test infrastructure. Axe Tools should have minimal impact on your application's core functionality. Our guidance is to deploy to production quickly and adjust as needed.

When can I expect to see my application's data appear in the accessibility report? ​

The raw accessibility data is loaded into the warehouse early each morning before the start of business. If your application is newly registered, it should appear in the Campus Data report at the beginning of the following day (if there is activity to report). Additionally, the report includes an information icon (circled i) in the upper-right-hand corner. Click this icon to see the last refresh date.

As a developer, what is the best way to review reported results for my application? ​

The best way to review your application's results is to open the report in Campus Data. However, there are multiple views of the report to inspect. Look on the bottom edge of the screen, and you will see there are two tabs. Select the "Developer" tab. Once the tab is loaded, drill down to your application using the "Team Name" and "Application Name" filters near the top-middle of the page.

Configuration ​

My accessibility report shows violations from browser extensions. How can I filter these out? ​

Browser extensions (like Grammarly, password managers, or ad blockers) can inject content into web pages that causes accessibility violations. These violations are not part of your application's code and are outside your control.

To filter out browser extension violations, set the filterExtensionViolations option to true in your Axe Tools configuration:

ts
app.use(AxeToolsPlugin, {
  appName: 'my-app',
  teamName: 'my-team',
  logReport: true,
  filterExtensionViolations: true
})

When enabled, Axe Tools will automatically exclude violations that originate from browser extensions (identified by URLs like chrome-extension://, moz-extension://, or extension://). See the Browser Extension Filtering section in the examples documentation for more details and configuration examples for different frameworks.

Should I use targetElement or filterExtensionViolations to handle browser extension issues? ​

Both options can help reduce false positives from browser extensions, but they work differently:

  • targetElement: Limits the scan to a specific part of your DOM (e.g., #app). This prevents scanning of any content outside that element, including extension-injected content that appears elsewhere on the page. Use this when you want to scan only your application's root container.

  • filterExtensionViolations: Scans the entire page but filters out violations specifically caused by browser extensions. This is useful when extensions inject content within your application's DOM. Use this when you want complete page coverage but want to exclude extension-related violations.

You can use both options together for maximum protection against extension-related violations. However, if extensions are injecting content outside your application's root element, targetElement alone may be sufficient.