Ontario small business websites have both a usability obligation and a legal exposure when accessibility is ignored. WCAG 2.2 is the global accessibility standard. AODA is Ontario's regulatory layer. The two together set the bar for what compliant websites look like in 2026. Most issues that fail accessibility also hurt conversion and search visibility, so the work pays double. This is the practical checklist, organized by priority, with no legal advice (consult a lawyer for that).
Accessibility is one of those topics small business owners avoid because they assume it's a legal minefield best handled by specialists. In practice, 80% of accessibility issues are practical UX fixes that any web developer or platform admin can implement. The 20% that requires expertise is rarely the part that gets a business in trouble.
This guide is the practical version. What to fix, in what order, with no legal advice. For legal questions, consult 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 references WCAG 2.0 Level AA as the conformance target.
Coverage and timing:
For small businesses with under 50 employees, AODA is less prescriptive but the spirit of the law applies. And the Ontario Human Rights Code applies regardless of business size — accessibility-related discrimination claims do not require AODA-scale operations.
Bottom line: aim for WCAG 2.2 Level AA across your site. The compliance benefit is downstream, but the UX benefit is immediate.
2. What does WCAG 2.2 Level AA actually mean in practical terms?
WCAG 2.2 has 50+ criteria. Most fall into 4 principles:
Level AA is the middle conformance tier — strict enough to cover most real users, lenient enough to be achievable for most sites.
The 12 most-violated criteria for SMB sites:
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 without 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 fail at 200% zoom 12. Inconsistent navigation across pages
If you fix these 12, you cover roughly 80% of WCAG 2.2 Level AA.
3. What's the right order to fix accessibility issues?
Prioritize by harm and effort:
Tier one (do this week):
Tier two (do this month):
Tier three (do this quarter):
This sequence covers most SMB sites within 30 to 60 hours of work, often less.
4. What about the Ontario-specific requirements?
A few requirements specific to Ontario:
For Toronto businesses with mixed online/offline operations, accessibility extends to your store as well. Wheelchair access, signage, hearing assistance — all part of the same compliance picture.
5. What tools should I use to test?
Three tools cover most needs, all free:
One: WebAIM WAVE (wave.webaim.org). Paste a URL. Get a visual annotation of all accessibility errors and warnings.
Two: axe DevTools (browser extension). Runs accessibility checks in Chrome DevTools. Good for in-development testing.
Three: Lighthouse Accessibility audit (built into Chrome DevTools). Runs as part of your regular Lighthouse score check.
Beyond automated tools, manual testing matters more:
Automated tools catch maybe 40% to 60% of real issues. Manual testing catches the rest.
6. What about AI-generated content and accessibility?
A growing concern in 2026 is sites pumping out AI-generated content with no human accessibility review. Common issues:
If your team is using AI to generate content, add an accessibility-review step. The AI does not know your accessibility requirements unless explicitly prompted, and the output often skips the basics.
7. What's the relationship between accessibility, SEO, and conversion?
Strong overlap on all three:
A site that is accessible to all users is also a site that is faster, more search-visible, and more conversion-optimized. The work compounds.
Start with one page
Pick your most-visited page (usually the homepage). Run WAVE. Fix the top 5 issues it identifies. Move to the next page next week.
By month three, your whole site will be in better shape and your team will have learned the patterns.