What Is Accessible Web Design?
Accessible web design means building websites that people with disabilities can perceive, operate, and understand. This includes people who are blind or have low vision and use screen readers, people who are deaf or hard of hearing and rely on captions, people with motor impairments who cannot use a mouse, and people with cognitive disabilities who need clear, simple language and structure.
In Canada, accessible web design is not only a best practice. For many organisations it is a legal obligation. The minimum standard is WCAG 2.1 AA, the Web Content Accessibility Guidelines at the double-A conformance level.
Why Accessible Web Design Matters for Canadian Organisations
Approximately 22% of Canadians aged 15 and older have a disability. An inaccessible website excludes a significant proportion of your potential audience (donors, program participants, patients, or clients) who rely on assistive technologies to access online information and services.
Beyond audience reach, accessibility carries legal weight. Ontario organisations with 50 or more employees are required to meet WCAG 2.0 Level AA under AODA, with penalties up to $100,000 per day for organisations. The Accessible Canada Act requires federally regulated entities to meet WCAG 2.1 AA. Many federal funding bodies now require WCAG 2.1 AA compliance as a condition of digital grants.
The Most Common Accessible Web Design Failures
Insufficient colour contrast. Normal text must achieve a contrast ratio of at least 4.5:1 against its background. Light grey text on white (a common modern design choice) frequently fails. Check your site using WebAIM's free contrast checker.
Missing or inadequate form labels. Every form field must have a programmatically associated label. Placeholder text that disappears when typing does not meet this requirement. Screen reader users navigating a form cannot identify what information is required without proper labels.
Poor heading structure. Pages must use a logical heading hierarchy: one H1, followed by H2 and H3 headings in order. Headings used purely for visual styling, or pages with multiple H1 elements, fail this requirement.
Keyboard navigation failures. Every interactive element (links, buttons, menus, forms) must be operable using a keyboard alone. Tab through your website without using a mouse. If anything is unreachable or inoperable, it is an accessibility failure.
Images without alt text. Every meaningful image must have descriptive alt text. Decorative images should have empty alt attributes so screen readers skip them.
How to Build Accessible Websites in Canada
The most cost-effective approach is to build accessibility in from the first wireframe rather than auditing and remediating after launch. Retrofitting accessibility to an existing site that was not built accessibly typically costs 30 to 50% of the original build cost. Building it in adds approximately 10 to 15%.
Testing requires both automated tools and manual review. Automated tools like axe DevTools, WAVE, and Lighthouse catch 30 to 40% of real accessibility barriers. Manual testing with a keyboard and a screen reader (NVDA on Windows, VoiceOver on Mac) is required to find the remainder.
What Accessible Web Design Costs in Canada
For new builds, expect WCAG 2.1 AA compliance to add 10 to 15% to project cost when built in from the start. For a typical $30,000 nonprofit website, this is $3,000 to $4,500. Standalone accessibility audits on existing Canadian websites typically run $2,500 to $7,500 depending on site size, manual testing scope, and depth of remediation roadmap. Remediation of an existing site typically runs $5,000 to $30,000 depending on how far the site is from compliance.
Automated-only audits are cheaper but miss 60 to 70% of real accessibility issues. For organisations facing AODA enforcement risk or federal funding compliance requirements, manual audits with screen reader testing are the only credible option.
Choosing an Accessible Web Design Partner
Ask any agency these specific questions: How do you test accessibility beyond automated scanners? Which screen readers does your team use (NVDA, VoiceOver, JAWS)? Can you show me live URLs of accessible sites you have built? What is your process when a remediation issue is found post-launch? Agencies that cannot answer these questions specifically are not genuine accessibility specialists.
Pragmatica builds all client websites to WCAG 2.1 AA as standard. Learn more about our accessibility services or get in touch to discuss an audit of your existing site.
