If your organization operates in Ontario, your website may be legally required to meet accessibility standards under the Accessibility for Ontarians with Disabilities Act (AODA). The website requirement applies to every municipality in the province, to other designated public sector organizations such as hospitals, school boards, colleges, and universities, and to businesses and non-profits with 50 or more employees in Ontario.
For most organizations, the website rules were phased in from January 1, 2014, and the final deadline for WCAG 2.0 Level AA passed on January 1, 2021. Even so, a significant number of Ontario websites still fail to meet the minimum requirements. Many organizations are unaware of the specific technical standards — or what it actually takes to comply. And if you run a business or non-profit with 20 or more employees, your next accessibility compliance report is due December 31, 2026 (more on that below). Need help getting compliant? Learn about our AODA accessibility audit and remediation services.
What Does the AODA Require for Websites?
Under section 14 of the AODA's Integrated Accessibility Standards Regulation (IASR, O. Reg. 191/11), designated public sector organizations — including every municipality — and businesses and non-profits with 50 or more employees in Ontario must make their public websites and web content conform to WCAG 2.0 Level AA. Since January 1, 2021, this has applied to all of their public websites and to web content published after January 1, 2012, with two exceptions: live captions and pre-recorded audio descriptions.
WCAG (the Web Content Accessibility Guidelines) is the international standard for web accessibility published by the World Wide Web Consortium (W3C). Ontario phased the requirement in:
- January 1, 2014 — new public websites, and the web content on them, had to meet WCAG 2.0 Level A. A "new" website includes an existing site that goes through a significant refresh.
- January 1, 2021 — all public websites and web content had to meet WCAG 2.0 Level AA, except success criteria 1.2.4 (live captions) and 1.2.5 (pre-recorded audio descriptions).
The rules cover websites and web-based applications you control, either directly or through a contract that lets you modify them, and there is a limited exception where meeting a requirement is not practicable (for example, when the tools to do it aren't commercially available). Internal sites such as intranets are not covered, except for the Ontario government and Legislative Assembly, which follow their own stricter schedule.
WCAG 2.0 is still the version named in the regulation. The W3C has since published WCAG 2.1 (2018) and WCAG 2.2 (2023), and says content that conforms to WCAG 2.2 also conforms to 2.1 and 2.0. That makes WCAG 2.2 Level AA a sensible best-practice target: it meets Ontario's legal standard and adds newer success criteria that 2.0 doesn't include.
In plain terms, WCAG 2.0 Level AA means your website must be:
- Perceivable — all content can be seen, heard, or read by assistive technology. Images need alt text, videos need captions, and text must have sufficient colour contrast.
- Operable — every function works with a keyboard alone. Menus, forms, and links must be navigable without a mouse.
- Understandable — content is clearly written, forms provide helpful error messages, and navigation is consistent across pages.
- Robust — the site works reliably across browsers, devices, and assistive technologies like screen readers.
Who Needs to Comply?
- All Ontario municipalities — towns, cities, counties, and regional governments, regardless of how many employees they have
- Broader public sector — hospitals, school boards, colleges, universities, public transit
- Large businesses and non-profits — organizations with 50 or more employees in Ontario
- Small businesses and non-profits (1–49 employees) — not required to make their websites conform to WCAG. They still have other AODA duties, including accessibility policies, staff training, accessible customer service, and providing information — including what's on their website — in an accessible format or with communication supports when someone asks, without charging more than they would for the standard version. Building to WCAG anyway makes those requests easy to handle and has you ready if you grow past 49 employees.
Note for municipalities: Every Ontario municipality is a designated public sector organization, so the website rules apply whatever your size. They cover web content published on your site after January 1, 2012, so treat the documents you post — council agendas and minutes, bylaws, and public notices, often as PDFs — as part of your website. Public sector organizations also have duties businesses don't, such as annual accessibility status reports and consulting people with disabilities on their multi-year accessibility plans.
Accessibility Compliance Reports Due December 31, 2026
As of September 2026: separate from the website rules, businesses and non-profits with 20 or more employees in Ontario must file an accessibility compliance report with the province every three years, and the current deadline is December 31, 2026. The report confirms you've met your current AODA requirements. It's filed online through the province's Accessibility Compliance Reporting Portal and certified by a senior officer with the legal authority to confirm it's complete and accurate.
When counting employees, include full-time, part-time, seasonal, and contract workers in Ontario — but not volunteers, independent contractors, or staff outside Ontario. Designated public sector organizations, including municipalities, file every two years; their last deadline was December 31, 2025, and a missed report still has to be filed. Filing is a legal obligation, and giving false or misleading information in a report is an offence under the AODA.
Most Common Accessibility Violations
Based on our audits of Ontario municipal and business websites, these are the issues we see most frequently:
- Missing alt text on images — screen readers cannot describe the image to visually impaired users
- Low colour contrast — normal-size text that doesn't meet the 4.5:1 contrast ratio against its background (large text needs 3:1)
- Missing form labels — input fields without proper labels are unusable with assistive technology
- No keyboard navigation — dropdown menus and interactive elements that only work with a mouse
- Inaccessible PDFs — scanned documents published as images inside PDFs, with no text layer
- Missing page titles and heading structure — pages without proper H1/H2/H3 hierarchy
- Auto-playing media — videos or audio that play automatically without user control
What Are the Consequences of Non-Compliance?
The AODA includes enforcement provisions. The province audits and inspects organizations, and organizations that fail to comply can face:
- Compliance orders — a director can order you to meet a requirement, or to file an overdue accessibility report, by a set deadline
- Administrative penalties — set by the regulation at $200 to $2,000 for individuals and unincorporated organizations and $500 to $15,000 for corporations, depending on how serious the contravention is and the organization's history. Only in the most serious repeat cases can a director apply the penalty daily, to a maximum of $50,000 (individuals and unincorporated organizations) or $100,000 (corporations).
- Fines on conviction — offences under the Act, such as failing to comply with a director's order or giving false information in an accessibility report, carry fines of up to $50,000 per day, or up to $100,000 per day for a corporation. Directors and officers who don't take reasonable care to prevent their corporation's offence can be fined personally, up to $50,000 per day.
- Human rights claims — the AODA doesn't replace the Ontario Human Rights Code, so people who face disability-related barriers can still bring a human rights claim
Beyond legal risk, an inaccessible website creates real barriers for community members with disabilities — residents who need to access public services, pay bills, read meeting agendas, or submit permit applications.
How to Check If Your Website Is Compliant
A proper accessibility audit combines automated scanning with manual review. Automated tools can catch technical violations like missing alt text and contrast issues, but manual testing is needed to evaluate keyboard navigation, screen reader compatibility, and content structure.
Key steps in an accessibility audit:
- Automated scan — crawl every page for WCAG 2.0 Level AA violations
- Manual review — test keyboard navigation, form usability, and screen reader output
- Document review — check that PDFs and downloadable files are accessible
- Prioritized report — categorize issues by severity and provide actionable fixes
How to Fix Accessibility Issues
Most accessibility issues are straightforward to fix once identified. Common remediation steps include:
- Adding descriptive alt text to all meaningful images
- Adjusting colour contrast ratios in your CSS
- Adding proper labels to all form fields
- Ensuring all interactive elements are keyboard-accessible
- Rebuilding PDFs with proper text layers and heading structure
- Adding skip-navigation links for keyboard users
- Implementing proper ARIA attributes where needed
The key is knowing exactly what needs to be fixed. Without a thorough audit, most organizations are guessing. If you are building or redesigning a website, our guide on why every Ontario business needs a professional website explains how to build accessibility in from the start. Our AODA compliance service covers the full process — from initial scan to remediation and ongoing monitoring.
Frequently Asked Questions
Who needs to comply with AODA website accessibility requirements?
Every Ontario municipality, whatever its size, and other designated public sector organizations such as hospitals, school boards, colleges, universities, and public transit must comply, along with every business and non-profit that has 50 or more employees in Ontario. Small businesses and non-profits with 1 to 49 employees are not required to make their websites conform to WCAG, but they still have other AODA duties, including accessible customer service, staff training, and providing information in an accessible format when someone asks.
What are the penalties for AODA non-compliance?
A director can order an organization to comply by a set date and impose administrative penalties. The regulation sets those at $200 to $2,000 for individuals and unincorporated organizations and $500 to $15,000 for corporations, based on how serious the contravention is and the organization's history; only in the most serious repeat cases can a penalty be applied daily, to a maximum of $50,000 or $100,000 respectively. Separately, offences under the Act — such as ignoring a director's order or giving false information in an accessibility report — carry fines on conviction of up to $50,000 per day, or $100,000 per day for a corporation. The AODA also doesn't replace the Ontario Human Rights Code, so people who face barriers can still bring human rights claims.
What are the most common AODA website accessibility violations?
The most common violations include missing alt text on images, low colour contrast (below the 4.5:1 ratio WCAG requires for normal-size text), missing form labels, no keyboard navigation for interactive elements, inaccessible PDFs without text layers, missing page titles and heading structure, and auto-playing media without user controls.
Related Articles
Need an Accessibility Audit?
ZABLEY provides AODA compliance audits for Ontario businesses and municipalities. We scan your website, identify every WCAG 2.0 Level AA violation, and deliver a detailed report with prioritized fixes.
Request a Free AssessmentKey Takeaways
- The AODA requires WCAG 2.0 Level AA websites from designated public sector organizations, including every municipality, and from businesses and non-profits with 50 or more employees in Ontario
- Small businesses and non-profits (1–49 employees) aren't required to meet WCAG, but must still provide information in an accessible format when asked
- Businesses and non-profits with 20 or more employees must file an accessibility compliance report by December 31, 2026
- Most websites have fixable issues — missing alt text, low contrast, and keyboard navigation are the most common
- An accessibility audit is the first step toward compliance
- Non-compliance can bring compliance orders and administrative penalties, and it excludes community members with disabilities