Most small business websites in Ontario fail basic accessibility tests. Not because the owners don't care, but because nobody told them what the tests are.
WCAG 2.1 AA is the standard. It's the benchmark written into Ontario's AODA legislation. And in practice, it's a concrete set of requirements that most modern sites can meet without a complete rebuild.
Here's what it actually asks for.
What WCAG is
WCAG stands for Web Content Accessibility Guidelines. Published by the W3C, the body that maintains web standards, it defines what makes a website usable by people with disabilities: visual impairments, motor limitations, cognitive differences, hearing loss.
There are three conformance levels. Level A is the minimum. Level AA is the standard referenced in laws, procurement policies, and professional practice. Level AAA is the ceiling, designed for specialized applications, and rarely required in full.
Ontario's AODA references WCAG 2.0 Level AA. WCAG 2.1 is a backwards-compatible update from 2018. Building to 2.1 AA satisfies the 2.0 requirement and is the current standard of practice.
The four principles
WCAG is organized around four principles, abbreviated as POUR.
Perceivable. All content is available to the senses. A user on a screen reader can't see images. Without alt text describing them, that content doesn't exist for that user.
Operable. All functionality works without a mouse. Keyboard-only users navigate with Tab and Enter. If a modal traps focus, or a form requires a click to submit, those users are blocked.
Understandable. Content and functionality behave predictably. Forms describe errors clearly. Navigation is consistent. Instructions precede actions.
Robust. The code works with assistive technologies. Screen readers, voice control software, and switch devices rely on valid, semantic HTML to understand the page. Invalid markup breaks that chain.
What AA actually requires
The full WCAG 2.1 checklist runs to dozens of criteria. For a typical small business site, a handful account for most of the issues found in real audits.
Contrast ratios
Text needs sufficient contrast against its background. The minimum is 4.5:1 for body text, 3:1 for large text (18pt or larger, or 14pt bold). The same 3:1 minimum applies to interface elements: buttons, form inputs, focus indicators.
Most audit failures on small business sites come from this one. Light grey text on white. Placeholder text that barely reads. Hover states where button text and background converge.
Text alternatives
Every non-decorative image needs an alt attribute describing the content. Decorative images get alt="", which tells screen readers to skip them. Linked images need alt text that describes the link destination, not the image itself. A photo of your storefront that links to the contact page should say "Contact us" in the alt, not "Storefront exterior."
Keyboard access
Every interactive element, links, buttons, form inputs, menus, must be reachable and operable by keyboard alone. Tab order follows a logical sequence. A visible focus indicator shows which element is active. Focus doesn't get trapped in any component without an escape path.
Page structure
Each page needs a unique, descriptive title. Heading levels follow a logical hierarchy: one H1, H2s for main sections, H3s for subsections. No skipped levels. The lang attribute on the <html> element tells assistive technology what language to expect.
Form usability
Every form input needs a programmatically associated label, not just a placeholder. Placeholders disappear on input; labels persist. Errors are described specifically ("Email address is required") rather than generically. Instructions appear before users make mistakes, not only after.
Responsive and zoomable
Two criteria added in WCAG 2.1 matter most for mobile. Content must reflow at 320 CSS pixels wide without horizontal scrolling. Text must scale to 200% without losing content or functionality. Both are standard mobile practice. Both catch poorly built template sites.
| Criterion | What it requires | Most common failure |
|---|---|---|
| 1.1.1 Non-text Content | Alt text on all meaningful images | Missing alt, or alt = filename |
| 1.4.3 Contrast (Minimum) | 4.5:1 for body text, 3:1 for large text | Light grey on white background |
| 1.4.11 Non-text Contrast | 3:1 for UI components and focus indicators | Low-contrast form borders |
| 2.1.1 Keyboard | All functionality operable by keyboard | Click-only sliders and modals |
| 2.4.7 Focus Visible | Keyboard focus indicator visible | outline: none applied globally |
| 2.4.2 Page Titled | Each page has a unique, descriptive title | Every page shares the site name only |
| 3.3.1 Error Identification | Form errors described specifically | Generic "invalid input" messages |
| 1.4.10 Reflow | No horizontal scroll at 320px width | Fixed-width containers, overflow issues |
AODA and Ontario businesses
Ontario's AODA passed in 2005. Its Integrated Accessibility Standards Regulation sets web accessibility requirements for businesses operating in Ontario. Organizations with 50 or more employees were required to meet WCAG 2.0 Level AA for new and significantly refreshed website content by January 2021.
That deadline has passed. Most small business websites in Ontario still don't meet it.
Enforcement has been light for small businesses. That's not an argument for inaction. Human rights complaints have been filed over inaccessible websites in Ontario. Accessibility compliance is increasingly a factor in procurement and RFP processes for businesses working with government or publicly funded organizations. The standard continues to move up, not down.
Accessible sites also convert better
The compliance argument is real. The business argument tends to land harder for most owners.
According to the WHO, approximately 15% of the world's population lives with some form of disability. Statistics Canada puts the proportion at roughly one in five Canadians. That's a real segment of every local market. A site that doesn't work for screen reader users, keyboard users, or low-vision users doesn't reach them.
The overlap between accessibility and general usability is significant. Good contrast makes text readable in direct sunlight on a phone. Keyboard navigation works on TV browsers, game controllers, and assistive devices. Clear form labels reduce errors for everyone, not only for users with cognitive differences.
Accessible sites tend to have cleaner markup, which reduces page weight and improves Core Web Vitals scores. Google indexes alt text, page titles, and heading structure. Accessibility improvements frequently improve organic search ranking as a side effect.
Where to start
A basic accessibility audit takes about 20 minutes with the right tools.
WAVE by WebAIM runs in your browser and flags errors directly on the page. Google's PageSpeed Insights includes an Accessibility score with itemized failures. Neither catches everything, but both catch the most common issues on typical small business sites.
The most likely failures: missing or uninformative alt text, insufficient contrast on body text or interface elements, removed focus styles, unlabeled form inputs, and mobile layouts that break at narrow widths.
Most of those are fixable without rebuilding. Some require structural changes that are far easier to make at the design stage. Custom-built sites handle this better than template builds because accessibility gets built into the code from the start, not patched on after the fact.
If you want a straight look at where your site stands, get in touch. An accessibility review is part of every audit I run.