Free accessibility check
Website Accessibility Checker (WCAG)
Find the accessibility problems that automated testing can catch reliably: missing labels, unnamed buttons, broken ARIA, missing landmarks and text that is hard to read.
Check accessibility
Enter a page. Its markup is checked, and its contrast is measured when a browser is available.
Why use the Accessibility Checker
Names and labels
Every link, button and form control must expose a name to assistive technology.
Contrast measured
Text contrast is computed against WCAG 2 AA for normal and large text in a rendered browser.
ARIA sanity
Invalid roles, aria-hidden on focusable elements and other patterns that break assistive technology are flagged.
Structure
The main landmark, the heading outline and the language attribute give screen reader users their bearings.
When to use the Accessibility Checker
Compliance groundwork
Start an accessibility review with the problems a machine can find.
Design systems
Check that components ship with names and labels.
Forms
Find inputs that a screen reader announces as just "edit text".
Icon buttons
Catch buttons that contain only an icon and no name.
Before a release
Add an automated pass to the release checklist.
Procurement
Get a quick view of a vendor's site before a deeper evaluation.
Understanding Accessibility
What automated checks can and cannot do
Automated tools reliably find missing labels, missing names, broken ARIA, missing alt attributes and low contrast. They cannot judge whether alt text is meaningful, whether focus order makes sense or whether a custom widget works with a keyboard.
A clean result is a good start, not a certificate. Test with a keyboard and a screen reader before claiming conformance.
The most common problems
- 1Unnamed controls. Icon buttons and links without text or aria-label.
- 2Unlabelled inputs. Placeholders used instead of label elements.
- 3Low contrast. Light grey text on white, below 4.5 to 1 for normal text.
- 4Hidden focusable elements. aria-hidden on links or buttons that can still receive focus.
WCAG and the law
WCAG 2 is the reference for accessibility laws such as the European Accessibility Act, the ADA in the United States and many public sector rules. Most require level AA. Automated checks cover part of AA.
Privacy, safety and limits
The page is read and rendered by AbackAuditBot from Aback servers, without cookies or a login. Pages behind authentication and states that need interaction, such as an open menu, are not tested.
Related tools and guides
Frequently asked questions
Does passing mean my site is WCAG compliant?
No. Automated checks cover a portion of the success criteria. Manual testing with a keyboard and a screen reader is needed for the rest.
What contrast ratio is required?
WCAG 2 AA requires 4.5 to 1 for normal text and 3 to 1 for large text, which is 24 pixels, or 18.66 pixels bold.
Why is contrast skipped?
Contrast depends on the rendered colours, so it needs a headless browser. When none is available the check is skipped with the reason.
What is an accessible name?
The text assistive technology announces for an element. It comes from the visible text, an aria-label, aria-labelledby, a label element or the alt attribute of an image.
Is ARIA required?
No. Native HTML elements are accessible by default. ARIA is for cases HTML cannot express, and wrong ARIA is worse than none.
Does accessibility affect SEO?
Several practices overlap, such as alt text, headings and descriptive links. More importantly, an accessible site works for more people.
Can I check every page?
Run a standard audit to sample up to 25 pages, or a Pro deep audit for up to 100.