Accessibility

Accessibility Audit

Scan any page for WCAG problems — missing alt text, unlabelled form controls and buttons, skipped heading levels, low-contrast text, missing landmarks and duplicate IDs. Each issue is scored by severity, highlights the element on click, and exports as JSON.

When you'd use it

• Catch accessibility problems before a compliance review does
• Check a page behind a login that online accessibility checkers cannot reach
• Produce evidence for an accessibility ticket, with the exact elements listed
• Spot-check a component you just built before opening a pull request

How to use Accessibility Audit

1. Open Accessibility Audit on the page you want to check.
2. Review findings grouped by severity — serious issues first.
3. Click any finding to scroll to and highlight the offending element.
4. Export the results as JSON to attach to a ticket.

Accessibility Audit FAQ

Does passing this mean the page is WCAG compliant?

No. Automated tools reliably catch perhaps a third of WCAG issues. Keyboard-only navigation, focus order, screen reader announcements and whether alt text is actually meaningful all need manual testing.

What does it actually check?

Missing and filename-style alt text, unlabelled form controls, links and buttons with no accessible name, heading order, colour contrast, missing lang, blocked zoom, positive tabindex, duplicate IDs, untitled iframes and missing landmarks.

How does it differ from the Contrast Checker?

The audit scans the whole page across many rules at once. The Contrast Checker is interactive — hover any text for a live ratio while you adjust a design.

Works well with