If you run a service business in the GTA and someone using a screen reader can’t book an appointment on your site, that’s not just a bad user experience. In Ontario, it can be a legal problem. AODA website compliance is one of the most overlooked requirements for local businesses, and enforcement has been picking up as more organizations hit the thresholds set out in the Integrated Accessibility Standards Regulation.
This isn’t a scare piece. Most of what AODA requires for websites is good practice anyway: clear navigation, readable text, forms that work with a keyboard. Here’s what actually applies to your business, what WCAG 2.0 Level AA means in plain terms, and how to check where your site stands.
What Is AODA and Does It Apply to Your Website
The Accessibility for Ontarians with Disabilities Act (AODA) requires public sector organizations and private businesses with 50 or more employees to make their websites conform to WCAG 2.0 Level AA. If your business crossed that headcount, your public-facing website and web content posted since January 1, 2012 falls under this requirement.
Businesses with fewer than 50 employees aren’t bound by the strict web content standard, but they’re not exempt from accessibility obligations entirely. The Ontario Human Rights Code still applies, and a customer who can’t use your booking form or read your pricing page can file a complaint regardless of company size. In practice, most contractors and local service businesses we work with are better off treating basic accessibility as a baseline, not a compliance checkbox to skip.
What WCAG 2.0 AA Actually Requires
WCAG 2.0 AA is a set of testable success criteria, not a vague standard. The parts that trip up local business websites most often come down to a handful of recurring issues.
| Common Issue | Why It Fails | Quick Fix |
|---|---|---|
| Images with no alt text | Screen readers can’t describe the image to the user | Add descriptive alt text to every meaningful image |
| Low contrast text on buttons | Text becomes unreadable for users with low vision | Use a contrast ratio of at least 4.5:1 for body text |
| Forms without labels | Screen reader users can’t tell what a field is for | Attach a visible label to every input field |
| Video with no captions | Deaf and hard-of-hearing users can’t follow the content | Add captions or a text transcript |
| Menus that only work with a mouse | Keyboard-only users can’t navigate the site | Test full site navigation using Tab and Enter only |
| Heading tags used for styling, not structure | Screen readers rely on headings to understand page structure | Use H1 through H3 in a logical order that matches content hierarchy |
None of this requires a rebuild. Most of it gets fixed at the template and content level, which is one reason it’s worth checking during any website redesign rather than treating it as a separate project later.
Why This Matters Beyond Legal Risk
Accessibility work overlaps with SEO and conversion more than most business owners expect. Alt text helps Google understand your images. Clean heading structure helps search engines and users both scan a page for the section they need. Forms with proper labels reduce abandonment because people aren’t guessing what a field wants. We covered a lot of this same ground from a pure conversion angle in our piece on website trust signals that turn visitors into booked jobs. Accessibility is the technical half of that same equation.
There’s also a simple math argument. Roughly 1 in 5 Ontarians identifies as having a disability. If your booking flow or contact form is hard to use for that share of the population, you’re turning away real customers before they ever reach the phone call or email that converts.
How to Check If Your Website Is Compliant
You don’t need a full audit to get a first read on where you stand. A few free tools will surface most of the common issues:
- WAVE (webaim.org/wave): browser-based scan that flags missing alt text, contrast issues, and form label problems on a page-by-page basis.
- axe DevTools: a browser extension developers use to catch accessibility issues during development, useful if you have any technical staff.
- Keyboard-only test: unplug your mouse and try to book an appointment on your own site using only Tab, Shift+Tab, and Enter. If you get stuck, so will a keyboard-only visitor.
- Mobile screen reader test: turn on VoiceOver (iPhone) or TalkBack (Android) and try to navigate your homepage and contact form. This also overlaps with the mobile UX issues we flagged in our guide to mobile website design for service businesses.
If your business is above the 50-employee threshold, a proper WCAG 2.0 AA audit against the full success criteria list is worth the cost of getting it done right, since a free scan only catches a portion of the actual requirements.
Steps to Fix Common Accessibility Gaps
- Run a WAVE scan on your five most-visited pages and fix flagged contrast and alt text issues first, since they’re usually the fastest wins.
- Rebuild any form that lacks visible labels, especially your main contact or booking form.
- Check your heading structure on every page template. One H1 per page, then H2s and H3s in order, no skipped levels.
- Test tab order on your navigation menu and fix any dropdown that traps keyboard focus.
- Add captions to any video content, including embedded testimonials or explainer videos.
FAQ
Does AODA apply to small businesses with under 50 employees?
The strict WCAG 2.0 AA web content requirement under AODA applies to organizations with 50 or more employees and to all public sector bodies. Smaller businesses aren’t bound by that specific standard, but they still fall under the Ontario Human Rights Code, which can apply to inaccessible services including websites.
What happens if my website isn’t AODA compliant?
Organizations covered by AODA can face compliance audits and financial penalties from the province for non-compliance. Beyond that formal risk, an inaccessible site simply loses customers who can’t complete a booking or contact form, which is a cost regardless of company size.
Is WCAG 2.0 AA the same as ADA compliance?
They’re related but not identical. ADA is a U.S. law and doesn’t specify a technical standard directly, though U.S. courts commonly reference WCAG 2.0 AA as the practical benchmark. AODA is Ontario’s law and explicitly requires WCAG 2.0 AA. Meeting WCAG 2.0 AA generally satisfies both.
How much does it cost to make a website accessible?
For most local service business sites, fixing the common issues (alt text, contrast, form labels, heading structure) is a matter of hours, not a rebuild. Costs rise if your site relies on custom interactive elements like sliders, modals, or booking widgets that need to be rebuilt for keyboard and screen reader support.
Accessibility issues rarely show up on a standard SEO report, but they affect the same pages that are supposed to be converting your traffic. Want to see where your site actually stands? Get a free SEO audit from Cadiente Digital and we’ll flag the technical and conversion issues holding your site back: https://cadientedigital.ca/seo-audit-services/