Website Accessibility Compliance: AODA and WCAG Standards for Calgary Websites

Calgary’s business community is growing fast, but thousands of local websites still fail basic accessibility tests. With 1 in 5 Canadians — over 6.2 million people — living with a disability, and over 70% of websites failing basic accessibility tests, the gap between accessible and inaccessible content is both a legal risk and a missed business opportunity. As Alberta companies watch AODA (Accessibility for Ontarians with Disabilities Act) compliance become mandatory for Ontario businesses and spread as a benchmark across Canada, the responsibility to make digital presence welcoming to all users is growing.

For Calgary businesses, website accessibility means more than checking regulatory boxes. It reaches a broader audience, improves search engine rankings, reduces legal liability, and shows genuine commitment to inclusivity in a city that prides itself on community values.

Table of contents

Understanding Web Accessibility in Canada

The Canadian Accessibility Landscape

Canada has taken steps toward equal access for people with disabilities, with web accessibility forming part of this national commitment. The Accessible Canada Act (ACA), passed in 2019, established a framework for identifying, removing, and preventing barriers to accessibility across federally regulated organizations. This federal legislation sets the stage for accessibility standards that impact digital services, including websites, mobile applications, and online platforms.

Canadian Accessibility Statistics:

• Over 6.2 million Canadians aged 15 and older live with one or more disabilities, representing approximately 22% of the population
• 1 in 3 seniors in Canada experiences some form of disability affecting their ability to use digital services
• 85% of Canadians with disabilities use the internet regularly, yet face significant barriers in accessing online content
• Only 24% of Canadian organizations have a formal accessibility policy in place for their digital properties
• Over 40% of Canadian small businesses are unaware of their accessibility obligations under current legislation
• The disability market in Canada is worth $55 billion annually in spending power

The Economic Case for Accessibility

Beyond legal compliance, web accessibility makes business sense. The disability community controls significant disposable income, and accessible websites consistently outperform inaccessible competitors in search rankings, user engagement, and conversion rates.

Business Benefits of Web Accessibility:

• Expanded audience reach — Accessible websites serve not only people with permanent disabilities but also those with temporary impairments and situational limitations, such as users on mobile devices in bright sunlight or with slow internet connections
• Improved SEO performance — Accessibility best practices align closely with search engine optimization requirements, including proper heading structure, descriptive alt text, and semantic HTML
• Reduced bounce rates — Users of all abilities stay longer and engage more deeply with websites that are easy to navigate, read, and interact with
• Enhanced brand reputation — Demonstrating commitment to accessibility positions your business as inclusive and socially responsible
• Legal risk mitigation — Proactive compliance reduces exposure to accessibility-related lawsuits, complaints, and regulatory penalties

AODA Compliance Requirements

Understanding the Accessibility for Ontarians with Disabilities Act

The Accessibility for Ontarians with Disabilities Act (AODA) was enacted in 2005 with the goal of making Ontario fully accessible by 2025. While AODA is Ontario-specific legislation, its influence has spread across Canada, with many provinces and municipalities adopting similar standards. For Calgary businesses operating nationally or serving Ontario customers, AODA compliance may be directly required. For purely Alberta-based operations, AODA standards still serve as the most comprehensive benchmark for web accessibility in Canada.

AODA Web Accessibility Requirements:

• All public websites and web content published after 2012 must conform to WCAG 2.0 Level AA
• Organizations with 50 or more employees must file annual accessibility compliance reports
• Websites and web content must be accessible to people with disabilities including those who are blind, deaf, have mobility impairments, or cognitive disabilities
• Accessibility statements must be published and maintained on organizational websites
• Training must be provided to employees who develop or maintain web content

National Impact and Alberta Context

While Alberta has not enacted specific web accessibility legislation comparable to AODA, the federal Accessible Canada Act applies to organizations under federal jurisdiction, including banks, telecommunications companies, transportation providers, and broadcasting entities operating in Calgary. Additionally, AODA requirements increasingly serve as de facto best practices across Canada.

Alberta-Specific Considerations:

