Website accessibility means people with disabilities can perceive, understand, navigate and use your site. For US businesses, the practical benchmark is the W3C’s Web Content Accessibility Guidelines (WCAG), ideally version 2.2 at Level AA. The ADA applies to businesses open to the public, but no federal rule yet sets a technical web standard for private companies, so audit, fix, and get counsel’s view.
This guide explains what WCAG 2.2 actually asks for, what federal rules and guidance say today, and a practical sequence for getting an existing website into good shape without wasting budget on shortcuts that don’t work.
Why accessibility is a business issue, not just a compliance box
Accessibility is often framed purely as legal risk. That framing undersells it. The CDC reports that more than 1 in 4 US adults have some type of disability, with cognition, mobility, hearing and vision disabilities among the most common. Those people are customers, patients, students, applicants and employees. If they can’t complete a form, read your pricing or check out, you lose the transaction regardless of whether anyone ever files a complaint.
Accessibility work also overlaps heavily with things you already care about:
- Usability. Clear labels, predictable navigation, readable contrast and forgiving forms help every visitor, including people on small screens or in bright sunlight.
- Search and discoverability. Descriptive headings, meaningful link text and text alternatives for images give search engines and AI systems cleaner signals about what a page contains.
- Code quality. Sites built with semantic HTML and well-structured components tend to be easier to maintain, test and extend.
The scale of the gap is significant. WebAIM’s 2026 analysis of the top one million home pages found that 95.9% had detected WCAG 2 failures, averaging 56.1 errors per page — and WebAIM stresses that automated checks catch only part of the picture. In other words, most websites have work to do, and the most common problems are fixable.
What WCAG is and how it is structured
WCAG is published by the World Wide Web Consortium (W3C) through its Web Accessibility Initiative. According to the W3C, the guidelines are organized around four principles — perceivable, operable, understandable and robust — often shortened to POUR. Under those principles sit testable “success criteria,” each assigned a conformance level.
| Level | What it represents | How it is typically used |
|---|---|---|
| A | The most basic requirements; failing them blocks some users entirely | The minimum floor, never a target on its own |
| AA | Level A plus criteria that remove the most common significant barriers | The level referenced by most regulations and procurement policies, and the usual business target |
| AAA | The most demanding criteria, not achievable for all content | Applied selectively where it makes sense, not as a site-wide requirement |
Three versions of WCAG 2 are current standards. The W3C states that WCAG 2.2 does not deprecate WCAG 2.1, and content that meets WCAG 2.2 also meets 2.1 and 2.0. The W3C encourages organizations to use the latest version. WCAG 2.2 is also an approved international standard, published as ISO/IEC 40500:2025.
What changed in WCAG 2.2
WCAG 2.2 became a W3C Recommendation on 5 October 2023, with an update published in December 2024. It adds nine success criteria to WCAG 2.1 and removes one (4.1.1 Parsing, which the W3C considered obsolete). Six of the nine new criteria apply at Level A or AA, which is where most businesses should focus:
| New criterion | Level | What it means in practice |
|---|---|---|
| 2.4.11 Focus Not Obscured (Minimum) | AA | When a keyboard user tabs to an element, it must not be completely hidden by sticky headers, cookie banners or chat widgets. |
| 2.5.7 Dragging Movements | AA | Anything done by dragging (sliders, reorderable lists, maps) also needs a single-pointer alternative, such as buttons or taps. |
| 2.5.8 Target Size (Minimum) | AA | Clickable targets should be at least 24 by 24 CSS pixels, with exceptions such as adequate spacing or links inside sentences. |
| 3.2.6 Consistent Help | A | If you offer help (contact details, chat, FAQ link) across multiple pages, keep it in the same relative place. |
| 3.3.7 Redundant Entry | A | Don’t make users re-type information they already entered in the same process; auto-fill it or let them select it. |
| 3.3.8 Accessible Authentication (Minimum) | AA | Logins must not rely solely on memory or puzzles; for example, allow password managers and pasting. |
The remaining three — Focus Not Obscured (Enhanced), Focus Appearance and Accessible Authentication (Enhanced) — are Level AAA.
Two of these deserve special attention in audits. Accessible authentication is frequently broken by login forms that block pasting or disable autofill, which the W3C’s guidance on Success Criterion 3.3.8 explicitly addresses. Focus not obscured is often broken by the sticky elements marketing teams add over time: a fixed header, a promotional bar and a chat launcher can together hide the element a keyboard user is trying to reach.
What US law and federal rules say today
This section summarizes published rules and guidance. It is not legal advice, and the right answer for your organization depends on your facts, industry and jurisdiction. Treat it as background for a conversation with qualified counsel.
Private businesses: ADA Title III
Title III of the Americans with Disabilities Act covers businesses open to the public. In its 2022 web guidance, the Department of Justice states that it has consistently taken the position that the ADA’s requirements apply to all the goods, services, privileges or activities offered by public accommodations, including those offered on the web. The same guidance says businesses can currently choose how they ensure their online offerings are accessible, and points to WCAG and the Section 508 Standards as existing technical standards that provide helpful guidance.
Put simply: there is no DOJ regulation that sets a specific WCAG version for private businesses’ websites, but the DOJ’s stated position is that the ADA’s obligations reach online services, and WCAG is the reference point it names. The guidance lists common barriers — poor color contrast, relying on color alone, missing alt text, missing video captions, inaccessible forms and mouse-only navigation.
State and local governments: ADA Title II
In April 2024, the DOJ published a rule requiring state and local governments’ web content and mobile apps to meet WCAG 2.1 Level AA, with specific exceptions (for example, certain archived content and preexisting documents). On April 20, 2026, the DOJ published an interim final rule extending the compliance dates: April 26, 2027 for entities with a total population of 50,000 or more, and April 26, 2028 for smaller entities and special district governments.
This matters to private companies too. The DOJ’s summary notes the rule reaches web content provided by contractors on a public entity’s behalf, so if you sell software, portals or content services to government customers, expect accessibility requirements to appear in contracts and procurement.
Recipients of HHS funding: Section 504
The Department of Health and Human Services has a parallel rule for organizations receiving HHS financial assistance, such as hospitals and health centers, also using WCAG 2.1 AA. In May 2026, HHS announced an interim final rule extending its deadlines to May 11, 2027 for recipients with 15 or more employees and May 10, 2028 for those with fewer than 15. Healthcare organizations should confirm with counsel how this applies to them.
Federal agencies: Section 508
Section 508 applies to federal agencies when they develop, procure, maintain or use information and communication technology. The Revised 508 Standards align with WCAG 2.0. Vendors selling to federal agencies are commonly asked to document the accessibility of their products.
A note on deadlines and state law
Rules and deadlines have changed more than once in the past two years, and some states have their own accessibility or civil rights laws. Because the regulatory picture keeps moving, we recommend confirming the current position with counsel before making commitments, and building to WCAG 2.2 AA so you are not re-working the site each time a rule references a newer version.
Why overlays and “one-line fixes” are not a strategy
Accessibility overlay widgets promise compliance by adding a script to your site. The evidence does not support relying on them. In April 2025, the Federal Trade Commission finalized an order requiring accessiBe to pay $1 million after alleging that its claims that its AI-powered tool could make any website WCAG-compliant were false, misleading or unsubstantiated. The order bars the company from claiming automated products ensure WCAG compliance without substantiation.
The underlying reason is structural. The W3C states plainly that no tool alone can determine if a site meets accessibility standards; knowledgeable human evaluation is required. A script injected after the page loads can’t reliably know what an image means, whether a form’s error messages make sense or whether a custom component behaves correctly with a screen reader. Those fixes belong in your templates, components and content.
The most common problems and how to fix them
WebAIM’s 2026 data shows the same handful of issues dominating year after year. Fixing them at the template and component level removes a large share of barriers quickly.
| Issue (share of home pages, WebAIM 2026) | What goes wrong | Typical fix |
|---|---|---|
| Low-contrast text (83.9%) | Text is hard or impossible to read for people with low vision | Adjust brand color tokens so text meets WCAG contrast ratios; check text over images |
| Missing image alt text (53.1%) | Screen reader users miss meaning, or hear file names | Write concise alt text for meaningful images; mark decorative ones as decorative |
| Missing form labels (51%) | Fields are announced without a name, so users can’t tell what to enter | Use visible, programmatically associated labels, not placeholder text alone |
| Empty links (46.3%) | Icon links announce nothing useful | Add accessible names to icon links and remove duplicate empty links |
| Empty buttons (30.6%) | Buttons such as menu toggles or search have no name | Give every button a text or accessible name |
| Missing document language (13.5%) | Assistive technology may mispronounce content | Set the page language attribute in the base template |
Figures are from the WebAIM Million 2026 report. Beyond these, audits of business sites commonly surface keyboard traps in menus and modals, missing captions on video, PDFs without structure and custom dropdowns that don’t work with assistive technology.
Work with GeekOzy
Build a website that works as hard as you do.
Tell us what you're working on. We'll come back with honest thinking on a practical next step.
Start a projectExplore Web & Digital ExperienceHow to audit your website properly
A credible audit combines tools with human judgment. We recommend three layers:
- Automated scanning across the site. Run a crawler-based checker to find repeated, machine-detectable issues such as contrast, missing labels and missing alt attributes. Use it for breadth, not as a verdict.
- Manual expert testing of key journeys. Test the paths that matter most — homepage, navigation, search, product or service pages, forms, checkout, login and account areas — with a keyboard only, with a screen reader, at 200% and 400% zoom, and on mobile.
- Testing with people with disabilities. The W3C recommends involving users with disabilities in evaluation because they reveal real-world problems that checklists miss.
Scope the audit around a representative sample of templates rather than every URL. On most sites, twenty or thirty templates and components generate the majority of pages, so fixing a template fixes hundreds of pages at once.
A practical remediation plan
Once you have findings, sequence the work by user impact and effort, not by the order issues appear in a report.
Phase 1: Remove blockers on critical journeys
Start with anything that stops someone completing a task: forms that can’t be submitted by keyboard, checkout steps a screen reader can’t operate, logins that block password managers, modals that trap focus. These carry the highest human and business cost.
Phase 2: Fix the design system and templates
Correct color tokens, focus styles, button and link components, form patterns and navigation once, in the shared code. This is where WCAG 2.2 criteria such as target size and focus not obscured are usually addressed.
Phase 3: Clean up content
Alt text, heading structure, link text, captions and document accessibility are content tasks. Give editors short guidelines and a checklist, and prioritize high-traffic and high-value pages and documents.
Phase 4: Prevent regressions
Add automated accessibility checks to your development pipeline, include accessibility in design reviews and acceptance criteria, and re-test key journeys on a regular cycle. If you’re planning a rebuild, bake these standards in from the start — our guide to a website redesign without losing rankings covers how to plan a relaunch safely.
Documentation: accessibility statements and conformance reports
Two documents help demonstrate good faith and answer customer questions:
- An accessibility statement on your website explaining your target standard, known limitations, how people can report problems or request information in another format, and how quickly you respond. Only state what is true today.
- An Accessibility Conformance Report (ACR), typically based on the Voluntary Product Accessibility Template (VPAT), if you sell software or digital services to government, education or enterprise buyers. It should reflect genuine testing, including partial support where that is the honest answer.
Avoid claiming full compliance or “ADA certification.” The DOJ’s web guidance describes no certification program for websites, and overstated claims can create their own problems, as the FTC’s action on accessibility marketing shows. Have counsel review public-facing statements.
Building accessibility into how you work
Organizations that sustain accessibility treat it as part of normal quality, not a one-off project. In practice that means:
- Ownership. A named person accountable for accessibility across design, development and content.
- Definition of done. New features and pages are not complete until they pass keyboard, screen reader and contrast checks.
- Procurement. Ask vendors of plugins, widgets, booking tools and payment components for evidence of accessibility, since third-party components often introduce barriers you can’t fix yourself.
- Training. Short, role-specific training for designers, developers and editors pays back quickly.
- A feedback channel. Make it easy for users to report issues, and route reports to someone who can act.
Accessibility also shapes the broader customer experience. Clearer forms, readable pages and predictable navigation reduce friction for everyone — which is why accessibility work often supports conversion rate optimization goals as well.
What about WCAG 3?
The W3C is developing WCAG 3, but describes it as an incomplete draft that will change and says it is not expected to be a completed standard for a few more years. The W3C’s own advice is that the best way to prepare for WCAG 3 is to meet WCAG 2.2 now. There is no reason to delay current work while waiting for it.
The bottom line
For most US businesses, the sensible target is WCAG 2.2 Level AA. Federal rules set explicit WCAG 2.1 AA requirements for government entities and HHS funding recipients, while the DOJ’s guidance for private businesses points to WCAG without mandating a version. Skip overlay shortcuts, audit with real human testing, fix templates and critical journeys first, and put processes in place so the site stays accessible. For your specific legal obligations, consult counsel.
If you’d like help auditing or rebuilding an accessible site, explore our Web & Digital Experience services or start a conversation with our team.
Sources
- CDC — Disability Impacts All of Us
- WebAIM — The WebAIM Million (2026)
- W3C WAI — WCAG 2 Overview
- W3C WAI — What’s New in WCAG 2.2
- W3C — Understanding SC 2.5.8 Target Size (Minimum)
- W3C — Understanding SC 3.3.8 Accessible Authentication (Minimum)
- U.S. Department of Justice — Guidance on Web Accessibility and the ADA
- U.S. Department of Justice — Fact Sheet: Title II Web and Mobile App Accessibility Rule
- Federal Register — Extension of Compliance Dates (Title II web rule), April 20, 2026
- HHS — OCR Extends Web and Mobile Accessibility Compliance Deadline
- Section508.gov — Laws and Policies
- FTC — FTC Approves Final Order Requiring accessiBe to Pay $1 Million
- W3C WAI — Evaluating Web Accessibility Overview
- W3C WAI — WCAG 3 Introduction



