← All owner guides

Owner guide · 8 min read

Does My Website Need to Be ADA Compliant?

If your business is open to the public, the US Department of Justice says the ADA covers what you offer online too. It has not set a detailed technical rule for private business websites, so most owners measure against WCAG Level AA, the web's accessibility standard. This is general information, not legal advice.

KC Hansen

Published October 21, 2026

WCAG 2.1 AA

the standard the 2024 rule sets for state and local government sites

4.5:1

the minimum contrast between normal text and its background (WCAG)

200%

how far text should enlarge without losing content (WCAG)

The short version: if your business is open to the public, the Department of Justice treats your website as part of how you serve the public, so it should work for people with disabilities. What the law does not give private businesses is a detailed checklist for websites. The checklist most people use is WCAG, the Web Content Accessibility Guidelines from the W3C, at Level AA. This guide explains what the government has actually said, what it hasn’t, and what you can check on your own site today. It is general information, not legal advice. If you have received a demand letter or have a specific legal question, talk to a lawyer.

What does the ADA say about business websites?

For websites, what matters most is how the Department of Justice reads the ADA. In its web guidance, the Department says businesses open to the public (it calls them “public accommodations,” covered by Title III of the ADA) must give people with disabilities full and equal access to their goods and services, “including those offered on the web” (ADA.gov web guidance).

The same page is just as clear about what it isn’t. It says the Department “does not have a regulation setting out detailed standards” for private business websites, and that businesses “have flexibility in how they comply.” It names WCAG and the federal government’s own Section 508 standards as existing technical standards that “provide helpful guidance.” The page also notes that guidance documents like it have no legally binding effect on their own. In plain words: the duty is real, the exact yardstick is left to you.

That guidance was published in March 2022, and the page itself says it doesn’t reflect the 2024 rule for state and local governments, covered next.

What changed in 2024, and who does it cover?

In 2024 the Department of Justice published a rule that sets a specific standard, WCAG 2.1 Level AA, but only for state and local governments under Title II of the ADA. That includes cities, counties, school districts and special districts, and the outside companies that build or run web content for them (ADA.gov fact sheet on the 2024 rule).

The compliance dates have moved. According to the same fact sheet, an interim rule published on April 20, 2026 extended them to April 26, 2027 for governments serving 50,000 people or more, and April 26, 2028 for smaller governments and special districts.

Title II (state and local government)Title III (businesses open to the public)
WhoCities, counties, schools, special districts, and their contractorsBusinesses open to the public, such as shops, restaurants and clinics
Does the ADA apply to their websites?YesThe Department of Justice says yes
Is there a set web standard in the rules?Yes: WCAG 2.1 Level AA, from the 2024 ruleNo detailed standard; WCAG named as helpful guidance
Key dateApril 26, 2027 or 2028, by populationNone set

The 2024 rule is not a rule for private businesses. But it tells you which standard the Department chose when it did write one down, and that is a useful signal. If you build a website for a city, as we have, the rule applies to that work directly.

What is WCAG, and which version should you use?

WCAG is the technical standard for accessible websites, written by the W3C, the group that writes the web’s core standards. Its tests come in three levels, A, AA and AAA. Level AA is the one most rules and most owners aim for.

WCAG 2.1 was published in June 2018 and WCAG 2.2 in October 2023. The W3C encourages using the newest version, and a site that meets 2.2 also meets 2.1 and 2.0 (W3C WCAG overview). So aiming for 2.2 Level AA covers both.

Here are a few of the WCAG tests in plain words, from the standard itself (WCAG 2.2):

  • Text descriptions for images. Images that carry meaning need a text alternative that serves the same purpose (Level A).
  • Readable contrast. Normal text needs a contrast ratio of at least 4.5:1 against its background, large text at least 3:1 (Level AA).
  • Zoom. Text can be enlarged up to 200 percent without losing content or function (Level AA).
  • Keyboard. Everything on the page works from a keyboard, not just a mouse (Level A).
  • Skip the repeated parts. There is a way to jump past blocks that repeat on every page, like the menu (Level A).
  • Visible focus. When you move through the page with the keyboard, you can see where you are (Level AA).
  • Captions. Prerecorded video with sound has captions (Level A).
  • Tap targets. Buttons and links are at least 24 by 24 pixels, with some exceptions (W3C, Target Size) (Level AA, new in 2.2).

Checks you can do yourself in ten minutes

