AODA Website Compliance: A Complete Guide for Ontario Businesses (2026)

Every image, icon, chart, and graphic on your website must have a text alternative that conveys the same information. Screen readers used by blind and low-vision visitors read this alt text aloud. Without it, images are invisible to these users — they hear only the file name or nothing at all.

• Write alt text that describes what an image communicates, not just what it looks like
• Decorative images that add no content should use alt="" so screen readers skip them
• Charts and graphs need a text summary of the data they display — not just "sales chart"

Users with motor impairments often cannot use a mouse. They navigate entirely by keyboard, using Tab to move between elements and Enter or Space to activate them. Every interactive element — buttons, menus, dropdowns, modals, forms — must be reachable and usable from the keyboard alone. Focus must always be visible so users know where they are on the page.

• Open your website and press Tab repeatedly — every clickable element must receive a visible focus ring
• Never use CSS "outline: none" without adding an alternative visible focus style
• Modals and dialogs must trap focus inside them while open and return focus to the trigger element when closed

Low-contrast text is the most widespread accessibility failure on the web — affecting 79% of sites globally. For users with low vision, color blindness, or age-related vision changes, text that blends into its background is effectively invisible. WCAG 2.0 AA requires a contrast ratio of at least 4.5:1 for normal body text and 3:1 for large text (18pt+ or 14pt+ bold).

• Use the free WebAIM Contrast Checker to test any text/background color combination before publishing
• Light gray text on white — common in modern designs — almost always fails
• Buttons, navigation items, and form labels are all subject to the same contrast requirements as body text

Any video on your website that contains spoken audio must include synchronized closed captions. This is not optional under AODA — it is a hard requirement for all organizations. Auto-generated captions from YouTube or Vimeo are a start, but they are frequently inaccurate, especially for technical terms, product names, and numbers. All captions must be reviewed and corrected before publishing.

• Review auto-captions carefully — error rates can exceed 20% for non-standard vocabulary
• Caption burn-in (text baked into the video file) does not satisfy AODA — captions must be togglable
• Audio-only content like podcasts requires a full text transcript published alongside the media

Screen reader users navigate web pages by jumping between headings — it is one of the fastest ways to scan a long page. When headings are missing, skipped (jumping from H1 to H4), or used purely for visual styling, navigation breaks entirely. Every page needs exactly one H1 describing the page topic, followed by H2 for major sections and H3 for subsections.

• Never skip heading levels — H1 → H2 → H3 is correct; H1 → H3 is not
• Do not use headings to make text look bigger — use CSS for visual styling
• Every page should have exactly one H1 that matches or closely reflects the page title

Placeholder text inside an input field disappears the moment a user starts typing. For screen reader users and people with cognitive disabilities, this creates confusion mid-entry — they lose track of what the field is asking for. Every form field must have a persistent visible label positioned above the input. Required fields must be identified with both a visual marker and text, not color alone.

• Never use placeholder text as a substitute for a proper field label
• Label elements must be programmatically associated with their input using the "for" and "id" attributes
• Error messages must name the specific field and explain exactly what went wrong and how to fix it

Screen reader users can generate a list of every link on a page to navigate quickly. If every link says "click here", "read more", or "learn more", that list is useless — they cannot tell where any link leads without reading the surrounding paragraph. Every link must make sense when read in isolation, with no surrounding context needed.

• Replace "click here to view our accessibility report" with "view our 2026 accessibility report"
• If a link opens in a new tab, add "(opens in new tab)" to the link text or an aria-label
• Icon-only buttons and links must have an accessible name via aria-label or visually hidden text

AODA's Information and Communications Standard explicitly covers documents published on your website, not just web pages. PDFs must include tagged structure (headings, lists, tables), selectable text rather than scanned images, and a meaningful reading order. A scanned PDF is just an image — screen readers cannot extract any content from it at all.

• Use Word or InDesign's built-in "Accessible PDF" export rather than printing to PDF
• Run all PDFs through Adobe Acrobat's Accessibility Checker before publishing
• For critical documents, consider publishing an accessible HTML version alongside the PDF

Does AODA apply to my business if I am not based in Ontario?

AODA applies to organizations that have employees in Ontario or that serve Ontario customers through their digital products. If your website is accessible to Ontario residents and you conduct business with them, the Information and Communications Standard applies to you — regardless of where your head office is located.

What is the difference between WCAG 2.0 and WCAG 2.1?

WCAG 2.1 (2018) adds 17 new success criteria to WCAG 2.0 (2008), focusing particularly on mobile accessibility, low vision, and cognitive disabilities. AODA currently mandates WCAG 2.0 AA. Meeting WCAG 2.1 AA automatically satisfies all WCAG 2.0 AA requirements — so building to 2.1 AA covers you for both AODA and US ADA requirements simultaneously.

What are the actual fines for AODA non-compliance?

Fines under AODA reach up to $50,000 per day for individuals and up to $100,000 per day for corporations and unincorporated organizations. In practice, the Ontario government typically begins with compliance orders before issuing fines, but organizations that ignore orders face escalating penalties.

My business has fewer than 50 employees. Do I still need to comply?

Yes — but with slightly different requirements. Small private sector organizations (1–49 employees) are required to meet WCAG 2.0 Level A (the lower tier) for websites. They are also encouraged to reach Level AA. The mandatory compliance reporting requirement applies to organizations with 20+ employees.

Can I use an accessibility overlay widget to comply with AODA?

No. Overlay tools that inject an accessibility toolbar onto your site do not constitute compliance and have been repeatedly challenged in courts across North America. They do not fix the underlying code and often create new barriers for screen reader users. AODA compliance requires fixing the actual source code and content of your website.

How often do I need to file an AODA accessibility compliance report?

Private sector and non-profit organizations with 20 or more employees must file every three years using the Ontario government's online compliance reporting tool. Public sector organizations file every two years. The report asks you to confirm that your organization has met its obligations under each AODA standard.