Website accessibility checklist: what to fix and who is responsible
Short answer: Website accessibility means people with disabilities can use your site, for example with a keyboard only or a screen reader (software that reads a page aloud). In the United States the Americans with Disabilities Act (ADA, the federal disability rights law) applies to business websites, but it names no technical standard, so most businesses aim for WCAG (Web Content Accessibility Guidelines, the W3C's published rules) at level AA. This page gives you the laws in plain words, a 15-minute test, a full checklist and a split of who owns each fix. It is information, not legal advice.
You want a checklist you can run this week to lower your risk of an accessibility complaint, and a clear answer on whether that job sits with you or your web agency.
I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.
The first thing to know is that no one can promise a site is "ADA compliant" with a tick box or a plug-in. What you can do is test against a known standard, fix what you find, record that you did it, and keep testing when the site changes. That is a defensible position and, more important, it makes the site usable for more of your customers.
This page covers what the US and EU rules say (and do not say), a 15-minute test anyone can run, a longer checklist, the free tools, the overlay debate, and who is responsible when an agency built the site. Check local law for your own case. This is not legal advice.
What the laws say, in plain words
United States, businesses. The US Department of Justice (DOJ) published web guidance on ADA.gov on 18 March 2022. It says the ADA applies to the web content of "public accommodations" (Title III, which covers businesses open to the public) and of state and local governments (Title II). It also says the DOJ has no regulation that sets detailed technical web standards for Title III businesses. It points to WCAG and Section 508 (the federal government's own accessibility rules) as helpful guidance. In short: the duty exists, the exact technical test for a private business is not written into a regulation, and WCAG is the yardstick most people use.
Do not say "the ADA requires WCAG 2.2 AA" for a private business site. It does not say that. WCAG 2.2 AA is a common practical target, not a legal rule for your site.
United States, governments only. The DOJ's Title II web rule requires WCAG 2.1 Level AA, but only for state and local governments. An April 2026 interim final rule pushed the dates back one year. As the Federal Register notice of 20 April 2026 states, entities with a population of 50,000 or more now have until 26 April 2027, and smaller entities and special districts until 26 April 2028. If a city or school district is your client, check the current dates on ADA.gov.
European Union. The European Accessibility Act (EAA, Directive 2019/882) applies to listed products placed on the market, and listed services provided to consumers, after 28 June 2025. Covered services include e-commerce, consumer banking, e-books, electronic communications, audiovisual media access and some passenger transport. Article 4(5) exempts microenterprises that provide services: a microenterprise is a business with fewer than 10 people and annual turnover or balance sheet not over EUR 2 million (Article 3(23)). So the EAA does not apply to "every website". It depends on what you sell, where your customers are and how big you are. Each EU country writes its own enforcement rules and penalties, so check your country's page.
Lawsuit volume. Trackers report thousands of suits a year. As reported in their year-end summaries (check each report for its scope), Seyfarth, a law firm, counted 3,117 federal website accessibility suits in 2025, and UsableNet, an accessibility software company, counted 5,114 digital suits (websites, apps and video, all courts). The scopes differ, so do not compare the two numbers. The point is that claims are common.
The standard most people use: WCAG 2.2 AA
WCAG is published by the World Wide Web Consortium (W3C, the group that sets web standards). WCAG 2.2 is a W3C Recommendation (a finished standard). It was first published in October 2023, and the current version is dated 12 December 2024. It has three levels, A, AA and AAA. Level AA is the usual target. WCAG 2.2 added nine new success criteria and removed one old one (4.1.1 Parsing). The ones that matter most for a small business site:
- Contrast (1.4.3): normal text needs a contrast ratio of at least 4.5 to 1 against its background. Large text needs 3 to 1.
- Reflow (1.4.10): content should work at a width equal to 320 CSS pixels (a unit of screen width; about a phone in portrait, or a desktop zoomed to 400 percent) without sideways scrolling.
- Target size (2.5.8, new in 2.2): buttons and links should be at least 24 by 24 CSS pixels, or have enough space around them, with exceptions.
- Focus not obscured (2.4.11, new in 2.2): when you tab to a control, a sticky header or cookie bar must not fully hide it.
The 15-minute test anyone can run
Run this on your home page, your main service page, your contact page and any page with a form. You do not need special skills.
- Keyboard only (4 minutes). Put the mouse away. Press Tab to move forward and Shift plus Tab to go back. Can you reach every link, button, menu and form field? Can you see where you are (a visible outline)? Can you open and close menus and pop-ups with Enter, Space and Escape? Fail if you get stuck, lose the outline, or a control cannot be reached.
- Zoom to 200 percent (2 minutes). Press Ctrl and plus (Command and plus on a Mac) until the browser shows 200 percent, then 400 percent. Fail if text is cut off, content overlaps, or you must scroll sideways to read a line.
- Look at colour and text (2 minutes). Is grey text on a white or photo background hard to read? Use a free contrast checker on any text you doubt. Fail if normal text is below 4.5 to 1. Also check that nothing relies on colour alone, such as a red border with no error message.
- Images (2 minutes). Hover or inspect the key images. Photos that carry meaning (a product, a team member, a map) need short alt text, the text a screen reader reads. Decorative images should have empty alt text. Fail if the logo link says "image123.png" or key text is baked into an image with no text version.
- Forms (3 minutes). Does every field have a visible label (not only grey placeholder text that vanishes)? Submit the form empty. Does an error message say which field is wrong and how to fix it? Fail if errors are shown only by colour or a vague "Error".
- Run two free tools (next section), and check that video has captions. Record the number of errors.
The full checklist (copy this)
Use this as a spreadsheet: one row per item, columns for page, result (pass, fail, not applicable), owner, date fixed.
| Area | What to check | Pass looks like |
|---|---|---|
| Structure | One main heading per page, headings in order, page title says what the page is | A screen reader user can jump by headings and understand the page |
| Keyboard | Every control works without a mouse, no traps, logical order | You can finish a contact form with the keyboard only |
| Focus | A clear outline on the focused control, not hidden by sticky bars | You always know where you are |
| Contrast | Text 4.5 to 1, large text 3 to 1, buttons and form borders 3 to 1 | Checker shows no failures on key pages |
| Zoom and reflow | Works at 200 percent zoom and at 320 pixel width | No lost content, no sideways scroll for text |
| Images | Meaningful alt text; empty alt for decoration; no key text only in images | The page makes sense with images off |
| Links and buttons | Link text makes sense alone ("Read the pricing guide", not "Click here") | A list of links is understandable |
| Forms | Visible labels, required fields marked in text, helpful errors, no CAPTCHA (a puzzle that checks you are human) with only an image puzzle | Errors name the field and the fix |
| Media | Captions on video, transcript for audio, no autoplay sound, pause control for moving content | Meaning is not lost without sound |
| Pop-ups and chat | Open with keyboard, close with Escape, focus returns, do not hide the page | Cookie bar and chat widget are usable by keyboard |
| Statement | An accessibility page with a contact route and a response time you can keep | People can report a barrier and get an answer |
Free tools and what they miss
WAVE (from WebAIM, a non-profit accessibility group) is a free page checker. Its own help page says "Only a human can determine true accessibility", gives no pass or approval badge and cannot check everything. axe, from the software company Deque, has free browser extensions for Chrome, Firefox and Edge. Deque says its tools find "up to 80%" of issues, but treat that as a vendor ceiling, not a measured result for your site, and Deque itself says expert manual testing is still needed. Automated checkers are good at missing alt text, low contrast and missing form labels. They cannot tell whether alt text is useful, whether the reading order makes sense or whether a menu works by keyboard.
My routine: run WAVE and axe on each key page, fix the errors, then do the 15-minute manual test, then, if the site matters to the business, spend an hour with a screen reader (VoiceOver is built into Apple devices and NVDA is a free Windows screen reader). Do the checker pass first so the manual pass is about real problems.
Overlays: why a plug-in does not make you compliant
An accessibility overlay is a script that adds a toolbar to your site and promises to fix problems automatically. The US Federal Trade Commission (FTC, the national consumer protection agency) approved a final order against accessiBe, an overlay vendor, in April 2025. The order requires a $1 million payment. The FTC's complaint alleged that claims that its accessWidget plug-in could make any site meet WCAG were false, misleading or unsubstantiated, and that it formatted third-party articles and reviews to look independent without disclosing its ties. The order bars it from saying its automated products can make any website WCAG-compliant, or keep it compliant over time, unless it has the evidence to support the claim.
That does not mean every overlay is illegal. It means a vendor claiming "100 percent compliant in 2 minutes" deserves doubt, and you should not rely on one as your plan. Fix the code and content.
Who is responsible: you, or your agency?
Legally, the business that owns the site and serves the customers is the one a complaint targets. A contract can move cost and effort to an agency, but it does not move the legal exposure away from you. So the practical question is who does which job, written down.
| Job | Usually the agency or builder | Usually the business owner |
|---|---|---|
| Theme, templates, menus, colours, focus styles, form markup | Builds to WCAG 2.2 AA and tests | Approves brand colours that pass contrast |
| Alt text, captions, PDFs, new pages, blog posts | Trains the team and sets defaults | Writes and checks every new item |
| Third-party add-ons (chat, booking, cookie bar, maps) | Chooses ones that can be keyboard-tested | Asks the vendor for its accessibility statement before paying |
| Testing after launch and after changes | Runs checkers and the manual test on a schedule if the care plan covers it | Re-runs the 15-minute test after big edits |
| Accessibility statement and a complaint route | Drafts it | Owns the inbox and answers on time |
If you are an agency, do not sell "ADA compliance" as an outcome. Sell "built and tested to WCAG 2.2 AA, with this report, on these pages, on this date", state what is out of scope (third-party tools, client-uploaded content) and put it in the contract. The article on contracts for website work in the AI era covers scope wording, and handing a website to a client covers training so new content stays accessible.
A worked example (made-up numbers)
Say a five-page site for a plumbing firm runs through WAVE and axe. The numbers below are invented to show the method.
- Checker results: 18 errors. 9 are low-contrast text (grey on white in the footer and a light-blue button). 5 are images with no alt text. 3 are form fields with no label. 1 is an empty link (a social icon).
- Manual test: the mobile menu cannot be opened with the keyboard, the cookie bar hides the focus outline on the first link, and the quote form's error message appears in red only.
- Fix list: darken two colours (one stylesheet change fixes the 9 contrast errors), add alt text (30 minutes), add three labels, rebuild the menu button as a real button, move the cookie bar so it does not cover focus, add text to the form error.
- Retest: errors drop to 0 in both tools, all six manual steps pass, and the results go into the spreadsheet with the date. Total time in this example: about half a day for a small site.
Note that the keyboard menu and the form error were the barriers a real customer would hit, and the tools flagged neither.
A test plan with pass and fail criteria
- Scope: list the 5 to 10 pages that carry your business: home, top services, contact, any booking or checkout, any login.
- Automated: pass is zero errors in WAVE and zero critical or serious issues in axe on those pages. Fail is anything else, and you log it.
- Manual: pass is all six steps of the 15-minute test on each page. One keyboard trap or an unlabelled form field is an automatic fail.
- Screen reader: pass is that you can find the phone number, read a service page and submit the contact form by sound alone.
- Record and repeat: date, tester, pages, results, fixes. A dated record is more useful than a badge if anyone complains. Re-test after any redesign, new plug-in or template, and at least twice a year.
AI website builders and templates often look fine and still fail the keyboard test, and claims that a builder "produces ADA-compliant sites" are vendor claims. Test the live site yourself, and see whether your AI-built site is ready for real customers and how to review website changes before they go live.
Who can do less, and who should do more
- Do the minimum (15-minute test plus tools): a brochure site, a local business with a phone number and a contact form, no payments.
- Do the full checklist and a screen-reader pass: any site that takes bookings, payments or applications, sells to the public, or sells into the EU.
- Get an expert audit: government, education or health clients, large e-commerce, or any business that has already received a demand letter. Do not answer a demand letter by buying a plug-in. Talk to a lawyer who works on accessibility cases.
- You may be outside the EAA: a microenterprise (see above) is exempt from the service rules. Check your country's rules before relying on that. US law has no such size exemption.
How I'd approach this
I would not start with a plug-in or a lawyer. I would start with an afternoon of testing, because most of the risk and most of the real barriers sit in a short list of things: contrast, keyboard use, form labels, alt text and captions. Fix those and you are ahead of most small business sites. If you want help, Blur Studio builds and cares for sites with these checks built in, and you can read what that covers on the business page.
First-week plan. Day 1: list your key pages and run WAVE and axe on each. Day 2: run the 15-minute manual test and fill in the checklist spreadsheet. Day 3: fix colours, labels, alt text and the keyboard menu. Day 4: retest, then spend an hour with a screen reader on the contact form. Day 5: publish a short accessibility statement with a real contact route, write the retest dates in your calendar, and add "run the 15-minute test" to your page-publishing checklist. Decision rule: if the checkers still show errors you cannot explain after the fixes, or you sell into the EU, or you have had a complaint, book a paid audit. Otherwise keep testing yourself, and keep the records.
You may also want fair housing and advertising rules for property manager websites.
You may also want a nonprofit fundraising website on a small budget.
I'm not a lawyer, accountant or other licensed adviser, and this page is general information, not advice. Rules and prices differ by country and change often, so treat it as a direction to think along, and please check with a lawyer or the relevant regulator before you act on it.
Questions people ask
Is my small business website required to be ADA compliant?
The ADA applies to the web content of businesses open to the public, according to the DOJ's 2022 guidance on ADA.gov. That guidance also says there is no regulation setting detailed web standards for these businesses, so there is no official tick box. Most businesses aim for WCAG 2.2 AA as a practical target. Check local law and ask a lawyer about your own situation.
Does the ADA require WCAG 2.2 AA?
No rule says that for private business sites. The DOJ's WCAG rule (version 2.1 AA) covers state and local governments only. For businesses, WCAG is guidance that courts, lawyers and agencies commonly use as the yardstick. Treat 2.2 AA as a sensible goal, not a legal definition.
Does the European Accessibility Act apply to my website?
It depends. The EAA covers listed services provided after 28 June 2025, such as e-commerce, consumer banking, e-books and electronic communications. Microenterprises (fewer than 10 people and turnover or balance sheet not over EUR 2 million) are exempt from the service rules. Each EU country sets its own enforcement, so check your national regulator's page.
Can an accessibility overlay or widget make my site compliant?
Do not rely on one. The FTC's April 2025 final order against accessiBe bars it from claiming its automated products make any site WCAG-compliant without evidence. Overlays can add helpful controls, but the real fix is correct code, content and testing. Read the FTC's press release before you buy anything that promises compliance.
How much of accessibility can free tools check?
Only part. WAVE says only a human can determine true accessibility, and Deque says expert manual testing is still needed even with axe. Use the tools for the easy errors, then do the keyboard, zoom and screen-reader checks by hand.
Who is liable, the agency or the business owner?
The business that owns the site is the usual target of a complaint, whatever the contract says. A contract can make the agency do the work and pay for fixes, but it should be written down: standard, pages in scope, test method and who handles new content. See contracts for website work in the AI era.
How often should I re-test?
After every redesign, new plug-in or template change, and at least twice a year. Add the 15-minute test to your checklist for publishing new pages, because new images, PDFs and videos are where problems creep back in.
What should an accessibility statement say?
Say which standard you aim for, what you have tested and when, any known gaps, and how to report a barrier with a real email or phone and a response time you can keep. Do not claim full compliance. A short, honest statement with a working contact route is better than a long badge page.
More in this topic: Websites: legal and trust basics (7 guides) →
Sources
- ADA.gov: Guidance on Web Accessibility and the ADA (18 March 2022)
- W3C: Web Content Accessibility Guidelines (WCAG) 2.2
- W3C WAI: What's new in WCAG 2.2
- WebAIM: WAVE help
- Deque: axe accessibility testing tools
- FTC: final order requiring accessiBe to pay $1 million (April 2025)
- Federal Register: DOJ interim final rule extending ADA Title II web compliance dates (20 April 2026)
- EUR-Lex: Directive (EU) 2019/882, European Accessibility Act