Quick Answer
An ADA compliant website is one people with disabilities can use as fully as anyone else. In practice, most businesses use the Web Content Accessibility Guidelines (WCAG) 2.1 or 2.2 at Level AA as the yardstick. That means readable contrast, text alternatives for images, labeled forms, keyboard access, and captions. This is general information, not legal advice.
The duty is real: ADA.gov web guidance says businesses “have flexibility in how they comply” but “must comply with the ADA’s requirements.”
A customer who can’t use a mouse tabs through your home page with a keyboard, and the focus vanishes into a menu they can’t see. Or they use a screen reader, and your "Book now" button is read aloud as "button."
That customer wants to buy from you. Your website just won’t let them. Making a site accessible fixes that, and it’s the heart of what people mean by an ADA compliant website.
The short answer on ADA website compliance
The Americans with Disabilities Act doesn’t list website rules for private businesses line by line. Instead, the Department of Justice expects businesses open to the public to give people with disabilities equal access, including online.
Here’s what that looks like in practice for most businesses.
- Use WCAG as your standard. WCAG 2.1 or 2.2, Level AA, is the benchmark most accessibility experts point to.
- Fix the common failures first. Low contrast, missing alt text, unlabeled forms, and empty links cause most problems.
- Test with people and tools. Automated checkers find some issues. Keyboard and screen reader testing finds the rest.
- Keep it up. Every new page, plugin, and image can add new barriers, so accessibility is ongoing work.
An accessible website isn’t a separate version of your site, and it isn’t a one-time ADA compliance project. It’s the same site, built so more people can use it. The work overlaps with good website design, clear writing, and fast pages.
Key Takeaways
Making a website ADA compliant comes down to:
- WCAG is the yardstick: Level AA of WCAG 2.1 or 2.2 is the standard most businesses work toward.
- A few failures cause most problems: Contrast, alt text, form labels, and empty links top the list.
- Tools aren’t enough: Automated scans miss issues that keyboard and screen reader tests catch.
- It’s ongoing: Each update can add barriers, so check accessibility as part of regular maintenance.
How the ADA and WCAG fit together
People often treat "ADA" and "WCAG" as the same thing. They’re related, but they do different jobs.
What the ADA covers
The ADA is a civil rights law that prohibits discrimination against people with disabilities. Title III covers businesses open to the public, which the law calls public accommodations. Title II covers state and local governments.
For businesses, the ADA.gov web guidance explains that the law’s general rules on equal access and effective communication apply to websites. It doesn’t name one required technical standard for private businesses. It does point to WCAG and the federal Section 508 Standards as helpful guidance.
What WCAG is
The Web Content Accessibility Guidelines are a technical standard from the World Wide Web Consortium, or W3C. The W3C’s WCAG overview describes WCAG 2.0, 2.1, and 2.2 as the international standard for making web content more accessible to people with disabilities.
WCAG is built on four principles. Content must be perceivable, operable, understandable, and robust. Under those sit testable success criteria at three levels: A, AA, and AAA. Level AA is the common target.
The rule for state and local governments
State and local governments have a specific technical standard. The Department of Justice’s rule on web accessibility adopted "WCAG 2.1, Level AA" as the technical standard for their websites and mobile apps.
Compliance dates depend on size. ADA.gov now lists April 26, 2027, for governments with a total population of 50,000 or more. Smaller ones and special districts have until April 26, 2028. That rule covers governments, not private businesses, but it shows which standard regulators use.
| Term | What it is | Who it applies to |
|---|---|---|
| ADA Title III | Civil rights law for public accommodations | Businesses open to the public |
| ADA Title II | Civil rights law for public entities | State and local governments |
| WCAG 2.1 / 2.2 | Technical accessibility standard from W3C | Anyone building web content |
| Level AA | The middle conformance level of WCAG | The usual target for businesses and governments |
The ADA sets the goal. WCAG gives you the checklist.
Why web accessibility pays off beyond the law
Accessibility issues don’t just affect people with disabilities. Good color contrast helps anyone reading outside. Captions help people in a quiet office. Clear forms help a customer in a hurry finish checkout.
An accessible website also tends to be a better-built website. Clean headings, descriptive links, and text alternatives give search engines and AI tools clearer content to read. Keyboard-friendly menus usually work better on touch screens too.
There’s a business case in the risk as well. Website accessibility lawsuits and demand letters reach businesses of every size. Building with WCAG in mind from the start is easier than retrofitting a site after a complaint. Regular accessibility testing keeps small problems from piling up.
Common accessibility failures
Common accessibility issues aren’t exotic. The same handful show up on site after site, and they’re fixable.
The WebAIM Million report tested the home pages of the top one million websites. It found detected WCAG failures on 95.9% of them. Most sites have work to do, and yours probably does too.
WebAIM also found that 96% of detected errors fall into six categories. Here they are, with the share of home pages that had each one.
| Failure | Share of home pages (WebAIM) | What it means |
|---|---|---|
| Low contrast text | 83.9% | Text too faint to read against its background |
| Missing alt text | 53.1% | Images with no text description for screen readers |
| Missing form labels | 51% | Form fields a screen reader can’t name |
| Empty links | 46.3% | Links with no text, like icon-only links |
| Empty buttons | 30.6% | Buttons with no readable label |
| Missing document language | 13.5% | Page language not set for screen readers |
Low color contrast
Poor color contrast is WebAIM’s most common finding. Light gray text on white looks sleek and reads badly. People with low vision can’t read it, and neither can anyone outdoors on a phone. WCAG Level AA asks for a contrast ratio of at least 4.5 to 1 for normal text.
Missing alt text
Alt text is a short description of an image that screen readers read aloud. Without it, a person who’s blind hears a file name or nothing at all. Decorative images can use empty alt text, so screen readers skip them.
Unlabeled forms and empty buttons
A contact form with placeholder text but no labels leaves screen reader users guessing. An icon-only button, like a magnifying glass for search, needs a text label too. These issues hit the pages that matter most, like booking and checkout.
Keyboard traps and hidden focus
Some people navigate with a keyboard alone. If menus, pop-ups, or sliders can’t be reached or closed with a keyboard, those users get stuck. A visible focus outline shows where they are on the page.
Many themes remove that outline because designers find it untidy. Put it back, and style it to match your brand instead. A "skip to main content" link also saves keyboard users from tabbing through the whole menu on every page.
Video without captions
Videos need captions for people who are deaf or hard of hearing. Captions also help everyone watching with the sound off. Audio-only content, like a podcast, needs a transcript.
Headings that skip around
Screen reader users often jump from heading to heading to scan a page. If headings are chosen for their size instead of their order, the page structure falls apart. Use one H1, then H2s and H3s in a logical outline.
Vague link text
Links that say "click here" or "read more" make no sense when a screen reader lists all the links on a page. Write link text that says where the link goes, such as "view our menu" or "download the price list."
Color as the only signal
A form that marks errors only in red leaves out people who can’t see red. Pair color with text or an icon, such as "This field is required." The same goes for charts and buttons that rely on color alone.
Inaccessible PDFs
Many sites post forms, menus, and brochures as PDFs. A scanned PDF is just a picture to a screen reader. Where you can, put the content on a web page. Where you can’t, use a tagged, accessible PDF.
Now ask yourself: could a customer book, buy, or contact you using only a keyboard?
Testing and fixing your website
Accessibility testing works best in layers. Each layer catches problems the others miss.
- Run a website accessibility checker. Free tools like WAVE or Lighthouse flag contrast, alt text, and label problems in minutes.
- Do the W3C’s Easy Checks. The W3C Easy Checks walk through page titles, headings, contrast, keyboard access, and more.
- Test keyboard accessibility. Unplug the mouse and try to use every menu, form, and button.
- Test with a screen reader. VoiceOver on Mac and iPhone and NVDA on Windows are free.
- Fix by template, not page by page. A fix to a header or form template repairs every page that uses it.
- Write an accessibility statement. Tell visitors how to report a problem and how you’ll respond.
Know the limits of each layer. The W3C says its Easy Checks "are not definitive," and a page could pass them while still having serious barriers. Automated checkers have the same blind spot.
Assign an owner, too. Digital accessibility slips when nobody is responsible for it. Name one person to review new pages and to answer accessibility reports from visitors.
Be careful with accessibility overlays, the widgets that promise one-line compliance. They can change colors or text size, but they don’t fix the underlying code. We recommend fixing the site itself.
Once your site is in good shape, keep it there. New pages, images, and plugins can add barriers, so build checks into your website maintenance routine. Accessibility and speed often go together, and our mobile website design and performance basics cover the overlap.
Accessibility isn’t a project you finish. It’s a habit you keep.
This is not legal advice
We build and fix websites. We’re not lawyers, and this post isn’t legal advice.
Your accessibility requirements depend on your business, your location, and how you serve customers. We can’t tell you whether your website is ADA compliant in a legal sense.
Website accessibility lawsuits do happen, and the law keeps changing. If you’ve received a demand letter, or you want to know what applies to you, talk to an attorney who handles ADA matters.
What we can tell you is practical. Building to recognized accessibility standards like WCAG 2.1 or 2.2 Level AA, testing regularly, and fixing what you find is a best practice. It’s also where we’d start on ADA compliance. It makes your site usable for more customers, whatever the legal picture.
ADA compliant website FAQs
Is ADA website compliance required for small businesses?
The ADA applies to businesses open to the public, and the Department of Justice says that includes access to their websites. No specific technical rule exists for private businesses, so most use WCAG. This is general information, not legal advice. An attorney can tell you what applies to your business.
What WCAG level should my website meet?
Most businesses aim for WCAG 2.1 or 2.2 at Level AA. That’s the standard the Department of Justice adopted for state and local government websites. Level A covers the most basic needs, and Level AAA is stricter than most sites can fully meet.
Can an accessibility checker make my website ADA compliant?
No tool can make a site compliant by itself. Automated checkers find many common issues, like low contrast and missing alt text, but they miss problems with keyboard access, focus, and meaning. Combine automated scans with manual keyboard and screen reader testing.
Do accessibility overlays work?
Overlays add a toolbar that changes things like text size or contrast. They don’t fix the code underneath, such as missing labels or keyboard traps. We recommend fixing those issues in the site itself so the site works with the tools people already use.
How much does it cost to make a website accessible?
It depends on the size of the site and how many issues it has. Fixing templates, forms, and images on a small site is a modest project. A large site with custom features takes more work. An audit is the best first step, because it shows what needs fixing.
Getting help in Reno
If you take one thing from this, build to WCAG Level AA and keep testing, because an accessible site works better for every customer.
White Peak is a web design and digital marketing agency in downtown Reno. We build and update websites with accessibility in mind for businesses in Reno, Sparks, Carson City, Truckee, and nationwide.
If your site needs an accessibility check or a rebuild, our web design in Reno work has these standards built in. Book a free consultation and we’ll review your site with you.
