AODA WEBSITE ACCESSIBILITY

Meet Ontario’s website accessibility requirements with work that goes beyond a scan.

The Accessibility for Ontarians with Disabilities Act creates accessibility requirements for organizations across Ontario—including specific requirements for public websites operated by designated public-sector organizations and businesses or non-profits with 50 or more employees in Ontario.

EqualAccess. helps your team identify accessibility barriers, test the real user experience, remediate issues in the website itself, retest the work, and document what was completed.

  • AODA-Focused
  • WCAG Testing
  • Manual Expert Review
  • Code-Level Remediation
  • Verification & Documentation

Website audits · Remediation · Retesting · Accessibility documentation · Ongoing support

KNOW THE TIMELINE

The 2026 reporting deadline is approaching—but the website requirement is already in force.

These are different obligations. The public-website requirement took effect on January 1, 2021. The 2026 date is a compliance reporting deadline for businesses and non-profits with 20 or more Ontario employees.

WEBSITE REQUIREMENT · IN FORCE

January 1, 2021

Public website accessibility requirement

Covered public websites and applicable web content must meet the referenced WCAG 2.0 Level AA requirements, with the specified exceptions. This requirement is already active.

DESIGNATED PUBLIC SECTOR · DEADLINE PASSED

December 31, 2025

Designated public-sector compliance report

Designated public-sector organizations report every two years. If your organization missed the 2025 deadline, Ontario instructs it to file the outstanding report as soon as possible.

BUSINESS & NON-PROFIT · 20+ ONTARIO EMPLOYEES

December 31, 2026

Business & non-profit compliance report

Businesses and non-profits with 20 or more employees in Ontario must file an accessibility compliance report. These organizations report every three years.

Reporting and website requirements use different thresholds. Having 20 employees can create a reporting obligation. For private businesses and non-profits, the specific public-website WCAG requirement applies at 50 or more employees in Ontario.

Official guidance: Ontario website requirements · Accessibility compliance reporting.

START WITH YOUR ORGANIZATION

Different AODA requirements apply at different organization sizes.

Choose your organization type and employee band to understand the distinction between reporting, public-website accessibility and planning.

REQUIREMENTS AT A GLANCE

Business / non-profit · 1–19 employees

Compliance report
Not required based on employee count
Public website WCAG
Not required solely by this employee count
Reporting deadline
No report required by this employee count
Policy & planning
Written multi-year plan not required solely by this count

Other AODA accessibility requirements can still apply, including accessibility policies, training and accessible information. Improving your website remains good practice.

REQUIREMENTS AT A GLANCE

Business / non-profit · 20–49 employees

Compliance report
Required · every three years
Public website WCAG
Not required solely by this employee count
Reporting deadline
December 31, 2026
Policy & planning
Written multi-year plan not required solely by this count

Reporting is required, but crossing the 20-employee reporting threshold does not itself trigger the 50+ employee public-website requirement. Other AODA obligations still apply.

REQUIREMENTS AT A GLANCE

Business / non-profit · 50+ employees

Compliance report
Required · every three years
Public website WCAG
Required for covered public websites
Reporting deadline
December 31, 2026
Policy & planning
Written accessibility policies and multi-year plan required

Ontario’s specific public-website requirement applies at this threshold. Scope the website, applicable content, technical target and any relevant exceptions.

REQUIREMENTS AT A GLANCE

Designated public-sector organization

Compliance report
Required · every two years
Public website WCAG
Required for covered public websites
Reporting deadline
December 31, 2025 · most recent deadline
Policy & planning
Written policies and multi-year accessibility planning required

If the 2025 report was missed, Ontario says to file the outstanding report as soon as possible. Ontario Public Service and Legislative Assembly reporting rules are separate from this summary.

Employee bands refer to employees in Ontario. Organization type, control of the website, content scope and applicable exceptions can affect the assessment. Read Ontario’s business guidance or designated public-sector guidance.

Not sure which requirements apply to your organization?

We can help scope the technical website accessibility work. Confirm questions about legal applicability with qualified legal counsel.

Get a Free Review

THE WEBSITE STANDARD

For covered websites, the technical baseline is WCAG 2.0 Level AA.

Ontario’s website guidance references WCAG 2.0 Level AA, with two specified exceptions. Covered public websites include applicable web applications and web content published after January 1, 2012.

