Accessibility is an important part of doing business in Ontario. For organizations that serve the public, accessibility is not simply a matter of good design. It is also a legal responsibility under the Accessibility for Ontarians with Disabilities Act, commonly known as AODA.
The AODA was enacted in 2005 with the goal of identifying, removing, and preventing barriers for people with disabilities. It establishes accessibility requirements across areas such as customer service, employment, transportation, information and communications, and public spaces.
For websites and digital content, AODA compliance is closely connected to the Web Content Accessibility Guidelines, or WCAG. Understanding the relationship between these two standards can help Ontario organizations create more accessible websites and reduce compliance risks.
What Is AODA Compliance?
AODA compliance means meeting the accessibility requirements established under Ontario's Accessibility for Ontarians with Disabilities Act.
The legislation applies to organizations operating in Ontario and is designed to remove barriers that can prevent people with disabilities from accessing goods, services, employment, information, and public spaces. The AODA contains five main standards:
- Customer Service
- Information and Communications
- Employment
- Transportation
- Design of Public Spaces
The Information and Communications Standards are particularly important for website owners because they address accessibility of digital information, websites, applications, and web-delivered content.
AODA compliance is broader than website accessibility alone. Organizations may also have obligations related to employee training, accessibility policies, feedback processes, accessibility plans, and compliance reporting, depending on their type and size.
Who Needs to Comply With AODA in Ontario?
AODA applies broadly to organizations in Ontario, but specific requirements and deadlines can vary according to organization type and employee count.
Public-sector organizations of all sizes have AODA obligations. Private businesses and nonprofits are also subject to the Act. Employee thresholds can determine which specific requirements apply, particularly for website accessibility and reporting.
For digital accessibility, organizations with 50 or more employees have a specific requirement to make applicable public-facing web content conform to WCAG 2.0 Level AA. Private organizations with 20 or more employees also have accessibility compliance reporting obligations. Smaller organizations may have fewer reporting requirements, but that does not mean accessibility should be ignored.
When determining workforce size for relevant AODA obligations, organizations may need to consider full-time, part-time, seasonal, and contract workers.
Does AODA Apply to Websites?
Yes. AODA applies to certain website and digital content requirements through its Information and Communications Standards.
The legislation requires applicable organizations to make their public web content accessible. This includes websites and web-based applications, while accessibility considerations can also extend to digital documents and other forms of online communication.
For organizations covered by the relevant web accessibility requirements, the technical benchmark is WCAG 2.0 Level AA. The goal is to ensure people with disabilities can perceive, operate, understand, and interact with digital content. Website accessibility is therefore an important part of an organization's broader AODA compliance program.
What Are the AODA Website Requirements?
AODA website requirements are based primarily on WCAG 2.0 Level AA. Rather than treating accessibility as a separate feature, organizations should consider accessibility throughout their website's design, development, content, and maintenance processes.
Some important areas include:
Alternative Text for Images
Images should have meaningful alternative text when they convey information. This allows screen reader users to understand content that would otherwise be inaccessible.
Keyboard Accessibility
Website functions should be usable without relying exclusively on a mouse. Users should be able to navigate interactive elements using a keyboard and receive a clear indication of where the keyboard focus is located.
Color and Contrast
Text and important visual information should have sufficient contrast so that users with low vision or color-related disabilities can distinguish content effectively.
Accessible Videos
Multimedia should be provided in accessible formats. Captions and transcripts can help people who are deaf or hard of hearing, while other WCAG requirements address access to audiovisual information.
Clear Structure and Semantic HTML
Headings, labels, links, forms, and other interface elements should have meaningful structures and relationships. Proper semantic markup also helps assistive technologies interpret website content.
Visible Focus Indicators
Keyboard users need to be able to see which element currently has focus. A clearly visible focus indicator makes navigation easier and reduces confusion.
Accessible Forms
Forms should have properly associated labels, clear instructions, understandable error messages, and controls that can be operated using a keyboard and assistive technology.
Accessible Digital Documents
AODA accessibility efforts should not stop with HTML pages. Organizations should also review PDFs, forms, videos, images, and other digital content that users need to access.
Is AODA Compliance Mandatory in Canada?
AODA compliance is mandatory for organizations covered by Ontario's legislation, but it is important to understand that AODA is an Ontario law, not a single accessibility law covering every organization across Canada.
Organizations operating in Ontario may have AODA obligations. Organizations under federal jurisdiction may also be subject to the Accessible Canada Act and other applicable federal requirements. Other provinces have their own accessibility legislation.
Therefore, saying that "AODA is mandatory throughout Canada" would be inaccurate. AODA applies specifically to Ontario, while other Canadian jurisdictions have their own accessibility frameworks. For eligible Ontario organizations, compliance is a legal requirement. The AODA also gives the government enforcement authority, and serious violations can result in significant monetary penalties.
What WCAG Level Is Required for AODA?
The AODA's website accessibility requirement is based on WCAG 2.0 Level AA for applicable organizations.
WCAG has three conformance levels:
- Level A: The basic level of accessibility requirements.
- Level AA: Builds on Level A and addresses a broader range of accessibility barriers.
- Level AAA: The highest level of WCAG conformance.
To meet Level AA, a website must meet the applicable Level A and Level AA success criteria. The AODA specifically references WCAG 2.0 Level AA for applicable web content, with limited exceptions concerning certain multimedia criteria.
WCAG 2.2 is a newer version of the guidelines and is increasingly being used as a best-practice benchmark. However, organizations should distinguish between the current legal requirement and newer accessibility practices when assessing their compliance obligations.
How Do I Check If My Website Is AODA Compliant?
Checking a website for AODA compliance should involve more than running an automated scanner.
A practical approach includes the following steps:
- Determine Your AODA Obligations
Start by identifying your organization type, number of employees, and applicable AODA requirements. This determines which accessibility and reporting obligations apply to your organization.
- Run an Automated Accessibility Scan
Automated accessibility testing can identify common problems such as missing alternative text, certain color contrast problems, form issues, and other detectable WCAG violations. However, automated testing cannot identify every accessibility barrier.
- Perform Manual Testing
Manual testing is essential. Test your website using keyboard-only navigation and assistive technologies such as screen readers. This can reveal issues that automated tools cannot reliably detect. Testing with people with disabilities can provide additional insight into real-world usability.
- Review Digital Content
Check more than your main web pages. Review PDFs, videos, images, forms, menus, interactive components, and other digital content that visitors need to use.
- Document Accessibility Issues
Maintain a record of identified accessibility problems and the steps taken to resolve them. This creates a more organized accessibility program and helps your team monitor progress.
- Conduct Regular Reviews
Accessibility is an ongoing process. New website content, design changes, plugins, applications, and updates can introduce new barriers. Regular testing helps organizations identify and address those problems. An accessibility statement can also provide users with information about your accessibility efforts and a way to report barriers or request assistance.
What Is the Difference Between AODA and WCAG?
AODA and WCAG are closely related, but they are not the same thing.
AODA is legislation. It is an Ontario law that establishes accessibility obligations for organizations and covers several areas, including customer service, employment, transportation, information and communications, and public spaces.
WCAG is a technical accessibility standard. Developed by the World Wide Web Consortium, WCAG provides specific criteria for making websites and digital content more accessible. Its principles are organized around four concepts: Perceivable, Operable, Understandable, and Robust.
The relationship can be summarized simply:
AODA = Ontario accessibility law
WCAG = Technical guidelines used to meet web accessibility requirements
For applicable Ontario organizations, AODA incorporates WCAG 2.0 Level AA as the technical benchmark for relevant web content. Therefore, testing a website against WCAG is an important part of assessing its AODA website compliance.
How WebMax Can Help With AODA Website Accessibility
To check your website for AODA-related accessibility issues, start by evaluating it against the applicable WCAG requirements. A practical first step is to use the WebMax Website Accessibility Checker, which can scan a website and identify common accessibility problems such as missing alt text, poor color contrast, improper heading structures, missing ARIA labels, keyboard navigation issues, and unlabeled form fields. WebMax provides an accessibility report and score that can help you understand which areas require attention.However, an automated scan should not be treated as proof that a website is fully AODA compliant. WebMax recommends combining automated testing with manual evaluation, including keyboard-only navigation, screen reader testing, and human review. For organizations that need additional assistance, WebMax also offers custom accessibility audits and remediation services that can provide detailed findings, remediation plans, and ongoing support.
A simple process is to scan your website, review the accessibility issues, prioritize and remediate the identified barriers, and then conduct manual testing and regular monitoring. This approach can help Ontario organizations work toward meeting the WCAG-based web accessibility requirements relevant to AODA while maintaining accessibility as the website changes over time.
Final Remarks from Webmax
AODA compliance is an important responsibility for organizations operating in Ontario. While the Act covers much more than websites, digital accessibility is a major part of its Information and Communications Standards.
For applicable organizations, WCAG 2.0 Level AA provides the key technical benchmark for website accessibility. Organizations should combine automated scans with manual testing, review digital documents and multimedia, address identified barriers, document remediation work, and regularly reassess their websites.
Most importantly, AODA compliance should not be viewed as a one-time website project. Accessibility needs to remain part of ongoing website design, development, content creation, testing, and maintenance. A consistent accessibility program can help organizations provide a better digital experience while meeting their legal responsibilities in Ontario.