A comprehensive guide to Digital Accessibility in Ontario
Obligations, penalties, and compliance under the accessibility for Ontarians with Disabilities Act (AODA, 2005)
The Accessibility for Ontarians with Disabilities Act (AODA, 2005) and its regulatory framework, the Integrated Accessibility Standards Regulation (IASR / O. Reg. 191/11), strictly govern access to digital information. The province’s objective is to eliminate digital barriers for the millions of Ontarians living with a disability.
This practical guide provides a detailed breakdown of all legal obligations imposed on organizations regarding websites, applications, and digital documents.
Which organizations are impacted by Ontario’s digital accessibility obligations?
Since January 1, 2021, the AODA requires that all public-facing web content be accessible if you are:
- A designated public sector organization; or
- A private business or non-profit organization with 50 or more employees.
Unlike federal regulations, this provincial mandate is universally applicable across all industries.
Find out if your organization is also subject to federal digital accessibility obligations
Which interfaces and documents must be accessible?
The regulations apply globally to all public-facing digital environments controlled by the organization:
- Public Websites: All public-facing websites, whether they are existing domains, brand-new sites, or platforms undergoing a major refresh.
- Web Content and Applications: Customer portals, online forms, transactional systems, and web-hosted applications.
- Downloadable Office Documents: All complex digital files (specifically PDFs, Word documents, or PowerPoint presentations) available for download on these websites. This obligation specifically targets documents originally published or uploaded after January 1, 2012.
- Interactive Kiosks: Software interfaces for physical self-service kiosks acquired by the organization must incorporate accessibility features (such as voice controls, high-contrast options, etc.).
How to comply with Ontario legislation regarding digital accessibility
To meet regulatory compliance requirements, organizations must adhere to technical standards, specific timelines, and reporting mandates.
The technical standard
The law designates the W3C’s Web Content Accessibility Guidelines (WCAG 2.0) Level AA as the legal standard (which inherently encompasses Level A requirements). Consequently, you must ensure that your digital content and interfaces comply with at least the Level A and AA criteria of the WCAG 2.0 framework.
Exceptions
Ontario regulations explicitly exempt public websites from two WCAG Level AA criteria:
- Criterion 1.2.4 (Live Captions) for real-time video streams.
- Criterion 1.2.5 (Audio Description (Prerecorded) for video content.
Training obligations
- The dates the training sessions took place.
- The exact number of individuals trained on those dates.
- The names of the participants.
When submitting your official Accessibility Compliance Report, one of the key indicators asks you to formally confirm that 100% of your staff has been trained and that this registry is kept up to date.
Contact us to discover our catalogue of e-learning solutions and tailored training programs.
Implementation and reporting deadlines
Because this declaration carries legal liability, it is imperative to report accurate information regarding your website’s accessibility levels and outline your roadmap for addressing any non-compliance issues.
Connect with our experienced auditors to navigate this highly technical process.
Admissible exemptions
The law allows exemptions based on technical feasibility (where it is “not practicable”). An organization may be exempted from making a specific element accessible only if:
- The required technology does not exist or does not allow for the source code to be adapted.
- The organization has no direct control over the tool (e.g., non-modifiable third-party proprietary software).
Requirement for Alternative Formats: If a technical exemption is invoked, the organization is legally required to provide an accessible alternative (e.g., a dedicated telephone assistance line or manual text transcriptions) upon request, at no additional cost, and within a reasonable timeframe.
What are the penalties for non-compliance with digital accessibility obligations?
The AODA features a progressive but financially significant enforcement framework designed to ensure organizational compliance.
Administrative penalties (Common infractions)
Overseen by the Accessibility Directorate of Ontario, these flat-rate penalties apply following an enforcement audit or a failure to file the required multi-year compliance report:
- Minor Infractions / Failure to Report: Fines generally start at $500 CAD for a first-time, unintentional omission.
- Major Infractions: In cases of deliberate non-compliance with standards or a refusal to train staff, penalties can reach up to $15,000 CAD by administrative order.
Maximum penalties (Persistent non-compliance)
In cases of flagrant bad faith, repeat offences, or a refusal to comply with an AODA inspector’s orders, the matter can be escalated to court, where judges can hand down cumulative daily fines:
- For Corporations (Corporations / Legal Entities): Up to $100,000 CAD per day for a continuing offence.
- For Directors and Officers: Personal liability may be incurred, subject to a maximum fine of $50,000 CAD per day.
How to make your website accessible
Organizations must be compliant with WCAG 2.0 Level AA. This means that 100% of Level A and AA criteria must be fully satisfied. We recommend the following operational framework to ensure total compliance:
Step 1: Mapping and sampling
Inventory all of your digital properties. Select a representative page sample that includes all layout templates and content types. This sample must feature essential, high-traffic pages such as the homepage, sitemap, contact forms, checkout pathways, help pages, and legal notices.
Step 2: Initial technical audit
Conducting a rigorous WCAG audit requires a comprehensive mastery of the guidelines and testing methodologies. The auditor must possess strong core knowledge of HTML and CSS, be able to locate defects directly in the code, and be proficient with testing tools and browser extensions. Furthermore, the auditor should be fluent in operating assistive technologies (such as screen readers, voice controls, and keyboard-only navigation) and possess a deep understanding of the real-world barriers faced by users with disabilities.
Note that automated testing tools alone cannot deliver a fully valid WCAG audit. While some tools can flag trends or high-level issues, they generate numerous false positives and miss 50% to 70% of actual accessibility errors. Most importantly, automated tools cannot help you build or prioritize a precise remediation roadmap.
Contact us today to speak with one of our experienced WCAG auditors.
Step 3: Code and UI remediation
Because technical deadlines have already passed for Ontario organizations, there is no time to lose in fixing accessibility bugs on your sites.
When you partner with our team for a professional WCAG audit, we extract an actionable, prioritized roadmap. This framework identifies priorities based on critical user journeys and major technical roadblocks. We can also prioritize remediation efforts based on the direct user impact relative to specific disability profiles and your priority demographics (age group, sociodemographic targets, etc.).
This allows us to deliver a realistic remediation plan tailored to your budget and resource constraints, whether scoped over a few months or multiple years.
Our team can support your internal teams throughout this lifecycle, from drafting technical specifications to production deployment during development sprints. We also frequently collaborate with third-party web and design agencies that may lack the internal technical expertise required to execute complex accessibility remediation.
Step 4: Team training
In accordance with Section 7 of the IASR, you must train your developers, UI/UX designers, and content contributors on web accessibility best practices, and document evidence of this training in your official registry.
Accessibility training should be standard during the onboarding phase for all new hires. For long-standing employees, regular knowledge refreshers should be provided.
Explore our e-learning options and customized training programs to help support your team’s development.
How to make your office documents and PDFs accessible
PDFs and office documents (Word, Excel) posted online are often the most common compliance failures flagged during regulatory checks. The core objective is to ensure that a digital document can be parsed seamlessly by assistive software, such as NVDA or JAWS screen readers, used by individuals who are blind.
Document accessibility is primarily governed by two major frameworks: WCAG and the PDF/UA standard. To ensure maximum compliance, a rigorous document audit can also employ specialized methodologies to verify that PDF files meet the criteria outlined in modern accessibility standards.
We can make all your documents compliant.
And here are the steps to follow:
Step 1: Auditing the document
- Automated Analysis: Using checking tools built into your authoring software (like the Microsoft Word Accessibility Checker) or specialized auditing tools for finalized files (Adobe Acrobat Pro), you run an initial scan. The algorithm instantly flags blatant structural issues, such as missing tags, images without descriptive alternative text, or insufficient colour contrast ratios.
- Manual Analysis: Because automated software only captures 30% to 40% of document errors, human intervention is critical. An expert auditor manually reviews the document against PDF/UA and WCAG best practices to identify remaining non-compliance issues.
Step 2: Executing remediation
This step requires technical expertise and is best handled by a professional trained in document remediation workflows, whether working within the source files (e.g., InDesign, Microsoft Office suite) or directly patching finalized files in Acrobat Pro.
Step 3: Exporting the compliance report
To validate your document, you must submit the final PDF to an independent, universal validator such as PAC (PDF Accessibility Checker), which adheres to international testing protocols.
By leveraging our professional document auditing services, you will receive:
- A detailed analysis grid based on current compliance baselines, complete with your official accessibility score.
- A document that complies with accessibility standards.
- A live assistive technology demo (screen reader testing visualization).
- A formal PDF/UA compliance report generated via Adobe Acrobat Pro.
Book
a discovery call
Assess the extent of your digital accessibility, development, or branding needs
Get concrete ideas for areas of improvement
Benefit from our expert advice, in-depth experience, and strategic vision in the field
Free • 45 minutes • Online