August 1, 2026
How to Make Your Website ADA Compliant (2026 Guide)
Making a website ADA compliant means matching it to WCAG 2.1 Level AA, the technical standard courts and regulators point to when they enforce the Americans with Disabilities Act online. This guide walks through the steps in order, from the free scan to the ongoing monitoring that keeps you compliant after launch.
- WCAG 2.1 Level AA is the standard to target for how to make your website ADA compliant in 2026 — Verdict: non-negotiable baseline.
- A 4.5:1 contrast ratio and 44x44px touch targets are the two most-failed checks on small business sites.
- Alt text, keyboard navigation, and captioned video cover the bulk of real-world lawsuits — fix these first.
- An accessibility overlay widget alone does not satisfy ADA compliance — automated scans still catch violations underneath it.
- Budget for a manual screen-reader pass; automated tools only catch 30-40% of WCAG failures on their own.
Why this matters
ADA Title III applies to any business open to the public, and courts have treated websites as places of public accommodation for years now. Small business sites get named in demand letters just as often as large retailers — a broken contact form or a menu with no alt text is enough to trigger one.
The fix isn't cosmetic. A site built around clear structure, readable contrast, and keyboard access also converts better for every visitor, not just the ones using assistive tech. That overlap is why accessibility work belongs in the same conversation as the best website security features for small business sites — both are foundational, not optional add-ons you bolt on later.
Nonprofits and public-facing services carry extra exposure here too, since grant funders and government partners increasingly ask for a written accessibility commitment before they'll sign a contract.
What you'll need
- Access to your website's code or CMS (WordPress, Shopify, Wix, or a custom-built site)
- A free automated scanner (WAVE, axe DevTools, or Lighthouse)
- A screen reader for manual testing (VoiceOver on Mac, NVDA on Windows — both free)
- A color contrast checker (WebAIM's is free and fast)
- 3-6 hours for a first pass on a typical 10-15 page small business site
- A plan for ongoing fixes, since new pages and new content re-introduce errors
The steps
1. Run an automated accessibility scan
Start with a free tool like WAVE or Lighthouse to get a baseline list of violations. This step accomplishes the triage — it sorts your problems into missing alt text, low contrast, unlabeled form fields, and broken heading structure, usually in under five minutes per page.
Run it on your homepage, your contact page, and any page with a form or a menu. Automated scans catch roughly 30-40% of WCAG failures; the rest need a human pass, which is why this is step one, not the only step.
Common mistake: stopping after the automated scan and assuming a clean report means full compliance. It doesn't.
2. Fix color contrast and text sizing
WCAG 2.1 AA requires a 4.5:1 contrast ratio for normal text and 3:1 for large text (18pt or 14pt bold and up). This matters because low-contrast text — light gray on white, pastel-on-pastel branding — is the single most common failure on small business sites.
Run every text/background combination through WebAIM's contrast checker and adjust hex values until each pair clears 4.5:1. Set base body text to at least 16px and make sure the page holds its layout at 200% browser zoom.
Common mistake: fixing contrast on the homepage and forgetting footer links and form placeholder text, which fail at the same rate as body copy.
3. Add alt text to every image
Alt text lets screen reader users know what an image shows, and it's required on every image that conveys information — logos, product photos, infographics, icons that act as buttons. This is often the fastest fix on the whole list.
Write one specific sentence per image describing its function or content, not its filename. Decorative images (background textures, dividers) get an empty alt attribute (alt="") so screen readers skip them instead of reading a filename aloud.
Common mistake: writing alt text like "image1.jpg" or stuffing it with keywords instead of describing what's actually shown.
4. Make navigation keyboard-only
Every link, button, form field, and menu item needs to work with the Tab key alone, no mouse required. This matters because keyboard-only navigation is how a large share of assistive-tech users browse, and it's one of the most-cited failures in ADA demand letters.
Tab through your entire site and confirm a visible focus outline appears on every clickable element, in the order it appears visually. Dropdown menus need to open and close with Enter and Escape, not just hover.
Common mistake: removing the default focus outline in CSS for aesthetic reasons and never replacing it with a custom one.
5. Caption and transcribe video and audio
Any video with dialogue needs captions, and any standalone audio (podcasts, voiceovers) needs a text transcript. This covers Deaf and hard-of-hearing users and also helps your video content get indexed by search engines.
Use YouTube's free auto-caption tool as a starting point, then correct it manually — auto-captions run 70-85% accurate on clear audio and worse on background noise. Post the corrected transcript directly below the embed.
Common mistake: relying on auto-generated captions without reviewing them for accuracy.
6. Label every form field
Every input needs a visible, programmatically-linked label — not just placeholder text that disappears once someone starts typing. This matters because a screen reader announces the label, not the placeholder, and an unlabeled field is unusable for anyone relying on audio cues.
Check contact forms, booking forms, and newsletter signups. Each field should announce its purpose ("Email address," "Phone number") and any required field should say so out loud, not just show a red asterisk.
Common mistake: using placeholder text as the only label, which vanishes the moment a user starts typing and leaves screen reader users with no memory of what field they're in.
7. Test with a screen reader
Run VoiceOver or NVDA across your five most-visited pages and listen to how the site actually sounds. This step accomplishes what automated tools can't: it tells you whether the experience makes sense, not just whether the code technically passes.
Listen for skipped headings, images announced with no context, and forms that jump around in an order that doesn't match the visual layout. Budget 30-45 minutes per page the first time through.
Common mistake: skipping this step because it feels slow — it's the step that catches what every automated scanner misses.
Get your site checked for ADA gaps
A flat monthly plan covers builds, hosting, and ongoing accessibility fixes.
8. Publish an accessibility statement and monitor ongoing
A short accessibility statement — what standard you follow, how to report an issue, contact info for accessibility complaints — signals good faith and gives visitors a clear path if something's broken. It won't stop every legal threat, but it's standard practice on compliant sites in 2026.
Re-scan after every content update, since a new blog post or product page can reintroduce contrast or alt text failures within a week of publishing.
Troubleshooting
- Automated scan shows zero errors but a lawsuit still names your site — automated tools miss manual-testing failures like illogical tab order or captions with wrong timing. Run a screen reader pass.
- Contrast checker fails your brand colors — darken the text color or add a solid background behind it rather than abandoning your palette entirely.
- PDF menus or forms aren't accessible — convert static PDFs to HTML pages; PDFs are one of the hardest formats to remediate and one of the most-cited failures for restaurants specifically.
- Overlay widget installed but scan still fails — overlay tools patch surface issues but don't fix underlying code; they're not a substitute for the steps above.
- Third-party booking or ordering widget fails contrast or keyboard checks — flag it to the vendor directly; embedded widgets from outside tools often need their own remediation request.
- New pages keep reintroducing errors — add a scan step to your content publishing checklist so nothing ships unchecked.
Tools and resources
- WAVE and axe DevTools — free automated scanners for a first-pass audit
- WebAIM Contrast Checker — free, instant 4.5:1 ratio testing
- VoiceOver (Mac) and NVDA (Windows) — free screen readers for manual testing
- A website maintenance plan that includes recurring scans, so compliance doesn't slip after the initial fix
- WCAG 2.1 Level AA documentation from W3C, the source standard behind every check above
What to do next
Once the site passes a manual screen reader test, put a recurring check on the calendar — quarterly at minimum, monthly if you publish often. Compliance isn't a one-time project; it's closer to the best website upgrades for growing small businesses, something you revisit as the site grows.
FAQ
How much does it cost to make a website ADA compliant?
Fixes range from a few hours of DIY work using free tools to a few thousand dollars for a full remediation on a large site. Small business sites with 10-15 pages typically need 3-6 hours for a first pass covering contrast, alt text, and form labels.
Is WCAG 2.1 AA legally required for ADA compliance?
WCAG 2.1 Level AA isn't written into the ADA statute itself, but courts and the Department of Justice consistently point to it as the technical benchmark. Meeting it is the closest thing to a legal safe harbor available in 2026.
Do accessibility overlay widgets make a site ADA compliant?
No. Overlay widgets adjust the display but don't fix underlying code issues like missing alt text or broken keyboard navigation. Automated scans still flag violations on sites running overlay tools.
What's the most common ADA violation on small business websites?
Low color contrast and missing alt text top the list, followed by unlabeled form fields and broken keyboard navigation. All four are fixable in a single afternoon on most small sites.
How often should I re-check my site for ADA compliance?
Re-scan after every major content update and run a full check quarterly at minimum. New pages, new images, and new forms all reintroduce accessibility errors even on a previously compliant site.
Does ADA compliance apply to small businesses with only a few employees?
Yes. Title III of the ADA covers any business open to the public, regardless of size, if the website is considered a place of public accommodation. Company size affects legal exposure, not the compliance requirement itself.
Can I test ADA compliance myself without hiring anyone?
Yes, for a first pass. Free tools like WAVE, WebAIM's contrast checker, and a built-in screen reader cover most of the checks in this guide, though a manual screen reader pass is worth the extra time.
One last thing
The fix most sites skip is the manual screen reader test, and it's the one that catches what actually gets flagged in real complaints — tab order that jumps around, captions that lag the audio, a form field that announces nothing at all. Run the automated scan first, but budget the 30-45 minutes per page for the manual pass before you call the job done.