What scanning cannot detect
Automated testing finds only part of all accessibility barriers. Here is what our scanner covers, and what needs a person to check.
What automated scanning detects
Compliable runs the open-source axe-core engine (v4.11.1) in a real headless Chrome browser, on desktop and mobile. Typical findings include:
What needs human review
These barriers cannot be confirmed by an automated scan, so a clean scan result does not mean a page is accessible.
Judgement and Meaning
A scanner can tell that something exists, but not whether it makes sense to a person.
Examples:
- Whether alt text actually describes the image
- Whether link and button text is clear in context
- Logical reading order and meaningful sequence
- Plain, understandable error messages and instructions
Interaction and Keyboard Use
Many interaction problems only show up when a person operates the page.
Examples:
- Completing tasks with a keyboard alone
- Logical focus order and visible focus indicators
- Menus, dialogs and custom widgets that trap or lose focus
- Behaviour with screen readers and other assistive technology
Media and Documents
Content in other formats needs its own review.
Examples:
- Accuracy of captions and transcripts
- Audio description for video
- PDFs and other downloadable documents
Content Outside the Scanned Page
Compliable scans public pages as a visitor's browser loads them.
Examples:
- Pages behind a login or paywall
- Content that only appears after user actions
- Third-party embeds such as chat, maps or payment forms, which may need fixes from the vendor
Need a full review?
Our expert audits cover what automated scanning cannot, with remediation guidance your team can act on.
Note: No automated tool can guarantee compliance with the AODA, the Accessible Canada Act, the ADA or any other law. Compliable reports are not legal advice. For legal guidance, consult a qualified lawyer.