An honest starting point. There is no official government checklist that certifies a private business website as “ADA compliant”, and no scan or guide can promise lawsuit protection. What exists is a practical benchmark — WCAG 2.2 Level AA, the standard U.S. courts reference — and a set of barriers you can genuinely find and fix. That is what this page is for. It is practical guidance, not legal advice.
How to use it. Work through the 18 checks on your homepage first, then on the one flow that makes you money: checkout, booking or contact form. Jot down pass or fail for each. Fix blockers (checks 3, 5 and 7) before polish. If you would rather start with the machine-provable problems, run our free instant homepage check first — it counts missing alt text, unlabelled controls, nameless links, missing language, title and H1 in seconds, with no email needed.
The 18 checks
1. Images have useful alt text
Every informative image needs a text alternative a screen reader can speak: a product photo should say what the product is, a chart should give its takeaway. Purely decorative images should have empty alt text (alt="") so they are skipped, not announced as a filename.
Check it free: Open your homepage and product pages. For each image ask: if I could not see this, what would I need to hear? Check in your site builder's image settings — if the alt field is blank or repeats the file name (IMG_2041.jpg), rewrite it in one short, factual sentence.
2. Text contrast is strong enough
Normal text needs a contrast ratio of at least 4.5:1 against its background; large text (about 24px, or 19px bold) needs at least 3:1. Light grey text on white and white text on pale brand colours are the most common failures on small-business sites.
Check it free: Pick your body text, your lightest menu text and your button text. Run each pair through our free WCAG Contrast Checker — if it fails AA, darken the text (or lighten the background) to the nearest passing shade the tool suggests.
3. The whole site works by keyboard alone
Everything a mouse can do — menus, popups, forms, checkout — must also work with Tab, Shift+Tab, Enter and Space. Keyboard access is how many blind, motor-impaired and power users navigate; a keyboard trap or a mouse-only menu is a complete blocker, not a minor flaw.
Check it free: Unplug your mouse. Tab through your homepage, open the menu, add something to the cart or open the booking form, and try to complete it. Note every place you get stuck, cannot reach, or cannot escape — especially popups and cookie banners.
4. You can always see where the keyboard focus is
The focused link or button must have a clearly visible outline. Many site themes remove the browser outline for looks (outline: none) and never replace it, leaving keyboard users tabbing blind.
Check it free: During the same keyboard walk-through, watch the screen: at every Tab stop you should be able to point to the focused element instantly. If you lose it, your theme needs a visible focus style — a developer can restore one in a few lines of CSS.
5. Every form field has a real label
Each input needs a programmatic label connected to it — placeholder text alone does not count, because it disappears while typing and many screen readers do not announce it. Errors must be described in text (not colour alone) and tell the person how to fix the problem.
Check it free: Click the visible label text of each field in your contact, checkout and booking forms: if the field does not gain focus, the label is not connected. Then submit a form empty and with a bad email — the error should name the field and the fix, in words.
6. Headings form a real outline
One H1 per page stating what the page is, then H2s for sections and H3s underneath — in order, without skipping levels for looks. Screen-reader users navigate by pulling up a list of headings, the way sighted users scan bold titles.
Check it free: Use your browser or site builder to list a page's headings. Read only the headings: do they outline the page like a table of contents? If a big styled paragraph is doing a heading's job, or levels jump from H1 to H4, restructure them.
7. Links and buttons say what they do
"Click here", "Read more" and icon-only buttons with no accessible name tell a screen-reader user nothing when links are read out of context — and link lists are a standard way to navigate. Link text should name the destination or action.
Check it free: Scan your pages for 'click here' and bare icons (cart, menu, social). Rewrite links to name the outcome — 'See the full accessibility report' beats 'Learn more'. Give every icon button an accessible label in your builder or code.
8. Video has captions, audio has a transcript
Pre-recorded video with speech needs accurate captions — auto-captions are a starting draft, not a finished result, especially for names and prices. Audio-only content such as podcasts needs a written transcript.
Check it free: Play your homepage or product video muted: are captions available, and do they match the words, including names and numbers? Fix auto-caption errors in your video platform's caption editor before embedding.
9. The page survives 200% zoom and a phone in portrait
Text must remain readable and usable when zoomed to 200%, and content must reflow on a narrow screen without two-dimensional scrolling. Low-vision users zoom every day; content that clips, overlaps or hides behind a fixed banner is lost to them.
Check it free: Zoom your key pages to 200% in a desktop browser and scroll: nothing should overlap, cut off or require sideways scrolling. Then repeat on your phone in portrait — check menus, prices and checkout buttons specifically.
10. Every page has a title and a declared language
Each page needs a unique, descriptive title (the text in the browser tab and search results) and the page language must be declared in the code, so screen readers use the right pronunciation and search engines understand the page.
Check it free: Open several pages: do the tab titles differ and describe each page? Site builders usually set the language automatically — if your site is hand-coded, confirm the html element carries the correct lang attribute.
11. Visitors can skip the navigation
A 'Skip to content' link as the first focusable element lets keyboard and screen-reader users jump past the menu instead of tabbing through every link on every page. Long menus without a skip link tax every single visit.
Check it free: Reload your homepage and press Tab once: a visible 'Skip to content' (or similar) link should appear and, when activated, move focus to the main content. If the first Tab stop is your logo or first menu item, add a skip link.
12. Linked PDFs and documents are not a dead end
Menus, price lists, intake forms and guides linked as PDFs are part of your website. A scanned-image PDF is completely silent to a screen reader, and untagged PDFs read in the wrong order. If a document matters, it needs real text, tags and a reading order — or an HTML equivalent.
Check it free: Download your linked PDFs and try to select the text with your mouse: if you cannot select it, it is a picture of text. Prioritize the documents customers need to act — menus, forms, price lists — and publish an accessible HTML version alongside.
13. Sticky bars never cover the element you are tabbing to
When a visitor tabs to a link, button or field, no part of it may be hidden behind a sticky header, a cookie banner or a fixed chat button. If you cannot see the thing you are about to activate, keyboard navigation breaks — even when the focus outline itself is perfect (check 4).
Check it free: During the keyboard walk-through, tab slowly through every page and watch the stops near the top of the screen and above any cookie banner or chat widget. If focus slides underneath a fixed bar at any stop, add scroll-margin-top (at least the bar’s height) to links, buttons and fields, or stop the bar overlapping content. Our audit runs this as part of the manual keyboard walk-through on every scanned page.
14. Buttons and links are at least 24×24 pixels
Every clickable target — menu items, icon links, quantity steppers, close buttons — needs to be at least 24 by 24 CSS pixels, or have enough clear space around it to make up the difference. Tiny targets are a daily barrier for customers with a hand tremor, arthritis or limited dexterity, and for anyone tapping on a moving bus.
Check it free: On your phone, work through the menu, cart +/− buttons, social icons and footer links with your thumb. In a desktop browser, right-click a small target, choose Inspect, and read its measured size in the developer tools — our audit measures the key targets on each scanned page this way. Anything under 24×24 with no spacing around it needs padding: usually a small CSS change.
15. Anything you can drag also works with a plain click or tap
A dragging motion must never be the only way to do something: sliders, before/after image comparisons, drag-to-reorder lists, map panning and drawing or signature pads all need a single-pointer alternative — arrow buttons, +/− steppers, up/down buttons, or a plain field that does the same job.
Check it free: Find every slider, carousel, map and reorder control on your key pages and try to finish the same task using only clicks or taps — arrows on the slider, a typed address instead of dragging the map, buttons instead of dragging list items. If dragging is the only way through, the control fails and needs the alternative added. This is a manual step in our audit’s flow walk-through.
16. Help sits in the same place on every page
If your site offers help — a contact link, a phone number, a help page or a chat — it must appear in the same relative place and order on every page that has it. A customer who found your phone number in the footer on the homepage should find it in the footer on the checkout page too, not have to hunt for it again.
Check it free: Open four or five pages side by side and compare where the phone number, contact link and chat button live: same header or footer position, same spot in the menu? If help moves around or disappears on some pages, standardize it in the site template. Our audit compares the help elements across all scanned pages.
17. Forms never ask twice for the same information
Inside one process — checkout, booking, intake — information a customer already gave you (name, email, address) must be carried forward automatically or offered back for selection, not typed a second time. Re-entry is allowed only where it is genuinely essential, like confirming a password, or where the earlier entry has expired for security reasons.
Check it free: Walk your checkout or booking flow from start to finish and note every field you are asked for twice. “Billing same as delivery” should be a checkbox, not a second blank form. Any repeated field with no carry-over is a settings fix in your shop or form tool — and a manual step our audit performs on your main money flow.
18. Signing in is not a memory test or a puzzle
Login must not depend on a cognitive test — remembering a password with no alternative, re-typing a code from memory, or picking the right pictures in an object-recognition puzzle — unless another method is offered: an emailed sign-in link, a passkey, a code sent to a device the customer owns, or password fields that accept paste from a password manager.
Check it free: Sign in the way a customer does. Can you paste your password from a password manager (paste must not be blocked)? Is there an email-link, passkey or device-code option next to the password box? If a picture puzzle is the only gate, add a modern alternative and unblock paste. Our audit reviews the sign-in flow wherever a site has one.
The checklist on one page
Print this page (your browser's print view trims the navigation) or copy this summary into your notes:
- Images have useful alt text
- Text contrast is strong enough
- The whole site works by keyboard alone
- You can always see where the keyboard focus is
- Every form field has a real label
- Headings form a real outline
- Links and buttons say what they do
- Video has captions, audio has a transcript
- The page survives 200% zoom and a phone in portrait
- Every page has a title and a declared language
- Visitors can skip the navigation
- Linked PDFs and documents are not a dead end
- Sticky bars never cover the element you are tabbing to
- Buttons and links are at least 24×24 pixels
- Anything you can drag also works with a plain click or tap
- Help sits in the same place on every page
- Forms never ask twice for the same information
- Signing in is not a memory test or a puzzle
What to do with your results
If you passed almost everything: keep the dated notes from your walk-through on file, and re-check after your next redesign, theme change or new booking/checkout tool. Accessibility drifts as sites change.
If you found a handful of failures: most of checks 1, 2, 6, 7 and 10 are quick fixes in a site builder or a short developer task. Work top-down by how many customers each barrier blocks, not by how easy the edit looks.
If you found failures everywhere: fix the money flow first — homepage, product or service page, checkout or booking, contact. A dated, severity-ranked report of the machine-provable barriers gives your developer a concrete work list instead of a vague “make it accessible”.
Outline in hand? Run it through the free Heading Structure Checker — 8 checks on heading order, in your browser, before you publish.
Already holding a letter? Read the ADA website demand letter guide — the first 7 days in order: preserve, measure, fix, respond.
Get the provable barriers found for you
The Full Report scans your site against WCAG 2.2 AA and returns a dated PDF: every barrier found, ranked by severity, each with a plain-English fix. $15 one-time. The Watch Plan ($18/month) re-checks monthly so new barriers do not creep back.
Or start with the free Contrast Checker · Free instant homepage check
Reports are a first-line check and documentation of good-faith effort — not a certification of ADA or WCAG compliance. Full refund if your report fails to generate; 30-day refund policy.
Frequently asked questions
Is there an official ADA checklist for websites?
No. The U.S. Department of Justice has not published a single official checklist or adopted a specific technical standard for private business websites under Title III. In practice, U.S. courts and the DOJ reference WCAG 2.1 or 2.2 at Level AA. This checklist is organized around WCAG 2.2 AA, which is the practical benchmark — but completing it is not a government certification.
How long does it take to run through this checklist?
For a typical small-business homepage and checkout or contact flow, plan on about 60 to 120 minutes: about 20 minutes for the automated checks, 25 minutes for the keyboard and focus walk-through, and the rest for headings, labels, captions, tap targets, form flows and zoom. Larger sites take longer — start with the pages customers actually use to buy, book or contact you.
What should I fix first if I find several problems?
Fix blockers first: anything that stops a keyboard or screen-reader user from completing your main task — buying, booking, submitting a form or finding your phone number. Then fix missing labels, alt text and contrast failures, which are the issues most often named in demand letters. Cosmetic and AAA-level improvements come last.
Can an automated scan replace this checklist?
No. Automated scanning reliably catches roughly 30 to 40 percent of barriers — the ones a machine can prove, like missing alt attributes, unlabelled controls and some contrast failures. It cannot judge whether alt text is meaningful, whether keyboard order makes sense, or whether an error message helps. Use a scan to find the provable problems fast, then use this checklist for the rest.
Does completing this checklist protect me from a lawsuit?
No checklist or scan can guarantee that. What it does do is remove real barriers for real customers and create a dated record of good-faith effort. If you receive a demand letter or are unsure about your legal position, talk to a qualified attorney — this page is practical guidance, not legal advice.
How often should I re-check my website?
Re-check after every redesign, theme change or new checkout, form or booking tool — and do a lighter pass every few months. Sites drift: a new plugin, popup or image upload can reintroduce barriers you already fixed. That ongoing re-check is exactly what a monitoring plan automates.
Written by ADA Site Check, Portland, Oregon. Questions: contact@getadasitecheck.com. This guide is practical information, not legal advice, and not a certification of compliance with the ADA, WCAG or Section 508.