Web Accessibility in 2026: The US Deadlines Moved, Canada's Did Not

In the space of three weeks this spring, two US federal agencies pushed back the digital accessibility deadlines they had spent two years telling organisations to prepare for. The Department of Justice moved first, on April 20. Health and Human Services followed on May 7, four days before its own deadline was due to bite. The reaction from a lot of boardrooms was predictable: we have another year. That reading is wrong for most businesses, and expensively wrong for some.

What actually changed

The DOJ rule finalised in April 2024 made WCAG 2.1 Level AA the binding technical standard for websites and mobile apps operated by state and local government entities under Title II of the ADA. Compliance was due to begin April 24, 2026. On April 20, 2026 — four days before that date — the DOJ issued an interim final rule extending the timeline by one year. Public entities serving populations of 50,000 or more now have until April 26, 2027; those under 50,000 have until April 26, 2028.

HHS did the same thing for healthcare. Its Section 504 rule required organisations receiving federal financial assistance — anyone taking Medicare, Medicaid, or an HHS grant — to meet WCAG 2.1 Level AA by May 11, 2026. On May 7, the Office for Civil Rights extended that to May 11, 2027 for recipients with 15 or more employees, and May 10, 2028 for those with fewer.

The standard did not change. The scope did not change. Only the date did — and only for the organisations those two rules covered in the first place.

Who did not get an extension

This is the part that gets lost. The DOJ extension applies to Title II — state and local government. Private businesses fall under Title III, and Title III has never had a compliance date to extend, because it has never had a published technical standard. What it has instead is a steady volume of private litigation, and none of that paused in April.

So if you run a private business in the US, the honest summary is: you were not on the clock that moved, you are still exposed to the risk that did not, and the extension you read about in the trade press was never yours.

• Private US businesses (Title III) — no deadline extended, because no deadline existed. Litigation risk unchanged.
• State and local government, public schools and universities (Title II) — extended to April 2027 or April 2028 by population served.
• Healthcare organisations taking federal funding (Section 504) — extended to May 2027 or May 2028 by headcount.
• Vendors and contractors building digital services for any of the above — your client's deadline is now your delivery date.

That last line deserves emphasis. If you build, host, or maintain software for a public entity or a federally funded healthcare provider, their obligation lands in your statement of work. We are already seeing WCAG 2.1 AA conformance written into procurement requirements as a pass/fail gate rather than a nice-to-have.

In Canada, the clock is running the other way

While US deadlines slipped, Canadian ones did not. 2026 is a reporting year under the Accessibility for Ontarians with Disabilities Act. Every organisation with twenty or more employees in Ontario must file an accessibility compliance report through the provincial portal by December 31, 2026. That is a hard date, it is months away rather than years, and it applies to ordinary private businesses — not just government.

The penalties are not symbolic. Non-compliance under the AODA can reach $100,000 per day for a corporation, and directors and officers can be held personally liable up to $50,000 per day. The current web requirement under the AODA remains WCAG 2.0 Level AA.

Federally regulated organisations have a parallel obligation under the Accessible Canada Act: identify barriers, publish an accessibility plan, set up a feedback process, and report on progress on a recurring cycle. Large federally regulated employers hit a reporting milestone this June; smaller ones are due next year.

The US extension bought time for public entities. It bought nothing for a private company in Toronto with twenty staff and a filing due December 31.

Why the "we will bolt something on later" plan keeps failing

The most quietly interesting detail in the DOJ's extension is its stated reasoning. Alongside resource and staffing constraints, the department cited the limits of current technology — including generative AI — for remediating inaccessible content. That is a federal regulator saying, in writing, that you cannot buy your way out of this at the end of the project.

It matches what we see in practice. Accessibility overlays and automated scanners catch a real but narrow slice of issues — colour contrast, missing alternative text, unlabelled form fields. They do not fix a keyboard trap in a custom date picker, a modal that never moves focus, a data table that means nothing when read aloud, or a checkout flow that cannot be completed without a mouse. Those are architecture decisions, and architecture is not something you patch at launch.

This is why we treat accessibility as a design and engineering discipline rather than a pre-launch audit. Designing to WCAG from the first wireframe adds very little to a build. Retrofitting it into a shipped product routinely costs an order of magnitude more, because the fix is no longer a stylesheet — it is the component library, the markup structure, and sometimes the user flow itself.

What to do in the next ninety days

• Establish which rules actually apply to you. Title II, Title III, Section 504, AODA and the ACA have different scopes, different standards and different dates. Most organisations we speak to have guessed at this rather than confirmed it.
• If you have Ontario employees, find out whether your compliance report is filed. December 31, 2026 arrives faster than a remediation project finishes.
• Get an audit against the standard that binds you — WCAG 2.0 AA for the AODA today, WCAG 2.1 AA for the US federal rules — and insist the output is a prioritised, costed backlog rather than a PDF of violations.
• Fix the flows that carry revenue and obligation first: sign-up, checkout, booking, payment, account recovery, and anything a customer cannot avoid.
• Put accessibility checks into CI so that fixed issues stay fixed. Manual audits decay the moment the next sprint ships.
• Write conformance into vendor contracts. If an agency is building your site, the standard belongs in the agreement, not in an email after launch.

The commercial case nobody puts in the compliance memo

Roughly one in five people has a disability. Accessible markup is also the markup search engines and AI answer engines parse most reliably — semantic headings, real landmarks, descriptive link text and proper form labels are the same signals that make a page machine-readable. Captions get watched in sound-off feeds. Keyboard-navigable checkouts convert better for everyone using a laptop in a hurry.

Teams that treat accessibility as a legal cost do the minimum, late, twice. Teams that treat it as a quality standard ship products that are easier to use, easier to rank, and — as it happens — already compliant when the deadline finally lands. Given that two regulators just told the market the technology cannot rescue a late start, the second approach is looking less like idealism and more like planning.