Key Takeaways
- AODA's digital requirements apply to Ontario organizations with 50+ employees — new websites must meet WCAG 2.0 Level AA, with the private sector deadline for new content having passed in January 2014.
- WCAG 2.0 Level AA has four pillars: Perceivable, Operable, Understandable, and Robust — most Ontario website failures occur in Perceivable (missing alt text) and Operable (keyboard navigation).
- The most common AODA failures on Ontario business websites are: missing alt text on images, insufficient text-to-background colour contrast, menus that can't be navigated by keyboard, and unlabelled form fields.
- Accessibility improvements generally benefit all users — better contrast, clear labels, and keyboard navigation improve usability for everyone, not just users with disabilities.
Ontario passed the Accessibility for Ontarians with Disabilities Act in 2005 with a stated goal of making Ontario fully accessible by 2025. The AODA's digital requirements — specifically the Web Content Accessibility Standards within the Integrated Accessibility Standards Regulation — set out what Ontario businesses must do to make their websites usable by people with disabilities. The requirements are based on WCAG 2.0 Level AA, an international standard developed by the World Wide Web Consortium. Many Ontario businesses are aware that AODA exists but uncertain about what it actually requires for their website, whether it applies to them, and what the practical steps to compliance look like. This is understandable — the legislation references WCAG 2.0, which is a technical document, and AODA enforcement has historically been less visible than the underlying compliance obligations. The result is widespread non-compliance, particularly among private sector organizations. As a designer who builds websites for Ontario businesses, I see AODA compliance failures in the majority of sites I audit — and most of them are fixable without rebuilding the site from scratch.
Definition: WCAG 2.0 Level AA
WCAG 2.0 (Web Content Accessibility Guidelines version 2.0) is an international standard developed by the World Wide Web Consortium (W3C) that defines how web content should be made accessible to people with disabilities. The guidelines are organised around three conformance levels: Level A (minimum accessibility), Level AA (standard accessibility — required by most accessibility laws including AODA), and Level AAA (enhanced accessibility). Level AA includes all Level A requirements plus additional criteria around colour contrast, keyboard focus visibility, live audio captions, and error identification in forms. AODA's IASR regulation mandates Level AA conformance for Ontario organizations subject to the legislation.
Which Ontario Businesses Must Comply with AODA Web Standards
AODA's web accessibility requirements apply to all public sector organizations and to private sector and non-profit organizations with 50 or more employees — but smaller organizations still carry obligations under the Ontario Human Rights Code.
Ontario's IASR divides organizations into categories that determine their accessibility compliance timelines. Public sector organizations (government agencies, public universities, hospitals) had the earliest deadlines — new or refreshed internet and intranet websites required to meet WCAG 2.0 Level AA from January 1, 2014. Large designated public sector organizations had to make all websites (including older content) conform to WCAG 2.0 Level A by January 1, 2012, and Level AA by January 1, 2014.
Private sector and non-profit organizations with 50 or more employees had a compliance obligation for new websites by January 1, 2014. All internet websites — including legacy content — must meet WCAG 2.0 Level AA by January 1, 2021, except where doing so is not technically feasible. Small private sector organizations (1–49 employees) are required to make new websites accessible but have reduced obligations on legacy content.
Critically, even Ontario businesses that fall below the AODA threshold aren't fully protected from accessibility obligations. The Ontario Human Rights Code prohibits discrimination on the basis of disability, and courts and tribunals have found that inaccessible websites can constitute a failure to accommodate people with disabilities. An Ontario business with 30 employees whose website is unusable with a screen reader is not facing AODA penalties — but could face a human rights complaint. Best practice is to treat WCAG 2.0 Level AA as the standard for any Ontario business website, regardless of size.
The Most Common AODA Accessibility Failures on Ontario Business Websites
The majority of Ontario business websites fail on a consistent set of WCAG 2.0 Level AA criteria — most of which are correctable without rebuilding the site.
Missing or inadequate image alt text is the single most common failure. Every image that conveys meaningful information — a product photo, a team member headshot, an infographic — requires an alt attribute that describes the image content for screen reader users who can't see it. Decorative images (background textures, dividers) should have empty alt attributes (`alt=""`) so screen readers skip them. Many Ontario websites have images with no alt text at all, or with unhelpful alt text like 'image1.jpg' or 'photo.' This is a straightforward fix in WordPress — accessible alt text can be added to every image in the Media Library.
Colour contrast failures are the second most common issue. WCAG 2.0 Level AA requires a contrast ratio of at least 4.5:1 between text and its background for normal-sized text, and 3:1 for large text (18pt regular or 14pt bold and above). Many Ontario business websites use light grey text on white backgrounds, dark text on coloured backgrounds that look contrasty visually but fail the mathematical ratio test, or reverse-out white text on medium-coloured buttons that don't meet the minimum. The WCAG Contrast Checker (freely available online) calculates ratios from any two hex colour codes — running your site's primary colour combinations through it takes about 15 minutes.
Keyboard navigation failures affect users who navigate websites without a mouse — including people with motor disabilities and power users. Every interactive element on a website (navigation menus, buttons, form fields, modal windows, dropdowns) must be accessible and operable using only the Tab, Enter, Space, and arrow keys. Common failures include: dropdown navigation menus that only open on mouse hover, modal windows that trap keyboard focus (pressing Tab cycles through all background elements rather than just the modal), and form submit buttons that don't respond to the Enter key. These failures often require CSS and JavaScript fixes but are addressable without a full site rebuild.
- Missing alt text on images — add descriptive alt text to all meaningful images in WordPress Media Library
- Insufficient colour contrast — check all text/background combinations with a WCAG contrast checker tool
- Keyboard-inaccessible navigation — ensure all menus, dropdowns, and interactive elements work without a mouse
- Unlabelled form fields — every input must have an associated `<label>` element (not just placeholder text)
- Missing skip navigation link — add a 'Skip to main content' link at the top of each page for screen reader users
A Practical Path to AODA Compliance for Ontario Business Websites
Most Ontario business websites can reach WCAG 2.0 Level AA compliance through a targeted audit and remediation process — without a complete rebuild.
Start with an automated audit using a tool like WebAIM's WAVE (web.webaim.org) or the axe browser extension. These tools catch a significant percentage of technical accessibility failures — missing alt text, contrast failures, missing labels, heading structure problems — and flag them with descriptions of the failure and how to fix it. Automated tools can't catch everything (some accessibility failures require human testing) but they identify the most common and most critical issues quickly. Running a WAVE audit on your Ontario business website homepage takes under a minute.
After the automated audit, do a manual keyboard navigation test: close your mouse and try to complete a typical user journey on your site using only your keyboard. Can you open and navigate your main menu? Can you fill out and submit your contact form? Can you activate every button and CTA? If any of these tasks fail, you've identified an operability issue that needs fixing. This test takes 10–15 minutes and consistently surfaces problems automated tools miss.
For WordPress-based Ontario business websites, several plugins help address AODA compliance issues without code changes: WP Accessibility adds skip navigation links and fixes common WordPress accessibility issues; WCAG 2.0 form plugins (Gravity Forms, WPForms) generate properly labelled, accessible forms by default; image alt text should be added through the WordPress Media Library rather than overriding it in individual posts. Theme selection matters significantly — accessibility-focused WordPress themes (those with the 'accessibility-ready' tag in the WordPress theme directory) build in keyboard navigation, proper heading hierarchy, and focus indicator styles from the start.
Experience Signal
Accessibility audits have become a standard part of our website assessment process at Webnixon. Of the last 15 Ontario business websites I audited heading into 2016, 14 failed at least three WCAG 2.0 Level AA criteria. The most common failure, by a significant margin, is colour contrast — particularly among sites that use light grey body text on white backgrounds as a design aesthetic. The design looks clean and modern in a well-lit office on a calibrated monitor; it's genuinely difficult to read for people with moderate vision impairment or in suboptimal viewing conditions (bright sunlight, low-end displays). The fix is rarely a dramatic visual change — moving from #999 to #767676 text on white barely looks different but goes from failing to passing 4.5:1 contrast. These are changes we can make in an afternoon. The businesses that approach accessibility as an impossibly complex undertaking are usually the ones who haven't started yet.
Frequently Asked Questions
Yes. Under AODA's Integrated Accessibility Standards Regulation (IASR), private sector and non-profit organizations with 50 or more employees were required to make new or significantly refreshed websites and web content conform to WCAG 2.0 Level AA by January 1, 2021. Organizations with 50+ employees must also make all internet websites (including legacy content) conform to WCAG 2.0 Level AA — except where technically infeasible — by January 1, 2021. Smaller private organizations (1–49 employees) have some requirements that apply to new websites but fewer obligations on legacy content. The Ontario government can issue compliance directives and, in cases of persistent non-compliance, administrative penalties.
WCAG 2.0 Level AA is a set of success criteria organized around four principles: Perceivable (content can be perceived by all users, including those using assistive technology), Operable (interface components work with keyboard navigation, not just mouse), Understandable (content and interface are clear and predictable), and Robust (content works reliably with current and future assistive technologies). In practical website terms, Level AA requires: alt text on all images, sufficient colour contrast (4.5:1 ratio for body text), keyboard-navigable menus and forms, form field labels, descriptive link text, and captions for pre-recorded video. Most Ontario business websites built before 2014 fail multiple Level AA criteria.
Under AODA, the Ontario government can designate an inspector to review compliance and issue compliance orders. Failure to comply with a compliance order can result in fines: up to $50,000 per day for corporations and up to $100,000 per day for corporations with directors or officers found to have authorized or participated in the contravention. In practice, the government has focused on large organizations and public sector bodies for enforcement. However, the legal exposure from AODA non-compliance is separate from the reputational and legal risk of discrimination complaints under the Ontario Human Rights Code, which can also apply when websites exclude users with disabilities.
Sources
Does Your Ontario Business Website Meet AODA Accessibility Standards?
Webnixon conducts accessibility audits for Ontario business websites and builds WCAG 2.0 Level AA compliant sites from the ground up. If you're unsure whether your site meets the standard, let's find out.
Get a Free Accessibility AuditAbout the author
Jim Yang
Marketing Manager
Jim oversees paid media and growth marketing at Webnixon, specializing in Google Ads, Meta advertising, and conversion rate optimization across B2B and B2C categories. He has managed multi-channel campaigns for businesses ranging from professional services to ecommerce retailers, consistently delivering cost-efficient lead generation against competitive benchmarks. He writes about paid advertising strategy, marketing measurement, and growth tactics for businesses.
Related Articles
Web Design
Web Design Trends Ontario Businesses Should Watch in 2026
Every year brings a wave of trend predictions, most of which are either obvious or impractical for the average Ontario small business website. This guide cuts through the noise to focus on the design directions that will actually affect how Ontario business websites perform in 2026 — from performance-first builds to AI-assisted personalisation and accessibility as a legal standard.
Web Design
What Makes a Homepage Actually Convert Visitors Into Customers?
Most business homepages look professional but fail to convert. The difference between a homepage that generates leads and one that just gets traffic comes down to six specific elements — and most businesses are missing at least three of them.
Web Design
How to Improve Website Page Speed: A Practical Guide for Ontario Businesses
Every extra second your website takes to load, you lose visitors. Studies show a one-second delay in page load time reduces conversions by 7%. This guide walks through the specific fixes that will make the biggest difference for a typical Ontario small business website.