Skip to main content

Free web accessibility checker

Web accessibility checker for ADA and WCAG

Is your website accessible? Enter any page URL and see whether it meets ADA, WCAG and EAA requirements, with clear findings down to the code.

Free. For example, nike.com or apple.com/iphone

tabnav Sample report

Accessibility report

Website
example.com
Standard
WCAG 2.1 AA
Laws
ADA · EAA
Checks
42

79/100

33 of 42 checks passed

  • Pass33
  • Fail6
  • Review3

Content & Media 13 checks

Images, icons and other visuals are reviewed for accurate text alternatives, and each element is checked so assistive technologies can interpret it correctly.

WCAGCheckLevelResult

1.1.1SVG and icon elementsAPass

1.1.1Image alternative textAFail

1.1.1Background image labelingAPass

1.1.1Canvas and object ARIA tagsAPass

1.1.1Image map alternative textAPass

1.4.4Content scalability to 200%AAPass

3.3.2Form control visible labelsAFail

3.2.5New window link indicatorsAAAReview

1.3.1Headings must contain textAPass

1.3.1List item structureAPass

1.3.1Proper landmark structureAPass

1.3.1Unique landmark namesAPass

1.3.1Submit buttons inside formsAPass

Keyboard & Focus 11 checks

Every interactive element is tested for keyboard use, with clear focus states, predictable movement and full operation without a mouse.

WCAGCheckLevelResult

2.4.4Link purpose descriptionsAFail

2.4.7Visible focus indicatorsAAFail

4.1.2Interactive element labelsAPass

2.4.1Skip navigation linksAPass

2.1.1Hidden element tabindexAPass

2.5.3Form accessible namesAPass

2.1.2Dialog keyboard trapAPass

2.1.2Dialog keyboard exitAPass

3.2.1Predictable focus changesAReview

2.5.3Label in nameAPass

2.4.6Single main headingAAPass

Page Structure 18 checks

Headings, landmarks and the page hierarchy are evaluated for clarity, so the structure follows patterns assistive technologies recognize.

WCAGCheckLevelResult

1.3.1Heading structure and rolesAPass

1.3.1Form control associationsAPass

2.4.2Page title elementAPass

2.4.4Link descriptionsAPass

2.4.1Search landmark roleAPass

3.1.1HTML language attributeAPass

3.1.2Inline language markupAAReview

4.1.2Non-semantic interactive rolesAPass

4.1.2Improperly nested interactive elementsAPass

4.1.2Empty interactive elementsAFail

4.1.2Hidden interactive elements excluded from screen readersAPass

4.1.2Labels should not contain interactive elementsAPass

4.1.2Submenu trigger aria-haspopupAPass

4.1.2Listbox contains option elementsAPass

4.1.2Option elements without interactive descendantsAPass

4.1.2Form ARIA accessible nameAPass

4.1.2Summary without interactive descendantsAPass

4.1.2Submenu aria-expanded stateAFail

Companies that work with tabnav

  • Greenpeace
  • Jaguar
  • Land Rover
  • SBK
  • Snüz
  • Walkative
  • Absolute
  • Lakewood Township
  • Silicon Valley Real Estate Team, Intero
  • Attorney General of Washington

By the numbers

One scan, 42 checks. Each one mapped to the WCAG criteria behind ADA and EAA requirements.

  • 42

    Automated checks in every scan

  • 17

    WCAG success criteria covered

  • 3

    Standards in one report: WCAG, ADA, EAA

  • $0

    To scan any page of your site

What a good check does

Three things every accessibility check should do. tabnav does all three.

Every issue comes with its WCAG criterion, its level and the code behind it, so your developers know exactly what to fix.

Start a free scan

example.com · findingsSample

WCAGCheckLevelResult

1.1.1Image alternative textAFail

1.4.4Content scalability to 200%AAPass

2.4.7Visible focus indicatorsAAFail

2.1.2Dialog keyboard trapAPass

Empty interactive element · 4.1.2

<button class="icon-close"></button>

Give the button an accessible name, for example aria-label="Close"

Why website accessibility matters

People with disabilities run into websites they can’t use every day. A form you can’t fill in with a keyboard. A button a screen reader can’t name. Gray text no one can read.

Every barrier like that is a customer who left halfway, and a sale that could have been yours. In the US, it can also lead to an ADA lawsuit.

There’s a simpler way.

The tabnav accessibility team

See how it works

Who you’re checking for

An accessible site works for every visitor. And each disability needs different checks.

What we check

42 checks in three categories. Each one tied to a WCAG success criterion and level.

Images, icons and other visuals are reviewed for accurate text alternatives, and each element is checked so assistive technologies can interpret it correctly.

  • 1.1.1SVG and icon elementsLevel A
  • 1.1.1Image alternative textLevel A
  • 1.1.1Background image labelingLevel A
  • 1.1.1Canvas and object ARIA tagsLevel A
  • 1.1.1Image map alternative textLevel A
  • 1.4.4Content scalability to 200%Level AA
  • 3.3.2Form control visible labelsLevel A
  • 3.2.5New window link indicatorsLevel AAA
  • 1.3.1Headings must contain textLevel A
  • 1.3.1List item structureLevel A
  • 1.3.1Proper landmark structureLevel A
  • 1.3.1Unique landmark namesLevel A
  • 1.3.1Submit buttons inside formsLevel A

Beyond the scan

Everything you need to become accessible. Expert testing, fixes, monitoring and documentation, in one place.

A full report for every page

Every check with its result, its WCAG criterion and level, and the code behind it.

Manual testing with assistive technology