1.2.4 Captions (Live)

1.2.5 Audio Description (Prerecorded)

The exceptions do not remove all media accessibility requirements.

Perceivable

People need to be able to perceive the content.

  • Alternative text
  • Colour contrast
  • Meaningful structure
  • Accessible media
  • Content that works when enlarged

Operable

People need to be able to use the interface.

  • Keyboard accessibility
  • Visible focus
  • Usable navigation
  • No keyboard traps
  • Accessible menus and controls

Understandable

People need to understand what the interface expects.

  • Clear labels
  • Form instructions
  • Useful error messages
  • Predictable navigation
  • Consistent interaction

Robust

The website needs to communicate correctly with browsers and assistive technologies.

  • Semantic HTML
  • Accessible names
  • Correct roles and states
  • Screen-reader compatibility
  • Reliable interactive components

Scope also depends on control of the website and the limited exceptions in section 14 of Ontario Regulation 191/11. Read Ontario’s guidance on website exceptions.

THE REQUIREMENT IS ALREADY ACTIVE

A website that was accessible in 2021 can have accessibility barriers today.

Websites change. New products, theme updates, plugins, rebuilt forms, campaign pages and third-party tools can all affect accessibility. Content teams add new images and documents. Developers ship new components.

That is why the work continues through assessment, testing, remediation, verification, documentation and ongoing support.

Explore Ongoing Monitoring & Support
ILLUSTRATIVE WEBSITE HISTORY
  1. Website reviewedA starting point recordedReviewed
  2. New checkoutA different purchase journeyReview
  3. New booking widgetA new vendor dependencyReview
  4. Theme redesignNavigation and templates changeReview
  5. Current accessibility reviewTest the experience people use todayNext step

Accessibility can drift as the website changes.

BEYOND AUTOMATED CHECKS

Accessibility requires human evaluation.

Automated testing helps identify detectable patterns quickly. Many requirements also depend on context, interaction and actual user experience. W3C explains that tools alone cannot establish accessibility; knowledgeable human evaluation is needed.

Ontario’s website guidance recommends project plans that combine automated, manual and assistive-technology testing, including screen readers.

Automated analysis

Find detectable technical patterns across pages and templates.

Manual expert testing

Evaluate requirements that need human judgment.

Keyboard testing

Check whether important experiences can be reached and operated without a mouse.

Assistive technology

Review relevant experiences with screen readers and other appropriate testing methods.

User journeys

Test what visitors are actually trying to accomplish.

Code review

Identify the underlying implementation creating the barrier.

W3C: evaluating web accessibility · Ontario: testing your website.

REAL WEBSITE USE

AODA accessibility matters where people need to complete a task.

We test the journey—not just the homepage. The scope follows what visitors need to do.

Ecommerce

  1. Find product
  2. Choose options
  3. Add to cart
  4. Checkout
  5. Confirmation

Restaurants & hospitality

  1. Find location
  2. Read menu
  3. Reserve
  4. Confirmation

Healthcare & services

  1. Find information
  2. Complete form
  3. Schedule
  4. Confirmation

Public sector

  1. Find service
  2. Understand requirements
  3. Complete application
  4. Submit

Common barriers along the way

  • Inaccessible navigation
  • Missing form labels
  • Keyboard-inaccessible controls
  • Unclear error messages
  • Low colour contrast
  • Poor heading structure
  • Unlabelled buttons
  • Inaccessible dialogs
  • Missing image alternatives
  • PDF accessibility barriers
  • Third-party booking or payment barriers

We evaluate accessibility in the context of what people are actually trying to do.

REAL REMEDIATION

Finding the barrier is only the beginning.

Identify the issue, understand its impact, map the requirement, correct the implementation, retest and document the result. Explore an example below.

ILLUSTRATIVE FINDING · NAV-01

A menu button has no accessible name.

01 · User impact
A screen-reader user hears “button” without knowing that it opens the navigation.
02 · WCAG mapping
4.1.2 Name, Role, Value · Level A
03 · Remediation
Use a native button with a meaningful name. Expose its expanded state and connect it to the navigation it controls.
04 · Retest & verify
Check the announced name and state, operate the menu with a keyboard, and record the result after retesting.
EXAMPLE WEBSITE · NAV-01

