Instant Results
Get a full accessibility report in under 10 seconds, no sign-up required.
Check Your Website
Enter any URL and get a full WCAG 2.1 AA accessibility report in seconds.
axe-core Powered
Built on Deque's axe-core engine — trusted by Microsoft, Google, and more.
WCAG 2.1 AA
Checks against the international standard for web content accessibility.
Free to Use
No account needed. Run as many checks as you like, completely free.
How It Works
Enter a URL
Type or paste any public website address into the checker above. No login or browser extension needed.
We Audit the Page
Our server loads the page in a headless browser, injects axe-core, and runs a full WCAG audit automatically.
Review Your Report
Violations are grouped by severity — critical, serious, moderate, and minor — with code snippets and fix guidance for each.
Fix & Re-check
Apply the suggested fixes in your codebase, then re-run the checker to confirm the issues are resolved.
What Is WCAG?
The Web Content Accessibility Guidelines (WCAG) are a set of internationally recognised standards published by the W3C that define how to make web content more accessible to people with disabilities, including those with visual, auditory, motor, and cognitive impairments.
WCAG is organised around four principles — content must be Perceivable, Operable, Understandable, and Robust (often called POUR). Each principle contains guidelines and testable success criteria rated at three conformance levels:
Level A
The minimum level. Covers the most basic accessibility requirements that, if not met, make it impossible for some users to access content at all.
Level AA
The standard required by most accessibility laws and regulations worldwide, including the EU Web Accessibility Directive and the ADA in the US.
Level AAA
The highest level of conformance. Addresses the widest possible range of users but is not always achievable for all content types.
a11y-check tests against WCAG 2.1 Level AA — the level required by law in most jurisdictions — plus best-practice rules from axe-core.
Common Accessibility Issues
These are the most frequently detected problems across the web. Each one affects real users and is straightforward to fix.
Missing image alt text
Images without an alt attribute are invisible to screen reader users. Every meaningful image needs a descriptive alternative text; decorative images should use alt="".
Insufficient colour contrast
Text that doesn't meet a 4.5:1 contrast ratio against its background is hard to read for users with low vision or colour blindness. WCAG 2.1 AA requires a minimum ratio of 4.5:1 for normal text and 3:1 for large text.
Form inputs without labels
Input fields must have a programmatically associated <label> element. Without one, screen reader users can't tell what information a field expects.
Keyboard traps and missing focus management
All interactive elements — links, buttons, form fields, modals — must be reachable and operable via keyboard alone. Modals that trap focus or widgets that can't be closed with the Escape key lock out keyboard users.
Missing or skipped heading levels
Headings create a navigable document outline for screen reader users. Skipping levels (e.g. jumping from <h1> to <h4>) breaks that structure and makes navigation confusing.
Links with non-descriptive text
Links labelled "click here" or "read more" provide no context when read out of order by a screen reader. Each link's text should describe its destination or purpose.
Why Accessibility Matters
Over 1.3 billion people worldwide live with some form of disability. On the web, barriers like poor colour contrast, missing keyboard support, or unlabelled form fields can make it impossible for these users to access information, complete tasks, or participate in online life.
Beyond the ethical case, accessibility is increasingly a legal requirement. The EU Web Accessibility Directive mandates WCAG 2.1 AA compliance for public sector websites. The European Accessibility Act (EAA), which comes into force in June 2025, extends these obligations to many private-sector products and services. In the US, Section 508 and the Americans with Disabilities Act (ADA) have been used in thousands of lawsuits against inaccessible websites.
Accessible websites also tend to rank better in search engines, load faster on low-bandwidth connections, and provide a better experience for all users — not just those with disabilities. Good accessibility and good usability are the same thing.
Frequently Asked Questions
Is a11y-check completely free?
Yes. There are no accounts, no rate limits, and no paid tiers. You can run as many accessibility checks as you need, completely free.
Does automated testing catch all accessibility issues?
Automated tools like axe-core can reliably detect around 30–40% of WCAG issues — the ones that are objectively testable, such as missing alt text or colour contrast failures. The remaining issues require manual testing with real assistive technologies, because they involve judgement about context, language clarity, and interaction design. Use a11y-check as your first pass, then follow up with keyboard and screen reader testing.
Which browsers and screen readers do you recommend for manual testing?
For Windows, test with NVDA or JAWS alongside Chrome or Firefox. On macOS and iOS, use Safari with VoiceOver. On Android, use TalkBack with Chrome. These combinations cover the majority of assistive technology users on the web.
Why does the checker sometimes fail to load a page?
Some websites block headless browsers or require authentication. Pages behind a login, on private networks, or actively blocking automated traffic can't be audited. If a site returns a timeout or connection error, check that the URL is publicly accessible and try again.
What is the difference between violations and incomplete results?
Violations are issues axe-core is certain about — they definitively fail a WCAG rule. Incomplete results (also called "needs review") are cases where axe-core detected something potentially problematic but couldn't automatically determine whether it's a real failure. These require a human to check manually.
Can I use a11y-check in my CI/CD pipeline?
The checker is a web UI tool, but the same axe-core engine it uses is available as an npm package and integrates with Jest, Playwright, Cypress, and other test frameworks. For automated CI/CD testing, consider using
axe-core directly or tools like @axe-core/playwright.