Find every accessibility issue that excludes users — and that regulators check for.
We audit your site against WCAG 2.2 AA in a real browser using axe-core — the same engine Deque, Microsoft Accessibility Insights, and other professional accessibility tools use. Then the AI goes into your pages, examines each finding in its real context, and reasons through whether it's an actual violation or a false positive — it doesn't just rubber-stamp what axe flagged. For findings where HTML analysis alone isn't enough — text over a background image, contrast in a gradient, elements visually obscured by a cookie banner — Anthropic's multimodal vision-AI analyses the pixels themselves and judges visually. Conclusions are explained in plain language, referencing DOS-lagen, the Accessibility Act, and EAA.
What we look for
axe-core tests every page against 100+ rules mapped to WCAG. We report exactly which rules are broken, which elements are problematic, and what needs to change.
Contrast and readability
Text against background below WCAG 2.2 AA threshold (4.5:1 for body text, 3:1 for large headings). Our most-common finding — often in "brand colours" on CTA buttons or footer links.
Structural semantics
Missing alt text on images, broken heading hierarchies, lists that don't use list tags, clickable div elements without role/tabindex. This is where screen readers lose track of the page.
Keyboard navigation
Focus visibility, tab order, skip links, modal traps. Users navigating without a mouse must be able to reach everything functional.
Forms and error messages
Label associations (a label element paired with its input field), error messages linked to the right field, required fields marked. All specific WCAG criteria that regulators check.
Which level do we audit against?
We audit against WCAG 2.2 level AA — what the law requires (via EN 301 549) and, in practice, the level every serious organisation targets. We don't audit against level A alone (no regulator accepts it) or level AAA (W3C advises against requiring AAA for whole websites, and it's not a legal requirement).
The standard we audit against — stricter than the current legal floor (WCAG 2.1 AA via EN 301 549 v3.2.1) and where the standard is heading. Covers all the criteria DIGG and PTS actually audit.
Which regulations we cover
The accessibility module is built around WCAG criteria mapped to Swedish and EU law.
- DOS-lagen (Swedish Act on Accessibility to Digital Public Services, SFS 2018:1937)
The requirement for municipalities, regions, government agencies, and publicly controlled bodies. Regulator: DIGG. We report every finding mapped to WCAG criteria that DOS-lagen references via EN 301 549.
- Accessibility Act (EAA implementation, SFS 2023:254)
In effect since 28 June 2025 for consumer-facing digital services — e-commerce, banking, e-books, transport info. We help distinguish what's in scope from what's optional for your site.
- EN 301 549 (harmonised EU standard)
The technical standard both DOS-lagen and the Accessibility Act reference. Our scanner maps every WCAG finding back to EN 301 549 clauses so you know exactly what must be fixed to comply.
How it works
- 1Enter your URL
No plugin to install. No code change. Just the address.
- 2axe-core runs on every page
Playwright + axe-core — the industry standard for automated accessibility testing. Same engine Deque, Microsoft Accessibility Insights, and similar tools use.
- 3The AI examines each finding — the code AND the pixels
Instead of a dry list of rule IDs, the AI opens the actual page, sees the element in its real context, and reasons through it: is this a real violation, a false positive, or something that needs more info? For findings where HTML alone isn't enough — text over a hero image, contrast in a gradient, a button visually hidden by the cookie banner — we send the screenshot to Anthropic's multimodal vision-AI, which analyses the image itself and judges visually. You get: what's wrong, which WCAG criterion it breaks, what it means for the user, and exactly how to fix it — often with code examples.
- 4Prioritised action plan
The AI knows a critical contrast fail on a CTA button matters more than a minor heading-hierarchy warning. You get an order to work through.
What you get
- Prioritised action plan with every WCAG violation explained in plain language
- AI advisor to chat with about edge cases — references WCAG and Swedish enforcement practice
- Every finding mapped to WCAG 2.2 AA criterion and EN 301 549 clause — ready to paste into an accessibility statement
- Email when new issues appear between scans
Start scanning your site — free for 30 days
No credit cards. No agents or plugins. See first results within minutes.
Get started