Website Accessibility for Small Business: What the ADA and WCAG Mean for Your Site
Website accessibility means people with disabilities can use your site, including people who rely on screen readers, keyboards, captions or zoom. For a US business open to the public, the Department of Justice says the ADA applies to what you offer online. The usual technical yardstick is WCAG 2 Level AA, and the most common problems are fixable.
This guide covers what the law and standards say, the most common errors and a sensible order of work. It is general information, not legal advice; if you have received a demand letter or complaint, talk to a lawyer.
Does the ADA apply to small business websites?
The Americans with Disabilities Act covers state and local governments (Title II) and businesses open to the public (Title III). In its guidance on web accessibility, published on ADA.gov on March 18, 2022, the Department of Justice says it has taken the position since 1996 that the ADA applies to web content, and that businesses open to the public must make the goods and services they offer online accessible to people with disabilities. Its examples of businesses open to the public include retail stores, banks, hotels, medical offices, restaurants and theaters.
Two details from that guidance matter for planning:
- There is no detailed DOJ regulation for private businesses' websites. The Department says businesses have flexibility in how they comply, but they still have to comply.
- It points to existing standards for how to do it: the Web Content Accessibility Guidelines (WCAG) and the federal Section 508 Standards.
What about the 2024 rule?
In April 2024 the Department published a Title II rule that requires state and local governments to make their web content and mobile apps meet WCAG 2.1 Level AA. That rule does not cover private businesses. According to ADA.gov, an interim final rule published April 20, 2026 moved the compliance dates to April 26, 2027 for governments serving 50,000 or more people and April 26, 2028 for smaller ones and special districts. If you build websites or apps for a city, county or school district, those dates apply to your client.
What is WCAG, and which level should you aim for?
WCAG is the international web accessibility standard from the World Wide Web Consortium (W3C). According to the W3C, WCAG 2.0 was published in December 2008, WCAG 2.1 in June 2018 and WCAG 2.2 on October 5, 2023. Later versions add requirements without changing the earlier ones, so a site that meets 2.2 also meets 2.1.
WCAG 2.2 has 13 guidelines under four principles: content must be perceivable, operable, understandable and robust. Each guideline has testable success criteria at three levels, A, AA and AAA. Level AA is the target most organizations and the 2024 government rule use, and it is a sensible goal for a business site.
What are the most common accessibility errors?
WebAIM, based at Utah State University, tests the home pages of the top one million websites each year with its WAVE tool. Its February 2026 run found detectable WCAG 2 failures on 95.9% of home pages, up from 94.8% in 2025. Six error types made up 96% of everything it detected:
- Low contrast text: 83.9% of home pages
- Missing image alt text: 53.1% of home pages
- Missing form input labels: 51% of home pages
- Empty links: 46.3% of home pages
- Empty buttons: 30.6% of home pages
- Missing document language: 13.5% of home pages
WebAIM notes that automated tools cannot detect every failure. The useful point for a small business: most of these problems are design and coding habits, not reasons for a rebuild.
How do you check your own website?
Use three passes. Each catches things the others miss.
- Run an automated checker on your home page, a service or product page, your contact form and your checkout or booking flow. Free browser tools such as WAVE or the accessibility audit in Chrome's Lighthouse are a reasonable start.
- Try it with a keyboard only. Press Tab through each page. Can you reach every link, menu and button? Can you see where the focus is? Can you submit the form and close any pop-up without a mouse?
- Try it with a screen reader. VoiceOver is built into Macs and iPhones, and NVDA is a free screen reader for Windows. Listen to whether headings, links and form fields make sense when read aloud out of visual context.
The DOJ guidance makes the same point about tools: automated checkers and overlays can help, but "a 'clean' report does not necessarily mean everything is accessible," so pair them with a manual check.
What should you fix first?
Start with the pages and tasks that bring in business, then work outward.
- Forms: give every field a visible label tied to it in code, say which fields are required in words (not only with red text), and describe errors clearly.
- Color contrast: fix light gray text and text over busy images. This is the most common error on the web and usually a style-sheet change.
- Images: add short alt text that says what an image is for; mark purely decorative images so screen readers skip them.
- Links and buttons: make sure icon-only buttons (menus, search, social icons) have an accessible name, and link text says where it goes.
- Headings and language: use real heading tags in order, and set the page language in the HTML.
- Video: add accurate captions to anything with speech.
- Keyboard and zoom: every action should work by keyboard, and the layout should hold up when text is zoomed.
- A way to report problems: the DOJ lists this as good practice. An email address on your accessibility page is enough to start.
Do accessibility overlays solve the problem?
An overlay is a script that adds a toolbar or tries to repair a page automatically. The DOJ guidance groups overlays with automated checkers as tools that "need to be used carefully." They can change surface details, but they cannot write meaningful alt text for your photos, fix a checkout flow built without keyboard support or restructure confusing pages. Fixing the underlying code and content is the reliable route.
How to keep a site accessible
Accessibility slips when new pages, plugins and campaigns go live without checks. Build it into the normal process:
- Add accessibility to the brief and design review for every new page.
- Choose themes, plugins and form tools that state their WCAG conformance, and test them before rollout.
- Include keyboard and screen reader checks in your QA before each release.
- Train the people who publish content to write alt text, use headings and caption video.
- Recheck the key pages every quarter.
How Loxvo can help
Loxvo's web design and development team builds and repairs sites with WCAG 2.2 Level AA as the working target, from contrast and forms to keyboard support. Our software testing and QA services can audit your key pages and flows with automated and manual checks and write up what to fix in priority order. Our developers work remotely from around the world, so US businesses get experienced people at a fair price. Email hello@loxvo.com to talk it through.
FAQ
Is WCAG a law in the United States?
WCAG itself is a technical standard, not a law. The ADA is the law. The 2024 Title II rule makes WCAG 2.1 Level AA the requirement for state and local governments, and the DOJ points businesses to WCAG as helpful guidance on how to meet the ADA.
Which WCAG level should a small business aim for?
Level AA. It is the level used in the 2024 government rule and the common target for organizations. Level A alone leaves out important items such as color contrast, and Level AAA is rarely required for a whole site.
Can a website be fully accessible after one audit?
An audit gives you a list of problems at one point in time. Sites change constantly, so accessibility needs checks on new pages and releases, plus a periodic review of the pages that matter most.
Where can I read the official guidance?
Start with the Department of Justice's "Guidance on Web Accessibility and the ADA" on ADA.gov and the W3C's WCAG 2 overview, which links to the WCAG 2.2 standard and a quick reference.