ADA Compliance Checker

Check your website for accessibility problems against WCAG 2.2.

A free ADA website compliance checker. ADA claims are measured against WCAG, the web accessibility rules. We load your site in a real browser, run every WCAG 2.2 rule software can test, and do the same on your contact and booking pages. You get each problem with who it stops and how to fix it.

We test the page you enter plus up to three more, contact and booking pages first.

Rated 5.0 on Google and Yelp

The report

See accessibility problems on your site and how to fix them

You get an accessibility score out of 100 and a fix list with the worst problem first. Each problem shows the elements it was found on, the WCAG rule behind it and the change that fixes it.

hansonplumbing.com
Loading your page in a real browser
pages tested
Testing…
Grade F
Every area we tested
Images have text alternativesProblem1 problem on 7 elements: images have no text description.
Text is readable against its backgroundProblem1 problem on 14 elements: text is too faint against its background.
Form fields are labeledProblem1 problem on 3 elements: form fields have no label.
Links and buttons say what they doProblem2 problems on 5 elements: links have no text; buttons have no text.
Page language, title and structurePassedPassed 6 tests.
Works without a mouseWorth fixing1 problem on 1 element: zooming is turned off on phones.
Screen reader code is validPassedPassed 9 tests.
Video, audio and moving contentNot on these pagesNothing of this kind on the pages we tested.
Fix these first
Form fields have no labelBlocks people
3 elements on /schedule-service · WCAG 4.1.2 (Level A)
Fix: Connect a visible label to every field, so a screen reader can say its name.
<input type="tel" name="phone">
Text is too faint against its background
14 elements on 4 pages · WCAG 1.4.3 (Level AA)
text on background: 2.54 to 1, needs 4.5 to 1

How it works

How the ADA check works

The checker opens your page the way a visitor's browser does and runs the WCAG rules inside it. It repeats that on the pages that take your leads, then hands you one list.

The check on hansonplumbing.com

Sample site

  1. 01Home pageLoaded in ChromeA real browser at 1366 × 900 with the scripts running, so the test sees the menus and forms a visitor gets.
  2. 02WCAG rules69 rules runWCAG 2.0 to 2.2, Levels A and AA. The rules come from axe-core, the open-source engine behind the accessibility score in Google Lighthouse.
  3. 03KeyboardTab pressed throughWe press Tab through the page the way a keyboard user moves, and report focus that gets stuck or cannot be seen.
  4. 04Phone sizeTested again at 390 wideThe same page at phone size, then at 320 pixels to catch a page that scrolls sideways.
  5. 05More pages3 more tested/schedule-service, /services/water-heaters and /about. Contact, booking and quote pages come first. Login, cart and policy pages are skipped.
  6. 06Fix list6 problemsA problem found on several pages is one entry. The list runs from what blocks people down to what is minor.

Accessibility score

43/100Grade F

Top of the fix listElements

  1. 1Form fields have no label3
  2. 2Images have no text description7
  3. 3Text is too faint14

4 pages tested, 6 problems on 30 elements.

Send judgment calls to a person
Text over a photo has no single background color to measure. The report lists those under checks by hand and never counts them against your score.
Count a shared header once
A logo with no description sits on every page. It is one element to fix, so the report counts it once.
Name the pages that refused us
A page behind a bot wall, or one that returns an error, is listed as not tested and stays out of the score.

Color contrast

Measure color contrast on every line of text

Pale gray text and white words on a bright button look clean and read badly. We measure each piece of text against the color behind it and show you your own colors with the ratio each one reaches.

The numbers WCAG asks for

4.5 to 1 for normal text and 3 to 1 for large text, which starts at 24 pixels, or about 19 pixels in bold.

Who reads it

People with low vision or color blindness, older eyes, and anyone looking at a phone outdoors.

Problem 3 of 6 · Serious

Text is too faint against its background

WCAG 1.4.3 Contrast (Minimum), Level AA · 14 elements on 4 pages

Family owned since 1987

2.54 : 1

needs 4.5 : 1

Book a visit

2.15 : 1

needs 4.5 : 1

Licensed and insured

7.56 : 1

passes 4.5 : 1

#9ca3af on #ffffff · #ffffff on #f59e0b · #4b5563 on #ffffff

Sample report. Each ratio is computed from the two colors shown.

Names and labels

Find what a screen reader cannot name

A blind visitor hears your page read aloud, one element at a time. An icon, a button or a form field with no name in the code is read as its type and nothing else. We find each one and give you the line of code that names it.

Four rules cover most of it

Links with no text, buttons with no text, images with no description and form fields with no label.

Each one comes with its fix

The report shows the element from your page beside a corrected example to copy.

  • A Facebook icon in the footerSays“link”Fixed“Facebook, link”
  • The menu button on a phoneSays“button”Fixed“Open menu, button”
  • A photo of a finished jobSays“IMG_2041.jpg, image”Fixed“New tankless water heater in a garage, image”
  • The phone field on a formSays“edit text”Fixed“Phone, edit text”

Spoken wording follows VoiceOver and differs a little between screen readers.

Walkthrough

Fix a booking form with no labels