You can find the most common problems without any special tools. The W3C publishes a set of “Easy Checks” for exactly this (W3C Easy Checks). Try these on your homepage and your contact page:

  1. Photos. Ask your web person, or check your site editor, whether each meaningful photo has a short description. A roofer’s photo should say something like “new architectural shingle roof on a two-story home,” not “IMG_4471.”
  2. Contrast. Look for light gray text on white, or white text on a pale photo. If it’s hard for you to read in sunlight, it’s hard for many people all the time.
  3. Zoom. On a computer, press Ctrl and the plus key (Command and plus on a Mac) until the page is at 200%. Text shouldn’t overlap or get cut off. On a phone, try pinching to zoom. If the page won’t zoom, that is a problem.
  4. Keyboard. Click the address bar, then press Tab over and over. You should be able to reach every link, button and form box, in a sensible order, and always see which one is selected.
  5. Forms. Each box on your quote form should have a label that stays visible, not just gray hint text that disappears when you start typing. Errors should say what’s wrong in words, not only by turning a box red.
  6. Video. If you have a video of your crew or your shop, turn the sound off. Can you still follow it with the captions? The W3C’s checks call for accurate captions, not only automatic ones, and automatic captions are worth reading through for mistakes.

Tip: the W3C is blunt that these quick checks are not the final word: a page “could seem to pass these checks, yet still have significant accessibility barriers.” Use them to find problems, not to declare a site finished.

Mistakes that cost owners the most

The most expensive mistakes are the ones that look like a shortcut.

  • Buying a widget instead of fixing the site. Some products promise that adding a plug-in makes a site compliant. In April 2025 the Federal Trade Commission approved a final order requiring the maker of one such widget to pay $1 million, over claims that its plug-in could make any website meet WCAG (FTC). Real accessibility is built into the pages.
  • Believing a badge. There is no official ADA certification for websites. Anyone who says a site is “certified” or guaranteed safe from lawsuits is selling something they can’t deliver.
  • Turning off zoom on phones. We often find older sites that block pinch-to-zoom to keep the layout tidy. That locks out people with low vision.
  • Photos of text. A flyer image with your prices on it can’t be read aloud by a screen reader. Put the words on the page as words.
  • Forms with no labels. A plumber’s booking form with three unlabeled boxes is a guessing game for anyone using a screen reader.
  • Checking once and never again. Every new photo, page or special can bring new problems. Accessibility is upkeep, not a one-time project.

What about edge cases?

A few situations come up often for local businesses:

  • Online booking or payment tools from another company. If customers book or pay through a third-party tool, that tool is part of how they reach your service. Ask the provider what accessibility standard it meets.
  • PDF menus and price lists. A scanned PDF is often just a picture. A cleaner’s price sheet or a restaurant’s menu works better as a real web page.
  • Businesses with no storefront. If customers never come to you, for example a mobile detailer or an online-only shop, how the ADA applies to you is a legal question. Ask a lawyer, not a web designer.

How we build accessibility into every site

Every site we build comes with the basics built in from the start, not added later. That means a skip link to jump past the menu, a visible focus outline for keyboard users, labels that screen readers can read, zoom allowed on phones, alt text on every image, and large tap targets. Every site has a published accessibility statement, so visitors know who to contact if something doesn’t work for them. Before launch, each site is run through an automated accessibility check and must show zero critical or serious issues. We also check it on real phone screen sizes. You can see examples in our work.

What we don’t do is promise a legal outcome. No web designer can honestly certify a site or guarantee it will never draw a complaint, and we won’t. What we can do is build to the published standard, use real text instead of pictures of text, and keep it that way. Every change we make for you on either monthly plan is held to the same standard as launch day.

The build is $5,000, one time, and you see the whole site working on your phone before you pay. After launch it’s $99 a month for Care or $249 for Growth, month to month. See the full offer on our websites page. If you’re comparing designers, our guide on how to choose a web designer has the questions to ask, including how they handle accessibility. When you’re ready, apply here and we’ll show you your new site.

Sites we've built

Real sites we built for local businesses. See all our work →

Accessibility checks you can do today

0 / 7

Tap to tick. Your ticks stay on this device.

Questions

Asked constantly. Answered honestly.

Is there an official ADA certification for websites? +

No. The Department of Justice does not certify websites, and no company can issue an official ADA certificate. Be wary of anyone selling a badge or a promise that a site is safe from lawsuits. What you can do is build to WCAG Level AA and keep checking.

Will an accessibility plug-in or widget make my site compliant? +

Don't count on it. In 2025 the Federal Trade Commission ordered the maker of one popular widget to pay $1 million over claims that its tool could make any website meet the WCAG standard. Real fixes go into the site itself.

Does the 2024 rule apply to my business? +

The 2024 rule with WCAG 2.1 Level AA as the standard covers state and local governments, and companies building web content for them. It does not, by itself, set a rule for private businesses. Ask a lawyer how the ADA applies to your situation.

Should I use WCAG 2.1 or 2.2? +

The W3C, which writes the standard, encourages using the newest version, 2.2. A site that meets 2.2 also meets 2.1, so aiming for 2.2 Level AA covers both.

$5,000 for your website + from $99/mo after. See it before you pay.

See your new site free
KC Hansen

founded YourProject.ai in Lehi, where we build websites for local businesses. His whole career in IT (security, cloud, DevOps) means every site is fast, secure and built right, and kept up to date every month. More about KC and every guide →