Scan the site
Crawl pages within your responsible scope and run automated accessibility checks.
$ a11y-tracker scan https://www.example.gov
Scanning 1,243 pages…
Scan completeTurn accessibility findings into a repair plan.
A11y Tracker groups repeated barriers, preserves the evidence, and verifies fixes with every new scan.
See how the worklist comes togetherWorklistRoot problems found in the latest scan.
All severities⌄Critical8Serious17Moderate23Minor31Total79
FindingSeverityStatusAffected pagesLast seen
Buttons missing accessible nameButtons must have accessible text CriticalOpen154May 12, 2026
Form inputs missing associated labelsAutomated WCAG finding CriticalOpen96May 12, 2026
Color contrast below 4.5:1Automated WCAG finding SeriousOpen203May 12, 2026
Links with the same accessible nameAutomated WCAG finding SeriousFixed47May 12, 2026
Images missing alternative textAutomated WCAG finding ModerateOpen71May 12, 2026
A clear, repeatable process for accessible experiences
Group the root problem
Aggregate repeated issues by root cause so your team can plan high-impact repairs.
{
"finding": "Buttons missing name",
"occurrences": 154,
"affected_pages": 154
}Verify the repair
Rescan to confirm fixes are in place and no regressions were introduced.
$ a11y-tracker rescan
Rechecking 154 affected pages
0 remaining · Status: FixedThe worklist between “we found issues” and “we fixed them.”
Automated scanners are good at detecting failures. A11y Tracker is built for the harder part: turning those failures into coordinated, evidence-backed repair work that stays current.
Triage root causes, not duplicate alerts
Repeated occurrences are grouped into stable findings, so a shared navigation defect becomes one repair—not hundreds of disconnected rows.
Give developers proof, not a spreadsheet dump
Each finding keeps the affected page, selector, HTML excerpt, screenshot, standards reference, user impact, and repair guidance together.
Show what changed—and what still needs people
Clean rescans verify fixes and surface regressions, while responsible scope language keeps automated results from being mistaken for compliance.
Evidence you can act on
Every finding includes the details developers need to reproduce, understand, and fix the issue.
- Selector
button.menu-btn- HTML
<button class="menu-btn" aria-hidden="true">…</button>- WCAG criterion
- 2.1.1 Keyboard
- Impact
- Users cannot access or understand this control.
Responsible scope
Automated testing helps you find and fix accessibility issues at scale. It does not replace expert judgment or user testing.
- Define your responsibility
Test the pages, templates, and components you create and control.
- Use automation as a force multiplier
Surface issues early, track them to resolution, and prevent regressions.
- Validate with people
Confirm the experience works for real users with diverse disabilities.
Vigilant. Civic. Operational.
Make accessibility work visible—and finishable.
See how A11y Tracker turns a real website scan into a prioritized repair plan your team can understand, hand off, and verify.