REMEDIATION EXAMPLE

Menu

Shop · Locations · Contact

A meaningful name and an exposed expanded state.

IMPLEMENTATION EXCERPT
<button aria-expanded="false"
        aria-controls="site-menu">
  Menu
</button>
Illustrative example only. Full component behaviour and testing evidence are evaluated within the agreed project scope.

ILLUSTRATIVE FINDING · FORM-01

A checkout field has no accessible label.

01 · User impact
A screen-reader user may not reliably understand what information the field requires.
02 · WCAG mapping
1.3.1 Info and Relationships; 3.3.2 Labels or Instructions · Level A
03 · Remediation
Add a visible label and associate it with the input. Review required-field instructions and validation in the complete form.
04 · Retest & verify
Confirm the field’s announced name, keyboard order and error recovery. Record whether the original barrier is resolved.
EXAMPLE WEBSITE · FORM-01

REMEDIATION EXAMPLE

Email address

you@example.com

The visible label is connected to its input.

IMPLEMENTATION EXCERPT
<label for="checkout-email">
  Email address
</label>
<input id="checkout-email"
       type="email" autocomplete="email">
Illustrative example only. Full component behaviour and testing evidence are evaluated within the agreed project scope.

ILLUSTRATIVE FINDING · KEY-01

The reservation dialog traps keyboard users.

01 · User impact
A visitor can enter the dialog but cannot close it and return to the reservation page using only a keyboard.
02 · WCAG mapping
2.1.2 No Keyboard Trap · Level A; 2.4.3 Focus Order · Level A
03 · Remediation
Implement a keyboard-operable close control and deliberate focus handling. Support an appropriate exit path and return focus to the trigger.
04 · Retest & verify
Open, navigate and close the dialog using only the keyboard. Check that focus returns to a useful location and the journey can continue.
EXAMPLE WEBSITE · KEY-01

REMEDIATION EXAMPLE

Your reservation

Choose a date · Confirm · Close

A usable exit path, with focus returned to the trigger.

IMPLEMENTATION EXCERPT
dialog.addEventListener("close", () => {
  reservationTrigger.focus();
});

// Test the full keyboard journey.
Illustrative example only. Full component behaviour and testing evidence are evaluated within the agreed project scope.

ILLUSTRATIVE FINDING · IMG-01

An informative product image has no useful alternative.

01 · User impact
A visitor using a screen reader misses information needed to understand or distinguish the product.
02 · WCAG mapping
1.1.1 Non-text Content · Level A
03 · Remediation
Write a context-appropriate text alternative for the informative image. Keep decorative images silent and review image links separately.
04 · Retest & verify
Check the alternative in its actual page context and with a screen reader. Confirm that the equivalent information is available without seeing the image.
EXAMPLE WEBSITE · IMG-01

REMEDIATION EXAMPLE

Product image

Navy backpack with a front zip pocket

An informative alternative, reviewed in context.

IMPLEMENTATION EXCERPT
<img src="backpack.webp"
     alt="Navy backpack with a
          front zip pocket">
Illustrative example only. Full component behaviour and testing evidence are evaluated within the agreed project scope.

ILLUSTRATIVE FINDING · VENDOR-01

An embedded booking control cannot be operated by keyboard.

01 · User impact
A visitor cannot select an appointment time and finish the booking journey without a mouse.
02 · WCAG mapping
2.1.1 Keyboard · Level A
03 · Remediation
Document the reproduction steps and identify who can modify the component. Give the vendor a clear requirement or review accessible alternatives.
04 · Retest & verify
Retest the vendor’s update within the website. Keep the issue marked open if the barrier remains, and document any interim access route.
EXAMPLE WEBSITE · VENDOR-01

REVIEW RECORD

Booking widget

Owner: vendor · Status: review required

Vendor dependencies remain visible in the finding record.

VENDOR ISSUE RECORD
Finding: appointment picker
Owner: booking vendor
Required: keyboard operation
Status: open until retested
Evidence: attached to the issue
Illustrative example only. Full component behaviour and testing evidence are evaluated within the agreed project scope.
Finding Fix Verification

A useful outcome includes the work after the findings register.

Explore Code-Level Remediation

FROM REVIEW TO VERIFIED IMPROVEMENTS