The form on hansonplumbing.com looks fine: three boxes with the words Name, Phone and Address printed above them. The report shows what is missing underneath.

1 · What the report found

hansonplumbing.com

4 pages tested

6 problems found

43

Grade F

Problem 1 of 6 · Blocks people

Form fields have no label

WCAG 4.1.2 Name, Role, Value, Level A · 3 elements on /schedule-service

Who it stops

People using a screen reader.

Who fixes it

Code change, for your developer.

Where we found it

<input type="text" name="name">
<input type="tel" name="phone">
<input type="text" name="address">

2 · What it means

A blind customer hears “edit text” three times and cannot tell which box is which.

The words above each box are plain text. Nothing in the code ties them to the fields, so a screen reader reads the fields without them, and voice-control software cannot find “Phone” when someone says it. This is the form that books the job.

3 · What to do next

  1. Add a visible label above each field and tie it to the field with for and id.
  2. Add autocomplete (name, tel, street-address) so browsers can fill the form in.
  3. Send the form using only the Tab, arrow and Enter keys, date picker included.
  4. Run the check again. The problem drops off the list and the score moves up.
<label for="phone">Phone</label>
<input id="phone" type="tel" autocomplete="tel">

Sample site. The score is the checker's own arithmetic for the six findings in the report above.

Why it matters

Why accessibility problems cost you customers

1 in 4

US adults report a disability

The CDC's count is more than one in four. Vision, hearing, movement and memory all change how someone uses a website.

94.8%

of home pages fail a scan

WebAIM tested the top million home pages in 2025. Nearly all had WCAG failures software could detect, and faint text was the most common.

5,114

lawsuits in 2025

UsableNet's count of digital accessibility suits filed in US courts that year. Many name small businesses, found by scans like this one.

Sources: CDC, Disability Impacts All of Us; WebAIM Million 2025; UsableNet 2025 year-end report.

After the report

Use the report to fix your site

  1. On your own

    Work through the fix list

    Each problem shows the element on your page, a corrected example and who makes the change. Mark each one fixed as you go, then test again.

  2. With our team

    Hand the list to us

    We fix the site's own code: form labels, contrast, image descriptions and menus that work by keyboard. We add no overlay.

    Get In Touch
  3. Next free tool

    Check the rest of the site

    The Website Checkup looks at speed, security and how recently your pages were updated, in one report.

    Run the Website Checkup

Questions

Questions about ADA website compliance

What does ADA compliance mean for a website?

The ADA itself gives no technical checklist for websites. Courts, settlements and the Department of Justice measure a site against WCAG, the Web Content Accessibility Guidelines, at Level AA. An ADA website compliance check is a test of your pages against those WCAG rules.

Is this an ADA compliance checker, a WCAG checker or a website accessibility checker?

All three names describe the same test. We run the WCAG 2.2 Level A and AA rules, which is the standard ADA website claims and Section 508 reviews both lean on, and report every accessibility problem the rules find.

Does a clean report mean my site is ADA compliant?

No, and no automated tool can tell you that. Software tests the parts of WCAG a machine can measure, such as missing labels, contrast and image text. A person has to judge whether an image description is accurate, whether a booking works from start to finish by keyboard, and whether a screen reader makes sense of the page. Fixing everything in this report clears the problems an automated scan can find.

Why do businesses get sued over their websites?

Title III of the ADA covers businesses open to the public, and the Department of Justice has said since 2022 that it covers their websites too. Thousands of website accessibility lawsuits and demand letters are filed in the US every year, and many name small businesses. Plaintiffs' firms find sites by running automated scans like this one.

Which standard do you test against?

WCAG 2.2, Levels A and AA. No regulation names a standard for private businesses yet. Settlements and court orders use WCAG 2.1 AA, and the Department of Justice set 2.1 AA for state and local government sites in 2024. Version 2.2 includes everything in 2.1 plus a few rules, such as a minimum size for tap targets.

Will an accessibility widget or overlay fix this?

No. An overlay is a script that adds a toolbar on top of the page and leaves the code underneath unchanged, so the same problems show up in a scan and to a screen reader. In 2025 the FTC ordered one overlay company to pay $1 million over claims that its tool made websites compliant.

Which pages do you test?

The page you enter, plus up to three more on the same site. You can name them yourself, or we pick them: contact, booking, quote and scheduling pages first, then services, then about. The first page is also tested at phone size and walked through with the Tab key.

Is it free?

Yes, with no trial and no card to enter, and the report is yours to keep, print and share.

What do you do with my email address?

You use it to unlock the report, and we send you a copy. Your address is never sold or shared.

Is this report legal advice?

No. It is a technical test of your pages. If you have received a demand letter or a lawsuit, talk to a lawyer, and send us the report so the fixes start right away.

Want the rest of the site checked too?Run the Website CheckupRun the SEO Report

Where Venbit comes in

Get your accessibility problems fixed

Venbit fixes accessibility problems in the site's own code: form labels, contrast, image descriptions and menus that work by keyboard. We add no overlay, so a screen reader gets the fixed page. Send us the report and we will tell you what it takes.

Or call us at (425) 314-1415

Try another free tool