What Is AODA Compliance?
AODA compliance means meeting the requirements of the Accessibility for Ontarians with Disabilities Act — Ontario legislation that requires organisations to make their websites, digital content, and services accessible to people with disabilities. For websites, the core requirement is meeting WCAG 2.0 Level AA standards.
If you are an Ontario organisation with 50 or more employees, AODA compliance is not optional. It is a legal obligation that has applied to non-profit and private sector organisations since January 2021. Penalties for non-compliance can reach $100,000 per day.
Free AODA Compliance Checklist
Before we go further — if you want a practical tool to audit your own website, we have put together a free 60-item AODA and WCAG 2.1 AA compliance checklist covering structure, visual design, keyboard navigation, forms, media, and technical requirements.
Download the free AODA Compliance Checklist (PDF) — no email required.
Who Does AODA Apply To?
AODA applies to all Ontario organisations with 50 or more employees — including non-profits, registered charities, associations, healthcare providers, and private businesses. Smaller organisations are exempt from enforcement but are strongly encouraged to comply as both a best practice and a legal risk management measure.
If your organisation receives federal government funding or is federally regulated, you may also be subject to the Accessible Canada Act (ACA), which references the higher WCAG 2.1 AA standard rather than WCAG 2.0.
What Does AODA Require for Websites?
Ontario Regulation 191/11, the Integrated Accessibility Standards Regulation (IASR), sets out the web content requirements under AODA. The three key requirements are:
WCAG 2.0 Level AA compliance. Your website must meet the Web Content Accessibility Guidelines at the AA level. This covers four principles: content must be Perceivable, Operable, Understandable, and Robust (POUR).
New and significantly refreshed content. Public sector organisations were required to comply by January 2016. Private and non-profit sector organisations with 50 or more employees were required to comply by January 2021. Any new website or significant refresh must meet these standards from launch.
Accessible feedback mechanisms. Organisations must provide accessible ways for users to give feedback about accessibility barriers on their websites — typically a clearly labelled contact method linked from the footer.
What Does WCAG 2.0 AA Actually Require?
The most commonly failed requirements on Canadian non-profit websites are:
Colour contrast. Normal text must have a contrast ratio of at least 4.5:1 against its background. Large text requires at least 3:1. Light grey text on white backgrounds — common in modern web design — frequently fails this test.
Alternative text. Every meaningful image must have descriptive alt text. Decorative images must have empty alt attributes so screen readers skip them entirely.
Keyboard navigation. Every interactive element — links, buttons, forms, menus — must be operable using a keyboard alone, without requiring a mouse. This is one of the most commonly failed and most impactful requirements.
Form labels. Every form field must have a programmatically associated label. Placeholder text alone does not meet this requirement — when a user starts typing, the placeholder disappears and screen readers cannot identify the field.
Heading structure. Pages must use a logical heading hierarchy (H1, H2, H3) that helps screen reader users navigate content efficiently. A page with multiple H1 tags or headings used for visual styling rather than structure will fail this requirement.
AODA Compliance Checklist: The Key Areas to Audit
When auditing your website for AODA compliance, work through these six areas systematically:
1. Structure and semantics. Each page has one H1, headings follow a logical hierarchy, the page language is declared, and landmark regions (header, nav, main, footer) are used correctly.
2. Visual design. Colour contrast meets the 4.5:1 ratio for normal text, focus indicators are visible, and information is never conveyed by colour alone.
3. Keyboard and navigation. All interactive elements work with keyboard only, no keyboard traps exist, and a skip navigation link is present at the top of each page.
4. Forms. Every field has a label, errors are specific and descriptive, and required fields are identified in text.
5. Images and media. All meaningful images have alt text, videos have accurate captions, and audio-only content has a text transcript.
6. Technical. HTML is valid, ARIA is used correctly, and the site has been tested with a real screen reader (VoiceOver on macOS, NVDA on Windows).
Download the full 60-item checklist with checkbox format ready to use in your next audit.
Why Pragmatica Recommends Building to WCAG 2.1 AA
AODA legally requires WCAG 2.0 AA, but the current international standard is WCAG 2.1. Building to 2.1 AA provides better coverage for mobile users, users with cognitive disabilities, and users with low vision — all audiences particularly relevant to non-profit services. It also satisfies the Accessible Canada Act for federally regulated organisations and future-proofs your compliance position as Ontario legislation evolves.
The practical difference between WCAG 2.0 and 2.1 is modest in effort but meaningful in outcome. We build all client websites to 2.1 AA as standard.
How to Achieve AODA Compliance
Start with a professional accessibility audit of your current website to establish a baseline. Automated tools like WAVE (wave.webaim.org) and axe catch approximately 30–40% of issues. Manual testing with a keyboard and screen reader is required to find the remainder — particularly keyboard traps, focus management failures, and dynamic content issues that automated tools cannot detect.
Work through remediation in priority order: structural issues first (heading hierarchy, form labels, keyboard navigation), then visual issues (contrast, alt text), then complex interactive content (modals, dropdowns, live regions).
Publish an Accessibility Statement on your website documenting your commitment, the standard you are working toward, any known issues under remediation, and a contact method for reporting barriers. This is a specific requirement under AODA's multi-year accessibility plan obligations.
The Cost of Non-Compliance
Penalties under AODA can reach $100,000 per day for organisations and $50,000 per day for individuals. Beyond financial risk, an inaccessible website excludes the very people your non-profit may be trying to serve — people with visual, auditory, motor, or cognitive disabilities who rely on assistive technologies to access information and services online.
The cost of building accessibility in from the start of a web project is significantly lower than the cost of retrofitting compliance after launch. For most non-profit website projects, WCAG 2.1 AA compliance adds 10–15% to the initial project cost when built in correctly. Retrofitting an existing site typically costs 30–50% of the original build cost.
Pragmatica builds WCAG 2.1 AA compliant websites for Canadian non-profits as a standard part of every project. Learn more about our accessibility services or get in touch to discuss an accessibility audit for your existing site.
