Ignore accessibility on an Ontario small business website and you've got two problems: customers who can't use the site, and legal exposure. WCAG 2.2 is the global accessibility standard. AODA is Ontario's regulatory layer on top of it. Together they set the bar for what a compliant website looks like in 2026. Here's the part that makes the work worth it: most issues that fail accessibility also hurt conversion and search, so fixing them pays twice. This is the practical checklist, sorted by priority, with no legal advice (talk to a lawyer for that).
Small business owners tend to skip accessibility because they assume it's a legal minefield only specialists can cross. It isn't. About 80% of accessibility problems are plain UX fixes any web developer or platform admin can ship. The 20% that needs real expertise is rarely the part that gets a business in trouble.
So this is the practical version. What to fix, in what order, no legal advice. For legal questions, ask an Ontario-licensed lawyer.
1. What does AODA actually require for websites?
The Accessibility for Ontarians with Disabilities Act (AODA) sets accessibility standards for organizations operating in Ontario. For websites, the relevant standard is the Information and Communications Standard, which points to WCAG 2.0 Level AA as the conformance target.
Coverage and timing break down like this:
- Public sector organizations face stricter, earlier requirements
- Private sector organizations with 50+ employees must meet WCAG 2.0 Level AA on new and significantly refreshed websites
- Smaller organizations have softer obligations but still sit under general accessibility expectations in the Ontario Human Rights Code
If you run a small business with under 50 employees, AODA is less prescriptive, but the spirit of the law still applies to you. And the Ontario Human Rights Code applies no matter your size. Accessibility-related discrimination claims don't require AODA-scale operations.
So aim for WCAG 2.2 Level AA across your whole site. The compliance payoff comes later. The UX payoff lands right away.
2. What does WCAG 2.2 Level AA actually mean in practical terms?
WCAG 2.2 has 50+ criteria. Most sort into 4 principles:
- Perceivable: users can see or hear your content
- Operable: users can navigate and interact
- Understandable: content is clear and predictable
- Robust: content works with assistive technologies
Level AA is the middle tier. Strict enough to cover most real users, loose enough that most sites can actually hit it.
These are the 12 criteria SMB sites violate most:
1. Insufficient color contrast (text vs background) 2. Missing alt text on images 3. Form fields without visible labels 4. Keyboard traps (you can tab in but not tab out) 5. Focus indicator missing or invisible 6. Auto-playing video or audio with no pause control 7. Time limits on forms or content 8. Inaccessible PDFs (image-based scans, no text layer) 9. Touch target size below 24x24 CSS pixels 10. Drag-only interactions with no alternative 11. Pages that break at 200% zoom 12. Inconsistent navigation across pages
Fix these 12 and you've covered roughly 80% of WCAG 2.2 Level AA.
3. What's the right order to fix accessibility issues?
Sort by how much harm each issue causes and how much effort it takes:
Tier one (do this week):
- Add alt text to every image. `alt=""` for decorative images, descriptive alt for content images.
- Audit color contrast with a free tool (WebAIM Contrast Checker). Fix any text under 4.5:1 ratio.
- Test the site with keyboard only (Tab, Shift-Tab, Enter, Space). Note any element you can't reach or interact with.
- Add visible focus indicators if your CSS strips them out.
Tier two (do this month):
- Label every form field with an associated `<label>` element
- Add skip-to-content links at the top of each page
- Set the lang attribute on `<html>` (en-CA for English Canadian sites)
- Test with a screen reader (VoiceOver on Mac, NVDA on Windows). Note where you get confused.
Tier three (do this quarter):
- Audit all PDFs and rebuild any that are image-based
- Fix time-limited interactions (auto-logouts, countdown timers)
- Test mobile touch target sizes (24x24 CSS pixels minimum, 44x44 ideal)
- Run an automated tool (axe DevTools, Lighthouse) and triage what's left
This sequence covers most SMB sites in 30 to 60 hours of work, often less.
4. What about the Ontario-specific requirements?
A few things apply specifically in Ontario:
- Public information must be accessible on request. If a customer asks for content in an alternate format (large print, audio), your business has to reasonably provide it.
- Customer service standards. Staff need training on serving people with disabilities. That's a process requirement, not a website one.
- Multi-year accessibility plans. Larger organizations have to publish them. Smaller ones should still write down their accessibility approach.
Run a Toronto business with both online and offline operations? Accessibility reaches your store too. Wheelchair access, signage, hearing assistance, all of it sits in the same compliance picture.
5. What tools should I use to test?
Three free tools cover most of what you need:
One: WebAIM WAVE (wave.webaim.org). Paste a URL. You get a visual annotation of every accessibility error and warning.
Two: axe DevTools (browser extension). Runs accessibility checks inside Chrome DevTools. Good for testing during development.
Three: Lighthouse Accessibility audit (built into Chrome DevTools). Runs alongside your regular Lighthouse score check.
Automated tools are the easy part. Manual testing matters more:
- Keyboard-only navigation. Tab through your whole site. Note what doesn't work.
- Screen reader test. Use VoiceOver (Cmd+F5 on Mac) to move through your homepage. Note where you'd get lost.
- Mobile zoom test. Grab a phone, crank the OS text size to maximum, browse your site. Note what breaks.
Automated tools catch maybe 40% to 60% of real issues. Manual testing catches the rest.
6. What about AI-generated content and accessibility?
Here's a problem that's getting bigger in 2026: sites pumping out AI-generated content with zero human accessibility review. The usual suspects:
- AI-generated images with no alt text
- AI-generated tables that look fine visually but have no proper header rows
- AI-generated forms that skip accessibility patterns entirely
If your team uses AI to generate content, add an accessibility-review step. The AI doesn't know your accessibility requirements unless you spell them out, and the output usually skips the basics.
7. What's the relationship between accessibility, SEO, and conversion?
All three overlap, hard:
- Alt text helps accessibility AND helps Google read your image content
- Proper heading hierarchy helps accessibility AND helps SEO
- Keyboard-friendly forms help accessibility AND convert better
- Color contrast and large touch targets help accessibility AND lift conversion
The same site that works for everyone tends to load faster, rank better, and convert more. Each fix you make feeds the next.
Start with one page
Pick your most-visited page (usually the homepage). Run WAVE. Fix the top 5 issues it flags. Move to the next page next week.
By month three your whole site is in better shape and your team knows the patterns cold.
