Find out where your website shuts out people with disabilities, and exactly what to do about it. Every finding is tied to its criterion and comes with a fix that has been tried against the code itself. The report also says where a person still has to look.
The Agentic Part
An agent checks semantic HTML, ARIA, contrast, keyboard operation and images against WCAG 2.1 AA and ties every finding to its exact criterion. For each finding, it checks a fix against the real code. Where a judgment needs a person, it flags that in the report.
Main Features
- First pass through common problem spots: unnamed buttons, blocked zoom
- Contrast values computed from the design tokens
- Internal page references checked for broken targets
- Fix recipes for CMS-exported and newly built pages
- Fixed audit workflow with checks for a missing browser
Use Cases
- A new landing page needs to launch without shutting anyone out, but nobody on the team knows exactly where the problems sit. Every finding gets tied to a WCAG 2.1 AA criterion.
- A contrast value on the site looks too weak for low-vision visitors, but which one isn't clear. Contrast values are computed from the site's own design tokens and checked.
- An internal link leads nowhere after a subpage got renamed. The check on internal page references catches it.
- A finding can't be decided automatically with confidence, say whether an image's description is accurate. The report shows where a person still needs to check.
What we build for you
- The site's own markup and design tokens
- The language recorded in the lang attribute
- Whether the legal scope applies or WCAG is voluntary
- Whether an accessibility statement is needed, and in which language
