Ontario’s Accessibility for Ontarians with Disabilities Act (AODA) requires organizations to meet defined web accessibility standards or face financial penalties. This AODA compliance checklist covers the key web content, design, and technical requirements your site must satisfy, so you can audit your current state, close the gaps, and demonstrate compliance with confidence.
What AODA Requires and Why It Matters for Your Website
The Accessibility for Ontarians with Disabilities Act establishes legally enforceable standards for how organizations in Ontario must make their digital content accessible to people with disabilities. For websites, the relevant requirements are drawn from the Web Content Accessibility Guidelines (WCAG) 2.0 Level AA, which define the technical and design standards that determine whether a site can be used effectively by people with visual, auditory, motor, and cognitive disabilities.
AODA compliance is not only a legal obligation for many Ontario-based organizations. It is also a business decision. Approximately 2.6 million people in Ontario live with a disability that affects how they interact with digital content. An inaccessible website excludes a significant portion of your potential audience and exposes your business to compliance risk as enforcement activities by the Ontario government have increased in recent years.
According to the Government of Ontario’s AODA documentation, private sector organizations with 50 or more employees and all public sector organizations are required to meet WCAG 2.0 Level AA standards for new and significantly refreshed websites.
At Conte Studios, accessibility is built into every website we design and develop. This checklist reflects the same standards we apply to every project we deliver.
AODA Compliance Checklist: Perceivable Content
Perceivable content means that all information and user interface components can be presented to users in ways they can perceive, regardless of their sensory abilities. This is the first and most foundational principle of WCAG 2.0.
Text Alternatives for Non-Text Content
Every image on your website must have a descriptive alt text attribute. Alt text allows screen readers to communicate the content of an image to users who cannot see it. Decorative images that convey no information should use an empty alt attribute (alt=””) so screen readers skip them. Images that convey meaningful information require descriptive alt text that communicates that meaning accurately.
Captions for Audio and Video Content
All pre-recorded video content that includes audio must have accurate captions. Captions provide the audio track in text form for users who are deaf or hard of hearing. Auto-generated captions from platforms like YouTube are not sufficient for compliance. They must be reviewed and corrected for accuracy before the content is considered compliant. Live audio content broadcast on the web must also provide real-time captions.
Sufficient Color Contrast
Text content must have a color contrast ratio of at least 4.5:1 against its background for normal-sized text and at least 3:1 for large text. This requirement exists because insufficient contrast makes text unreadable for users with low vision or color blindness. Test your site’s contrast ratios using a free tool like WebAIM’s Color Contrast Checker. Common failure points include light gray text on white backgrounds and colored text on similarly colored backgrounds.
Content Does Not Rely Solely on Color
Information conveyed using color alone is inaccessible to users who cannot perceive color differences. Error states in forms must use more than red coloring to communicate the problem. Charts and graphs must use patterns or labels in addition to color to distinguish data sets. Links within body text must be distinguishable from surrounding text by more than color alone, typically through underline formatting.
AODA Compliance Checklist: Operable Interface
An operable interface means that all functionality of the website can be operated through a keyboard alone, without requiring a mouse or touch screen. This is critical for users with motor disabilities who rely on keyboard navigation or assistive input devices.
Full Keyboard Accessibility
Every interactive element on your site, including navigation menus, buttons, forms, modal dialogs, carousels, and dropdown menus, must be fully operable using only a keyboard. Tab through your entire site manually. Confirm that every interactive element receives visible focus, responds to expected keyboard inputs, and does not trap keyboard focus in a way that requires a mouse to escape.
Visible Focus Indicators
Keyboard users navigate by moving focus between interactive elements. A visible focus indicator, typically a border or outline around the focused element, communicates to keyboard users where they currently are on the page. Many CSS resets and design frameworks remove default browser focus outlines for aesthetic reasons. This breaks keyboard accessibility. Custom focus indicators that meet contrast requirements are required for AODA compliance.
No Keyboard Traps
If a user navigates into a component using keyboard input, they must be able to navigate out of it using keyboard input alone. Modal dialogs, embedded widgets, and custom interactive components are the most common sources of keyboard traps. Test every interactive element for keyboard escape functionality before considering your site compliant.
Sufficient Time for Timed Content
If your site includes session timeouts, timed content, or auto-advancing carousels, users must have the ability to pause, stop, or extend the timing. Users who read slowly, use assistive technology, or have cognitive disabilities may require more time to process content than the default timing allows. Auto-playing content that cannot be paused is a common compliance failure.
AODA Compliance Checklist: Understandable Content
Understandable content means that information and the operation of the user interface must be comprehensible to users.
Identify the Page Language
The HTML lang attribute on every page must be set to the correct language of the page content. Screen readers use the lang attribute to select the appropriate pronunciation and reading rules. A page in English that is marked as French will be read with incorrect pronunciation, making it significantly harder to understand for screen reader users. This is one of the most common and most easily corrected accessibility failures.
Descriptive Error Messages for Forms
When a form submission fails, the error messages must identify the specific field that has an error, describe what the error is, and suggest how to correct it where possible. Error messages that say only “Please correct the highlighted fields” without specifying what is wrong or how to fix it fail this requirement. Screen reader users also need error messages to be programmatically associated with the fields they describe.
Consistent Navigation
Navigation components that appear on multiple pages must be presented in a consistent order and behave consistently. Users who rely on memory and pattern recognition to navigate, including many users with cognitive disabilities, depend on consistent navigation to use a site efficiently. Changing the order or behavior of navigation elements between pages without clear reason creates confusion and increases cognitive load.
Clear Labels for All Form Inputs
Every form field must have a descriptive, programmatically associated label. Placeholder text inside form fields does not satisfy this requirement because it disappears when the user begins typing, leaving the field without context. Use visible HTML label elements associated with each input via the for and id attributes, not placeholder text alone.
AODA Compliance Checklist: Robust Technical Implementation
Robust implementation means that content can be reliably interpreted by a wide variety of user agents, including assistive technologies. This involves correct HTML semantics and ARIA usage.
Valid, Semantic HTML
Properly structured HTML using semantic elements like nav, main, header, footer, article, and section allows assistive technologies to correctly interpret and navigate the page structure. Screen readers use these landmark elements to provide users with page navigation shortcuts. Non-semantic HTML that uses divs for everything requires manual ARIA role assignments to achieve equivalent accessibility.
ARIA Labels for Interactive Components
Custom interactive components like carousels, modal dialogs, accordions, and custom dropdown menus must include appropriate ARIA (Accessible Rich Internet Applications) attributes that communicate their role, state, and property to assistive technologies. An icon button with no text label must have an aria-label attribute. A modal dialog that opens must communicate that it is a dialog and manage focus correctly on open and close.
Accessible PDF and Document Downloads
If your site includes downloadable PDF documents, those documents must also meet accessibility standards. PDFs must include a logical reading order, proper heading structure, alt text for images, and be tagged so that screen readers can process them correctly. Scanned PDFs that are essentially images of text are not accessible without Optical Character Recognition and proper tagging. Our content and media page include document accessibility review as part of comprehensive content projects.
How to Audit Your Site Against This Checklist
Start with automated testing using a tool like WAVE (Web Accessibility Evaluation Tool) or Axe. These tools identify many of the most common WCAG failures automatically and flag the specific elements and pages that require attention. Automated testing catches approximately 30 to 40 percent of accessibility issues.
Manual testing is required for the remainder. Tab through your site using only a keyboard. Test with a screen reader such as NVDA (Windows) or VoiceOver (Mac and iOS). Review your color contrast ratios manually using a checker tool. Submit test forms and evaluate the error messages. Watch auto-playing content and confirm it can be paused.
For businesses in Ontario launching a new site or undertaking a significant site redesign, accessibility compliance review should be a standard part of the development process, not a post-launch correction. Our web design services incorporate AODA compliance into every project at the build stage.
According to the Rick Hansen Foundation Accessibility Certification program, businesses that proactively address accessibility demonstrate a commitment to inclusion that resonates with both customers and talent, beyond the compliance requirement itself.
Penalties for AODA Non-Compliance
Organizations that fail to meet AODA requirements face administrative penalties of up to $100,000 per day for corporations and up to $50,000 per day for individuals. Penalties are levied following the filing of complaints and subsequent investigation by the Accessibility Directorate of Ontario. The risk is not hypothetical. Enforcement activity has increased as compliance deadlines have passed and awareness of the law has grown among disability advocates.
For businesses that want expert guidance on building and maintaining an accessible site, our VIP Program provides the ongoing technical and design support to stay compliant as your site evolves.
Frequently Asked Questions
1. What does AODA require for websites?
AODA requires that websites meet the Web Content Accessibility Guidelines (WCAG) 2.0 Level AA standard. This covers four areas: perceivable content (text alternatives, captions, sufficient contrast), operable interface (keyboard accessibility, no traps, sufficient timing), understandable content (clear language, consistent navigation, descriptive errors), and robust implementation (valid HTML, ARIA usage, accessible documents).
2. Does AODA apply to small businesses?
AODA applies to all organizations in Ontario, including private sector businesses with one or more employees. However, the specific compliance requirements differ by organization size. Businesses with fewer than 50 employees have different deadlines and some reduced requirements compared to larger organizations. All businesses with a public-facing website should review the requirements applicable to their organization size
3. Can I use automated tools to check AODA compliance?
Automated tools like WAVE and Axe are useful starting points and will catch a significant number of common accessibility failures. However, automated testing alone cannot verify full AODA compliance. Many accessibility requirements, including keyboard operability, logical reading order, and the meaningfulness of alt text, require manual testing and human judgment. A complete compliance audit combines both automated and manual testing methods.
4. What is the difference between AODA and WCAG?
AODA is Ontario’s provincial accessibility legislation. WCAG (Web Content Accessibility Guidelines) is the international technical standard that AODA references and requires organizations to meet for web content. AODA specifies what organizations must do legally. WCAG specifies the technical criteria for web accessibility that satisfy that legal requirement. Complying with WCAG 2.0 Level AA means complying with the web accessibility component of AODA.
5. Do PDF documents on my website need to be accessible?
Yes. Documents available for download from your website, including PDFs, must meet accessibility standards under AODA. This means documents must have proper heading structure, correct reading order, alt text for images, and appropriate tagging so screen readers can process them. Scanned PDFs that are images of text are not accessible without additional remediation.
6. How often should I review my site for AODA compliance?
AODA compliance should be reviewed whenever significant new content, features, or design changes are added to the site. A comprehensive annual audit is a reasonable baseline. Sites that undergo frequent content updates or feature additions benefit from a more regular review cadence. Compliance is not a one-time milestone. It is an ongoing operational standard.
Build an Accessible Website That Meets AODA Standards.
Conte Studios builds websites that are accessible by design, not by afterthought. We incorporate AODA and WCAG compliance into every project from the ground up.
Book a strategy call — let’s talk about what your brand needs next.
Key Takeaways
- AODA requires Ontario organizations to meet WCAG 2.0 Level AA standards for web content. Non-compliance can result in penalties of up to $100,000 per day for corporations.
- All images must have descriptive alt text, or an empty alt attribute for decorative images.
- Text contrast ratios must meet 4.5:1 for normal text and 3:1 for large text.
- Every interactive element on the site must be fully operable using only a keyboard with visible focus indicators.
- Form fields require visible, programmatically associated labels. Placeholder text does not satisfy this requirement.
- The HTML lang attribute must be correctly set on every page for screen readers to select the appropriate language settings.
- Downloadable PDF documents must also meet accessibility standards including logical reading order and correct tagging.
- Compliance audits require both automated testing tools and manual testing including keyboard navigation and screen reader evaluation.
