Accessibility report
79/100
33 of 42 checks passed
- Pass33
- Fail6
- Review3
Free web accessibility checker
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.
79/100
33 of 42 checks passed
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
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
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
By the numbers
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
Every issue comes with its WCAG criterion, its level and the code behind it, so your developers know exactly what to fix.
The scan opens menus, clicks buttons and reveals hidden content, so it finds issues in dynamic sections that standard scanners miss.
Each finding comes with a plain-language explanation, who it affects, and a link to the free WCAG Academy that shows how to fix it.
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"
ExampleProducts ▾PricingContact
Found inside a menu that only appears after a click
Image alternative text 1.1.1 · Level A
What we check
Every <img> element must include an alt attribute. Functional images need meaningful alt text; decorative ones use an empty value (alt="").
Why it matters
Alternative text lets assistive technologies describe images. Without it, screen reader users miss what the image shows.
AffectsBlind usersLow vision
How to fix it in WCAG Academy
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
Who you’re checking for
What to check
Browse with a screen reader and a keyboard, without seeing the screen.
What to check
Zoom in on the screen and rely on strong contrast.
What to check
Need readable text and a clear path from start to finish.
What to check
Motion and distractions make it hard to focus on a task.
What to check
Browse with a keyboard, a switch or voice control.
What to check
Get information through text, not sound.
What to check
Need plain language and clear instructions.
What we check
Images, icons and other visuals are reviewed for accurate text alternatives, and each element is checked so assistive technologies can interpret it correctly.
Every interactive element is tested for keyboard use, with clear focus states, predictable movement and full operation without a mouse.
Headings, landmarks and the page hierarchy are evaluated for clarity, so the structure follows patterns assistive technologies recognize.
Beyond the scan

Every check with its result, its WCAG criterion and level, and the code behind it.
Our specialists test your site with screen readers, zoom and keyboard navigation, and catch what automation can’t judge.
A report from months ago doesn’t show your site today. Scheduled scans watch it as it changes and alert you to new issues.
Our team fixes the accessibility barriers and documents every fix.
Scan and fix issues in plain language, applied directly to your site.
Help responding to ADA demand letters and lawsuits.
A full expert audit, with clear steps to fix every finding.
Any platform
Certificate of compliance
Formal confirmation and a certificate of compliance once remediation is complete
Testing and fixes measured against WCAG 2.2 AA
Compare
From$39/month
Guide
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.
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.
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.
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.
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.
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
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.
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.
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.
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.
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.
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.
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.
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
Scan your domain and get clear WCAG, ADA and EAA findings that show what needs attention first.