AODA and your Ontario municipality's website

What the law actually says

Ontario's accessibility statute is the Accessibility for Ontarians with Disabilities Act, 2005 — the AODA. The Act is a framework; the operative requirements sit in a regulation made under it, the Integrated Accessibility Standards Regulation (O. Reg. 191/11, usually shortened to the IASR).

Websites are dealt with in section 14 of the IASR. For designated public sector organizations, it says your internet websites and web content must conform with the Web Content Accessibility Guidelines (WCAG) 2.0, at Level AA, on a schedule: Level A for new websites by January 1, 2014, and Level AA for all internet websites and web content by January 1, 2021.

Three details in that section matter more than most people realize.

You are a "designated public sector organization" no matter how small you are. The IASR defines that term to mean "every municipality" and a list of other bodies. No population floor, no employee threshold. The 50-employee test you may have read about applies to private organizations. A township of 900 people is as squarely covered as Toronto.

The two exceptions are narrow and specific. Public sector organizations do not have to meet success criterion 1.2.4 (Captions, live) or 1.2.5 (Audio descriptions, pre-recorded). That is the entire list. Live-streamed council meetings do not need real-time captioning under this regulation; everything else in WCAG 2.0 AA still applies.

It reaches content published after January 1, 2012. Section 14 applies to websites and web content an organization controls directly or through a contract that permits modification, and to content published after January 1, 2012 — which is very nearly everything on your site, including the agendas, minutes, by-laws and budgets you post as PDFs. There is a qualifier ("except where meeting the requirement is not practicable," judged against things like the availability of commercial software or tools), but it is a narrow one — not a licence to leave a website inaccessible because fixing it is inconvenient.

Ontario has its own clock

This is worth being blunt about, because the search results are actively misleading Canadian clerks.

Almost all of the "municipal website accessibility deadline" content on the open web is American. It concerns Title II of the Americans with Disabilities Act and a rule made by the U.S. Department of Justice — a rule that set WCAG 2.1 AA as the standard, gave large entities an April 2026 date and smaller ones April 2027, and then, in April 2026, pushed both dates back by a year.

An Ontario clerk reading that could be forgiven for relaxing. Do not. The AODA is provincial legislation passed by the Legislative Assembly of Ontario, and nothing the U.S. Department of Justice does changes a word of it. There is no mechanism by which an American extension reaches your website. Your obligation is not being extended, because it is not pending — it commenced on January 1, 2021, and every day since has been a day on which your site was supposed to conform. The American deadline is still in the future. Yours is five and a half years in the past.

AODA and ADA Title II, side by side

Two practical consequences. First, a municipality that builds to WCAG 2.1 AA has more than satisfied the AODA: the W3C is explicit that "content that conforms to WCAG 2.1 also conforms to WCAG 2.0." Second, 2.1 AA is the level that covers both jurisdictions if you have any American exposure. That is the level we build to, and it is why our WCAG 2.1 AA checklist is a safe working document for an Ontario clerk even though the province asks for 2.0. The American picture in full is tracked in where the ADA Title II rule actually stands.

The compliance report — the obligation people forget

Unlike the American rule, Ontario asks you to tell it, in writing, that you are complying. Under the AODA, organizations file an accessibility compliance report with the province through a self-serve online form. The schedule is set out in the IASR: designated public sector organizations — you — file every two years.

Businesses and non-profits with 20 or more employees file every three years, and that is where a lot of the confusion comes from: the widely-cited December 31, 2026 deadline is the private-sector one, not yours. Ontario's reporting page lists the public sector deadline as December 31, 2025 — now passed — and tells organizations that missed it to file the 2025 report as soon as they are able. On the two-year cycle the next public sector report falls due at the end of 2027; confirm that on Ontario's reporting page before you diarize it, because it is the province's page that governs.

So the question for most Ontario clerks reading this in mid-2026 is not "when is my report due" but "did we file the one that was due last December?" It is worth walking down the hall and asking.

What happens if you don't file

Ontario says plainly that failing to complete your compliance report can lead to enforcement measures, which can include financial penalties. The mechanics run in stages: inspections and audits, then a director's order to comply, then money. Two different sets of numbers get quoted here, and they are routinely mixed up.

• Administrative monetary penalties are the everyday tool, set out in schedules to the IASR. For a corporation the amount runs from $500 to $15,000 per contravention, scaled by the severity of the impact and by your contravention history. For individuals and unincorporated organizations, $200 to $2,000.
• Offence fines are the sharp end, and they are what people mean when they cite six-figure numbers. Section 37 of the AODA makes it an offence to give false or misleading information in an accessibility report, or to fail to comply with a director's or Tribunal order. On conviction the maximum is $50,000 for each day the offence occurs or continues — or $100,000 for each day if the person is a corporation. A director or officer who fails in their duty to take reasonable care to prevent the corporation from committing that offence faces up to $50,000 per day personally.

