AI Summary
Web accessibility isn't just about compliance—it's about reaching 26% of adults who have a disability and creating better experiences for everyone. This guide covers the legal landscape (ADA, Section 508, WCAG), practical implementation techniques, testing strategies, and common fixes for the most frequent accessibility issues. You'll learn how to audit your current site, prioritize fixes, and build accessibility into your development process.
Why Web Accessibility Matters
One in four American adults—about 61 million people—lives with a disability. Many of these individuals rely on websites for essential services, shopping, and information. When your website isn't accessible, you're excluding a significant portion of your potential customers.
The Business Case for Accessibility:
- • Market reach: People with disabilities have $490 billion in disposable income in the US
- • Legal protection: ADA lawsuits increased 320% from 2017 to 2023
- • SEO benefits: Accessible sites often rank higher (semantic HTML, alt text, clear structure)
- • Better UX for everyone: Accessibility improvements benefit all users
- • Brand reputation: Demonstrates commitment to inclusivity
Beyond business benefits, accessibility is simply the right thing to do. The web was designed to be universal—accessible to everyone regardless of ability. When we build inaccessible sites, we break that promise.
Understanding the Legal Landscape
Web accessibility law can seem confusing, but the key requirements are straightforward. Here's what you need to know:
Americans with Disabilities Act (ADA)
Title III of the ADA prohibits discrimination in "places of public accommodation." Courts have increasingly ruled that websites are places of public accommodation, especially for businesses with physical locations. In 2022, the Department of Justice issued guidance confirming that the ADA applies to websites.
Lawsuit Risk:
ADA website lawsuits have exploded in recent years. In 2023, there were over 4,600 web accessibility lawsuits filed in federal and state courts. Settlements typically range from $10,000 to $100,000, plus attorney fees and required remediation. Small businesses are increasingly targeted.
Section 508
Section 508 of the Rehabilitation Act applies to federal agencies and any organization receiving federal funding. It explicitly requires compliance with WCAG 2.0 Level AA. If you're a government contractor or receive federal grants, Section 508 compliance is mandatory.
WCAG: The Technical Standard
The Web Content Accessibility Guidelines (WCAG) are the internationally recognized standard for web accessibility. While not a law itself, WCAG is referenced by most accessibility legislation worldwide and used by courts as the benchmark for compliance.
WCAG Conformance Levels:
- Level A (Minimum): Basic accessibility requirements. Without these, some users cannot access your content at all.
- Level AA (Standard): The target level for most organizations. Addresses the most common barriers for users with disabilities.
- Level AAA (Enhanced): Highest level of accessibility. Not always achievable for all content, but good to aim for where possible.
The Four WCAG Principles (POUR)
WCAG is organized around four fundamental principles. All 50+ success criteria fall under these principles:
1. Perceivable
Information must be presented in ways users can perceive. This includes text alternatives for images, captions for videos, and sufficient color contrast.
2. Operable
Interface components must be operable by all users. This means keyboard accessibility, sufficient time to read content, and no content that causes seizures.
3. Understandable
Information and operation must be understandable. This includes readable text, predictable navigation, and help for users who make mistakes.
4. Robust
Content must be robust enough to work with current and future technologies, including assistive technologies like screen readers.
Most Common Accessibility Issues (And How to Fix Them)
The WebAIM Million study reveals that most accessibility issues are relatively easy to fix. Here are the top problems and their solutions:
1. Low Color Contrast (83% of websites)
Text must have sufficient contrast against its background for users with low vision or color blindness to read it.
WCAG Contrast Requirements:
- • Normal text: 4.5:1 minimum contrast ratio
- • Large text (18px+ bold or 24px+ regular): 3:1 minimum
- • UI components and graphics: 3:1 minimum
Tool Recommendation:
Use the WebAIM Contrast Checker (webaim.org/resources/contrastchecker) to test your color combinations. Input your text and background colors to instantly see if they pass WCAG requirements.
2. Missing Image Alt Text (55% of websites)
Screen readers read alt text to describe images to blind users. Without it, images are invisible to these users.
Alt Text Best Practices:
- • Informative images: Describe the content and function concisely
- • Decorative images: Use empty alt (alt="") to hide from screen readers
- • Functional images (buttons/links): Describe the action, not the image
- • Complex images: Provide long descriptions nearby or via a link
- • Don't say "image of" or "picture of": Screen readers already announce it's an image
Alt Text Examples:
<!-- Informative image --> <img src="team-photo.jpg" alt="The Verlua team at our Denver office"> <!-- Decorative image --> <img src="decorative-divider.svg" alt=""> <!-- Functional image (logo that links home) --> <a href="/"><img src="logo.svg" alt="Verlua home"></a> <!-- Image with text --> <img src="sale-banner.jpg" alt="50% off all services through January">
3. Empty Links and Buttons (50% of websites)
Links and buttons must have accessible names that describe their purpose. Icon-only buttons without labels are inaccessible to screen reader users.
Fixing Icon-Only Buttons:
<!-- Bad: No accessible name --> <button><svg>...</svg></button> <!-- Good: Screen reader text --> <button> <svg aria-hidden="true">...</svg> <span class="sr-only">Close menu</span> </button> <!-- Also good: aria-label --> <button aria-label="Close menu"> <svg aria-hidden="true">...</svg> </button>
4. Missing Form Labels (46% of websites)
Every form input must have an associated label that describes what information is expected. Placeholder text is not a substitute for labels.
Proper Form Labeling:
<!-- Bad: Placeholder-only --> <input type="email" placeholder="Email address"> <!-- Good: Explicit label --> <label for="email">Email address</label> <input type="email" id="email"> <!-- Also good: Wrapped label --> <label> Email address <input type="email"> </label> <!-- For visually hidden labels --> <label for="search" class="sr-only">Search</label> <input type="search" id="search" placeholder="Search...">
5. Keyboard Accessibility Issues
Everything that works with a mouse must also work with a keyboard. This is essential for users who cannot use a mouse due to motor disabilities, and it also helps screen reader users.
Keyboard Accessibility Checklist:
- ✓All interactive elements focusable with Tab key
- ✓Focus order matches visual reading order
- ✓Focus indicator clearly visible (don't remove outline)
- ✓No keyboard traps (can always tab away from any element)
- ✓Skip links to bypass navigation
- ✓Dropdown menus and modals keyboard accessible
Never Do This:
/* WRONG: Removes focus indicator */
*:focus { outline: none; }
/* RIGHT: Style the focus indicator */
*:focus {
outline: 2px solid #2563eb;
outline-offset: 2px;
}How to Test Your Website for Accessibility
Effective accessibility testing requires a combination of automated tools and manual testing. No single tool can catch all issues.
Automated Testing Tools
Recommended Tools:
axe DevTools (Browser Extension)
Industry-standard tool that integrates with browser DevTools. Catches common issues and provides clear remediation guidance.
WAVE (Browser Extension or Online)
Visual tool that highlights issues directly on your page. Great for quick visual scanning.
Lighthouse (Built into Chrome)
Includes accessibility audit as part of overall performance testing. Good for CI/CD integration.
Important Limitation:
Automated tools only catch 30-40% of accessibility issues. They're great for finding obvious problems (missing alt text, low contrast), but cannot verify things like whether alt text is meaningful, keyboard navigation is logical, or content is understandable.
Manual Testing Essentials
- 1.Keyboard-only navigation: Put your mouse aside and navigate your entire site using only Tab, Enter, Escape, and arrow keys. Can you access everything?
- 2.Screen reader testing: Test with NVDA (free for Windows), VoiceOver (built into Mac/iOS), or TalkBack (Android). Does the experience make sense?
- 3.Zoom testing: Zoom to 200% and ensure content remains readable and usable without horizontal scrolling.
- 4.Color dependency: View your site in grayscale. Is information still conveyed without color?
Building Accessibility Into Your Process
Retrofitting accessibility is expensive. Building it in from the start costs only 10-20% more and creates a better foundation for your website.
Accessibility-First Development:
- 1.Design phase: Check color contrast, plan for focus states, consider touch target sizes
- 2.Development: Use semantic HTML, test keyboard navigation as you build
- 3.Content: Write meaningful alt text, use clear headings, create captions
- 4.QA: Run automated tools, perform manual keyboard/screen reader testing
- 5.Ongoing: Include accessibility in code reviews, monitor for regressions
Making your site accessible also supports better conversion optimization—clearer navigation and better usability benefit all users, not just those with disabilities.
Frequently Asked Questions
Is my website legally required to be accessible?
In the United States, website accessibility requirements depend on your business type. Government websites and federally funded organizations must comply with Section 508. Private businesses are subject to Title III of the Americans with Disabilities Act (ADA), which courts have increasingly applied to websites. The Department of Justice issued guidance in 2022 confirming that websites must be accessible. While there's no single technical standard mandated by law, courts typically reference WCAG 2.1 Level AA as the benchmark for compliance.
What is WCAG and which version should I follow?
WCAG (Web Content Accessibility Guidelines) is the international standard for web accessibility, published by the W3C. The current recommended version is WCAG 2.2, released in October 2023. It has three conformance levels: Level A (minimum), Level AA (recommended target for most websites), and Level AAA (highest, but not always achievable). Most legal requirements and best practices target WCAG 2.1 or 2.2 Level AA, which includes 50 success criteria covering perceivability, operability, understandability, and robustness.
How much does it cost to make a website accessible?
Accessibility costs vary widely depending on your current site's state and complexity. For a typical small business website, an accessibility audit costs $1,000-$5,000, and remediation can range from $2,000-$25,000 depending on the number of issues. However, building accessibility into new projects from the start costs only 10-20% more than inaccessible development. The cost of non-compliance is often higher: ADA lawsuit settlements average $25,000-$75,000, plus legal fees and required remediation.
Can accessibility overlays make my site compliant?
Accessibility overlay widgets (like AccessiBe, UserWay, or AudioEye) are controversial and generally not recommended as a compliance solution. While they may help some users, they cannot fix fundamental accessibility issues in your code, can interfere with users' existing assistive technology, and have been specifically criticized by disability advocacy groups. Over 700 accessibility professionals signed a statement against overlays. Courts have ruled against companies using overlays as their only accessibility measure. Use overlays only as a temporary band-aid while implementing proper fixes.
What are the most common accessibility issues on websites?
The WebAIM Million study analyzes the top 1 million websites annually. The most common issues are: low contrast text (83% of pages), missing alt text on images (55%), empty links (50%), missing form labels (46%), missing document language (46%), and empty buttons (27%). The good news: these are all relatively easy to fix. Addressing just these six issues would resolve the majority of detected accessibility problems.
How do screen reader users navigate websites?
Screen reader users navigate primarily using keyboard controls and semantic HTML structure. They use headings (H1-H6) to scan page structure, skip links to bypass navigation, landmark regions (header, main, nav, footer) to jump between sections, tab key to move between interactive elements, and ARIA labels when native semantics are insufficient. This is why semantic HTML, proper heading hierarchy, and keyboard accessibility are fundamental to accessible design.
Do I need to provide alternatives for videos?
Yes, WCAG requires alternatives for video content. At Level A, you need captions for pre-recorded video with audio. At Level AA, you also need captions for live video and audio descriptions for pre-recorded video where needed. Captions should be accurate, synchronized, and include relevant non-speech audio (like [door slams]). Auto-generated captions are a starting point but require human review for accuracy. Audio descriptions narrate important visual information for blind users.
How do I test my website for accessibility?
Use a combination of automated and manual testing. For automated testing, use tools like axe DevTools, WAVE, or Lighthouse to catch obvious issues (they find about 30-40% of problems). For manual testing, navigate your entire site using only a keyboard, test with a screen reader (NVDA is free for Windows, VoiceOver is built into Mac/iOS), and check color contrast with tools like the WebAIM Contrast Checker. For comprehensive testing, consider user testing with people who have disabilities.
Your Accessibility Action Plan
Week 1: Audit
- □Run axe DevTools on your top 5 pages
- □Test keyboard navigation on your homepage and key conversion pages
- □Check color contrast on all text
- □Document all issues found
Week 2-3: Quick Fixes
- □Add missing alt text to all images
- □Fix color contrast issues
- □Add labels to all form fields
- □Add accessible names to icon buttons
Month 2: Structural Fixes
- □Ensure proper heading hierarchy (H1 → H2 → H3)
- □Add skip navigation links
- □Fix keyboard navigation issues
- □Add ARIA landmarks where needed
Need Help With Accessibility Compliance?
At Verlua, we build accessible websites from day one and help existing sites achieve WCAG 2.2 compliance. Our accessibility audits identify issues, prioritize fixes, and provide actionable remediation plans.
Get an Accessibility AuditStay Updated
Get the latest insights on web development, AI, and digital strategy delivered to your inbox.
No spam, unsubscribe anytime. We respect your privacy.
Comments
Comments section coming soon. Have questions? Contact us directly!
Related Articles
Website Conversion Optimization for Local Services
Practical CRO strategies to convert more visitors to phone calls and form submissions.
Read MoreLanding Page Design: 15 High-Converting Examples
Discover 15 high-converting landing page examples with detailed breakdowns.
Read MoreWhy Most Local Business Websites Fail
67% of local business websites fail to generate leads. Discover the 10 most common failures.
Read More