AODA Color Contrast Compliance for Ontario Websites

AODA-compliant colors are colors that meet WCAG 2.0 Level AA: at least 4.5:1 contrast for normal text and 3:1 for large text. Ontario's regulation points directly at WCAG, so the numbers are the same ones used worldwide, and the same checker works.

This guide is general information, not legal advice.

What the AODA actually says

The Accessibility for Ontarians with Disabilities Act is implemented through the Integrated Accessibility Standards Regulation (Ontario Regulation 191/11). Section 14 requires designated organizations to make their public websites and web content conform to WCAG 2.0 Level AA, with two exceptions that do not affect color: live captions (1.2.4) and pre-recorded audio description (1.2.5). The Ontario government publishes the requirements and who they apply to at ontario.ca.

It applies to the Ontario public sector and to private-sector and non-profit organizations with 50 or more employees in Ontario. If that is you, every public page, PDF and web app counts. Organizations under 50 employees are not bound by the web standard but are still covered by the Ontario Human Rights Code, which has been used in accessibility complaints.

Federally regulated organizations across Canada (banks, airlines, telecoms, Crown corporations, the federal government) fall under the Accessible Canada Act instead. Its standards work references WCAG 2.1, so building to 2.1 AA satisfies both regimes.

The exact WCAG numbers

• 4.5:1 for normal text (Success Criterion 1.4.3, Level AA).
• 3:1 for large text: 14pt (about 18.66px) bold, or 18pt (24px) regular.
• 3:1 for UI components and meaningful graphics such as icons, input borders, focus rings and chart lines (1.4.11, Level AA, added in WCAG 2.1).
• 7:1 and 4.5:1 at Level AAA (1.4.6); not required by any of the laws discussed here.
• Logos and purely decorative text are exempt; disabled controls are exempt.

WCAG 2.0, the version the AODA cites, has no contrast rule for UI components. WCAG 2.1 added the 3:1 rule (1.4.11). Meet it anyway; it costs nothing and the federal standard expects it.

Real pairs, measured

Where Ontario sites usually fail

• Bilingual toggles and footers set in light gray, treated as decoration when they are navigation.
• PDF forms and reports published on the site: the standard covers them, and they are rarely checked.
• Red-and-green status colors with no text label (fails 1.4.1, not just contrast).
• Hover-only link colors that pass on hover but not at rest.
• Treating the 50-employee threshold as a reason to skip it, then growing past it without a plan.

How AODA compliance is checked

Ontario enforces the AODA through self-reported compliance reports, filed on a multi-year cycle, plus audits and inspections by the Accessibility Directorate. An auditor does not read your CSS; they ask for evidence that the website meets WCAG 2.0 AA, and a dated contrast report is the most concrete evidence you can hand over. Director's orders and administrative penalties exist for non-compliance; the amounts and process are set out in the regulation, so check the current ontario.ca guidance rather than relying on figures quoted in blog posts.

In practice the pressure comes less from the Directorate and more from procurement. Ontario public bodies, universities, hospitals and school boards must buy accessible goods and services, so a vendor whose product fails contrast loses tenders. A short accessibility conformance report with measured ratios is often a bid requirement.

Bilingual and public-sector specifics

Many Ontario organisations publish in English and French. Both versions must meet the same contrast standard, and the language switcher itself is navigation, so it cannot be set in decorative light gray. Public bodies also tend to carry legacy PDF content; the AODA web standard covers documents published on the site, so statements, forms and annual reports need the same checks. If a PDF cannot be fixed, the regulation allows an accessible alternative on request, but that is a fallback, not a strategy.

When choosing brand colors, assign a darker text shade of each brand hue for links and labels, and keep the saturated version for headings and backgrounds behind white text that has been measured. A red like #D71920 passes for white text at about 5:1, which is why it works on buttons, but the same red on a light-gray card may not.

Edge cases

• Text over photos on hero banners: measure against the busiest part of the image or add a solid panel.
• Placeholder text is text; give it a passing color or use visible labels.
• Logos are exempt; the same brand color reused for body links is not.
• Embedded third-party tools (booking, payment, chat) are part of your site for compliance purposes.
• Live captions and audio description are the only WCAG 2.0 AA criteria the AODA excludes; nothing about color is excluded.

How to check your site

1. List every text style and its background: body, secondary, links, buttons, placeholders, footer, error and success states, dark mode if you have one.
2. Paste each pair into the contrast checker. It reports the ratio and AA/AAA status for normal and large text.
3. For pairs that fail, keep the hue and move only the lightness until the ratio passes. The palette generator shows tints and shades of your brand color so you can pick the nearest passing one.
4. If the brand colors came from a logo or mockup, pull the exact values with the image extractor rather than eyeballing them.
5. Check icons, borders and focus rings against their adjacent colors for 3:1.
6. Record the results. A dated table of pairs and ratios is the evidence an auditor, regulator or opposing counsel will ask for.

Ontario also requires an accessibility compliance report from designated organizations on a set schedule. Keep your contrast test results; they are the easiest part of that report to evidence.