Every screen you test
Checks run where your tests go, including screens behind a sign-in, a cart or an error state.
Accessibility engine
Accessibility evidence on every release, not yearly
WCAG 2.2 AA checks run inside the tests you already have, manual review sits beside them, and the audit trail is ready to export.
- WCAG 2.2 AA in every test
- Manual review tracked too
- Audit trail ready to export
Open the 'Checkout' page
Check accessibility of 'Checkout' against WCAG 2.2 AA
Press 'Tab' until 'Pay now' has focus
Check that 'Pay now' is fully visible while focused
Coverage that grows with your suite
Automated and manual
axe rules and human review items sit in one checklist per screen, not a scan report and a spreadsheet.
Ready for audit
Every run and review is logged with the person, the build and the evidence, ready to export.
How the accessibility engine works
One more step
An accessibility check applies axe rules to each screen at the moment your test opens it.
- Contrast and name, role and value on every scanned screen
- Dialogs, menus and errors scanned in their open state
- Each finding names the rule, the control and the screen, with a screenshot
What tools can't judge
Many WCAG criteria need a person. The engine tracks them beside the automated results.
- Focus not obscured and target size: automated step plus review
- Non-text content: a reviewer confirms alt text describes the image
- Accessible authentication: sign-in without a memory or puzzle test
Automated checks never prove conformance on their own.
Track review in Quality ViewThe record compliance needs
Accessibility is a compliance question as much as a quality one.
- Status per screen and criterion: pass, fail, needs review or not applicable
- Export to support a conformance report or internal audit
- Trend across releases shows whether things got better or worse
Findings on shared screens
Findings attach to screens in the App Model, so you can see what has been scanned and reviewed.
- Checks run in the same flow as your functional tests
- Results land in Quality View beside functional, visual and security evidence
- An open AA failure on a key screen can block a go decision, with a human sign-off
Questions
Does it make my app WCAG compliant?
No tool can do that alone. The engine finds what automation can, organizes the manual review, and keeps the evidence.
Do I need a separate accessibility tool?
No. A check is one more step in a test you already have.
Get one key journey audit-ready
Bring a key journey and see automated checks, manual review and the audit trail come together.