Accessibility Checker
Scan a page against WCAG and see your compliance exposure.
An automated scan reliably catches roughly a third of accessibility problems. A clean result here is a good sign, not a certificate of compliance — keyboard traps, unclear labels and confusing flows need a person to find.
Scan a page against the same axe-core rules Google Lighthouse uses, and see which WCAG success criteria it fails. Each finding names the criterion it maps to, so the result is something you can hand to a developer or a lawyer rather than a number without provenance.
Is my business legally required to be accessible?
Quite possibly. The European Accessibility Act applies to a wide range of products and services sold to EU consumers, including e-commerce and banking. In the United States, ADA Title III has been applied to websites through a long line of case law. The UK Equality Act imposes a duty to make reasonable adjustments. Whether it applies to you depends on your sector, size and where your customers are — this scan tells you your technical position, not your legal one.
How much can an automated scan actually catch?
Research consistently puts it around a third of WCAG issues. Automated tools are excellent at things with a definite answer — a missing alt attribute, insufficient contrast, an unlabelled form field. They cannot judge whether alt text is meaningful, whether a keyboard user can escape a modal, or whether your error messages make sense. A clean automated result is necessary but not sufficient.
What standard should we be aiming for?
WCAG 2.2 Level AA is the reference point nearly all legislation points at, and it is achievable for most sites. Level AAA is not expected across an entire site and is unrealistic for some content types.
Our site is built with a page builder. Does that matter?
It matters a lot, because it limits what you can change. Some builders emit reasonably accessible markup; others produce structures that cannot be fixed without leaving the platform. Worth finding out before you commit to a remediation plan.
Where should we start?
Work through the automated violations first — they are the cheapest fixes and often the highest-frequency ones. Then get a real audit that includes keyboard-only and screen-reader testing on your key journeys: sign-up, checkout, contact. Those journeys are where inaccessibility actually costs you customers.
We build the kind of software this tool is a small piece of — web platforms, mobile apps and design systems, end to end.