Accessibility is no longer a design preference; it is a legal, commercial, and ethical requirement that every serious business in North America must take seriously. In 2026, courts in the United States, the Ontario Human Rights Tribunal, and the Accessibility Commissioner of Canada continue to treat inaccessible websites as a form of discrimination, and the financial penalties for ignoring this reality are rising every quarter.
If your website serves customers, patients, students, or employees anywhere in the US or Canada, this guide explains what has changed in 2026, which laws apply to you, and how to bring your site into durable compliance with WCAG 2.2 Level AA.
Why 2026 Is a Turning Point for Digital Accessibility
Three events have reshaped the accessibility landscape heading into spring 2026.
First, the US Department of Justice finalised its Title II technical rule for state and local government websites in April 2024, and the compliance deadline for larger jurisdictions began taking effect in April 2026. WCAG 2.1 Level AA is now the operative federal baseline for public sector web content in the United States, and most private sector litigation is referencing the same standard.
Second, WCAG 2.2 is now the published W3C recommendation, and nine new success criteria have been added to the guidelines. Courts and procurement teams in both countries are steadily migrating from WCAG 2.1 to WCAG 2.2 in their accessibility clauses, so businesses that audited against the older version last year may find gaps in 2026.
Third, Canada has entered the active enforcement phase of the Accessible Canada Act, and the Accessibility for Ontarians with Disabilities Act requires compliant websites for any organisation with 50 or more employees in Ontario. The Canadian Radio-television and Telecommunications Commission also extended captioning and accessibility obligations to more digital services this year.
Put simply, the regulatory floor is rising on both sides of the border; businesses that delay are now the exception, not the norm.
The Laws You Need to Understand
United States
The Americans with Disabilities Act (ADA) is the primary federal statute. Title III applies to places of public accommodation, and the Second, Ninth, and Eleventh Circuit Courts of Appeal have all held that commercial websites serving the public fall within its scope.
Section 508 of the Rehabilitation Act applies to federal agencies and contractors. Any vendor bidding on US federal work must produce an Accessibility Conformance Report, commonly known as a VPAT 2.5 document, that attests to WCAG 2.x conformance.
The Twenty First Century Communications and Video Accessibility Act governs captioning and advanced communication services, and the Air Carrier Access Act extends accessibility obligations to airline websites and kiosks.
State laws matter too. California’s Unruh Civil Rights Act, New York State Human Rights Law, and Colorado’s HB21-1110 have all been used as independent legal footholds for website accessibility claims, and statutory damages under Unruh alone start at 4,000 US dollars per violation.
Canada
The Accessible Canada Act (ACA) governs federally regulated organisations including banks, telecoms, airlines, and Crown corporations. Regulated entities must publish an accessibility plan every three years, operate a feedback process, and report on progress.
The Accessibility for Ontarians with Disabilities Act (AODA) requires private and non-profit organisations with 50 or more employees operating in Ontario to conform their public-facing websites and web content to WCAG 2.0 Level AA, and the province is actively consulting on raising this to WCAG 2.1 AA in the next review cycle.
Manitoba, Nova Scotia, and British Columbia each have standalone accessibility statutes, and Quebec’s access to information framework obliges public bodies to provide accessible digital services under its own provincial regime.
How the Laws Agree
Both legal systems converge on a single practical standard: conform to the latest stable version of the Web Content Accessibility Guidelines at Level AA, document your conformance, and establish a continuous remediation process. If you do those three things, you are meeting the technical expectations of regulators in every major North American jurisdiction.
What Changed in WCAG 2.2
WCAG 2.2 introduces nine new success criteria. Six of them sit at Level A or AA and therefore matter for regulatory compliance. The most consequential changes for 2026 audits are the following.
Focus Not Obscured (AA) requires that when an element receives keyboard focus, it is not entirely hidden by sticky headers, cookie banners, chat widgets, or other floating UI. This is the single most common new failure we are seeing in audits of legacy sites.
Dragging Movements (AA) requires any drag-and-drop interaction to have a single pointer alternative. Carousels, signature pads, and kanban boards are frequent offenders.
Target Size (AA) mandates that interactive targets are at least 24 by 24 CSS pixels, with specific exceptions for inline text links and compact toolbars. Many older mobile menus fail this criterion.
Consistent Help (A) requires that help mechanisms such as contact details, chatbots, or self-serve help widgets appear in the same relative order across pages.
Redundant Entry (A) requires forms to avoid asking the user for the same information twice within a single session unless it is essential for security.
Accessible Authentication (AA) bans cognitive function tests such as character puzzles, image identification CAPTCHAs, or memorising complex one-time codes as the sole path to login. Passkeys, email magic links, and properly captioned CAPTCHA alternatives are compliant.
If your last accessibility audit predated 2024, at least some of these will be gaps on your production site today.
The Real Financial Risk in 2026
The common assumption that accessibility lawsuits are a nuisance cost is no longer accurate. In the United States, federal and state court filings citing website accessibility surpassed 4,500 in 2024, and specialised plaintiffs’ firms are increasingly bringing class-wide claims against retail, healthcare, hospitality, and fintech brands.
A typical settlement in the US currently ranges from 8,000 to 25,000 US dollars for a first-time defendant, not counting the mandatory remediation, expert fees, and monitoring costs, which routinely push total expenditure beyond 75,000 US dollars.
In Canada, AODA administrative penalties can reach 100,000 Canadian dollars per day for corporations, and the Canadian Human Rights Tribunal has awarded damages of up to 40,000 Canadian dollars for pain and suffering in accessibility cases involving federally regulated services.
The lesson is consistent: remediating proactively is almost always cheaper than defending reactively.
A Practical Path to Compliance
Step One: Commission an Honest Audit
Automated scanners such as axe DevTools, Lighthouse, WAVE, and Siteimprove catch roughly thirty to forty percent of WCAG violations. The remainder, particularly cognitive, motor, and screen reader issues, require manual testing with assistive technology. A credible audit blends automated scanning, keyboard only navigation tests, screen reader walkthroughs using NVDA and VoiceOver, and structured reviews by people with lived disability experience.
Step Two: Triage and Prioritise
Not every finding carries the same legal and user impact. We recommend grouping issues into four tiers: blockers that prevent task completion, major barriers that cause frustration, minor issues that degrade polish, and documentation gaps. Blockers must be fixed within weeks, majors within one to two quarters, and minors on a rolling basis.
Step Three: Build Accessibility Into Your Engineering Process
Accessibility degrades when it is treated as a final QA pass. It stays healthy when it becomes part of code review, automated testing, design critique, and procurement. Teams that pass axe-core checks in CI, enforce Storybook a11y addons, and require a keyboard test in every pull request ship far fewer regressions.
Step Four: Publish an Accessibility Statement
A public accessibility statement is required under AODA and ACA for regulated entities, and it is strongly recommended for every business in the US. A strong statement lists the conformance standard, the date of the most recent audit, known outstanding issues with remediation timelines, the contact details of your accessibility lead, and a clear complaints and feedback channel.
Step Five: Plan for Continuous Conformance
Websites change constantly. A single redesign, marketing campaign, or CMS plugin update can introduce dozens of new failures. Sustainable compliance requires quarterly regression audits, accessibility training for content editors, and a feedback loop that captures real user issues quickly.
Country Specific Notes
If You Sell in the United States
Document a WCAG 2.2 Level AA conformance claim and keep a dated audit report on file. If you hold US federal contracts, maintain a current VPAT 2.5 document. Treat state laws in California, New York, Colorado, and Illinois as independent enforcement risks, and design your cookie, chat, and consent widgets so that they never obscure keyboard focus.
If You Sell in Canada
Publish a bilingual accessibility statement in English and French for any federally regulated service, respect AODA’s public sector and large enterprise obligations in Ontario, and map your accessibility plan to the Accessible Canada Act’s three year cycle. Captioning obligations under the CRTC extend to video content on your owned digital channels, so caption new video within a documented timeline.
If You Sell on Both Sides of the Border
Adopt the higher standard across your entire digital estate. WCAG 2.2 Level AA is the common denominator; use it as your baseline, produce one unified audit report per release, and maintain separate country specific statements to capture jurisdictional nuances.
A Word on AI Generated Accessibility Overlays
Accessibility overlays and widgets are marketed aggressively across North America, but the evidence against them is now overwhelming. They typically introduce new barriers for screen reader users, they fail to address root cause issues in your code base, and they are explicitly called out as insufficient by the US Department of Justice, the National Federation of the Blind, and leading Canadian disability advocacy groups.
Overlays cannot replace accessible HTML, semantic structure, and thoughtful design. Treat any vendor promising single line script compliance with deep scepticism.
How eLan Technology Helps US and Canadian Clients
eLan Technology has been engineering WCAG and ADA compliant websites for North American clients since 2002. Our practice is focused, documented, and outcome driven.
We conduct hybrid audits that combine automated scanning with manual testing by trained accessibility specialists, and we deliver a remediation plan sequenced by legal risk, user impact, and engineering cost. Every deliverable includes evidence artefacts that your legal team can attach to a VPAT, an accessibility statement, or an AODA filing.
For US clients we produce VPAT 2.5 aligned conformance reports, map findings to Section 508 and the ADA, and support remediation across React, Next.js, Astro, WordPress, Shopify, and headless stack environments. For Canadian clients we support bilingual accessibility statements, AODA and ACA reporting cycles, and CRTC aligned captioning workflows.
Beyond audits, we build new websites that are accessible by design. Our delivery model pairs a designer, a front end engineer, and an accessibility specialist on every project, and we run axe-core, Lighthouse CI, and keyboard-only QA inside our continuous integration pipeline so that regressions are caught before they reach production.
If your organisation has received a demand letter, is preparing for a procurement review, or simply wants to move from reactive firefighting to confident, continuous compliance, we would welcome a conversation.
Final Thoughts
ADA, AODA, and the Accessible Canada Act are not obstacles; they are a framework for reaching the 1 in 4 North American adults who live with a disability. Businesses that embrace WCAG 2.2 Level AA as a baseline commitment in 2026 will see three durable benefits at once: reduced legal exposure, stronger search and conversion performance, and a brand that genuinely serves everyone.
The cost of getting started is small, the cost of delay compounds every quarter, and the craft of building accessible websites has never been more mature. If you want help getting your site to conformance this quarter, our accessibility team is ready to start.