Our specialists test your site with screen readers, zoom and keyboard navigation, and catch what automation can’t judge.

Monitoring through the year

A report from months ago doesn’t show your site today. Scheduled scans watch it as it changes and alert you to new issues.

Manual audit

A full expert audit, with clear steps to fix every finding.

Any platform

Check any website. WordPress, Shopify, Wix, Webflow and custom code. If it has a URL, you can check it.

  • WordPress
  • Wix
  • Shopify
  • Webflow
  • Elementor
  • Framer
  • tabnav
  • Joomla
  • Drupal
  • Magento
  • Squarespace
  • HubSpot
  • Next.js

Certificate of compliance

Be ready with documented proof of your accessibility work.

Formal confirmation and a certificate of compliance once remediation is complete

Testing and fixes measured against WCAG 2.2 AA

Compare

Become accessible. Instead of managing dozens of manual tests on your own, one service that handles it all.

Managed accessibility

  • Manual and automated testing
  • Expert fixes, no code changes
  • Documentation of every fix
  • Monthly scans and reports
  • Litigation support
  • Certificate of compliance

From$39/month

What you would manage on your own without a service

  • Testing with NVDA and JAWSManual
  • VoiceOver on iPhone and MacManual
  • Testing with TalkBack on AndroidManual
  • Switch and voice control testingManual
  • Testing with screen magnifiersManual
  • Testing on desktop, tablet and mobileManual
  • Testing every browserEvery update
  • A full-site check every monthMonthly
  • Retesting after every site updateMonthly
  • Keeping accessibility evidenceLegal
  • Documenting every fixLegal
  • Responding to ADA demand lettersLegal
  • Responding to accessibility lawsuitsLegal
  • Preparing a VPAT for procurementLegal
  • Updating your statementManual
  • Making your PDFs accessibleManual

Guide

Website accessibility testing in the US. What to know before you start.

What is a website accessibility test?

An accessibility test checks whether people with disabilities can use your website on their own: read the content, move between pages, fill in forms and complete tasks. It compares the site with defined criteria, such as alt text for images, full keyboard navigation, color contrast, heading structure and labels for form fields.

What does the ADA require for websites?

Title III of the Americans with Disabilities Act covers businesses that are open to the public, and courts have applied it to websites. Title III doesn’t name a technical standard, so WCAG 2.1 or 2.2 at level AA is the benchmark used in most lawsuits and settlements. For state and local governments, a 2024 Department of Justice rule under Title II sets WCAG 2.1 AA as the standard. Read more in our ADA compliance guide.

What is WCAG, and which level do you need?

The Web Content Accessibility Guidelines (WCAG), published by the W3C, are the international standard for web accessibility. Each guideline has success criteria at three levels, A, AA and AAA. Level AA is the target in most laws and lawsuits, including ADA cases, Section 508 and the European Accessibility Act. The latest version is WCAG 2.2. See our WCAG guide.

What’s the difference between automated and manual testing?

An automated scan reads your site’s code and finds the issues that can be measured, such as missing alt text, empty buttons or unlabeled fields. Manual testing covers what a tool can’t judge: whether the alt text really describes the image, whether the focus order makes sense, and whether a screen reader conveys the information clearly.

Why isn’t an accessibility widget enough on its own?

A widget lets visitors adjust the display, for example to enlarge text or raise contrast. It doesn’t fix problems in your site’s code: a button without a name, a form without labels or a component that doesn’t work with a keyboard stay broken. That’s why the site itself needs to be tested, and what’s found needs to be fixed.

How often should you test, and what comes next?

Test after any major change to your site, before launching new pages, and every few months. After a test, start with the barriers that block key tasks, fix by priority and test again. Publishing an accessibility statement tells visitors what you’ve done and how to reach you about accessibility.

FAQ

FAQs about the web accessibility checker

What does a web accessibility checker do?

A web accessibility checker scans your website against WCAG 2.1 AA to find barriers for people with disabilities. It flags issues like missing alt text, low color contrast, keyboard traps and unlabeled form fields, so you know what to fix.

Why is accessibility testing important?

Accessibility testing makes sure your site is usable for everyone, including people who use assistive technologies. It improves the experience for every visitor, helps you meet WCAG and ADA requirements, and lowers legal risk.

How can I test my website for accessibility for free?

Enter your website address in the checker on this page and run a free scan. You get a report with an overall score, issues grouped by category, and clear steps to fix them.

What’s included in the accessibility report?

The report shows an overall accessibility score, issues grouped by category such as images, forms, keyboard navigation and page structure, and plain-language guidance for resolving each one, with the WCAG success criterion and level behind it.

Which standards does the checker test against?

Each check is mapped to a WCAG success criterion and its level (A, AA or AAA). WCAG 2.1 AA is the benchmark used for ADA compliance in the US, and the basis of the European Accessibility Act (EAA) requirements.

Does a free scan prove my website is ADA compliant?

No. An automated scan finds the issues that can be detected in code, but it is not a certification and does not on its own show full compliance. Some criteria can only be verified by manual testing. A certificate of compliance comes with tabnav’s remediation service, after manual testing and fixes.

How often should accessibility testing be done?

Test your website every few months, and after any major design or content update. Regular testing helps you stay compliant and keep an accessible experience for every visitor.

Does improving accessibility help with SEO?

Yes. Good accessibility practices, such as semantic headings, descriptive alt text and a clear page structure, often improve search visibility and engagement.

Didn’t find an answer? Contact us

Start with a smarter accessibility scan

Scan your domain and get clear WCAG, ADA and EAA findings that show what needs attention first.

Free. Enter your domain, for example yourcompany.com

How the accessibility checker works