PDF Accessibility Checker
Check a PDF for tagging, title, language, alternative text, headings, tables, links and forms. Your file is checked in your browser and never uploaded.
Free tool · WCAG 2.2 A and AA
Website Accessibility Checker
Enter the address of a public web page. We load it in a real browser, run the axe-core rule engine against WCAG 2.0, 2.1 and 2.2 Level A and AA success criteria, and give you a report that groups issues by severity, shows the affected elements and explains how to fix them.
- Free, no sign-up
- WCAG 2.0, 2.1 and 2.2 rules
- Fix guidance for every issue
What we check
What the checker tests
The checker loads your page in a real Chromium browser at desktop size, waits for it to finish loading, then runs the open-source axe-core (opens in a new tab) engine against rules for WCAG 2.2 (opens in a new tab) Level A and AA.
Each issue in the report shows how serious it is, which WCAG success criteria it relates to, the affected elements, and how to fix it. Items axe-core can't decide on are listed separately for you to review by hand.
- Accessible namesImages, buttons, links and form fields without a name
- Colour contrastText that doesn't meet the minimum contrast ratio
- Page language and titleMissing or invalid language and page titles
- ARIAInvalid or misused ARIA attributes and roles
- Target sizePointer targets below the WCAG 2.2 minimum
- StructureProblems in lists, tables and frames
Know the limits
What automated testing can't tell you
Automated tools find a meaningful share of common barriers, but not all of them. They can't judge whether alt text is accurate, whether headings describe their sections, whether everything works with a keyboard, or whether error messages are helpful. A clean report does not mean a page conforms to WCAG. Combine it with manual testing, including with assistive technology, and consider a professional audit for important services.
Frequently asked questions
-
Is the accessibility checker free?
Yes. To keep it available for everyone, each visitor can run up to 10 scans an hour and 30 a day.
-
If the report finds no issues, is my page WCAG compliant?
No. Automated rules can only detect some types of accessibility barrier. Many WCAG success criteria, such as whether alt text is meaningful, whether the page works with a keyboard, or whether captions are accurate, need a person to check. Use this report as a starting point, not as proof of conformance.
-
Which standards does it test against?
It runs the axe-core rules mapped to WCAG 2.0, 2.1 and 2.2 at Level A and AA. Rules for AAA criteria and general best practices are not included in the results.
-
Can it check pages behind a login, or my whole website?
It checks one public page per scan. It cannot log in, submit forms, or crawl your site. To check many pages of a WordPress site, use the free AccessMate plugin from your dashboard.
-
Why did my scan fail?
Common reasons are that the website blocks automated browsers, the page needs a login, it took too long to load, or the address points to a file rather than a web page. The report explains which one applied.
-
What happens to the data from my scan?
We store the address you entered, the page title and the scan results so we can show your report. Anyone with the report link can view it. Reports are deleted automatically after 30 days.
Related tools
Accessibility Statement Generator
Answer three short steps to create an honest accessibility statement you can publish. Built in your browser; nothing is sent to us.
Alt Text Generator
Upload an image and get a suggested alt text from AI, tailored to how the image is used. Review it, edit it and copy it into your page.
