Web accessibility (WCAG 2.2): the 2026 guide

Web accessibility is the quiet area of web development where most agencies worldwide have no real expertise, and where, increasingly, refusing to do the work is starting to cost businesses real money. Government tenders ask for it. US-facing B2B clients require it. EU regulations now mandate it. And about 1.3 billion people worldwidelive with some form of disability that affects how they use the web, most of them invisible to your analytics dashboard.

This is the practical guide for businesses worldwide in 2026: what web accessibility actually means, who is legally required to comply, what the standards look like, what it costs, and how to know your site is genuinely usable by everyone.

What “web accessibility” actually means

Web accessibility means designing and building websites that work for people with disabilities, visual, auditory, motor, cognitive, and for the technologies they use to navigate the web. That includes:

• Screen readers(NVDA, JAWS, VoiceOver, TalkBack), software that reads page content aloud for users who can't see the screen.
• Keyboard-only navigation: for users who can't use a mouse due to motor disabilities, RSI, or temporary injury.
• Magnification: for low-vision users.
• Voice control: Dragon, Siri, Alexa-driven web navigation.
• Cognitive aids: high-contrast modes, reading rulers, simplified views.

Importantly, accessibility benefits everyone, not just disabled users. The same practices that make a site screen-reader-friendly also make it work better on slow connections, on older devices, for non-native English speakers, for users in bright sunlight, and for anyone using a phone one-handed on a train.

WCAG 2.2, the global standard

The Web Content Accessibility Guidelines (WCAG), published by the World Wide Web Consortium (W3C), are the international standard. Version 2.2 was published in October 2023, it's the current target for most compliance work in 2026.

WCAG organises requirements around four principles (POUR):

• Perceivable: users must be able to perceive the content (visible to sight, audible to hearing, or readable by assistive tech). Alt text on images, transcripts for audio, captions on video, sufficient colour contrast.
• Operable: users must be able to operate the interface. Everything works with keyboard alone. No content flashes too fast to trigger seizures. Enough time to read and use content.
• Understandable: content and operation must be understandable. Clear language. Predictable behaviour. Helpful error messages.
• Robust: content must work across current and future user agents, including assistive technologies. Semantic HTML. ARIA where appropriate.

WCAG defines three conformance levels:

• Level A: minimum, basic accessibility. Required by virtually no legal regime; treat as the floor.
• Level AA: the standard target. Required by ADA (US), EAA (EU), most government procurement worldwide, India's RPwD Act, the UK Equality Act and the Ontario AODA in practice. This is the target for almost every business.
• Level AAA: highest level. Required only in specific exceptional contexts (some government services, healthcare-critical content). Not achievable for all content types, even the W3C doesn't recommend AAA as a site-wide goal.

Who legally needs to comply

Several overlapping legal regimes apply, depending on where your business operates and where your users live:

United States, Americans with Disabilities Act (ADA)

The ADA has been interpreted by US courts to apply to public-facing websites of businesses operating in commerce in the United States. Web accessibility lawsuits in the US are now a real industry: over 3,000 ADA web lawsuits are filed annually, including against non-US businesses with US customers. The standard the courts look at is WCAG 2.1 AA (and increasingly 2.2 AA).

European Union, European Accessibility Act (EAA)

The EAA, fully effective from June 2025, requires accessibility for e-commerce websites, banking services, transport booking, e-readers and other digital products serving EU consumers. Applies to non-EU businesses selling into the EU. Standard: EN 301 549, which references WCAG 2.1 AA (moving toward 2.2 AA).

United Kingdom, Equality Act 2010 + Public Sector Bodies Accessibility Regulations

The UK Equality Act requires “reasonable adjustments” for disabled users. Public sector and government-funded sites must conform to WCAG 2.1 AA under the 2018 regulations. Private businesses face increasing litigation risk under the Equality Act.

Canada, AODA (Ontario) + federal ACA

The Accessibility for Ontarians with Disabilities Act requires Ontario businesses with 50+ employees to meet WCAG 2.0 AA. The federal Accessible Canada Act (2019) extends similar requirements to federally regulated businesses.

India, RPwD Act 2016

The Rights of Persons with Disabilities Act, 2016 mandates accessibility of “information and communication technology” and “appropriate technology” for persons with disabilities. The Department of Empowerment of Persons with Disabilities has published guidelines referencing WCAG. Government websites and many regulated industries (banking, insurance, healthcare) are required to meet these standards.

For private businesses, RPwD compliance is increasingly part of government tender requirements and corporate procurement diligence.

Industry-specific requirements (global)

• Healthcare: accessibility is a soft requirement under most healthcare regulations and a hard requirement for any public-funded or insurance-facing platform in the US, UK, EU and increasingly in India.
• Government tenders: most national and many state/provincial government tender processes worldwide include WCAG conformance as a mandatory eligibility criterion.
• Banking, insurance, fintech: regulators in the US, UK, EU, India and elsewhere increasingly require accessibility for consumer-facing platforms.
• Education: institutions globally face increasing accessibility pressure, especially those serving public funding or international students.

The dozen accessibility issues we find on 80% of audits

Across hundreds of accessibility audits, a small set of issues account for most violations. If you fix these twelve, you'll resolve most of your conformance gap:

• Missing or unhelpful alt text on images. Decorative images need empty alt (alt=""); meaningful images need descriptive alt.
• Buttons that aren't actually buttons. <div onClick> is invisible to screen readers and not keyboard-operable. Use<button>.
• Form fields without labels. Every input needs a<label> with a for attribute oraria-label.
• Modal dialogs with broken focus management. When a modal opens, focus should move into it and be trapped until it closes. Most custom modals fail.
• Colour contrast below 4.5:1. Body text on background must hit this ratio. Light grey on white usually fails. Most brand designs have at least one violation here.
• Custom dropdowns and date pickers without keyboard support. Highly common in fancy UI libraries. Test with Tab + arrow keys.
• Heading order skipping levels. An H1 followed by an H4 confuses screen readers. Follow logical hierarchy.
• Auto-playing video or audio. Disorients screen-reader users and violates WCAG 1.4.2.
• Tiny click targets on mobile. Buttons under 44×44px fail WCAG 2.5.5 (AAA in 2.1, AA in 2.2).
• Form errors shown only in colour. Red border on an invalid field is invisible to screen readers and to colour-blind users. Add text errors.
• PDF content that isn't tagged. Untagged PDFs are unreadable on screen readers. Either tag them properly or replace with HTML.
• Focus indicators removed. CSS outline: none without a replacement breaks keyboard navigation entirely. Always provide a visible focus state.

The “compliance overlay” scam

A category of products, AccessiBe, UserWay, EqualWeb, audioEye and similar, claim to make any website instantly accessible by adding a JavaScript widget. They do not work.

Multiple US lawsuits have found explicitly that overlay widgets do not satisfy ADA. Hundreds of disability advocacy organisations have signed an Overlay Fact Sheet formally recommending against them. The most experienced accessibility consultants treat them as worse than no fix at all, they create the illusion of compliance while doing nothing, and in many cases actively interfere with native screen-reader functionality.

Real accessibility comes from fixing the underlying HTML, semantics, focus management, and visual design, not bolting on a script.

What auditing actually involves

A real WCAG audit is part automated, part manual. Both halves matter:

Automated scans

Tools like axe DevTools, WAVE, Lighthouse and Pa11y catch about 30–40% of WCAG violations, the easily-detectable rule-based ones (missing alt, low contrast, missing labels, broken landmarks). Run these first; fix what they find.

Manual review

The other 60–70% requires humans. A real audit includes:

• Screen reader walkthrough on at least one of NVDA, JAWS, or VoiceOver.
• Complete keyboard-only navigation of every key user journey.
• Manual evaluation of complex interactions (forms, modals, autocomplete, carousels).
• Mobile assistive tech (VoiceOver iOS, TalkBack Android).
• Cognitive load review of error messages, instructions, navigation patterns.

Anyone offering an accessibility audit that doesn't include a manual screen-reader component is selling you a Lighthouse run with extra steps. The real work is the manual review.

What it costs

• WCAG 2.2 AA audit, small marketing site (10–30 pages): $600–$2,000 USD (₹50,000–₹1.5 lakh). 2–3 weeks. Includes automated + manual review and a written report.
• Remediation, same site: $1,200–$5,000 USD (₹1 lakh–₹4 lakh). 4–8 weeks of engineering work. Depends on issue volume.
• Conformance statement + retest: $500–$1,000 USD (₹40,000–₹80,000). After remediation, a final pass to verify and produce the public statement.
• Large web application (100+ pages, complex flows): $5,000–$20,000 USD (₹4 lakh–₹15 lakh) total, scoped to the actual surface area.
• Annual retest retainer: $500–$1,500 USD/year (₹40,000–₹1.2 lakh). Necessary because every site decays.

The SEO and conversion bonus

Accessible sites typically:

• Score higher on Lighthouse and Core Web Vitals (semantic HTML is faster to render).
• Rank better on Google (Google's algorithms favour clean semantics).
• Have lower bounce rates (clearer hierarchies, better navigation).
• Convert better on forms (clearer labels, better error messages).
• Read more easily for everyone (not just disabled users), including non-native English speakers.

Real accessibility work pays for itself in measurable SEO and conversion gains, on top of the legal and ethical case.

Where to start this week

• Run a Lighthouse accessibility audit on your top 5 pages. Free, built into Chrome DevTools. Get a baseline score. Aim for 95+.
• Test keyboard navigation. Close your mouse. Use Tab, Shift+Tab, Enter, Space, Escape, arrow keys. Can you reach every interactive element? Can you tell where focus is?
• Check colour contraston your body text and key buttons. WebAIM's Contrast Checker (free) or the Stark plugin. Body text needs 4.5:1; UI elements need 3:1.
• Add real alt text to every meaningful image on your site. Set decorative images to empty alt.
• Audit your forms. Every input has a visible label? Error messages are clear text, not just colour? Required fields are clearly marked?

Those five exercises will surface the worst 20% of issues. The remaining 80% is what a real audit catches.

How RoseLeap can help

We package WCAG 2.2 AA conformance for businesses worldwide through our Web Accessibility service. Audit, remediation, screen-reader and keyboard testing, conformance statement, and annual retest, for healthcare sites, government-tender work, US-facing B2B, and any team that takes inclusion seriously.

Tell us about your site at the contact page. We come back with a fixed-fee scope and a date you can claim WCAG 2.2 AA conformance by, within one business day.