A practical process for understanding and improving your website.

Here is the AODA engagement in detail, from the initial scope through ongoing support. The agreed engagement determines which work and deliverables are included.

  1. 01

    Scope

    Identify website properties, templates, important pages, components, third-party tools, key journeys and the applicable technical target.

    OutputDefined testing scope

  2. 02

    Assess

    Run automated analysis and review the website structure.

    OutputInitial accessibility signals

  3. 03

    Manual Testing

    Test keyboard behaviour, forms, navigation, content, components and important interactions.

    OutputValidated findings

  4. 04

    Assistive Technology

    Test relevant functionality using appropriate assistive technologies.

    OutputReal interaction evidence

  5. 05

    Prioritize

    Organize findings by user impact, recurrence, business importance and technical dependency.

    OutputRemediation plan

  6. 06

    Remediate

    Correct accessibility barriers where technical access and project scope allow.

    OutputImplemented accessibility improvements

  7. 07

    Retest & Verify

    Test the affected experience again and record whether the implemented fix resolves the original barrier.

    OutputVerification evidence

  8. 08

    Document

    Record scope, findings, fixes, verification results and remaining limitations.

    OutputAccessibility documentation

  9. 09

    Maintain

    Continue reviewing the website as it changes, under an agreed ongoing support scope.

    OutputOngoing accessibility support

2026 ACCESSIBILITY COMPLIANCE REPORT

Know the technical state of your website before your organization certifies its report.

Businesses and non-profits with 20 or more employees in Ontario must submit their 2026 AODA accessibility compliance report by December 31, 2026.

The report records whether the organization meets its applicable requirements. Ontario can audit and inspect organizations and use enforcement measures where appropriate.

Get a Free Review

We can help with the website side.

Website accessibility assessment
Understand the current technical state.
WCAG testing
Evaluate applicable website requirements.
Findings register
Document validated barriers and affected functionality.
Remediation
Correct barriers within agreed technical scope.
Retesting
Check whether implemented fixes resolved the original issue.
Technical documentation
Give your internal team or certifier a clearer record of completed work.

EqualAccess. does not file or legally certify your AODA compliance report.

Your organization’s authorized certifier is responsible for the report. We provide technical testing, remediation and documentation for the website portion of the work.

Read Ontario’s reporting guidance

AN IMPORTANT AODA DISTINCTION

Reporting requirements and website requirements use different employee thresholds.

For businesses and non-profits, 20 employees is not the same as 50 employees.

20+

EMPLOYEES IN ONTARIO

Reporting

Accessibility compliance report due
December 31, 2026

is a different threshold from
50+

EMPLOYEES IN ONTARIO

Reporting + website WCAG
+ multi-year plan

Additional requirements for covered public websites, documented accessibility policies and multi-year accessibility planning.

A 25-person business can have an AODA reporting obligation without being subject to the specific 50+ employee public-website WCAG requirement solely because of its employee count.

FROM POLICY TO IMPLEMENTATION

Accessibility plans work better when they connect to measurable technical work.

Businesses and non-profits with 50 or more employees in Ontario, along with designated public-sector organizations, must maintain a written multi-year accessibility plan.

Covered organizations must review and update the plan at least once every five years and post it on their website if they have one.

We can support the digital accessibility portion of your roadmap while your internal compliance or legal team manages broader organizational AODA obligations.

Ontario: accessibility plans and policies.

  1. Objective

    Improve keyboard accessibility.

  2. Technical work

    Test navigation, menus, dialogs, forms and important user journeys.

  3. Remediation

    Correct inaccessible interaction patterns.

  4. Verification

    Retest affected functionality.

  5. Documentation

    Record progress and remaining work.

THE EXPERIENCE EXTENDS BEYOND YOUR CODEBASE

Booking tools, ecommerce apps, forms and embedded services can create barriers too.

Ontario’s website provisions consider control of the website, directly or through a contractual relationship that allows modification. Third-party experiences therefore need a clear scope and an identified owner.

  • Reservation systems
  • Payment providers
  • Chat tools
  • Cookie banners
  • Store locators
  • Recruitment systems
  • Embedded forms
  • Customer portals
  • Product apps
  • Checkout extensions
YOUR IMPLEMENTATION

Your team controls it.