Be precise about what triggers the big number. The $100,000-a-day maximum is not a fine for having an inaccessible website; it is the ceiling on conviction for an offence such as ignoring a director's order or misreporting. (And yes, it is the corporate figure that would apply to a municipality: under the Municipal Act, 2001, "the inhabitants of every municipality are incorporated as a body corporate.") Ontario's enforcement escalates. Ignoring the province is what makes it expensive; filing an accurate report is cheap.

Your other AODA obligations, in one place

The website standard is one requirement among several. The ones a clerk is usually accountable for:

• A multi-year accessibility plan — established, documented, posted on your website, available in an accessible format on request, and reviewed at least once every five years. Public sector organizations must do this in consultation with persons with disabilities and, where one exists, the accessibility advisory committee. An upper-tier municipality and its lower-tier municipalities may prepare a joint plan.
• An annual status report on progress against that plan, also posted and available in an accessible format on request. A yearly job, and separate from the compliance report you file with the province.
• An accessibility advisory committee, if your population is 10,000 or more. Section 29 of the AODA requires the council of every such municipality to establish one, and a majority of its members must be persons with disabilities. Below 10,000 the committee is optional, and two or more municipalities may establish a joint committee instead of each running their own.
• Accessible formats and communication supports on request, accessible feedback processes, accessible procurement, and training.

Notice how much of that list assumes a website you can actually publish to: a plan posted, a status report posted, feedback received accessibly. A content management system that fights you on all three is not neutral infrastructure.

A careful word about French

This one is frequently overstated, sometimes by vendors selling translation add-ons, so we will be careful.

Ontario's French Language Services Act gives a person the right to receive services in French from a government agency or institution of the Legislature — in a head or central office, or in an office located in or serving a designated area (the areas are set out in O. Reg. 272/25). "Government agency" is a defined term: ministries, bodies whose members are appointed by the Lieutenant Governor in Council, and organizations designated as public service agencies. Municipalities are not in that definition. Ontario's own guidance says it directly — if you need to go to a municipal office, "the law does not require them to provide services or information in French."

What the Act does do is give you the option. Under section 14, the council of a municipality in a designated area may pass a by-law providing that its administration be conducted in both English and French and that all or specified municipal services be made available in both languages. Once that by-law is in effect, residents have the right to deal with any office of the municipality in either language.

So the accurate framing is that French service is an obligation you may have chosen — or may be under community pressure to choose — rather than one the province has imposed. Plenty of Ontario municipalities publish bilingually regardless, because their residents are francophone and it would be strange not to.

Which is worth saying, because bilingual content is not a plugin for us. Every content type in a Munikit site carries English and French fields — pages, news, notices, agendas, staff directories — so a francophone resident gets a French page, not a machine translation of one. If your council ever passes that by-law, the site does not need rebuilding to honour it. More on our features page.

Practical first steps for an Ontario clerk

1. Find out whether the 2025 compliance report was filed. Before anything else. If it was not, file it — late is better than never, and the province says as much.
2. Check that your multi-year plan and your latest annual status report are actually posted, and that both are available in an accessible format on request. These are the cheapest items on the list and the most commonly missed.
3. Confirm your advisory committee obligation. Population 10,000 or more means a committee, with a majority of members who are persons with disabilities. If a neighbouring municipality is in the same position, a joint committee is expressly permitted.
4. Test the website against WCAG 2.0 AA — and distrust the automated report. Free scanners catch only machine-detectable failures. A clean scan is not conformance; keyboard operation, focus order, form labelling and document accessibility need a human.
5. Ask whether your platform can even get there. Some content management systems emit markup that no amount of staff diligence will make conformant, because the templates themselves are the barrier. If that is your situation, remediation is money spent renting a problem.

Where Munikit fits

Plainly, since you are on our website. We build municipal sites to WCAG 2.1 AA and test every page — which, as above, satisfies the AODA's WCAG 2.0 AA requirement with room to spare. Bilingual English/French content is built into every content type, not bolted on. The site can be hosted in Canada if data residency matters to your council. It is $17,500–$27,500 all-in, one-time, launched in 6–8 weeks, and you own the code — no annual platform licence, no escalator clause, which is a different conversation to have with your treasurer than the one subscription platforms invite.

We will not tell you that any website is permanently, perfectly compliant. Accessibility is a property of content as much as of code, and your staff will keep publishing content. What we will say is that the platform should never be the reason you fail — and that if it is, that is a solvable problem.

This page is a guide, not legal advice. It reflects the law as published on Ontario's e-Laws as of the currency date shown there (July 8, 2026). For a determination about your municipality's obligations — particularly your reporting status and any enforcement correspondence — speak with your accessibility lead, your solicitor, or the Accessibility Directorate of Ontario. If the regulation changes, we update this page and change the "last reviewed" date above.