• Alberta Human Rights Act prohibits discrimination based on physical or mental disability, which courts have interpreted to include inaccessible digital services
• Canadian Charter of Rights and Freedoms guarantees equal protection and benefit of the law without discrimination based on mental or physical disability
• Courts and tribunals in Canada are taking accessibility complaints seriously, with increasing awards for those denied equal access to digital services
• Calgary businesses serving national markets should meet or exceed AODA requirements to limit legal exposure in multiple jurisdictions

WCAG 2.1 and 2.2 Standards Overview

The Four Principles of Web Content Accessibility Guidelines

The Web Content Accessibility Guidelines (WCAG) are the international standard for web accessibility. The guidelines are organized around four principles: Perceivable, Operable, Understandable, and Robust (POUR).

WCAG Level AA Compliance is the standard most commonly referenced in legislation worldwide, including AODA, the European Accessibility Act, and Section 508 in the United States. WCAG 2.1 added success criteria for mobile accessibility, low vision, and cognitive disabilities. WCAG 2.2 (published in 2023) introduced additional criteria for focus appearance, accessible authentication, and draggable content.

Perceivable

Users must be able to perceive the information being presented through at least one of their senses:

Text Alternatives:

• Non-text content must be provided with text alternatives that serve the equivalent purpose
• Alt text for images should be meaningful and descriptive, conveying the function and content of each image
• Decorative images should be marked as decorative or provided with null alt attributes to avoid distracting screen reader users
• CAPTCHA alternatives must include audio or other non-visual options for authentication

Time-Based Media:

• Pre-recorded video content must have captions synchronized with the audio track
• Audio descriptions should be provided for video content that conveys important visual information
• Live audio and video must have real-time captions for accessibility
• Sign language interpretation is recommended for content and communications

Adaptable Content:

• Content must maintain its meaning and structure when presented in different ways, including when users adjust text size, font, spacing, or color settings
• Proper heading hierarchy with a single H1 and logical nesting of H2 through H6 headings helps screen readers navigate content effectively
• Semantic HTML elements like lists, tables, and landmarks provide structural meaning that assistive technologies can interpret
• Reading order must be preserved in the code even when visual presentation differs from source order

Distinguishable Content:

• Color contrast ratios must meet minimum requirements of 4.5:1 for normal text and 3:1 for large text
• Color should not be the sole means of conveying information, indicating an action, prompting a response, or distinguishing a visual element
• Text resizing up to 200% must not cause loss of content or functionality
• Images of text should be avoided except for logos and branding elements

Operable

User interface components and navigation must be operable by all users:

Keyboard Accessibility:

• All functionality must be available from a keyboard for users who cannot use a mouse
• Keyboard focus indicators must be clearly visible, typically through outlines, highlights, or other visual cues
• No keyboard traps where users cannot move focus away from a component using the keyboard alone
• Focus order must be logical and intuitive, following the visual layout of the page

Enough Time:

• Users must be able to adjust, extend, or disable time limits on content requiring timed responses
• Moving, blinking, or auto-updating content must have mechanisms to pause, stop, or hide it
• Session timeouts should provide warnings and sufficient time to extend sessions before losing data
• Carousels and sliders should include pause, play, and navigation controls

Seizures and Physical Reactions:

• Content must not contain flashing effects that flash more than three times per second, as these can trigger seizures
• Animations triggered by user interaction should not violate flash thresholds
• User preferences for reduced motion should be respected through operating system and browser settings

Navigable Content:

• Skip navigation links must be provided to allow users to bypass repetitive content and navigate directly to main content areas
• Page titles must describe the topic or purpose of the page
• Focus order must be logical and preserve meaning and operability
• Link purpose must be determinable from the link text alone or from the link text combined with its programmatically determined context
• Multiple navigation mechanisms should be available, such as site search, sitemaps, and navigation menus
• Headings and labels must describe topic or purpose clearly and concisely

Understandable

Information and interface operation must be understandable:

Readable Text:

• The primary language of the page must be specified in the HTML lang attribute
• Unusual words, idioms, and abbreviations should be defined on first use with explanations or a glossary
• Reading level should not exceed lower secondary education level where possible, or simplified summaries should be provided
• Pronunciation guidance should be available for words that are ambiguous without phonetic information

Predictable Behavior:

