Accessibility readiness guide

Know which clock is yours.

A source-linked planning aid for teams sorting Ontario reporting, Ontario public website guidance, and U.S. public-entity Title II dates.

LAST REVIEWED / 2026-09-09

Maintained by Virtually(Creative) Accessibility.
Technical planning information, not legal advice.

20+Ontario reporting threshold in the official guidance
50+Ontario public website guidance threshold
2027U.S. Title II date for the 50,000+ population tier
2028U.S. Title II date for smaller entities and special districts

Read the scope first

The same word—different clocks.

Ontario reporting guidance, Ontario web guidance, and U.S. DOJ Title II guidance describe different scopes, standards, and dates. Use the matching section below—not a blended deadline.

Keep the boundary visible

Scope is the decision.

What does the Ontario 20+ number answer?

It points you to the Ontario accessibility compliance report guidance and its reporting threshold. It is not the Ontario public website threshold.

What does the Ontario 50+ number answer?

It points you to Ontario’s web guidance for public website accessibility. Keep that web workstream separate from the reporting workstream.

Who do the U.S. 2027 and 2028 dates describe?

The DOJ resource identifies the rule as Title II for state and local public entities; the Federal Register extension distinguishes the population tiers and special districts. This page does not apply those public-entity dates to private businesses or decide Title III coverage.

What to do next

Turn the date into a workable plan.

Once your scope is clear, choose the smallest useful next step. This planning path is technical and operational; it does not replace legal or procurement review.

Discuss a scoped next step
  1. 01

    Confirm your lane.

    Note your organization type, employee count, public-entity status, population served, special-district status, and the journey or website in scope.

  2. 02

    Find the blockers.

    Request accessibility scoping for a first look at the journey that matters most—useful input for sequencing technical work.

  3. 03

    Build the workstream.

    Explore the services for implementation support, documentation and a scoped plan your team can carry into its review process.

Official sources

Keep the links attached.

Last reviewed September 9, 2026 by Virtually(Creative) Accessibility. Regulatory scope and dates can change; re-check the live official guidance and route coverage and legal interpretation to appropriate reviewers before publication, procurement or filing.

  1. 01

    Ontario: Completing your accessibility compliance report

    Source for the 20-or-more-employee reporting threshold, three-year cadence, and December 31, 2026 deadline.

  2. 02

    Ontario: How to make websites accessible

    Source for the scoped public website WCAG 2.0 AA guidance for public organizations and businesses/non-profits with 50 or more employees.

  3. 03

    U.S. DOJ: Web Accessibility Rule under Title II

    Source for the public-entity scope, WCAG 2.1 AA standard, and April 26, 2027 date for entities serving populations of 50,000 or more.

  4. 04

    Federal Register: Extension of compliance dates

    Source for the April 26, 2028 date for entities serving populations below 50,000 and special districts.

Make the next step concrete

Bring the deadline. Leave with a clearer path.