Skip to content

axe DevTools

Scan one page in your browser and find the exact elements behind accessibility findings. Review the results, check a fix, and follow up with a keyboard and screen reader.

Read official information

What can you check in the browser?

Install the axe DevTools browser extension, open a test page, then open your browser’s developer tools and choose axe DevTools. A full-page scan lists accessibility findings and lets you inspect the part of the page that triggered one.

Deque documents Chrome and Edge support and a limited Firefox version. The extension runs scans using axe-core, a separate open-source library developers can add to their own automated tests.

What should you keep out of a scan?

The extension scans the screen in your open tab. For a sign-in flow, use an approved test account and a copy of the page that contains only fictional data. Deque marks the extension as unsuitable for personal data. Keep real names, messages and account details out of the page you test.

Before scanning a private test page, check how your installed extension handles usage and test results. If your plan offers AI data sharing, check that setting too. Deque documents separate controls. Save or share results only through a destination your team has approved.

Can you check a dialog that only appears after a click?

Use a disposable settings dialog with no live accounts, data or save actions connected. Confirm that before opening the sample. If you can’t check the setup, use a paper sketch and describe where focus should go.

  1. Scan with the dialog open
    Open the sample dialog and scan that screen. If its Close button is only a decorative icon with no name, look for the button-name finding. Inspect which button it points to.
  2. Give the button a useful name
    Give the button the accessible name ‘Close settings’, which a screen reader can announce. Scan again with the dialog open and check the finding for that button.
  3. Check the whole interaction
    Start at the button that opens the dialog. Use the keyboard to open it and check that focus is inside. With a screen reader on, listen for the Close settings button. Press Escape and check that focus returns to the button that opened the dialog.

What does the free extension cover?

The free extension runs an automated check on one page at a time. Deque lists paid Pro features for guided manual checks, saving and exporting results, and testing a sequence of screens. Those Pro extension features are available in Chrome and Edge.

On November 11, 2026, Deque’s public subscription page displayed a 14-day Pro trial and $60 per user per month after it. The page did not name the currency. Confirm the currency and terms before paying. Deque lists integration with automated release checks under a separate Web bundle.

What should you hand off with a finding?

Record the screen state, the affected control and what a visitor could not do. Then write how you checked the fix by hand. An automated report covers the checks it can run on that screen. It leaves questions such as where focus goes after you close a dialog.

Deque documents Pro exports of findings as CSV, JSON and JUnit XML. An export can include the tested address or a piece of the page’s HTML. Review those fields before handing a report to someone else.