• Navigation patterns must be consistent across pages within the same website
• Components with consistent labeling must appear and function predictably throughout the site
• Changes of context such as opening new windows or moving focus should occur only with user initiation or with warning
• Forms and data entry should follow consistent, predictable patterns

Input Assistance:

• Error identification must clearly describe what went wrong and where
• Labels and instructions must be provided for all input fields
• Error suggestions should recommend corrections where possible without compromising security
• Error prevention for legal, financial, and data-critical submissions should include confirmation and reversal mechanisms

Robust

Content must be robust enough to be interpreted by a wide variety of user agents, including assistive technologies:

Compatibility:

• Valid HTML ensures assistive technologies can parse and interpret content correctly
• ARIA landmarks and roles must be used appropriately to convey page structure and functionality to screen readers
• Status messages should be programmatically determinable through ARIA live regions
• Custom widgets and components must provide appropriate ARIA labels, roles, states, and properties

Accessibility Features for Websites

Screen Reader Compatibility

Screen readers like JAWS, NVDA, VoiceOver, and TalkBack are essential tools for blind and low-vision users. Ensuring your website works with these technologies requires careful implementation of semantic HTML, ARIA attributes, and proper content structure.

Screen Reader Optimization Techniques:

• Semantic HTML elements such as <nav>, <main>, <header>, <footer>, and <aside> provide built-in landmarks that screen readers use for navigation
• ARIA labels and descriptions provide additional context for interactive elements that may not be fully described by their visual presentation
• Proper heading structure with logical nesting enables screen reader users to navigate content by heading level
• Descriptive link text — avoiding generic phrases like “click here” or “read more” — ensures users understand the destination of each link
• Form labels and error messages must be programmatically associated with their corresponding input fields
• Alt text for images must be descriptive and contextually appropriate, conveying the same information that visual users receive

Keyboard Navigation

Approximately 10% of people with disabilities rely exclusively on keyboard navigation, including users with motor disabilities, repetitive strain injuries, and those who cannot operate a mouse. Every interactive element on your website must be accessible and operable through keyboard input alone.

Keyboard Accessibility Requirements:

• Tab order must follow a logical sequence that matches the visual layout of the page
• Focus indicators must be clearly visible, typically with a minimum 2-pixel outline or highlight
• Custom components like dropdowns, modals, and accordions must implement keyboard interaction patterns consistent with their ARIA roles
• Escape key functionality should close modals, menus, and overlays
• Enter and space keys should activate buttons and links
• Arrow keys should navigate within custom components like menus, tabs, and tree views
• Users must be able to move focus away from any component using standard keyboard navigation

Color Contrast and Visual Design

Over 8% of men and 0.5% of women have some form of color vision deficiency, making color contrast one of the most impactful accessibility improvements you can make. Proper contrast also benefits users in bright environments, with low-quality displays, or with age-related vision changes.

Color and Contrast Standards:

• Normal text under 18px must maintain a minimum contrast ratio of 4.5:1 against its background
• Large text 18px and above or 14px bold and above requires a minimum contrast ratio of 3:1
• UI components and graphical objects must maintain a 3:1 contrast ratio against adjacent colors
• Focus indicators should provide high contrast against surrounding elements
• Color palettes should be tested in grayscale to ensure information is not conveyed through color alone
• Dark mode compatibility is increasingly important for users with light sensitivity and visual fatigue
• Text over images must have sufficient contrast, which may require overlays or text shadows

Alternative Text for Images

Alt text serves multiple purposes: it provides screen reader users with equivalent information, it displays when images fail to load, and it improves SEO by giving search engines context about image content.

Alt Text Best Practices:

• Informative images require descriptive alt text that conveys the same information a sighted user would receive
• Functional images (such as icons used as links or buttons) need alt text describing the function, not the appearance
• Decorative images should have empty alt attributes (alt="") or be implemented as CSS background images so screen readers ignore them
• Complex images like charts, graphs, and infographics require long descriptions in addition to concise alt text
• Image links need alt text describing the link destination, not the image itself
• Logo images should include the business name in the alt text
• Alt text should be concise, typically under 125 characters, while still conveying the essential information

Captions and Transcripts

Multimedia content requires captions, audio descriptions, and transcripts to ensure equal access for users who are deaf, hard of hearing, or blind.

Multimedia Accessibility Requirements:

• Pre-recorded video with audio must have synchronized captions that include dialogue, speaker identification, and meaningful sounds
• Pre-recorded video must also have audio descriptions of important visual content not conveyed through dialogue alone
• Live video streams require real-time captioning for accessibility
• Audio-only content like podcasts must be accompanied by transcripts that include speaker identification and descriptions of non-speech sounds
• Transcripts should be easy to find and ideally located near the multimedia content they describe
• Video players must be keyboard accessible and support caption toggling
• Sign language interpretation is recommended for communications such as emergency information and public service announcements

Accessibility Testing and Auditing

Automated Testing Tools

Automated accessibility testing tools provide a quick way to identify common accessibility issues across your entire website. While automated tools cannot catch every accessibility barrier (they typically detect only 20-30% of all accessibility issues), they are a necessary part of any testing strategy.

Automated Accessibility Testing Tools:

• WAVE (Web Accessibility Evaluation Tool) — Provides visual feedback by injecting icons and indicators directly into the tested page, highlighting errors, warnings, and ARIA features
• axe DevTools — Browser extension and library that performs accessibility audits and integrates directly into development workflows and CI/CD pipelines
• Lighthouse — Built into Chrome DevTools, providing accessibility audits alongside performance, SEO, and best practices scores
• Siteimprove — Enterprise platform offering automated scanning, monitoring, and reporting across entire website portfolios
• AccessiBe and UserWay — Automated overlay solutions that claim to improve accessibility, though expert guidance is needed as overlays cannot fully address all accessibility requirements

What Automated Tools Can Detect:

• Missing or empty alt text on images
• Insufficient color contrast ratios
• Missing form labels and ARIA attributes
• Improper heading hierarchy
• Missing document language declarations
• Broken skip navigation links
• Empty links and buttons
• Duplicate IDs and accessibility attributes

Manual Testing Methods

Automated testing must be complemented by manual testing to catch the 70-80% of accessibility issues that automation cannot detect. Manual testing includes keyboard-only navigation testing, screen reader testing, and visual review.

Manual Testing Procedures:

Keyboard-Only Navigation Testing:

• Navigate every page element using only the Tab, Shift+Tab, Enter, Escape, and Arrow keys
• Verify that all interactive elements are reachable and operable with keyboard input alone
• Confirm that focus indicators remain visible at all times
• Check that focus order follows a logical sequence consistent with the visual layout
• Ensure no keyboard traps prevent users from moving focus away from any component

Screen Reader Testing:

• Test with at least two screen readers, such as NVDA (Windows, free) and VoiceOver (Mac, built-in)
• Navigate content using heading structure, landmark regions, and link lists
• Verify that custom components announce their purpose, state, and available actions correctly
• Confirm that dynamic content updates are announced through appropriate ARIA live regions
• Test form validation and error message announcements

Visual Review:

• Zoom the browser to 200% and verify no content is lost, truncated, or overlapping
• Apply high contrast mode and custom style sheets to verify content remains readable
• Test with custom font sizes increased to ensure text reflows without breaking layout
• Disable images and verify that all information conveyed through images is also available through alt text or surrounding content
• Confirm that all functionality is available without requiring specific sensory abilities such as precise mouse control or color perception

User Testing with People with Disabilities

The most valuable accessibility testing comes from direct feedback from people with disabilities who use assistive technologies daily. User testing reveals real-world barriers that automated tools and even experienced developers can miss.

User Testing Best Practices:

• Recruit participants with a range of disabilities including visual, hearing, motor, and cognitive impairments
• Test with participants who use different assistive technologies including screen readers, voice recognition software, screen magnifiers, and switch devices
• Focus on real tasks that users would typically perform on your website, such as making a purchase, filling out a form, or finding contact information
• Document video recordings of user testing sessions (with permission) to share findings with your development and design teams
• Prioritize issues based on severity and frequency, addressing critical barriers that block task completion immediately
• Conduct regular user testing as accessibility issues can be introduced with any new feature or content update

Accessibility and the Law

Legal Risk Mitigation

The legal landscape for digital accessibility in Canada is shifting. Enforcement actions are increasing and awareness of accessibility rights is growing. Calgary businesses that neglect web accessibility face real legal exposure.

