WCAG 2.2 · ADA · EAA · Section 508
Run a free WCAG 2.2 AA scan in seconds. Combine automated testing with expert manual audits to identify code-level barriers and build a clear remediation roadmap for your team.
Source: World Health Organization, Disability and health fact sheet (opens in a new tab)
Source: WebAIM Million 2026 (opens in a new tab) · published 30 March 2026
Source: WebAIM Million 2026 (opens in a new tab) · published 30 March 2026
Compliance deadlines
Which rule applies to you depends on where your customers are and what kind of organisation you run. These are the three with dates attached.
European Accessibility Act
Any business selling to consumers in the EU, wherever it is registered
In force since 28 June 2025
Already enforceable. The only exemption for services is microenterprises — fewer than 10 employees and under €2 million annual turnover. Being based outside the EU does not exempt you.
EN 301 549
ADA Title II
US state and local government, including public universities
26 April 202726 April 2028 — populations under 50,000 and special districts
The DOJ extended both dates by one year on 20 April 2026. The extension moved the deadline only — the underlying obligation stayed in force throughout.
WCAG 2.1 AA
HHS Section 504
US healthcare organisations receiving federal funding
11 May 202710 May 2028 — recipients with fewer than 15 employees
Extended by one year on 7 May 2026. Meeting the Title II rule does not satisfy this one; an organisation can fall under both.
WCAG 2.1 AA
We test to WCAG 2.2 AA. Where a regulation names WCAG 2.1 AA — Title II, Section 504, EN 301 549 — testing to 2.2 covers it, and every finding is tagged with the version its criterion belongs to.
ADA Title III is the exception. No regulation names a technical standard for private businesses; courts and the DOJ reference WCAG instead. That is why you will not find a Title III “deadline” on this page. Anyone selling you one is inventing it.
Full deadline calendar and sourcesEAA guideADA guide
Dates reviewed 14 August 2026. This is regulatory information, not legal advice — check your own obligations with counsel.
A visitor-facing widget, developer tooling, and manual audits by testers who use assistive technology daily. Every finding is routed to whoever can actually fix it — content editor, designer, developer, or the vendor who owns that embed.
Install the widget with one line of code, or one click on WordPress. Visitors get control over contrast, text size, spacing, motion and navigation. It changes what they see — not your site's code. No technical skills required.
Programmatic scans and scheduled re-scans. Every finding arrives with the selector, the WCAG success criterion, and a fix snippet tested against NVDA, JAWS and VoiceOver — then exports to Jira, GitHub, Trello or Asana. JSON, CSV and PDF on any plan; REST API on Infrastructure.
Manual audits by testers who use assistive technology daily. Submit your URLs and get a PDF and Excel report mapping every finding to its success criterion, with dates and evidence — the trail regulators and courts look for.
Pages are discovered through your sitemap and crawled. Each is tested against WCAG 2.2 AA by our automated engine, which reliably detects 30–50% of the success criteria. We say which findings fall inside that range and which do not.
Each finding is labelled widget-addressable or developer-only, then assigned to whoever can actually fix it: content editor, designer, developer, or the vendor who owns that third-party embed. A ticket assigned to “front-end” is a ticket nobody owns.
Findings convert to tickets on a built-in Kanban board and export to Jira, GitHub, Trello or Asana with the selector and the fix in the body. Where a manual audit is in scope, our testers cover the criteria automation cannot judge — screen reader flows, focus order, whether an error message explains how to recover. Re-scan to confirm a finding is gone rather than moved.
Every scan is dated and kept, including the runs where things got worse. Raised on the 16th, closed on the 24th — eight days open. No document is an automatic legal pass. What this gives you is a record of continuing, documented effort rather than a reconstruction made afterwards.
Manual audits are included on Infrastructure and available on any plan.
Six services, one account. Every finding carries the same label — widget-addressable or developer-only — whether it came from an automated scan or a human tester.
A floating panel that gives visitors control over font size, contrast, colour filters, spacing, dyslexia-friendly fonts, reduced motion and keyboard navigation. Preferences are stored in their own browser, not on our servers.
On-demand scanning against WCAG 2.2 AA. A 0–100 score, severity for each finding, and — the part nobody else gives you — every issue labelled widget-addressable or developer-only. No login needed for the score.
Human-led WCAG 2.2 AA testing: screen reader passes with NVDA, JAWS and VoiceOver, keyboard-only navigation, focus order and contrast analysis. PDF and Excel reports with a remediation roadmap.
Framework-specific fix snippets for plain HTML, React, Vue and Angular, pre-tested against NVDA, JAWS and VoiceOver. Toggle broken and fixed code to hear what a screen reader announces. Export to Jira, GitHub, Trello or Asana.
Re-scans compared against your baseline — every 24 hours on Launch, every 12 on Scale, continuous on Infrastructure. When something that used to pass stops passing, you get the URL, the selector, the criterion, and whether it needs a developer.
Accessibility statements, dated compliance reports, and VPAT/ACR documentation. Every certificate links to a live transparency profile showing which areas are accessible and where work is ongoing — a snapshot, not a shield.
From criterion to obligation
Every finding corresponds to a WCAG success criterion. The criterion is what regulations point to — which is why one missing attribute can appear in three different legal frameworks at once. Here is a real one, followed all the way through.
See compliance coverageThe finding
Product images have no alternative text
.product-grid img — 112 occurrences
The criterion
WCAG 2.2 · 1.1.1 Non-text Content · Level A
Who enforces it
Who fixes it
Content editor
A widget cannot write a meaningful description
Note the last step. This finding appears in four legal frameworks and our widget resolves none of them. That is the distinction the rest of this page is about.
Partners
The full list lives on our FAQ page.
Start with our free-forever plan to secure your website. No credit card required, no trial expiration.
