ADA website compliance checklist: 10 checks you can run yourself
Is your website ADA compliant? A checklist can't tell you that, but it can show you where buyers with disabilities get stuck. The checks that matter most are keyboard access, a visible focus outline, alt text on images, readable color contrast, labeled form fields with clear error messages, captions on video, readable PDFs, real headings, and text that survives zooming. You can run all ten in an afternoon with a browser and free tools.
The Department of Justice hasn't set a technical standard for private businesses' websites. Its guidance points to WCAG, and WCAG 2.1 or 2.2 Level AA is the common target. What the checks below do is find the barriers a buyer would hit, so you know what to ask whoever runs your site. None of this is legal advice.
Checked against the Department of Justice's ADA guidance and Title II rule, W3C's WCAG 2.2, the EU's accessibility directive and Alkali's first-hand experience building B2B websites, November 2026. Not legal advice.
- Ten guided checks with free tools, saved in this browser
- A record sheet in Google Sheets, Word and PDF
- Sourced to DOJ, W3C and EU texts and our own build work
Where the ten checks look
- Keyboard only
- Check 01
- Visible focus
- Check 02
- Zoom to 200%
- Check 10
Getting around
Can someone reach every menu and page without a mouse, see where they are, and zoom in without the layout breaking?
- Alt text
- Check 03
- Color contrast
- Check 04
- Video and motion
- Check 07
- PDFs
- Check 08
- Headings and links
- Check 09
Reading the page
Do the photos, specs, videos and PDFs that prove what you make reach someone who can't see them, hear them or read small gray text?
- Visible labels
- Check 05
- Errors in words
- Check 06
- Input kept on error
- New in 2.2
Sending the request
Can every field be understood, and does a typo get a clear message instead of a wiped form?
Run the ten checks
This is written for the owner, GM or marketing lead of an established B2B company who wants to know where the website stands before hiring an auditor. Maybe a large customer's vendor questionnaire asked about accessibility. Maybe you read the web accessibility definition and wondered whether your own site would pass the keyboard test.
Work through the checks in order if you can. The first two decide whether a keyboard user can reach anything at all, and checks five and six cover the quote form, which is where a barrier costs you an actual request. Each one says how to run it, why it matters to the people evaluating you, and the exact question to put to your web team, with the WCAG success criteria it relates to so they know what you mean.
Check 1 of 10
01Get through the site and send a quote request with only the keyboard
WCAG 2.1.1 Keyboard (A), 2.1.2 No Keyboard Trap (A), 2.4.3 Focus Order (A)
How to test it
- Open your homepage, put the mouse out of reach, and press Tab to move forward (Shift+Tab goes back). Enter follows a link or presses a button.
- Open each item in the main navigation, including any drop-down menus, and reach a product or service page.
- Go to your quote or contact form, fill in every field, and submit it. Space ticks a checkbox and the arrow keys move through a list of options.
- Tab into anything a third party added, such as a chat widget, cookie banner, dealer locator or product configurator, and check you can Tab back out of it.
- Note anywhere you get stuck, have to reach for the mouse, or the focus jumps somewhere that doesn't follow the page.
Why a buyer cares
Some buyers can't use a mouse at all, and others simply move faster on the keyboard. If the quote form can't be submitted without a mouse, that request never arrives, and nobody on your side knows it was attempted.
What to ask your web team
Can every link, menu, button and form field on the site be reached and used with the keyboard alone, including chat widgets, cookie banners and configurators, without getting trapped, and can you show me the quote form working that way?
Your result for check 1
02Check you can always see where the keyboard is
WCAG 2.4.7 Focus Visible (AA), 2.4.11 Focus Not Obscured (Minimum) (AA, new in 2.2)
How to test it
- Repeat the Tab walk from the first check and watch for the outline or highlight that marks the current link or field.
- Note any stretch where you press Tab and can't tell what's selected.
- Scroll down a long page and keep tabbing. Check the highlighted item is never completely hidden behind a sticky header, a chat bubble or a cookie banner. Partly covered is worth fixing too, but completely hidden is where the AA line sits.
What it looks like
- No visible focus
- Visible focus
Why a buyer cares
Keyboard access is useless if the person can't see where they are. A missing focus outline is often one line of styling someone removed because they didn't like how it looked.
What to ask your web team
Do all links, buttons and fields show a clearly visible focus style, and does anything that sticks to the screen ever completely cover the focused item?
Your result for check 2
03Check product and project photos describe what they show
WCAG 1.1.1 Non-text Content (A)
How to test it
- Turn on the screen reader your computer already has: VoiceOver on a Mac (Command+F5) or Narrator on Windows (Ctrl+Windows+Enter). Press the same keys to turn it off.
- Open a product or capabilities page and move through it. Listen to what's read out for each image.
- Without a screen reader: right-click a photo, choose Inspect, and look for alt= in the highlighted line. alt="" is right for decoration, wrong for a product photo.
- Note images read as a file name (IMG_4471.jpg), as just "image", or skipped when they carry information, and charts or diagrams that have no text version.
What it looks like
- File
- IMG_4471.jpg
- Alt text: IMG_4471.jpg
- Says nothing
- Alt text: Machined aluminum pump housing with four threaded mounting holes
- Describes it
A screen reader reads the first one out as a file name. The second tells the buyer what you made.
Why a buyer cares
Your photos are your proof: the parts you've made, the equipment you run, the finished projects. A buyer using a screen reader gets none of that unless each image says what it shows, and the same text helps search engines understand the page.
What to ask your web team
Does every meaningful image have alt text that describes what it shows, and do charts, diagrams and images of text have a text equivalent on the page?
Your result for check 3
04Check text contrast with a free checker, and that color isn't the only signal
WCAG 1.4.3 Contrast (Minimum) (AA), 1.4.11 Non-text Contrast (AA), 1.4.1 Use of Color (A)
How to test it
- Look for the usual suspects: light gray text, text over photos or video, white text on a pale brand color, and thin outlines around form fields.
- Use a free contrast checker such as WebAIM's (webaim.org/resources/contrastchecker/). Read the two colors with a free color-picker browser extension, or ask your web team for them, and enter both.
- Regular body text needs a ratio of at least 4.5:1. Large text needs 3:1, and so do icons, and field borders where the border is what shows you the field is there.
- Look for places where color alone carries meaning, such as required fields marked only in red, or links that differ from the text around them only by color, unless that link color contrasts at least 3:1 with the surrounding text.
What it looks like
Lead time: 4 to 6 weeks
2.4:1Fails, 4.5:1 neededLead time: 4 to 6 weeks
7.0:1Passes
Measured at body text size, where 4.5:1 is the line.
Why a buyer cares
Low contrast is one of the easiest barriers to spot. It hurts people with low vision, and it hurts anyone reading a spec on a phone in bright light on a plant floor.
What to ask your web team
Do the brand colors and text styles meet WCAG contrast ratios everywhere they're used, including text over images, and is meaning ever carried by color alone?
Your result for check 4
05Check every field on the quote form has a real label
WCAG 3.3.2 Labels or Instructions (A), 1.3.1 Info and Relationships (A), 4.1.2 Name, Role, Value (A)
How to test it
- Type into each field. If the only label was gray text inside the box and it disappears once you start typing, the field has a placeholder, not a label.
- Click on the label text next to a field. On most properly built forms that puts the cursor in the field, so it's a quick sign the label is connected, though not the only way to connect one.
- With the screen reader from check three on, tab through the form and listen: each field should announce its name, and whether it's required.
- Check any required format (part numbers, dates, file types and sizes for drawings) is stated before the person types, not only in an error afterward.
Why a buyer cares
The quote form is where interest turns into revenue. A field that isn't announced is a field the person has to guess at, and guessing on a form asking for quantities, tolerances or drawings is how requests get abandoned.
What to ask your web team
Does every form field have a visible label that stays on screen and is connected to the field in code, and are required fields and formats stated up front?
Your result for check 5
06Submit the form with mistakes and read what it tells you
WCAG 3.3.1 Error Identification (A), 3.3.3 Error Suggestion (AA), 3.3.7 Redundant Entry (A, new in 2.2), 4.1.3 Status Messages (AA), 1.1.1 Non-text Content (A) for CAPTCHAs
How to test it
- Submit the quote form empty, then again with a badly formatted email address.
- Check each problem is described in words next to the field ("Enter an email address like name@company.com"), not only by turning the border red.
- Check what you already typed is still there after the error. W3C's guidance on 3.3.7 Redundant Entry uses a form that keeps the submitted details after an error as an example of meeting it, and losing a half-written request is how requests get abandoned.
- If the form uses a puzzle or image challenge to stop spam, note it. WCAG asks for an alternative that doesn't depend on seeing the image.
Why a buyer cares
Most people make the odd typo. An error that says only "invalid" or flashes red, or one that wipes a half-written request, can send the buyer to the next supplier's form. That's true whether or not they use assistive technology.
What to ask your web team
When a form submission fails, is each error described in text next to the field and announced to screen readers, and does the form keep what the person already entered?
Your result for check 6
07Check videos have captions, and anything that moves can be stopped
WCAG 1.2.2 Captions (Prerecorded) (A), 1.2.5 Audio Description (Prerecorded) (AA), 2.2.2 Pause, Stop, Hide (A)
How to test it
- Play your plant tour, product demo or capabilities video with the sound off. Check captions are available and keep up with the speech.
- Read a minute of the captions. Automatic captions can get product names, materials and part numbers wrong, so check those words in particular.
- Watch it with your eyes closed. If the picture shows things the narration never says, such as a finished part or a process step, AA also asks for audio description.
- Look for anything that moves on its own: a background video, an auto-rotating slider, a scrolling ticker. If it plays for more than five seconds, there should be a way to pause or stop it.
Why a buyer cares
Some buyers watch with the sound off, in an open office or on a plant floor, and Deaf or hard-of-hearing buyers depend on captions. Motion that can't be stopped makes a page hard to read for people with attention or vestibular conditions.
What to ask your web team
Do all our videos have accurate captions, does the narration (or an audio description) cover what the picture shows, and does every auto-playing video, slider or animation have a pause control?
Your result for check 7
08Check your spec sheets, catalogs and other PDFs can be read
WCAG 1.1.1 Non-text Content (A), 1.3.1 Info and Relationships (A), 2.4.2 Page Titled (A)
How to test it
- Open the PDFs buyers download most: spec sheets, line cards, catalogs, certifications, the capability statement.
- Try to select a sentence of text. If you can't, the PDF is a scanned image, and a screen reader gets nothing from it.
- Selectable text doesn't mean the PDF is tagged, which is what a screen reader needs. Open it in the free Adobe Acrobat Reader, choose File > Properties, and look for Tagged PDF: Yes or No.
- Look at the browser tab or window title. A title like "Scan_0042" suggests the document was never set up properly.
- Check that tables of specs read in a sensible order and that key figures aren't locked inside images.
Why a buyer cares
The spec sheet is often the document an engineer forwards to the person who signs off. If it's a flat image, it can't be read aloud, searched or copied from, so the document that sells you on paper says nothing to some of the people evaluating you.
What to ask your web team
Which of our PDFs are scanned images or untagged, can the important ones be made accessible, and should the key specs also live as text on the web page itself?
Your result for check 8
09Check headings, spec tables and link text make sense on their own
WCAG 1.3.1 Info and Relationships (A), 2.4.6 Headings and Labels (AA), 2.4.4 Link Purpose (In Context) (A)
How to test it
- On a Mac, turn on VoiceOver and press Control+Option+U to open the rotor, then use the arrow keys to find the Headings and Links lists. On Windows, the free NVDA screen reader lists them with Insert+F7.
- Read the heading list for one key page. It should read like a table of contents, with a main title and sections underneath, rather than being empty or not matching the page's sections. One main heading per page, and levels in strict order, are good practice rather than WCAG rules.
- On a product page with a spec table, right-click a column heading and choose Inspect. Real header cells show as <th>. If the headings are ordinary cells, or the whole table is a picture, a screen reader can't tell which value belongs to which size.
- Read the links list. A "Learn more" can be fine at WCAG level AA if the sentence or list item around it says where it goes. Read on their own, as in this list, a dozen of them tell a screen reader user nothing. That link-only test is the stricter AAA criterion, 2.4.9, so treat it as a target rather than the AA line.
Why a buyer cares
Screen reader users often move around a page by jumping between headings, the way a sighted reader skims. Pages with no real headings force them to listen to everything in order, and the same structure is what search engines and AI assistants use to work out what a page covers.
What to ask your web team
Does each page use a main heading and real heading levels for its sections, are spec tables built as real tables with header cells, and does every link say where it goes, in its own text or the sentence around it?
Your result for check 9
10Zoom to 200% and check nothing breaks
WCAG 1.4.4 Resize Text (AA), 1.4.10 Reflow (AA)
How to test it
- On a desktop browser, press Ctrl and + (Command and + on a Mac) until the zoom reaches 200%.
- Check all text is still there and readable: nothing cut off, overlapping, or hidden behind other content, and the menu and quote form still work.
- With the browser window about 1280 pixels wide, keep zooming to 400%. The page should reflow, usually into a single column, so you can read it by scrolling down only. Wide spec tables, maps and diagrams may still scroll sideways. The rest of the page shouldn't.
Why a buyer cares
Plenty of buyers zoom in, whether they have low vision or are simply reading small print without their glasses. A layout that falls apart at 200% loses them, and the fix is usually the same work that makes the site behave on a phone.
What to ask your web team
Does the site still work at 200% browser zoom, and does it reflow without sideways scrolling at 400%, apart from wide spec tables, maps and diagrams?
Your result for check 10
Your results
0 problems found, 0 passed, 10 not run yet.
Send your results to your web team
The export lists each problem you found with your notes and the question to ask, ready to paste into an email. For a printed record with owner and date columns, use the record sheet below.
This self-check doesn't send your results or notes anywhere. They stay in this browser.
Run the checks on your own pages the way a first-time visitor meets them, with any accessibility widget closed. Your results stay on this device, and the results step copies or downloads a summary to send on.
What this checklist is, and what it isn't
It's an owner's first look, built to find the barriers a buyer actually hits on a supplier's site: finding a product, reading the specs and sending a quote request. It's narrower than it might sound.
Not an audit
A specialist with screen reader experience tests far more than ten things and will find problems these checks can't. Treat a clean run here as a reason to keep going, not a reason to stop.
Not legal advice
Whether and how the ADA applies to your company depends on your facts. If a demand letter or lawsuit arrives, talk to a lawyer before you reply.
Not a certificate
No checklist, scan or badge makes a site compliant on its own. What it gives you is a dated record of what you tested and what you found, which is more useful in a vendor questionnaire than a blank.
Not a widget
The checks look at the site itself, the way a visitor meets it. An accessibility menu added on top doesn't change what they find, as the section on overlays below explains.
What do the ADA rules for websites actually say?
This part is factual and deliberately narrow. Every date below is from the primary source, linked at the end of the page.
The ADA and private businesses
The Department of Justice's guidance on web accessibility, published March 18, 2022, says the ADA requires businesses open to the public to provide full and equal enjoyment of their goods and services, and that this applies to what they offer on the web.
The same guidance says the DOJ doesn't have a regulation setting detailed standards, that businesses have flexibility in how they comply, and that existing technical standards such as WCAG and the federal Section 508 Standards provide helpful guidance. It also notes that guidance documents have no legally binding effect on their own. Whether a company that sells only to other businesses counts as open to the public is itself a question for counsel.
The 2024 rule for state and local governments
On April 24, 2024, the DOJ published a rule under Title II of the ADA that makes WCAG 2.1 Level AA the technical standard for the websites and mobile apps of state and local governments. An interim final rule published April 20, 2026 moved the compliance dates to April 26, 2027 for governments serving 50,000 people or more, and April 26, 2028 for smaller ones and special district governments. The National Federation of the Blind sued in May 2026 to undo that extension, and the case was still open when we checked, so confirm the current dates on ada.gov.
The rule doesn't cover private companies' own websites. The duty sits with the government, but it reaches content and apps a private company provides on a government's behalf through its contract, which matters if you supply cities, counties, public utilities or state agencies with anything their public uses online.
WCAG, the standard the guidance points to
WCAG, the Web Content Accessibility Guidelines, is published by the W3C and sorts its requirements into levels A, AA and AAA. WCAG 2.2 became a W3C Recommendation on October 5, 2023. It keeps the 2.1 success criteria essentially as they were, apart from one obsolete criterion it removes, 4.1.1 Parsing, and adds nine new ones, six of them at level A or AA.
That's why a new build can sensibly ask for 2.2 AA, even though the DOJ's rule for governments names 2.1 AA. Two of the checks in the tool cite criteria that only exist in 2.2, and they're marked, so a team building to 2.1 knows which ones are extra.
The European Accessibility Act
The directive applies to certain products, and to services provided to consumers after June 28, 2025, including e-commerce. It covers anyone who offers services to consumers in the EU, not only EU companies.
Two details matter for a B2B supplier. The directive defines e-commerce services as ones aimed at concluding a consumer contract, and it exempts microenterprises providing services, meaning fewer than 10 persons and no more than EUR 2 million in annual turnover or balance sheet. If you sell online to EU consumers, ask counsel how it applies to you. If you sell only to other businesses, you're in a different position, but confirm that too.
Do accessibility widgets and overlays make a site compliant?
If you've looked into this at all, you've seen the plug-ins that add an accessibility icon to every page and promise compliance for a monthly fee. Two primary sources are worth knowing before you buy one.
What the DOJ's guidance says
The DOJ's guidance says automated checkers and overlays can be helpful tools but have to be used carefully, and that a clean report from an automated checker doesn't necessarily mean everything is accessible.
What the FTC did
On April 22, 2025, the Federal Trade Commission approved a final order requiring accessiBe to pay $1 million, after saying the company claimed its accessWidget plug-in could make any website compliant with WCAG.
None of that means every tool is useless. Automated scanners, such as Lighthouse in Chrome's developer tools, catch real problems quickly. It means a widget isn't a substitute for checking the site itself, so run the checks on your pages the way a first-time visitor meets them, without opening any accessibility menu.
What should you fix first?
Fix in the order a buyer travels, then make sure it stays fixed.
Anything that blocks the quote form, the navigation or the main product pages
That's the path from interest to a request, so a barrier there costs you more than one anywhere else. Keyboard traps, unlabeled fields and errors that wipe the form come first.
Contrast, focus styles and headings
These usually live in shared templates and styles, so one change carries across every page built from them. A design system is where they belong, so new pages start out right.
The PDFs buyers download most
Start with the spec sheets and the capability statement, and consider putting key specs on the page as text as well, so they're readable without opening a file at all.
Three answers in writing from whoever runs the site
Which WCAG version and level they build and test to. Whether new pages and content are checked before they go live, rather than once at launch. And who on your side owns accessibility after launch, because a site that passes today can fail next month when someone uploads a scanned spec sheet or a video without captions. Ongoing website maintenance is the usual home for that.
The record sheet
The same ten checks in short form, for handing to someone on your team or keeping a dated record of what you tested. Tick items off here and your progress saves in this browser, or print it, copy it to Google Sheets, or download it as Word or PDF with owner and date columns.
- 0/5
Getting around with the keyboard
WCAG 2.1.1 Keyboard (A), 2.1.2 No Keyboard Trap (A), 2.4.3 Focus Order (A), 2.4.7 Focus Visible (AA), 2.4.11 Focus Not Obscured (Minimum) (AA, new in 2.2).
- 0/5
Images and color
WCAG 1.1.1 Non-text Content (A), 1.4.3 Contrast (Minimum) (AA), 1.4.11 Non-text Contrast (AA), 1.4.1 Use of Color (A).
- 0/5
The quote form
WCAG 3.3.2 Labels or Instructions (A), 1.3.1 Info and Relationships (A), 4.1.2 Name, Role, Value (A), 3.3.1 Error Identification (A), 3.3.3 Error Suggestion (AA), 3.3.7 Redundant Entry (A, new in 2.2), 4.1.3 Status Messages (AA), 1.1.1 Non-text Content (A) for CAPTCHAs.
- 0/5
Video, motion and documents
WCAG 1.2.2 Captions (Prerecorded) (A), 1.2.5 Audio Description (Prerecorded) (AA), 2.2.2 Pause, Stop, Hide (A), 1.1.1 Non-text Content (A), 1.3.1 Info and Relationships (A), 2.4.2 Page Titled (A).
- 0/6
Structure and zoom
WCAG 1.3.1 Info and Relationships (A), 2.4.6 Headings and Labels (AA), 2.4.4 Link Purpose (In Context) (A), 1.4.4 Resize Text (AA), 1.4.10 Reflow (AA).
Sources
- US Department of Justice, Guidance on Web Accessibility and the ADA (March 18, 2022)ada.gov
- US Department of Justice, Fact Sheet: New Rule on the Accessibility of Web Content and Mobile Apps (Title II)ada.gov
- US Department of Justice, Title II web rule page (current compliance dates)ada.gov
- Federal Register, Extension of Compliance Dates, interim final rule, 91 FR 20902 (April 20, 2026)govinfo.gov
- National Federation of the Blind v. Department of Justice, No. 1:26-cv-02007 (D. Md.), case summaryclearinghouse.net
- W3C, Web Content Accessibility Guidelines (WCAG) 2.2w3.org
- W3C Web Accessibility Initiative, What's New in WCAG 2.2w3.org
- W3C, Understanding 1.4.1 Use of Color (link contrast technique G183)w3.org
- W3C, Understanding 2.4.11 Focus Not Obscured (Minimum)w3.org
- W3C, Understanding 2.4.4 Link Purpose (In Context)w3.org
- W3C, Understanding 3.3.7 Redundant Entryw3.org
- W3C, Understanding 1.4.10 Refloww3.org
- WebAIM, Contrast Checkerwebaim.org
- Directive (EU) 2019/882 on the accessibility requirements for products and services (European Accessibility Act)eur-lex.europa.eu
- Federal Trade Commission, FTC Approves Final Order Requiring accessiBe to Pay $1 Million (April 22, 2025)ftc.gov