Accessibility Is Not Optional: Building AODA-Compliant Websites in Ontario

The Law Is Clear (Even If Most Businesses Ignore It)

Under the Accessibility for Ontarians with Disabilities Act (AODA), organizations with 50 or more employees must make their websites and web content accessible. This is not a suggestion. It is Ontario law, enforceable with penalties of up to $100,000 per day for corporations.

The standard referenced is WCAG 2.0 Level AA. In practice, most accessibility professionals recommend targeting WCAG 2.1 AA, which covers mobile accessibility and additional use cases not addressed in version 2.0.

Despite the law being in effect since 2014, compliance rates are poor. A 2024 analysis of Ontario business websites found that over 90% failed to meet WCAG 2.0 AA standards. Many of these businesses do not know they are non-compliant. The enforcement has been inconsistent, but this is changing. Complaints are increasing, and the Ontario government has signalled stronger enforcement.

What Accessibility Actually Means

Web accessibility means that people with disabilities can perceive, understand, navigate, and interact with your website. This includes people who are:

• Blind or have low vision: These users navigate with screen readers (software that reads page content aloud) or screen magnifiers. Your website needs proper HTML structure, text alternatives for images, and keyboard navigation.
• Deaf or hard of hearing: Video content needs captions. Audio content needs transcripts.
• Motor impaired: Users who cannot use a mouse navigate entirely with a keyboard, voice commands, or assistive switches. Every interactive element must be reachable and usable without a mouse.
• Cognitively impaired: Clear language, consistent navigation, and predictable behaviour help users with learning disabilities, attention disorders, or cognitive impairments.

In Canada, approximately 6.2 million people (22% of the population aged 15 and over) have one or more disabilities. That is not a niche audience. That is a significant portion of your potential customers.

The WCAG 2.1 AA Requirements (Plain Language)

WCAG organizes its guidelines under four principles. Your website must be Perceivable, Operable, Understandable, and Robust. Here is what that means in practical terms:

Perceivable

• Alt text for images: Every non-decorative image must have descriptive alternative text. Screen readers read this text to blind users. "IMG_4523.jpg" is not alt text. "Team meeting in the Toronto office boardroom" is.
• Video captions: All pre-recorded video with audio must have synchronized captions. Auto-generated captions are a starting point but usually need human editing for accuracy.
• Colour contrast: Text must have a contrast ratio of at least 4.5:1 against its background (3:1 for large text). This ensures readability for users with low vision or colour deficiencies.
• Do not rely on colour alone: If you use red text to indicate an error, also use an icon or text label. Approximately 8% of men have some form of colour vision deficiency.

Operable

• Keyboard navigation: Every interactive element (links, buttons, form fields, menus) must be reachable and usable with only a keyboard. Tab order must follow a logical sequence.
• No keyboard traps: Users must be able to navigate into and out of every component using only the keyboard. Modal dialogs are the most common offender.
• Enough time: If content auto-advances (carousels, session timeouts), users must be able to pause, stop, or extend the time limit.
• Skip navigation: Provide a "Skip to main content" link at the top of each page so keyboard users do not have to tab through the entire navigation on every page.

Understandable

• Language declaration: Set the lang attribute on your HTML element. This tells screen readers which language to use for pronunciation.
• Consistent navigation: Navigation menus must appear in the same location and order across all pages.
• Error identification: Form validation errors must clearly identify which field has an error and describe how to fix it. "There was an error" is not helpful. "Email address must include an @ symbol" is.
• Labels for inputs: Every form field must have a visible, associated label. Placeholder text alone is not sufficient because it disappears when the user starts typing.

Robust

• Valid HTML: Clean, standards-compliant HTML ensures that assistive technologies can reliably parse your content.
• ARIA when needed: Use ARIA (Accessible Rich Internet Applications) attributes to provide additional context for interactive components like tabs, accordions, and modal dialogs. But remember: no ARIA is better than bad ARIA.
• Testing with actual assistive technology: Automated tools catch about 30% of accessibility issues. The other 70% require manual testing with screen readers (NVDA on Windows, VoiceOver on Mac) and keyboard navigation.

Common Violations We Find on Toronto Business Websites

When we audit websites for AODA compliance, these issues appear most frequently:

1. Missing alt text: Found on 85% of sites we audit. Often the most images on the site have empty alt attributes or none at all.
2. Insufficient colour contrast: Found on 78% of sites. Light gray text on white backgrounds is the most common offender.
3. Missing form labels: Found on 65% of sites. Forms use placeholder text instead of proper label elements.
4. No keyboard navigation support: Found on 60% of sites. Custom dropdown menus and modal dialogs are typically the worst offenders.
5. Missing page language: Found on 45% of sites. A one-line fix that many developers simply forget.
6. Auto-playing video or audio: Found on 30% of sites. This violates WCAG guidelines and is also annoying for all users.

How to Fix Your Website Without a Full Rebuild

You do not need to rebuild your entire website to achieve compliance. We typically approach AODA remediation in three phases:

Phase 1: Quick wins (1-2 days)

• Add lang attribute to HTML element
• Add alt text to all images
• Fix colour contrast issues
• Add skip navigation link
• Ensure all form fields have proper labels

Phase 2: Structural fixes (1-2 weeks)

• Implement proper heading hierarchy (h1, h2, h3 in order)
• Add keyboard navigation to custom interactive components
• Fix focus management for modals and dropdowns
• Add ARIA attributes to complex components
• Add captions to video content

Phase 3: Ongoing compliance (monthly)

• Automated accessibility scanning in your deployment pipeline
• Manual screen reader testing for new features
• Accessibility review for new content
• Regular audits against WCAG 2.1 AA criteria

For most Toronto business websites, Phase 1 and Phase 2 can bring you to substantial AODA compliance for $3,000 to $10,000 depending on the size and complexity of the site.

The Business Case Beyond Compliance

Legal compliance is the floor, not the ceiling. Accessible websites also deliver measurable business benefits:

• Larger addressable market: 22% of Canadians have a disability. An inaccessible website excludes them.
• Better SEO: Accessibility best practices (proper heading structure, alt text, semantic HTML) directly improve search engine optimization. Google cannot see your images any better than a screen reader can.
• Improved usability for everyone: Captions help users watching video in noisy environments. High contrast helps users in bright sunlight. Keyboard navigation helps power users who prefer not to use a mouse.
• Reduced legal risk: Accessibility lawsuits are increasing in both Canada and the US. Proactive compliance is significantly cheaper than reactive legal defense.

Tools for Testing

Start with these free tools:

• axe DevTools: Browser extension that scans your page and identifies WCAG violations with specific fix recommendations.
• WAVE: Web accessibility evaluation tool from WebAIM. Visual overlay showing accessibility issues directly on your page.
• Lighthouse: Built into Chrome DevTools. Includes an accessibility audit that covers common WCAG issues.
• NVDA: Free screen reader for Windows. Install it and try navigating your own website with your eyes closed. This exercise is more educational than any automated tool.

At Fusion Interactive, we build accessible websites from the start and offer AODA compliance audits and remediation for existing sites. Every website we deliver meets WCAG 2.1 AA standards. If your Ontario business needs to get compliant, we can assess your current state and create a practical remediation plan.