Legal Exposure for Inaccessible Websites:

• Canadian Human Rights Commission complaints can be filed against federally regulated organizations for inaccessible digital services
• Provincial human rights tribunals in Alberta and across Canada have jurisdiction over accessibility discrimination claims
• Class action lawsuits have been filed in Canada against companies with inaccessible websites, seeking damages for systemic discrimination
• AODA compliance orders can result in penalties of up to $100,000 per day for Ontario organizations, with national businesses exposed to similar standards
• US legal exposure for Calgary businesses serving American customers, as the Americans with Disabilities Act (ADA) website accessibility litigation continues to grow

Statistics on Accessibility Litigation:

• Over 4,600 website accessibility lawsuits were filed in the United States in 2023 alone, with Canadian litigation following a similar upward trend
• Canadian accessibility complaints have increased significantly since the passage of the Accessible Canada Act
• Average settlement costs for accessibility lawsuits range from $25,000 to $250,000 or more, not including legal fees and remediation costs
• Remediation costs for retrofitting an inaccessible website are typically 3-5 times higher than building accessibility in from the start

Expanded Audience Reach

Making your website accessible expands your potential customer base. The disability community is a substantial and often underserved market segment.

Market Opportunity Statistics:

• Canadians with disabilities control over $55 billion annually in disposable income
• The global disability market is estimated at over $1.2 trillion in annual disposable income
• 70% of Canadians with disabilities will leave a website that is difficult to use, taking their business to competitors
• 82% of customers with disabilities prefer to do business with companies that demonstrate accessibility commitment
• Family and friends of people with disabilities often factor accessibility into their purchasing decisions, further expanding the addressable market

SEO Benefits

Accessibility and SEO share a common foundation: both require content to be well-structured, descriptive, and easy to navigate. Implementing accessibility best practices directly improves search engine rankings.

Accessibility Features That Boost SEO:

• Proper heading structure helps search engines understand content hierarchy and relevance
• Descriptive alt text provides image context for search engines, improving image search rankings
• Semantic HTML improves crawlability and helps search engines understand page structure
• Clear link text provides better anchor text for search engine ranking algorithms
• Fast page load speeds benefit both accessibility (users with slow connections) and SEO (Core Web Vitals)
• Mobile responsiveness is needed for both accessibility and mobile search rankings
• Transcripts and captions provide additional text content for search engines to index

Brand Reputation and Corporate Responsibility

Demonstrating commitment to accessibility signals that your Calgary business values inclusivity and social responsibility.

Brand Benefits of Accessibility:

• Positive brand perception among the 85% of Canadians who believe companies should prioritize accessibility
• Enhanced employer brand attracting top talent who value inclusive workplace practices
• Competitive differentiation in markets where competitors have not invested in accessibility
• Alignment with ESG goals increasingly important to investors and stakeholders
• Community goodwill from demonstrating commitment to Calgary’s diverse population
• Leadership positioning as Alberta moves toward more comprehensive accessibility standards

Implementing Accessibility in Your Development Workflow

Design Phase

Accessibility must be integrated from the earliest stages of website design to avoid costly retrofitting.

Accessibility-First Design Principles:

• Color palette selection should prioritize sufficient contrast ratios from the beginning, testing primary, secondary, and accent colors against WCAG requirements
• Typography choices must consider readability, with minimum font sizes, appropriate line heights (1.5 is recommended), and sufficient letter spacing
• Layout structure should accommodate zoom to 200% without horizontal scrolling or content loss
• Interactive element sizing must meet minimum target sizes (WCAG 2.2 requires touch targets of at least 24x24 pixels with 44x44 pixels strongly recommended)
• Focus indicator design should be incorporated into the visual design system rather than added as an afterthought
• Content hierarchy must be established through proper heading structure, not visual styling alone
• Form design should include clear labels, instructions, error messages, and sufficient spacing for touch interaction

Development Phase

During development, accessibility considerations must be implemented in code and verified continuously.

Accessibility Development Practices:

