Accessibility Isn't a Checkbox. It's a Design Standard.
Most conversations about web accessibility start with compliance — avoiding lawsuits, meeting government requirements, hitting WCAG targets. Those are legitimate reasons to care. But they're not the most compelling ones.
The most compelling reason is simpler: 61 million Americans live with a disability. Nearly 1 in 4 adults. And the vast majority of websites remain functionally unusable for a significant portion of that group — not because of malice, but because accessibility gets treated as an add-on rather than a design principle.
When you design for accessibility from the start, you don't just serve users with disabilities better. You build a cleaner, faster, more usable experience for everyone. The constraints of accessible design — clear hierarchy, sufficient contrast, logical navigation, descriptive labels — are constraints that produce better design in general.
This article is a practical overview of where most sites fail, what the standards actually require, and why getting this right is one of the highest-ROI design investments a brand can make.
Where Most Websites Are Failing
The WebAIM Million report — an annual audit of the top one million websites — makes for uncomfortable reading. The numbers have barely moved in years:
- 95.9% of home pages contain detectable WCAG failures
- The average page has 56.8 accessibility errors — up 13.6% year over year
- 81% of pages have low-contrast text, with an average of 34.5 instances per page
- 21.6% of images lack alternative text
- 35.5% of form inputs have no proper labels
- 37.9% of pages skip heading levels, breaking screen reader navigation
Those aren't edge-case failures. They're the basics. And the fact that they persist at this scale suggests the problem isn't awareness — it's that accessibility never makes it onto the design brief in the first place.
Government sites, interestingly, now outperform commercial sites significantly — 37.2% fewer errors on average. The reason is simple: they're legally required to comply and are held accountable for it. Commercial brands mostly aren't, until they get sued.
The Legal Exposure Is Real and Growing
ADA Title III has been applied to websites with increasing frequency. The legal and financial exposure is not theoretical:
- First ADA web violations can cost up to $75,000, with repeat violations reaching $150,000
- Over 8,000 web accessibility lawsuits are filed annually in the US
- 40% of cases are concentrated in New York and California, but no state is immune
- Notably, 77% of ADA lawsuits target small businesses — not just enterprise brands
- 25% of lawsuits specifically cite accessibility overlay tools as harmful, not compliant
That last point matters. A growing number of brands have installed overlay plugins — JavaScript widgets that claim to make a site accessible — as a quick fix. Courts and accessibility auditors are increasingly finding these tools inadequate and, in some cases, actively harmful to screen reader users. They are not a substitute for properly built accessible experiences.
The Department of Justice has been explicit: web accessibility is covered under the ADA. Enforcement isn't a question of if — it's when.
What WCAG Actually Requires
The Web Content Accessibility Guidelines (WCAG) are organized around four principles: content must be Perceivable, Operable, Understandable, and Robust (POUR). Within those principles, there are three levels of compliance:
WCAG A — Minimum requirements. A floor, not a target.
WCAG AA — The industry standard. This is what most legal frameworks reference, what enterprise clients expect, and what the majority of brands should be building to. It covers color contrast ratios, keyboard navigation, screen reader compatibility, error identification in forms, and more.
WCAG AAA — The highest level, requiring features like sign language interpretation, enhanced contrast, and live captions. Not required for most contexts, but the benchmark for brands committed to full inclusion.
For the vast majority of commercial websites, WCAG AA is the right target. It's achievable, it satisfies legal requirements in most jurisdictions, and it meaningfully improves the experience for users with disabilities without requiring a complete architectural overhaul.
The Five Most Common Failures — and How to Fix Them
1. Color Contrast and Text Readability
This is the most widespread failure — and one of the easiest to fix. WCAG AA requires a minimum contrast ratio of 4.5:1 for normal text and 3:1 for large text. Light gray on white, pale yellow on white, or low-saturation color combinations on similar backgrounds routinely fail.
Tools like the WebAIM Contrast Checker or Figma's built-in accessibility plugins make it straightforward to verify contrast ratios during design. The fix is almost always a shade adjustment — not a rebrand.
2. Keyboard Navigation
Every interactive element on your site — buttons, menus, dropdowns, modals, forms — must be reachable and operable via keyboard alone. This matters for users with motor disabilities and for anyone using assistive technology.
The test is simple: unplug your mouse and try to use your own site. If you get stuck, so will your users. Tab order should be logical, focus states should be visible, and keyboard traps (where Tab gets stuck in a component with no exit) must be eliminated.
3. Image Alternative Text
Alt text is not a SEO tactic — it's a functional requirement. Screen readers read alt text aloud to users who cannot see images. Missing or poor alt text (“image1.jpg” or “photo”) provides no meaningful information.
Good alt text describes the purpose of the image in context: “Bar chart showing 40% increase in conversion rate after redesign” is useful. “Chart” is not. Decorative images that carry no informational value should have empty alt attributes (alt="") so screen readers skip them.
4. Form Labels and Error Handling
Forms are where many sites fail worst for users with assistive technology. Every input field must have a programmatically associated label — not just a placeholder that disappears when the user starts typing. Error messages must clearly identify which field failed and why, in plain language.
This is a development issue as much as a design issue. Placeholder-only forms are visually clean but functionally broken for screen reader users.
5. Heading Structure and Document Hierarchy
Headings aren't just visual hierarchy — they're navigational landmarks for screen reader users. A screen reader user can jump between H2s to scan a page, much like a sighted user skims subheadings. Skipping levels (jumping from H1 to H4, using headings for visual styling rather than structure) breaks that navigation entirely.
The rule is simple: use headings to convey structure, not appearance. If you want large bold text that isn't a section heading, use CSS styling — not an H2.
Where AI Is Changing Accessibility Practice
The tooling around accessibility has improved significantly with AI, and it's worth understanding where it genuinely helps versus where it falls short.
Automated auditing at scale. AI-powered accessibility scanners (Deque's axe, Siteimprove, and others) can now crawl entire sites and flag WCAG violations faster and more comprehensively than manual review alone. These tools catch the detectable failures — missing alt text, contrast ratios, unlabeled form fields — across hundreds of pages in minutes. They're a first pass, not a complete audit, but they've dramatically lowered the cost of identifying issues.
AI-generated alt text. Several tools now use computer vision to automatically generate descriptive alt text for images. The quality has improved to the point where AI-generated descriptions are often a better starting point than a developer's blank field. They still require human review for context-sensitive or complex images, but they eliminate the most egregious failures at volume.
Natural language accessibility checking. Large language models can now review content for plain language compliance — flagging jargon, overly complex sentence structures, or content that would be difficult for users with cognitive disabilities to parse. This is a capability that was previously entirely manual.
The limits of AI. Automated tools still cannot catch everything. WCAG requires judgment calls — whether a description is actually meaningful, whether navigation is genuinely logical, whether a design decision creates cognitive overload. Those assessments require human testers, ideally including users with disabilities. AI is a powerful accelerant for the mechanical work of accessibility; it's not a replacement for human evaluation.
The best accessibility programs today combine automated scanning, AI-assisted remediation, and regular human testing. The cost of that combination has dropped significantly — which means there's less and less justification for treating accessibility as too expensive to prioritize.
The Business Case Is Stronger Than Most Brands Realize
Beyond legal compliance, the business ROI of accessible design is direct and measurable:
Revenue from an underserved market. People with disabilities in the US have an estimated $548 billion in discretionary spending power. Brands whose sites work for them capture that revenue. Brands whose sites don't, lose it — often permanently. Research shows 62% of users with disabilities will switch to a competitor if they encounter access barriers.
SEO performance. Accessible HTML is clean, well-structured HTML. Proper heading hierarchy, descriptive alt text, fast-loading pages, and logical document structure all contribute directly to crawlability and search performance. Accessibility and SEO share a significant overlap in best practices.
Reduced support costs. Sites with clear labels, logical navigation, and descriptive error messages require less customer support. Users can complete tasks independently. That reduces inbound support volume and customer frustration simultaneously.
Broader reach, not narrower. Captions help users watching video without sound in a public space. High-contrast text is easier to read in bright sunlight on a phone. Large tap targets help users with motor control issues — and also anyone using a phone one-handed. Accessibility improvements benefit the full user population, not just those with formal disabilities.
What Good Looks Like: Brands Setting the Standard
Apple has made accessibility a core product value rather than an afterthought. VoiceOver, their screen reader, works across every device and app they ship — and has for years. The BBC publishes detailed accessibility guidelines and runs regular audits. Microsoft's Inclusive Design framework has influenced product development industry-wide and produced practical toolkits freely available to any design team.
These aren't small businesses with limited resources. But they've demonstrated that accessibility at scale is achievable when it's treated as a design requirement from the start, not a retrofit at the end.
Where to Start
If your site hasn't had an accessibility audit, that's the first step. Run it through an automated scanner — axe DevTools, Lighthouse, or WAVE — to get a baseline of current failures. The output will likely be humbling. It's also actionable.
Prioritize by impact: contrast failures and missing alt text affect the most users and are the fastest to fix. Form labeling and keyboard navigation require more development effort but are critical for any site with conversions as a goal.
For new builds and redesigns, the most cost-effective approach is designing accessibly from the start. Retrofitting accessibility onto an inaccessible design is significantly more expensive than building with accessibility requirements in the brief.
How Fahrenheit Approaches Accessibility
At Fahrenheit, accessibility is built into our design and development process — not bolted on at the end. We audit for WCAG AA compliance, design with inclusive principles, and work with development teams to ensure that what's designed stays accessible through implementation.
For brands carrying existing accessibility debt, we help prioritize remediation based on legal exposure, user impact, and implementation cost — turning a compliance problem into a measurable improvement in user experience and search performance.
Accessibility done well isn't a constraint on creative work. It's a quality standard that makes every design decision more intentional.