Mobile friendly website design: why phone visitors matter most
Google ranks the mobile version of your site, and phones bring close to half of Canadian web traffic. Here is how to design for the screen that matters most.
Read articleWhat the law actually says in Canada and Alberta, what WCAG 2.2 AA asks for in plain words, and the 10 accessibility fixes that cover most real-world problems.
More than one in four Canadians aged 15 and older has a disability that limits daily activities. If your website does not work with a screen reader, a keyboard or zoomed-in text, a real share of your potential customers cannot book, call or buy. Website accessibility in Canada is also a legal topic that confuses a lot of owners, especially in Alberta, where the rules look different from Ontario or the federal level.
This guide sorts it out in plain language. We cover the numbers behind the problem, what WCAG 2.2 AA actually asks for, what the law requires federally, in Ontario and here in Alberta, the 10 fixes that cover most real issues, how to test your own site and why accessible sites tend to perform better for everyone. We are web designers, not lawyers, so treat the legal section as orientation and get advice for your specific situation.
Statistics Canada's 2022 Canadian Survey on Disability found that 27% of Canadians aged 15 and older, or 8.0 million people, had one or more disabilities that limited their daily activities. That was up from 22% in 2017.
Disability on the web is broader than people expect. It includes people who are blind and use screen readers, people with low vision who zoom to 200% or more, people with tremors or arthritis who cannot use a mouse precisely, people who are Deaf or hard of hearing, and people with learning, memory or attention differences who need clear structure and plain language. Add the temporary and situational cases (a broken wrist, glare on a phone screen at a Calgary bus stop, an older customer whose eyesight is changing) and accessibility starts to look like plain good usability.
Every year WebAIM runs an automated accessibility scan of the home pages of the top one million websites. The 2026 report found that 95.9% of home pages had detected WCAG 2 failures, with an average of 56.1 errors per page. That was a 10.1% increase from 51 errors per page in 2025, reversing several years of small improvements. Pages are also getting heavier: the average home page grew to 1,437 elements, up 14.3% in a year.
Automated tools only catch a portion of real issues, so the true picture is worse. The good news is that the most common problems are well known and fixable.
The Web Content Accessibility Guidelines (WCAG) are the international standard. The W3C published WCAG 2.2 on 5 October 2023. It is organized around four principles, often shortened to POUR, with success criteria at three levels: A, AA and AAA. Level AA is the standard most laws and policies point to.
Importantly, the W3C says content that conforms to WCAG 2.2 also conforms to 2.1 and 2.0. So if you build to 2.2 AA, you also meet the older versions that some laws still reference.
| Principle | What it means | Small business examples |
|---|---|---|
| Perceivable | People can see or hear the content in some form | Alt text on photos, captions on videos, readable contrast |
| Operable | People can use every control | Works with a keyboard, visible focus, big enough tap targets |
| Understandable | Content and controls make sense | Clear labels, plain error messages, consistent menus |
| Robust | Works with assistive technology | Proper HTML headings, buttons and form elements |
WCAG 2.2 added nine success criteria over 2.1. A few matter a lot for small business sites:
This is the section most owners care about, and the one with the most myths. Here is where things stand in fall 2026.
The Accessible Canada Act came into force in 2019 with the goal of a barrier-free Canada by 2040. It applies to the federal government and federally regulated sectors such as banking, telecommunications and transportation. Information and communication technologies are one of its seven priority areas. Regulated organizations must publish accessibility plans, set up feedback processes and report on progress.
Most Calgary plumbers, dentists and law firms are provincially regulated, so the ACA does not apply to them directly. It does apply if you are, say, a trucking company operating across provincial borders or a federally regulated financial business.
Ontario has the most specific web rules in the country. Under the AODA, since January 1, 2021, businesses and non-profits with 50 or more employees in Ontario, plus designated public sector organizations, must make public websites meet WCAG 2.0 Level AA, with exceptions for live captions and pre-recorded audio descriptions. If your Alberta company has 50+ employees and operations in Ontario, check whether this applies to you.
Alberta does not currently have a provincial accessibility law with web standards. According to Medicine Hat News, eight of Canada's ten provinces have accessibility legislation, and Alberta and Prince Edward Island are the two without. A private member's bill, the Accessible Alberta Act (Bill 206), was introduced in March 2026; Barrier-Free Alberta reported that it was defeated at second reading on March 23, 2026.
That does not mean accessibility is optional in a legal sense. The Alberta Human Rights Commission states that providers of goods and services to the public have a duty to accommodate to the point of undue hardship, and disability is a protected ground under the Alberta Human Rights Act. The Commission's guidance does not set website-specific technical rules, but if a customer cannot book with you because your site blocks them, the human rights framework is where that conversation would start.
You will see "ADA compliance" in a lot of plugin ads. The Americans with Disabilities Act is US law. A business that only serves customers in Calgary, Airdrie or Okotoks is governed by Canadian and Alberta rules. If you sell into the US or have US operations, get legal advice. In both countries, WCAG 2.2 AA is the technical standard that matters in practice.
| Jurisdiction | Main rule | Who it covers | Web standard |
|---|---|---|---|
| Federal | Accessible Canada Act (2019) | Federal government and federally regulated sectors | Accessibility plans and reporting; ICT is a priority area |
| Ontario | AODA | Public sector and organizations with 50+ employees in Ontario | WCAG 2.0 AA (with two exceptions) |
| Alberta | No provincial accessibility act; Alberta Human Rights Act applies | Businesses serving the public | No set web standard; duty to accommodate |
| Practical target for everyone | WCAG 2.2 AA | Any business | Covers 2.0 and 2.1 as well |
Because six error types make up 96% of what WebAIM detects, a short list gets you most of the way. Here are the ten fixes we prioritize on small business sites, roughly in order of impact.
| # | Fix | Why it matters | Effort |
|---|---|---|---|
| 1 | Raise text contrast | Low contrast was on 83.9% of home pages; grey-on-white text fails often | Low |
| 2 | Add meaningful alt text to images | Screen reader users hear nothing, or a file name, without it | Low |
| 3 | Label every form field | Unlabeled fields make booking and contact forms unusable | Low |
| 4 | Fix empty links and buttons | Icon-only links (social, search, menu) need accessible names | Low |
| 5 | Set the page language | One line of code so screen readers pronounce text correctly | Very low |
| 6 | Use real headings in order | Lets people jump through sections, also helps SEO | Low to medium |
| 7 | Make everything keyboard accessible | Menus, sliders and pop-ups must work with Tab and Enter | Medium |
| 8 | Show a visible focus style | People need to see where they are when tabbing | Low |
| 9 | Make tap targets big enough | At least 24 by 24 CSS pixels; we aim for 44 to 48 | Low |
| 10 | Caption videos and avoid auto-play | Helps Deaf users and anyone watching on mute | Medium |
Forms deserve special attention because they are where leads happen. Visible labels, clear error messages and no puzzle CAPTCHAs help everyone, which we cover in why your contact form isn't converting. Tap targets and readable text also overlap heavily with good mobile design, covered in our mobile-first design guide.
Accessibility overlays promise compliance with a line of script. They cannot reliably fix missing labels, broken heading structure or keyboard traps, because those problems live in the site itself. Use automated tools to find issues, then fix them in the code and content.
You do not need special training to find the biggest problems.
Write down every problem. Most will map to the ten fixes above.
Leaving the legal side aside, accessibility is a straightforward business decision.
The structure that makes a homepage convert, as outlined in our homepage anatomy guide, is the same structure that makes it accessible: clear headings, one idea per section and obvious actions.
Alberta has no provincial accessibility law with website standards as of fall 2026. A private member's bill, the Accessible Alberta Act (Bill 206), was defeated at second reading in March 2026. The Alberta Human Rights Act still requires businesses serving the public to accommodate people with disabilities to the point of undue hardship, so ignoring accessibility carries risk. For legal advice on your situation, talk to a lawyer.
Aim for WCAG 2.2 Level AA. It was published in October 2023, and the W3C says content that conforms to 2.2 also conforms to 2.1 and 2.0. Ontario's AODA references WCAG 2.0 AA, so meeting 2.2 AA covers that too.
The Americans with Disabilities Act is a US law. A Calgary business serving local customers is governed by Canadian and Alberta rules, not the ADA. If you sell into the US or have US locations, ask a lawyer whether US rules apply to you. Either way, WCAG 2.2 AA is the practical target.
No tool can make a site accessible on its own. Overlays cannot fix missing labels, poor heading structure or inaccessible forms in a reliable way. Automated checkers are useful for finding problems, but fixes belong in the site's code and content, plus a manual keyboard and screen reader check.
It depends on how the site was built. Many issues, such as alt text, contrast, link text and form labels, are quick content or styling fixes. Sites built on heavy themes or page builders sometimes need deeper work. Building accessibility in from the start is always cheaper than retrofitting.
Start with a free automated checker such as WAVE, then do three manual checks: navigate the whole page with only the Tab and Enter keys, zoom the browser to 200%, and turn on your phone's screen reader for a few minutes on your homepage and contact form.
We recommend WCAG 2.2 AA as the target for every new build, and accessibility fixes fit naturally into a website redesign. If you want to know where your current site stands, book a free 15-minute call and we will check contrast, labels, keyboard access and mobile tap targets with you, then give you a prioritized fix list.
Dimitri runs Clear Pixel, a Calgary web studio building fast, clean websites for small businesses across North America.
Tell us about the project. We’ll map out scope, timeline, and a fixed price. No pressure, no obligation.