
Website Accessibility Checkers Compared
A website accessibility checker scans your pages against the Web Content Accessibility Guidelines (WCAG) and flags problems like missing alt text, low color contrast, unlabeled form fields and broken heading structure. Good free options include WAVE, axe DevTools, Google Lighthouse and Pa11y. No checker can confirm a site is fully accessible: Google's AI Overview, summarizing accessibility sources, says automated tools catch roughly 30% to 50% of issues, so you also need a short manual test with a keyboard and a screen reader.
What an accessibility checker does
A checker reads your page's code and compares it to rules based on WCAG. It is good at finding problems that can be detected by looking at the code:
- Images with no alternative text
- Text and background colors with too little contrast
- Form fields with no label
- Missing page language or page title
- Skipped heading levels or empty headings
- Links with no text, like an icon with no label
- Buttons that are not real buttons
- Some ARIA (accessibility code attribute) errors
It then shows a list of errors and warnings, often marked on the page itself.
If accessibility is new to you, start with our website accessibility guide.
What automated checkers miss
Automated tools cannot judge meaning or experience. They cannot tell you:
- Whether alt text actually describes the image well (only that it exists). See alt text.
- Whether the whole site works with a keyboard alone.
- Whether focus moves in a logical order and is always visible.
- Whether a screen reader announces things in a way that makes sense.
- Whether error messages explain how to fix the problem.
- Whether videos have accurate captions.
- Whether content is understandable and instructions are clear.
- Whether menus, popups and carousels can be operated by everyone.
That is why a "100% score" in a tool is a starting point, not proof of compliance.
Free and paid checkers compared
Features and pricing change. Check each tool's site for current details.
| Tool | Type | Cost | Best for | Notes |
|---|---|---|---|---|
| WAVE (WebAIM) | Browser extension and online checker | Free; paid API for bulk | Visual, page by page review | Shows icons on the page; easy for non developers |
| axe DevTools (Deque) | Browser extension | Free core; paid Pro | Developers and QA | Low false positives; detailed fix guidance |
| Google Lighthouse | Built into Chrome DevTools | Free | Quick check alongside performance and SEO | Accessibility score covers a subset of checks |
| Pa11y | Command line and CI tool | Free, open source | Automated testing in development | Needs technical setup |
| Accessibility Insights (Microsoft) | Browser extension | Free | Guided manual and automated testing | Includes a step by step assessment |
| AccessibilityChecker.org | Online scanner | Free scan; paid plans | Quick site overview | Includes a legislation primer |
| Siteimprove, AudioEye, others | Site wide monitoring platforms | Paid | Ongoing monitoring of large sites | Check what is automated vs reviewed by people |
A practical combo: WAVE for a visual first look, axe for detail, Lighthouse as part of your regular site health checks, and Accessibility Insights to guide a manual pass.
Types of checkers
| Type | What it checks | When to use |
|---|---|---|
| Browser extensions | The page you have open, including content behind logins | Spot checks and fixing specific pages |
| Online scanners | A URL or a few pages | Quick overview before a deeper audit |
| Site wide crawlers and monitors | Many pages on a schedule | Large or frequently updated sites |
| Developer tools (CI) | Code before it goes live | Prevent new problems in development |
| Screen readers (NVDA, JAWS, VoiceOver) | The real experience for blind users | Manual testing |
How to run a check step by step
- Pick your key pages. Home page, a main service page, a blog post, your contact or booking form, checkout if you have one, and any page with video.
- Run WAVE on each page. Note errors (red) first, then contrast errors, then alerts.
- Run axe on the same pages for detailed issue descriptions and fix suggestions.
- Check templates, not just pages. Most issues come from shared headers, footers and page templates, so one fix can solve many pages.
- Do the 15 minute manual test below.
- Log every issue in a sheet with page, issue, WCAG criterion, severity, owner and status.
- Fix, then retest with the same tools.
Add accessibility to your regular website audit so it does not drift.
How to prioritize the results
Scan reports can list hundreds of items. Sort them like this:
| Priority | What it includes | Examples |
|---|---|---|
| 1. Blockers | Stops someone from completing a key task | Form fields with no labels, buttons that cannot be reached by keyboard, a checkout that traps focus |
| 2. Serious | Makes key content hard to use | Low contrast body text, missing alt text on informative images, no captions on key videos |
| 3. Moderate | Causes confusion or extra effort | Skipped heading levels, vague link text like "click here" |
| 4. Minor | Best practice improvements | Redundant alt text, decorative images not marked as decorative |
Fix site wide template issues first (one fix, many pages), then key conversion pages, then everything else.
The 15 minute manual test
Run this on your home page and your most important form.
Keyboard (5 minutes)
- Put the mouse away. Press Tab to move through the page.
- Can you see where you are at all times (visible focus)?
- Can you reach and use every link, button, menu and form field?
- Does the order make sense?
- Can you close popups with Escape or a reachable close button?
- Is there a "skip to content" link?
Zoom and reflow (3 minutes)
- Zoom the browser to 200%. Does text stay readable without overlapping?
- At 400% zoom on a narrow window, can you read without scrolling sideways?
Screen reader (5 minutes)
- Turn on VoiceOver (Mac or iPhone) or NVDA (free on Windows).
- Listen to the page title and headings. Do they describe the page?
- Do images, buttons and form fields announce meaningful names?
- Submit a form with an error. Is the error announced and clear?
Media and content (2 minutes)
- Do videos have accurate captions?
- Does anything flash or auto play with sound?
- Is color the only way information is shown?
Many fixes also improve usability for everyone. See UX design and what makes a good website.
Overlays are not a fix
Some tools sell a script or widget that claims to make your site compliant instantly. These overlays can add useful options, but they do not fix the underlying code problems, and many disability advocates report they interfere with assistive technology. Treat any "one line of code to compliance" promise with caution and fix issues in the site itself.
WCAG versions and the law
- WCAG 2.1 and 2.2. WCAG 2.2 is the latest W3C recommendation and adds criteria on focus visibility, target size and accessible authentication. Many laws and settlements still reference 2.1 AA. Building to 2.2 AA covers both.
- United States. The ADA covers many businesses open to the public, and courts have applied it to websites. Lawsuits are common. See our guide to ADA compliance for websites.
- European Union. AccessibilityChecker.org notes the European Accessibility Act required many private websites serving EU customers to comply by June 28, 2025.
- Canada (Ontario). AccessibilityChecker.org reports AODA fines of up to $50,000 a day for individuals and $100,000 a day for corporations.
This is general information, not legal advice. Check the rules that apply to your business with a qualified professional.
How often to test
| When | What to test |
|---|---|
| Before launching a new site or redesign | A full automated scan plus manual testing of every template |
| Every new page template or major feature | Automated scan and keyboard test |
| Monthly | Automated scans of key pages and recently published content |
| Quarterly | Manual keyboard and screen reader test on key pages and forms |
| Yearly | A fuller review against WCAG AA, ideally including testing by people who use assistive technology |
Content changes create new issues constantly: an image uploaded without alt text, a PDF that is not tagged, a video without captions. Train everyone who publishes content on the basics.
Accessibility statement template
An accessibility statement tells visitors your commitment and how to report problems. It does not replace fixing issues, but it is good practice and shows you take reports seriously.
Accessibility statement for [business name]
We want everyone to be able to use [website]. We aim to meet the Web
Content Accessibility Guidelines (WCAG) 2.2 Level AA.
What we do:
- Test our site with automated tools and manual checks
- Train our team on accessible content
- Fix reported issues as quickly as we can
Known limitations:
- [List any known issues and when you plan to fix them]
Feedback:
If you have trouble using any part of our site, contact us at
[email] or [phone]. We aim to respond within [number] business days.
Last reviewed: [date]
Link it from your footer.
Fixes that solve the most issues
In many scans, a handful of fixes clear a large share of errors because they live in shared templates:
| Fix | Where to make it |
|---|---|
| Add labels to every form field | Form templates and plugins |
| Raise text and button color contrast | Theme colors and design system |
| Add alt text to informative images, mark decorative ones as decorative | Image library and page templates |
| Use one H1 and logical H2 and H3 order | Page templates and content guidelines |
| Make menus and popups keyboard friendly | Header, navigation and modal components |
| Add a visible focus style | Theme CSS |
| Add captions to videos | Video platform settings |
| Give links descriptive text | Content guidelines for writers |
Fix these at the template level, retest, and the next scan will usually be much shorter.
Automated checker vs professional audit
| Automated checker | Professional accessibility audit | |
|---|---|---|
| Cost | Free to low | Paid, priced by scope |
| Speed | Minutes | Days to weeks |
| Coverage | Code level issues only | Code, usability and assistive technology testing |
| Output | List of flagged items | Prioritized findings with fixes and WCAG references |
| Best for | Ongoing checks and quick fixes | Redesigns, legal risk, larger sites |
FAQ
How do I check if a website is accessible?
Run a free checker like WAVE or axe on your key pages, fix the errors it finds, then test manually with a keyboard and a screen reader. Automated tools alone cannot confirm accessibility.
Is there a free accessibility checker?
Yes. WAVE, axe DevTools (free version), Google Lighthouse, Microsoft Accessibility Insights and Pa11y are all free.
Is WCAG 2.1 or 2.2 required?
It depends on the law or contract involved. Many US references still point to WCAG 2.1 AA, while 2.2 is the current W3C recommendation. Building to 2.2 AA meets both.
Can a website be 100% ADA compliant?
There is no official ADA certification for websites, and sites change constantly. The realistic goal is to meet WCAG AA, test regularly, fix issues quickly and publish an accessibility statement with a way to report problems.
Build accessibility into your site
Lucid Brands's Design and Development team builds and fixes websites to WCAG standards, from templates to forms, and keeps them checked as you update content. Contact us to talk about your site, or start with a free website audit.
Your path to lucidity
Get Started With a Free Website Audit
Not sure where to begin? Start with a free website audit. Our team analyzes your website's SEO, speed, content and user experience to identify what to improve first.
Explore More
Related Resources

Website Accessibility (ADA/WCAG)
What website accessibility means, how the ADA and WCAG apply to businesses, the most common issues, how to test your site, whether overlays work, costs, and a prioritized checklist.
Read More
ADA Compliance for Websites
Does your website need to be ADA compliant? What the ADA and DOJ say, why WCAG 2.1 and 2.2 AA are the working standard, a practical checklist, how to test in Chrome, why overlays fall short and what affects the cost.
Read More
Contractor Website Design
How to design a contractor website that turns local searches into calls and estimates: must have pages, a homepage wireframe, trade specific tips, trust signals, service area pages, tracking and a launch checklist.
Read More