We can remediate the issue directly where technical access and the engagement scope allow.

DEVELOPER OR AGENCY

Your partner controls it.

We can provide the finding, technical requirement and verification support.

THIRD-PARTY VENDOR

The vendor controls it.

We can document the barrier, help communicate the issue, review available alternatives and retest changes.

Where is the barrier? Who controls it? What can realistically be changed?

We do not promise that every third-party component can be modified. Document unresolved barriers and any access alternatives; confirm legal scope and limited exceptions with your advisers.

LEGAL BASELINE VS. CURRENT STANDARD

AODA references WCAG 2.0 AA. Why do we also talk about WCAG 2.2?

We separate what AODA currently requires from where accessibility standards have evolved. W3C encourages use of its latest WCAG version; that does not automatically change Ontario’s referenced legal baseline.

AODA REGULATORY BASELINE

WCAG 2.0 AA

For covered websites, with the specified exceptions for live captions and prerecorded audio description.

Applicable baseline

BROADER MODERN ACCESSIBILITY TARGET

WCAG 2.2 AA

Additional current criteria when appropriate for the engagement, with scope and reporting agreed clearly.

Additional agreed scope

WCAG 2.2 removed Success Criterion 4.1.1 Parsing. Where an engagement must report against WCAG 2.0, we retain the relevant baseline checks and reporting. Findings distinguish the applicable AODA baseline from additional current accessibility best practices.

Clear scope. Clear testing target. Clear reporting.

CLEAR TECHNICAL EVIDENCE

Know what was tested, what was found and what happened next.

Your engagement can include the following, depending on scope. The record makes completed work, remaining barriers and testing limitations visible.

YOUR ACCESSIBILITY PROJECT

A working record.
A clearer next step.

Agreed scope → Findings → Work completed → Retest evidence

Deliverables defined in scope
  1. 01

    Accessibility assessment

    Agreed pages, templates, components and user journeys.

  2. 02

    Automated test results

    Detectable patterns requiring investigation.

  3. 03

    Manual expert findings

    Human-validated accessibility barriers.

  4. 04

    Assistive-technology testing

    Relevant screen-reader and interaction evidence.

  5. 05

    WCAG mapping

    Findings connected to the criteria and testing target.

  6. 06

    Prioritized remediation plan

    An order of work based on user impact and website importance.

  7. 07

    Code-level remediation

    Implemented fixes where included and technically possible.

  8. 08

    Verification & retesting

    Re-evaluation of corrected functionality.

  9. 09

    Technical accessibility report

    Findings, fixes, status, scope and known limitations.

  10. 10

    Ongoing accessibility support

    Continued review as your site evolves.

BUILT FOR REAL ONTARIO ORGANIZATIONS

Accessibility support that works with the website and team you already have.

Ecommerce & Retail

Product pages · Filters · Navigation · Cart · Checkout · Accounts · Third-party apps

Restaurants & Hospitality

Menus · Locations · Reservations · Ordering · Gift cards · Contact forms · Booking systems

Healthcare & Services

Forms · Appointments · Portals · Documents · Provider information · Customer journeys

Non-Profits

Public information · Donations · Forms · Events · Documents · Member experiences

Municipalities & Public Organizations

Public services · Applications · Forms · Documents · Information portals · Third-party systems

Agencies & Internal Web Teams

Technical findings · Developer guidance · Remediation support · Verification · Training

We can work directly with your organization, your developer, your agency, or your technical vendors.

KNOW THE BOUNDARY

Website accessibility is one part of AODA compliance.

AODA standards extend beyond websites. Other duties, including accessibility training and accessible information, depend on your organization and circumstances. Ontario’s training requirements can apply to organizations with one or more employees in specified roles and circumstances.

The broader AODA program

  • Customer service
  • Information and communications
  • Employment
  • Transportation
  • Design of public spaces

EqualAccess. focuses on the digital side.

  • Website and web application accessibility
  • Code remediation
  • PDF and document accessibility
  • Technical accessibility documentation
  • Digital accessibility consulting
  • Team training
  • Ongoing website support
Explore Consulting & Training

EqualAccess. provides digital accessibility services, not legal advice or blanket certification of an organization’s overall AODA compliance.

AODA IS ENFORCEABLE

Reporting and accessibility obligations should be taken seriously.

