No one can hand you a badge that makes an ADA compliant website permanent. What exists is a legal duty that applies differently to governments and businesses, a technical standard (WCAG) that most people use as the yardstick, and a short list of fixes for the barriers that turn up most often.
This guide separates what the Department of Justice has actually said from what vendors say, then gives you a first-month plan that costs little. It is general information, not legal advice. If you have received a demand letter or run a regulated organization, talk to an attorney.
One honest warning up front: the quick-fix products that promise compliance with one line of code are the part of this topic most likely to waste your money. We cover why below. If you are judging a site overall, our website design evaluation criteria give you the wider checklist.
Rebuilding or fixing a site? Request an estimate and we will reply with scope and a price range for a sensible first phase.
What the law actually says
Two parts of the Americans with Disabilities Act matter for websites, and they are not the same.
Title II covers state and local governments. In April 2024 the Department of Justice published a rule setting technical requirements for government websites and mobile apps. According to DOJ’s own first-steps page, the standard is WCAG 2.1 Level AA. An April 2026 interim final rule moved the compliance dates: April 26, 2027 for entities with a population of 50,000 or more, and April 26, 2028 for smaller entities and special district governments. If you run a library district, parks department or similar public body, that rule is yours to read closely.
Title III covers businesses open to the public. DOJ’s web guidance, dated March 2022, says these requirements apply to goods and services “including those offered on the web.” It also says plainly that the Department “does not have a regulation setting out detailed standards” for them. Businesses can choose how to comply, but they still have to make sure what they offer the public is accessible. DOJ names WCAG as helpful guidance, not as a rule that private businesses must meet by a date.
Whether a particular nonprofit, church or festival organization counts as a Title III business is a legal question that this article cannot answer for you. Ask counsel. What you can do without a lawyer is make the site work for more people, which is the point of the law anyway.
WCAG in plain language
The Web Content Accessibility Guidelines are published by the W3C. The current version is WCAG 2.2, and W3C says content that meets 2.2 also meets 2.1 and 2.0. Every testable requirement is rated A, AA or AAA, and Level AA is a common target. That is also the level DOJ chose for the government rule.
All of it hangs on four ideas. A site should be:
- Perceivable. Images have text alternatives, video has captions, text is readable against its background.
- Operable. Everything works from a keyboard, and nothing traps focus.
- Understandable. Forms have clear labels and useful error messages.
- Robust. The code is clean enough that assistive technology can interpret it.
Where sites actually fail
The accessibility group WebAIM scans the home pages of the top one million sites every year. In its 2026 results, 95.9% of home pages had detectable WCAG failures, averaging 56.1 errors per page. The most common problems were:
- Low-contrast text: 83.9% of home pages
- Missing image alt text: 53.1%
- Missing form input labels: 51%
- Empty links: 46.3%
- Empty buttons: 30.6%
- Missing document language: 13.5%
That list is useful because it is boring. Most barriers are not exotic. They are gray text on a white background, a donate button with no name a screen reader can read, and a contact form whose fields have no labels.
What to do first for an ADA compliant website
- Fix the pages people transact on. DOJ’s guidance uses an event registration form as its example of how an inaccessible page can block access to a service. Start with your contact form, donation page, booking or registration flow, and menu.
- Run the W3C easy checks. Most of the W3C’s preliminary checks can be done in any browser without special tools: page titles, alt text, headings, contrast, text resizing, keyboard access with visible focus, form labels, and captions on video. W3C is clear they are quick, not definitive.
- Use the keyboard yourself. Put the mouse aside and press Tab through your key pages. If you cannot see where you are, or cannot reach the donate button, you have found a real problem.
- Fix contrast and labels site-wide. These are usually changes to a theme or template, so one fix can repair many pages.
- Caption your video and write real alt text. Describe what an image communicates, not “image1.jpg.”
- Publish a way to reach a person. A working email address or form for accessibility problems, answered by someone, is worth more than a long statement.
Why overlay widgets are not a fix
Accessibility overlays are scripts you add to a site, usually with a small icon in a corner, that claim to repair accessibility automatically. That promise deserves skepticism.
In April 2025 the FTC approved a final order against the overlay vendor accessiBe. The FTC alleged that the company’s claim that its plug-in could make any website WCAG compliant was false, misleading or unsubstantiated. The order requires a $1 million payment and bars that claim unless the company has evidence for it. That order is about one vendor’s marketing, not a ruling on every overlay, but it tells you how much weight to give a promise of “instant compliance.”
DOJ makes the same point about tools in general: a “clean” automated report does not necessarily mean everything is accessible. Overlays can sit on top of a site, but the underlying problems, such as unlabeled fields, low contrast and broken keyboard order, live in the site’s own code and design. Fix those at the source.
When to bring in a professional
Do the first four steps yourself. Bring in help when you have a custom-built site, a booking or payment system, or a template you cannot edit. Ask any developer or auditor how they test (automated scan plus manual keyboard and screen reader checks is the honest answer), which WCAG version and level they target, and what they will deliver: a prioritized list, fixes, or both. The evaluation criteria linked above are a good checklist for comparing any web firm, and our web developer page explains how we work.
The honest verdict
DIY is a sensible start for most small sites running on a mainstream builder or a well-made WordPress theme. Do the easy checks, fix contrast, labels and alt text, test with a keyboard, and set a reminder to repeat it twice a year.
Hire help when the site is custom, handles payments or registrations, serves a public body under the Title II rule, or has already drawn a complaint. In that case also involve an attorney for the legal side. Do not buy a one-line widget and treat the question as closed.
If you are rebuilding anyway, W3C advises evaluating early, when problems are easier to address. When you want accessibility built into a new website or a custom web application, we can scope it.
Frequently Asked Questions
Is there an official ADA compliance certificate for websites?
No. The Department of Justice says it has no regulation setting out detailed technical standards for businesses, and WCAG is a set of guidelines, not a certification program. WCAG is the common yardstick, but conformance is something you demonstrate through testing and fixing, not something a seal proves. Treat any vendor that sells a “certified compliant” badge with caution and ask what testing sits behind it.
Does the ADA website rule apply to my small business?
The 2024 DOJ rule sets technical requirements for state and local governments, not private businesses. Businesses open to the public fall under Title III, where DOJ says the law covers goods and services offered on the web but does not set detailed standards. Whether a given nonprofit or organization is covered is a legal question, so ask an attorney. Making the site accessible is wise either way.
What WCAG level should I aim for?
Level AA is a common target. It is the level DOJ chose for the government rule, and it covers the common barriers: text contrast, alt text, keyboard access, form labels and captions. The W3C encourages using the latest version, WCAG 2.2, and says content that meets 2.2 also meets 2.1 and 2.0, so building to 2.2 AA also satisfies the older versions.
Can an accessibility overlay or plugin make my site compliant?
Not on its own. In 2025 the FTC finalized an order against one overlay vendor over claims that its tool could make any website WCAG compliant, alleging those claims were false, misleading or unsubstantiated. DOJ also notes that a clean automated report does not guarantee accessibility. Problems like missing labels, low contrast and keyboard traps are best fixed in the site itself, then checked by hand.