Website accessibility services aren't a checkbox. They're how you stop quietly turning customers away. If a visitor is blind, deaf, or has a motor or cognitive impairment, a poorly built site keeps them out — legally, morally, and financially.
According to the Seyfarth ADA Title III Report, more than 8,000 ADA Title III website accessibility lawsuits were filed in federal court in recent years, and settlements run from low five figures to well past $100K. The bigger cost is the one nobody invoices for: missing customers. Per CDC Disability Impacts All of Us, 1 in 4 US adults has a disability. Excluding that audience is excluding a quarter of your potential market.
This guide explains what accessibility means, what compliance actually looks like in 2026, and how to fix what matters first.
TL;DR
- Accessibility means everyone can use your site: blind users on screen readers, deaf users with captions, colorblind users, motor-impaired users.
- WCAG 2.2 Level AA is the baseline US courts and most regulators reference. Aim there.
- Cost to remediate an existing site: $5K to $15K, 4 to 8 weeks. Building accessible from day one costs 10 to 15% more and saves 3 to 5x later.
- Skip accessibility overlays. Courts have already pushed back on them. Fix the actual code.
- Start with alt text, color contrast, keyboard navigation, and form labels. That handles roughly 70% of real issues.
Table of contents
- What website accessibility actually is
- The legal picture: ADA and WCAG
- The business case
- WCAG 2.2 standards explained
- Common accessibility issues
- Audit and fix process
- Building accessible sites from scratch
- Accessibility myths
- Reflecting on what compliance is really about
- FAQ
- Next steps
What website accessibility actually is
Accessibility means anyone can use your website, regardless of:
- Vision: blind users on screen readers, low-vision users on magnification, colorblind users who can't distinguish red from green
- Hearing: deaf and hard-of-hearing users who need captions and transcripts
- Motor: users with limited mobility who navigate by keyboard or voice
- Cognitive: users with dyslexia, ADHD, or processing disorders who need clear language and predictable layouts
A blind user lands on your site. The screen reader reads what you wrote. If you wrote nothing, it says nothing.
<!-- Bad: screen reader says nothing -->
<img src="product.jpg">
<!-- Good: screen reader describes the image -->
<img src="product.jpg" alt="Blue running shoes, size 10, $89">
Same site. One user understands the page. The other doesn't.
Accessibility isn't a feature. It's a baseline, like HTTPS or mobile responsiveness in 2026.
The legal picture: ADA and WCAG
ADA (Americans with Disabilities Act)
The ADA, passed in 1990, requires businesses to provide equal access to goods and services. Courts have applied it to the internet for years. If you operate in the US, your site is in scope.
Enforcement reality:
- The US Department of Justice can sue
- Private plaintiffs file under Title III
- Settlements run roughly $15K to $50K, with some exceeding $100K, per the Seyfarth Title III Report
Who gets sued? Retailers, nonprofits, software companies, law firms, medical practices. The "we're too small to get sued" theory has not held up well.
WCAG 2.2 (Web Content Accessibility Guidelines)
WCAG is the international standard from the W3C Web Accessibility Initiative. It's not a US law on its own, but US courts and federal procurement (Section 508) reference it as the standard for "reasonable" accessibility.
WCAG has three levels:
| Level | Standard | Effort | Target |
|---|---|---|---|
| A | Minimum | Low | A floor, not a goal |
| AA | Widely adopted | Medium | The industry baseline. Aim here. |
| AAA | Enhanced | High | Specialized applications, government, education |
Level AA covers four pillars:
- Perceivable — users can see or hear content
- Alt text on images
- Captions on video
- Color contrast 4.5:1 minimum
- Operable — users can navigate
- Keyboard navigation, no mouse required
- Visible focus indicators
- No content flashing more than 3 times per second
- Understandable — content is clear
- Readable language
- Consistent navigation
- Error messages that explain how to fix the problem
- Robust — works with assistive tech
- Semantic HTML
- ARIA labels where the semantic markup runs out
- Compatibility with screen readers and voice control
The business case
1. A larger market
Per CDC data, 1 in 4 US adults has a disability — roughly 61 million people. If your site excludes them, you're excluding 25% of the prospects you paid to reach.
2. Better SEO
Accessibility and SEO overlap more than most teams expect:
- Alt text helps image search
- Captions help video search
- Semantic HTML helps crawlers
- Faster, cleaner pages rank better
Result: accessible sites tend to rank better.
3. Better UX for everyone
Accessibility helps people who don't think of themselves as disabled:
- High contrast helps anyone reading on a sunny patio
- Keyboard navigation helps anyone whose trackpad is misbehaving
- Plain language helps non-native English speakers
- Captions help anyone watching at a volume that won't wake a sleeping child
4. Reduced legal risk
Documented accessibility effort — audit, fixes, ongoing maintenance — is the strongest defense if a complaint shows up. You can't promise zero risk, but you can stop being the easy target.
5. Inclusive hiring and culture
Accessible design helps employees with disabilities work alongside everyone else. The byproduct is a culture that doesn't have to apologize for itself in recruiting decks.
6. The reputational layer
Customers, partners, and journalists notice. Inaccessible sites are increasingly seen as a tell that the business cuts corners elsewhere.
WCAG 2.2 standards explained
Perceivable — content people can sense
Alternative text. Every meaningful image gets descriptive alt text.
<!-- Bad -->
<img src="hero.jpg">
<!-- Good -->
<img src="hero.jpg" alt="Sunlit beach with palm trees and calm blue water">
Color contrast. Minimum 4.5:1 for body text, 3:1 for large text. Use the WebAIM Contrast Checker to verify.
<!-- Bad: 2.6:1 contrast -->
<p style="color: #888; background: white;">Gray text on white</p>
<!-- Good: 12:1 contrast -->
<p style="color: #333; background: white;">Dark text on white</p>
Captions and transcripts. Video gets captions for deaf users and transcripts for search engines.
<video controls>
<source src="product-demo.mp4" type="video/mp4">
<track kind="captions" src="captions.vtt" srclang="en" label="English">
</video>
<p>Transcript: <a href="transcript.pdf">Download full transcript</a></p>
Operable — content people can use
Keyboard navigation. Tab reaches every interactive element. Enter and Space behave the way users expect.
<form>
<label for="email">Email</label>
<input id="email" type="email">
<label for="message">Message</label>
<textarea id="message"></textarea>
<button type="submit">Send</button>
</form>
Focus indicators. The keyboard user always sees where they are.
button:focus-visible {
outline: 2px solid #0066cc;
outline-offset: 2px;
}
No flashing content above 3 Hz. Flashing media can trigger seizures. WCAG is explicit about this.
Understandable — content people can follow
Readable language. Short sentences. The reading level your audience actually uses.
<!-- Bad: jargon for jargon's sake -->
<p>Optimize ROI through scalable platform-driven outcomes.</p>
<!-- Good: a real sentence -->
<p>Use the platform to grow sales by 30% in 3 months.</p>
Consistent navigation. The header and footer behave the same on every page. Users shouldn't have to relearn the site.
Labeled forms. Every input has a visible label tied to it.
<!-- Bad -->
<input type="email" placeholder="Email">
<!-- Good -->
<label for="email">Email</label>
<input id="email" type="email">
Robust — content assistive tech can parse
Semantic HTML. Use the right element for the right job.
<!-- Bad -->
<div onclick="navigate('/')">Home</div>
<!-- Good -->
<a href="/">Home</a>
<!-- Good: a real button -->
<button type="button" onclick="toggleMenu()">Menu</button>
ARIA labels when semantic HTML runs out.
<button aria-label="Close menu">
<span aria-hidden="true">×</span>
</button>
Common accessibility issues
Issue 1: missing alt text
Impact: blind users have no idea what your images show.
Fix: write descriptive alt text. Not "image.jpg." Describe what's there.
| Bad alt | Good alt |
|---|---|
| "photo" | "Team of 5 engineers at desks with laptops" |
| "icon" | "Green checkmark indicating success" |
| "diagram" | "Flowchart showing customer journey from awareness to purchase" |
Issue 2: poor color contrast
Impact: users with low vision or on bright screens can't read the text.
Fix: run WebAIM's contrast checker on every text/background combination. Aim for 4.5:1 on body text.
Issue 3: no keyboard navigation
Impact: users who can't use a mouse can't use your site.
Fix: tab through every page yourself. If you can't reach something, neither can they. Add visible focus indicators.
Issue 4: unlabeled form fields
Impact: screen readers announce "edit, blank" instead of "Email."
Fix: every input gets a <label> with a matching for attribute. Placeholders aren't labels.
Issue 5: no video captions
Impact: deaf users miss the message entirely.
Fix: caption every video. Use auto-captions as a draft, then edit to fix names, terms, and the inevitable "Cuez" turning into "Choose."
Issue 6: inaccessible PDFs
Impact: scanned PDFs are images. Screen readers can't read them.
Fix: OCR the document, or convert it to HTML. HTML is almost always more accessible than PDF.
Issue 7: auto-playing media and Flash relics
Impact: auto-play startles users and breaks screen reader output. Flash hasn't loaded since 2020.
Fix: HTML5 video, no auto-play, controls visible. Replace any remaining Flash. If the team isn't sure where it is, it's still on a page somewhere.
Audit and fix process
Step 1: automated audit (1 day)
Free tools that find the obvious issues:
- WAVE (WebAIM) — browser extension, highlights issues inline
- axe DevTools — detailed reports
- Google Lighthouse — built into Chrome DevTools, includes an accessibility score
- WebAIM Contrast Checker — for color contrast
What I usually find on a first scan:
- Missing alt text on 30 to 50% of images
- Poor color contrast on 20 to 40% of pages
- Missing form labels on 15 to 30% of forms
- Missing ARIA on custom buttons and icons
Step 2: manual testing (1 to 2 weeks)
Automated tools catch 60 to 70% of issues. Manual testing catches the rest:
- Screen reader testing with NVDA (free) or JAWS
- Keyboard testing — tab through the whole site, check focus visibility
- Color blindness simulation in DevTools
- Zoom testing at 200%
- Real mobile device testing, not just the browser emulator
Step 3: user testing (optional, recommended)
Five users with disabilities will reveal usability issues no tool catches. Cost: $1K to $3K. Value: catches the 20% of issues that would have triggered a complaint after launch.
Step 4: remediation (4 to 8 weeks)
| Fix | Effort | Cost |
|---|---|---|
| Add alt text | 1 to 2 weeks | $1K to $3K |
| Fix color contrast | 1 week | $500 to $1K |
| Fix keyboard navigation | 2 to 3 weeks | $2K to $4K |
| Add form labels | 1 week | $500 to $1K |
| Add captions to videos | 1 to 2 weeks | $1K to $3K |
| Add ARIA labels | 1 to 2 weeks | $1K to $2K |
Total remediation for a typical 50 to 100-page site: $5K to $15K.
Step 5: ongoing maintenance
After the fix, accessibility goes into the workflow:
- Code review with accessibility checks
- Automated tests in CI/CD (axe-core, pa11y)
- Quarterly audits
- A way for users to report issues
Annual maintenance budget: 5 to 10% of the original remediation cost.
Building accessible sites from scratch
If you're starting fresh, accessibility costs about 10 to 15% more upfront and saves 3 to 5x in remediation later.
An accessibility-first process
- Use semantic HTML.
<button>,<nav>,<main>,<article>instead of div soup. - Design for accessibility from the first sketch. High contrast, larger type, predictable layouts.
- Test with a keyboard before shipping any page.
- Test with a screen reader. NVDA on Windows, VoiceOver on Mac, both free.
- Write alt text as you place images, not in a sprint two months later.
- Automate testing. axe-core or pa11y in CI catches regressions before they ship.
Accessibility in design systems
If you're building a component library, make accessibility part of the foundation:
- Buttons: keyboard reachable, visible focus
- Forms: labels mandatory, error states clear
- Cards: semantic heading hierarchy, descriptive links
- Modals: focus trapped inside, focus restored on close
- Icons: hidden from screen readers if decorative, labeled if functional
A solid design system prevents most accessibility issues. A weak one forces every developer to relearn the same lessons in their own way.
Accessibility myths
Myth 1: "accessibility makes sites ugly"
Good accessibility is good design. High contrast, clear labels, simple navigation help everyone. The "ugly accessible site" is almost always just an ugly site.
Myth 2: "we can use an accessibility overlay"
Overlays paste a widget on top of the same broken code. They improve a few automated metrics. They don't fix the underlying issues. US courts have already pushed back on overlay-only "fixes." Fix the code.
Myth 3: "accessibility is only for legal compliance"
Compliance is the floor. The ceiling is a 25% larger addressable market, better SEO, and a UX everyone benefits from.
Myth 4: "blind users don't visit websites"
Blind and low-vision users use websites every day. According to WHO data, at least 2.2 billion people globally have some form of vision impairment. They are using the internet right now.
Myth 5: "accessibility requires perfect code"
Perfect accessibility isn't realistic. WCAG 2.2 Level AA is realistic. Some advanced widgets only make it to Level A, and that's okay. Progress beats perfection.
Reflecting on what compliance is really about
After 17 years of building sites, the accessibility projects that paid off were never the ones driven by fear of a lawsuit. They were the ones where the team treated accessibility like quality.
A site that's keyboard-navigable, fast, contrast-correct, and labeled is a site that's been built carefully. A site that fails accessibility tests usually fails performance tests, mobile tests, and SEO audits at the same rate. The accessibility audit is a stand-in for the question "did anyone actually look at this with a critical eye."
I've watched teams ship a perfect-looking redesign that scored 47 on Lighthouse accessibility. I've also watched teams ship a quiet little site that scored 98 because they cared. The second team almost always had better conversion, better organic traffic, and lower support tickets. Accessibility wasn't the cause. It was a tell.
If you take one thing from this article, take this: don't run an accessibility project. Run a quality project, and let the accessibility score be a side effect.
FAQ
Is accessibility a legal requirement in the US?
Yes, under the ADA. US courts have read it to require WCAG-level "reasonable" accessibility for public-facing websites. Per the Seyfarth Title III Report, thousands of website lawsuits land in federal court each year. Even if you haven't been targeted, the exposure is real.
What's the difference between ADA and WCAG?
ADA is the law. WCAG is the standard that defines what "accessible" looks like. Courts use WCAG 2.1 or 2.2 Level AA as the practical baseline.
Do I need WCAG AAA?
No. AA is the industry standard and enough for ADA exposure on most commercial sites. AAA is for specialized contexts (government, education, certain healthcare).
How much does accessibility cost?
Audit and fix on an existing site: $5K to $15K, 4 to 8 weeks. Building accessible from day one: a 10 to 15% premium on development. Annual maintenance: 5 to 10% of the original remediation cost.
What's the single highest-impact fix?
Alt text. It's the most common missing element (30 to 50% of sites) and it directly affects the largest assistive-tech population. Fix alt text and you've handled roughly a third of all accessibility issues.
Do I have to caption every video?
Ideally yes. Practically, prioritize the videos on the homepage, landing pages, and core product pages. The more you caption, the better the experience and the better the SEO — captions get indexed.
Next steps
The takeaway in one paragraph: accessibility means everyone can use the site. WCAG 2.2 Level AA is the line. Existing sites need a $5K to $15K audit-and-fix pass. New sites are 10 to 15% more expensive to build right and 3 to 5x cheaper to maintain. Skip overlays. Start with alt text, contrast, keyboard, and labels.
Get a quote in 60s. I'll review your site, point at the accessibility issues that matter most, estimate remediation cost, and explain your real legal exposure. Honest feedback, not a sales pitch.
Related reading:
- Websites — fixed-price builds from $2,999, 14-day money-back guarantee, 1-year bug warranty
- Applications — monthly subscription from $4,999/mo
- LAK Embalagens case study — B2B manufacturer site, 45% bounce rate cut, 3x impressions
- Imohub case study — 120k+ properties, Top 3 Google rankings
- Website redesign services
- Mobile-friendly website design