Skip to main content

Accessibility testing

TestingBot helps you find accessibility problems in your websites in two ways: automated scans with the open-source axe-core engine, which check pages against WCAG rules, and manual testing with a real screen reader in a Live session.

Automated scans find issues that can be decided from the page's code, such as missing labels or low colour contrast. They cannot judge everything WCAG asks for, so a scan without violations means no automated violations were found, not that the page is accessible.

Which tool to use

You want to Use Good to know
Monitor a URL without writing code, and get an alert when new issues appear Scheduled accessibility scans Runs once or on a schedule in the latest Chrome on Windows 11, with a desktop or phone viewport. Opens the URL without logging in. Pages on localhost or a staging server work through the TestingBot Tunnel.
Scan pages your Selenium tests reach, including pages behind a login tb:accessibility in Selenium One executeScript('tb:accessibility') call returns the axe-core result. Nothing to install in your project.
Add accessibility assertions to a Playwright, Cypress or WebdriverIO suite Playwright, Cypress, WebdriverIO Uses Deque's or the community's axe-core package in your own project, so you choose the axe-core version and rules. Runs on TestingBot browsers like the rest of your suite.
Hear how a page or app sounds to a screen reader user Screen readers in Live TalkBack on Android devices and emulators, VoiceOver on iOS simulators, VoiceOver or NVDA in desktop browsers on macOS and Windows. Manual testing, not a scan.

What gets checked

Scheduled scans and tb:accessibility run axe-core 4.11.1 with its default rules: the WCAG 2.0 and 2.1 level A and AA rules plus axe-core's best-practice rules. axe-core ships its WCAG 2.2 rule, target-size, switched off, so these scans do not check WCAG 2.2's new success criteria. In a Selenium test you can turn it on, or pick other rules, with tb:accessibility options. The accessibility rules overview describes each rule and how to fix it.

Manual checks

Keyboard use, focus order, what a screen reader announces and whether alt text is accurate all need a person. See what automated checks don't catch for a checklist.