• Semantic HTML must be the foundation, with ARIA used only when native HTML semantics are insufficient
• Keyboard event handlers must supplement mouse and touch interactions for all interactive elements
• Dynamic content updates must use ARIA live regions to announce changes to screen reader users
• Form validation must provide clear, programmatically associated error messages
• Custom components must implement appropriate ARIA roles, states, and properties
• Responsive breakpoints must maintain accessibility at all screen sizes
• Performance optimization directly impacts users with cognitive disabilities and those using older devices or slow connections

Quality Assurance Testing

Accessibility testing must be a standardized part of every QA cycle, not a one-time audit performed at project completion.

QA Testing Checklist:

• Automated scans using tools like axe DevTools and WAVE must be run on every page template before release
• Keyboard-only testing must verify full functionality for every interactive element
• Screen reader testing with at least one screen reader (NVDA or VoiceOver) must be completed for critical user flows
• Color contrast verification using tools like the WebAIM Contrast Checker must confirm all text and UI elements meet WCAG thresholds
• Content zoom testing at 200% must verify no content loss or layout breakage
• Form and error message testing must ensure all validation states are communicated to assistive technologies
• Mobile accessibility testing must confirm touch targets are appropriately sized and spaced
• PDF and document accessibility must be verified for downloadable content

Ongoing Monitoring and Maintenance

Accessibility is not a one-time project milestone but an ongoing commitment requiring continuous monitoring and improvement.

Ongoing Accessibility Management:

• Regular automated scans should be scheduled — weekly for active development sites, monthly for stable content sites
• Content author training ensures that editors and content creators understand accessibility requirements when adding new pages, images, and documents
• Third-party integrations must be evaluated for accessibility before adoption and monitored for accessibility regressions after updates
• CMS and platform updates should include accessibility regression testing
• Annual professional audits provide comprehensive assessment by accessibility experts
• User feedback mechanisms allow visitors to report accessibility issues they encounter
• Accessibility statement maintenance ensures your published commitment remains accurate and up to date

Choosing the Right Accessibility Partner

What to Look for in an Accessibility Consultant

Selecting the right partner for accessibility compliance matters. Not all web development agencies have genuine expertise in accessibility, and superficial fixes can sometimes create more barriers than they remove.

Qualifications to Evaluate:

• IAAP certification — The International Association of Accessibility Professionals offers Certified Professional in Accessibility Core Competencies (CPACC) and Web Accessibility Specialist (WAS) credentials
• Demonstrated experience with WCAG 2.1 and 2.2 AA compliance across multiple projects and industries
• Familiarity with Canadian accessibility legislation including AODA, the Accessible Canada Act, and provincial human rights codes
• User testing methodology that includes direct engagement with people with disabilities
• Sustainable approach that builds accessibility into development workflows rather than relying on overlay tools or post-production fixes
• Comprehensive service offerings covering design, development, testing, training, and ongoing monitoring

Red Flags to Avoid:

• Overlay solutions that claim to make websites fully accessible with a single line of code — these tools address only a fraction of accessibility issues and can actually interfere with assistive technologies
• Agencies that treat accessibility as an add-on rather than an integrated part of their development process
• Vendors who rely solely on automated testing without manual review and user testing components
• Promises of “100% accessibility” — true accessibility is an ongoing process, not a destination
• Lack of Canadian context — agencies unfamiliar with AODA, the Accessible Canada Act, and provincial requirements may miss important compliance obligations

Integration with Calgary Web Development Services

For Calgary businesses, the most effective accessibility solutions come from partners who understand both accessibility standards and the local market context. Webtrophy’s approach integrates accessibility throughout the entire web development lifecycle.

How Webtrophy Approaches Accessibility:

• Accessibility requirements are defined during the discovery phase and documented as project specifications
• Design reviews include accessibility evaluation before development begins
• Development sprints include accessibility checkpoints and peer reviews
• QA testing encompasses automated scanning, manual testing, and screen reader verification
• Post-launch monitoring includes regular accessibility audits and continuous improvement
• Client training empowers your team to maintain accessibility standards when publishing new content

Ready to make your Calgary business website accessible and AODA/WCAG compliant? Webtrophy’s web design and development services build accessibility in from the ground up.

Contact Webtrophy for an accessibility consultation. Our Calgary-based team knows Canadian accessibility requirements and builds websites that meet WCAG 2.1 AA standards.

This article is part of Webtrophy’s web accessibility series for Calgary businesses.