Website Accessibility Basics: ADA Compliance and Inclusive Design
Over one billion people worldwide live with some form of disability. If your website isn't accessible, you're excluding potential customers and potentially exposing your business to legal risk. Here's what every small business owner should know about web accessibility.
What Is Web Accessibility?
Web accessibility means designing and building websites so that people with disabilities can perceive, understand, navigate, and interact with them. This includes people who are blind, deaf, have motor impairments, cognitive disabilities, or temporary limitations like a broken arm.
Accessible websites aren't just for people with permanent disabilities. They also benefit:
- Older adults with declining vision or motor skills
- Mobile users navigating in bright sunlight or one-handed
- People with slow internet who need lightweight, well-structured pages
- Search engines: accessible code is inherently more machine-readable
ADA and Legal Requirements
The Americans with Disabilities Act (ADA) prohibits discrimination against individuals with disabilities in all areas of public life. While the ADA was written before the internet era, courts have increasingly interpreted it to apply to websites, especially for businesses that serve the public.
Key Legal Points
- ADA Title III applies to "places of public accommodation," and courts have extended this to websites
- Thousands of ADA website lawsuits are filed each year, primarily targeting e-commerce and service businesses
- The DOJ has referenced WCAG 2.1 AA as the standard for web accessibility compliance
- Having an accessibility statement on your website demonstrates good faith effort
Understanding WCAG Standards
The Web Content Accessibility Guidelines (WCAG) are the international standard for web accessibility. They're organized around four principles, known by the acronym POUR:
The POUR Principles
- Perceivable: Information must be presentable in ways all users can perceive (alt text for images, captions for videos)
- Operable: Interface components must be navigable via keyboard, not just mouse
- Understandable: Content and navigation must be clear and predictable
- Robust: Content must work across different browsers and assistive technologies
WCAG has three conformance levels: A (minimum), AA (recommended), and AAA (highest). Most legal standards and best practices target WCAG 2.1 Level AA.
Common Accessibility Issues (and How to Fix Them)
Many accessibility problems are straightforward to fix once you know what to look for. Here are the most frequent issues found on small business websites:
1. Missing Alt Text on Images
Screen readers rely on alt text to describe images to blind users. Every meaningful image needs descriptive alt text. Decorative images should have empty alt attributes (alt="") so screen readers skip them.
- Good:
alt="Team meeting in our Fort Lauderdale office" - Bad:
alt="image1.jpg"or missing entirely
2. Poor Color Contrast
Text must have sufficient contrast against its background. WCAG AA requires a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text. Light gray text on white backgrounds is a common offender.
3. No Keyboard Navigation
Many users navigate websites entirely with a keyboard. All interactive elements (links, buttons, form fields, menus) must be reachable and operable via Tab, Enter, and arrow keys. Custom dropdown menus and modal windows are frequent problem areas.
4. Missing Form Labels
Every form input needs a properly associated <label> element. Placeholder text alone is not sufficient. It disappears when users start typing and isn't reliably read by screen readers.
5. Auto-Playing Media
Videos or audio that play automatically can be disorienting for screen reader users and people with cognitive disabilities. Always let users initiate media playback and provide controls to pause, stop, and adjust volume.
6. Missing Heading Structure
Screen reader users navigate pages by heading hierarchy (H1, H2, H3). Pages should have a single H1 and use headings in logical order. Never skip from H2 to H4 for styling purposes.
Quick Accessibility Audit Checklist
You don't need to be a developer to catch common issues. Run through this checklist on your own site:
DIY Accessibility Check
- Tab through your site: Can you reach every link, button, and form field using only the keyboard? Can you see where the focus is?
- Zoom to 200%: Does everything remain readable and functional?
- Check images: Right-click images and inspect for alt text
- Test contrast: Use a free tool like WebAIM's Contrast Checker
- Try a screen reader: VoiceOver (Mac) or NVDA (Windows) are free
- Run an automated scan: WAVE, axe DevTools, or Lighthouse accessibility audit
Accessibility and SEO: The Overlap
Good accessibility practices directly benefit search engine optimization:
- Alt text helps Google understand image content
- Heading structure helps search engines parse page hierarchy
- Descriptive link text ("View our services" vs "Click here") improves both usability and crawlability
- Fast load times and mobile responsiveness are ranking factors and accessibility requirements
Accessibility Overlays: Do They Work?
You may have seen website plugins that add an accessibility widget (a floating button with font size and contrast controls). While well-intentioned, these overlays have significant limitations:
- They don't fix underlying code issues. They apply surface-level patches
- Many disability advocacy organizations actively oppose overlay products
- Courts have not accepted overlays as proof of ADA compliance
- Some overlays actually interfere with assistive technology users
The reliable path to accessibility is building it into your website's code, content, and design, not bolting on an aftermarket tool.
Building Accessibility Into Your Process
The most cost-effective approach is incorporating accessibility from the start of a web design project:
- Design phase: Choose accessible color palettes, readable fonts, and clear layouts
- Development phase: Use semantic HTML, ARIA labels, and keyboard-friendly components
- Content phase: Write descriptive alt text, use plain language, structure content with headings
- Testing phase: Run automated scans plus manual keyboard and screen reader testing
- Ongoing: Check accessibility when adding new content or features
Key Takeaways
- Web accessibility is both a legal requirement and a business advantage
- WCAG 2.1 AA is the widely accepted standard. Aim for that level
- Most common issues (alt text, contrast, keyboard nav) are straightforward to fix
- Overlays are not a substitute for proper accessible design and development
- Building accessibility in from the start costs far less than retrofitting later
- Accessible websites perform better in search, work better on mobile, and serve more customers
Need an accessible website?
I build websites with accessibility baked in from day one, not patched on after the fact.
Start Your Project