Ontario may use compliance reports, audits, inspections and enforcement measures to verify whether organizations meet applicable requirements. Failing to submit a required report can lead to enforcement action and financial penalties.

The practical goal is to understand where your organization stands, address barriers and maintain evidence of accessibility work.

AODA WEBSITE ACCESSIBILITY FAQ

Common questions.
Clear starting points.

Website requirements, reporting dates and the technical work involved.

Does every Ontario business need its website to meet WCAG 2.0 AA?

No. Ontario’s specific public-website requirement applies to designated public-sector organizations and businesses or non-profits with 50 or more employees in Ontario. Organizations below that employee threshold can still have other AODA responsibilities and are encouraged to improve website accessibility.

Is December 31, 2026 the AODA website compliance deadline?

No. The applicable website accessibility deadline was January 1, 2021. December 31, 2026 is the accessibility compliance reporting deadline for businesses and non-profits with 20 or more employees in Ontario.

What WCAG version does AODA require for websites?

Ontario’s current website guidance references WCAG 2.0 Level AA, with exceptions for Success Criteria 1.2.4 Captions (Live) and 1.2.5 Audio Description (Prerecorded). EqualAccess. can also test against newer WCAG criteria when a broader current accessibility target is appropriate.

Does WCAG 2.2 replace AODA’s legal WCAG 2.0 requirement?

Not automatically. WCAG 2.2 is the current W3C WCAG 2 standard, but Ontario’s AODA website provisions still reference WCAG 2.0 AA. We distinguish the applicable regulatory baseline from additional current best-practice testing, including the treatment of the older Parsing criterion in baseline reporting.

Can an automated accessibility scanner prove our website meets AODA requirements?

No. Automated tools are useful for detecting certain issues, but they cannot evaluate every accessibility requirement or user interaction. Knowledgeable human evaluation is necessary for a complete assessment of the agreed scope. A sampled assessment does not establish conformance of untested content.

Does AODA apply to website content created before 2012?

The specific website provisions cover applicable web content published after January 1, 2012. Older content and intranets are not automatically subject to the same public-website rule, but other accessible-information obligations may still apply when information is requested in an accessible format. Confirm the scope and any exceptions for your circumstances.

What if part of our website is controlled by a third-party vendor?

Third-party integrations should be considered when they are part of the user experience. The website control provisions include direct control or a contractual relationship allowing modification. We can identify barriers, clarify what your team controls, provide technical guidance to the vendor and verify changes where possible. We cannot promise that every vendor component can be modified.

What if we have 20–49 employees?

Businesses and non-profits with 20 or more employees in Ontario must file the 2026 accessibility compliance report. The specific public-website WCAG requirement applies to businesses and non-profits with 50 or more Ontario employees; crossing the 20-employee reporting threshold does not by itself trigger it. Other AODA obligations still apply.

Can EqualAccess. help us prepare for the 2026 compliance report?

We can help with the technical website accessibility side: reviewing the website, identifying barriers, mapping findings to applicable criteria, remediating issues, retesting changes and documenting the work. Your organization’s authorized certifier remains responsible for the compliance report itself. EqualAccess. does not file or legally certify that report.

Can EqualAccess. certify that our organization is AODA compliant?

No. A website audit is not certification of an organization’s entire AODA legal compliance. EqualAccess. provides technical digital accessibility evaluation, remediation, verification and documentation within an agreed scope, with remaining limitations recorded.

How often should we test our website?

There is no single testing schedule that fits every organization. Review websites that change frequently more often, especially after redesigns, new templates, new functionality, significant integrations or changes to critical user journeys. Accessibility works best as part of ongoing development, with testing frequency agreed around your website’s risk and rate of change.

START WITH THE WEBSITE

Know where your website stands before the next step.

Whether you’re preparing your December 31, 2026 AODA report, reviewing an older website, launching a redesign, or building a stronger accessibility process, the first step is understanding the actual barriers.

We’ll help you determine what should be tested, what needs to be fixed, and what a practical remediation and verification plan looks like.

Get a Free Review

Already have an audit, compliance checklist, WCAG report, accessibility plan or list of issues? Bring it to the review and we’ll start from what you already have.

EqualAccess. provides technical digital accessibility services, not legal advice.

Opens in a new tab.