Skip to content
EN
Free · 30 minConsultation →
05 Pricing Prices and packages 07 About me Who I am, how I work
Language
PLPolskiEN (US)Englishcoming soonEN (CA)EnglishRUРусскийcoming soonITItalianocoming soonESEspañolcoming soonDEDeutschcoming soonFRFrançaiscoming soon
01 Services
Not sure where to start?Short quiz, 1 minute. I’ll suggest what will bring you customers fastest.→
02 Industries All →
03 Cities All →
60cities and towns 6up to 700 km from Winnipeg 36further, over Zoom
Clients in Winnipeg, the rest of Canada online
04 Case studies All →
06 Knowledge All →
AODA · WCAG 2.0, 2.1, 2.2 · accessible by default

Website
accessibility

Website accessibility means people with low vision, limited mobility, hearing loss or cognitive difficulties can use your site as easily as anyone else. I build it in from the first wireframe, following WCAG 2.x AA, the standard AODA refers to in Ontario.

Free: a 30-minute call, an action plan and a price range in writing.

Website accessibility: older man with glasses enlarging text on an accessible website on his tablet by a window
What I build in

Accessibility
from the first
sketch

Contrast and text size

Text that meets AA contrast ratios and can be enlarged without breaking the layout.

Keyboard navigation

Every link, menu and form usable without a mouse, with a visible focus outline.

Screen reader structure

Proper headings, landmarks, labels and alt text so assistive technology can read the page.

Accessible forms

Visible labels, clear error messages next to the field, no reliance on colour alone.

Motion and media

Reduced-motion support, no auto-playing sound, captions for video you provide.

Plain language

Short sentences and clear headings help everyone, especially people reading in a second language.

Process

How accessibility
fits the project

01

Requirements

Your size, province and sector: what applies to you.

02

Design

Contrast, type scale, focus states and tap targets checked in the mockups.

03

Build

Semantic code, labels, alt text, keyboard support.

04

Test

Automated checks plus manual keyboard and screen reader passes.

05

Hand over

Guidance for adding accessible content yourself, and an accessibility statement draft.

Pricing

What an accessible
website costs

Accessibility is part of how I build, not a paid add-on. Final prices in Canadian dollars.

■ Business website[01]
from $3,000 CAD

Accessible multi-page site, built to WCAG 2.x AA practices.

  • Accessible design and code
  • Keyboard and screen reader checks
  • Content guidance
Get a quote→
Accessibility review call[02]
$70 CAD/h

A walkthrough of your current site's main barriers.

  • Zoom session
  • Prioritized notes
Book a consultation→

Website accessibility in plain words

Website accessibility means building a site that people with disabilities can perceive, operate and understand. That includes someone using a screen reader because they're blind, someone who navigates with a keyboard because of a tremor, someone who enlarges text to 200%, someone with colour blindness, and a lot of older customers whose eyesight and fine motor control aren't what they were. In a country with an ageing population, that's a large share of your potential customers.

The international reference is the Web Content Accessibility Guidelines, WCAG, published by the W3C. Version 2.0 came out in 2008, 2.1 in 2018 and 2.2 in 2023. Each is organized into levels A, AA and AAA. Level AA is the common target for business websites.

AODA: what Ontario requires

The Accessibility for Ontarians with Disabilities Act sets standards for organizations operating in Ontario. Its information and communications standard requires public sector organizations, and private and non-profit organizations with 50 or more employees, to make their public websites and web content conform to WCAG 2.0 Level AA, with a few exceptions such as live captions and pre-recorded audio descriptions. Smaller organizations aren't covered by that website rule, though AODA has other obligations depending on size.

I'm not a lawyer, and I don't give legal opinions. What I do is build sites so that WCAG 2.x AA is the baseline, which covers the technical side of the AODA website requirement. The AODA website accessibility guide explains the rules in more detail.

Elsewhere in Canada

Outside Ontario, provinces are at different stages: Manitoba, Nova Scotia and British Columbia have their own accessibility laws, with standards being developed and phased in. Federally regulated organizations, such as banks, telecoms and interprovincial transport, fall under the Accessible Canada Act. Even where no rule applies to you, an accessible site is easier for everyone and tends to perform better in search, because search engines read structure much like assistive technology does.

What I check on every site

  • Colour contrast for text and buttons meets AA ratios
  • Text can be resized and the layout reflows on narrow screens without sideways scrolling
  • All functions work with a keyboard, in a logical order, with a visible focus
  • Headings follow a clear hierarchy; landmarks mark header, navigation, main content and footer
  • Images have meaningful alt text; decorative images are hidden from screen readers
  • Form fields have visible labels, errors are described in words, not only in red
  • Touch targets are large enough for a thumb
  • Motion respects the reduced-motion setting, and nothing flashes

I test with automated tools first, then manually with a keyboard and a screen reader, because automated tools catch only part of the issues.

Barriers I see most often

Light grey text on white backgrounds, because it looks elegant in a mockup. Buttons that say only "Click here" or "Learn more", which mean nothing to a screen reader user jumping between links. Pop-ups that trap keyboard focus. Menus that open only on mouse hover. Phone numbers placed in images. Each one is easy to avoid during design and annoying to fix after launch.

Content you add later

A site can launch accessible and slowly drift as new content is added: images without alt text, headings chosen for their size, PDFs scanned as images. During training I show you how to keep new content accessible, and the edit panel asks for alt text when you upload an image. Accessible design overlaps a lot with good UX/UI design, so it rarely feels like extra work.

Accessibility and Quebec

I build and write sites in English; French versions are outside my work. If your organization serves Quebec and your own team or translator produces a French version, it needs the same accessibility as the English one: language attributes set correctly so screen readers pronounce text properly, translated alt text and form messages. Rules on French content itself are covered in Quebec French-language website rules.

Related

Accessibility
and compliance

FAQ

AODA and WCAG
questions

Does AODA apply to my website?

Under AODA's information and communications standard, public sector organizations and private or non-profit organizations in Ontario with 50 or more employees must make their public websites meet WCAG 2.0 Level AA, with a few exceptions such as live captions. Smaller businesses aren't required to, but accessible sites serve more customers. For a definite answer on your obligations, check with the Ontario government's guidance or a lawyer.

What's the difference between WCAG 2.0, 2.1 and 2.2?

Each version adds criteria on top of the previous one. 2.1 added items for mobile, low vision and cognitive needs, such as content that reflows on small screens. 2.2 added more, such as minimum target sizes and focus that isn't hidden. AODA references 2.0 AA; building to the newer versions covers it and goes further.

Can you certify my site as compliant?

No. I build to WCAG 2.x AA practices and test with automated tools, keyboard and screen readers, but I don't issue certificates or legal opinions. If you need formal sign-off, an independent accessibility auditor can review the finished site.

Can you make my existing site accessible?

I don't patch sites built by someone else. Accessibility problems often sit deep in the theme and markup, so fixes on top rarely hold. I can walk you through the main barriers on a paid call and, if it makes sense, rebuild the site accessibly on the same domain.

Are accessibility overlay widgets enough?

Generally, no. Toolbars that promise one-click compliance don't fix the underlying code, and many people who use assistive technology find them get in the way. Accessibility has to be in the design and markup itself.

Accessible site

Need a site
everyone can use?

Tell me about your business, its size and province. I'll reply within one business day with what applies to you and what a new site would cost.

  • 9 short steps
  • No obligation
  • I reply personally
What happens after you send it
  1. I reply within 1 business dayPersonally, by email or on WhatsApp, whichever you prefer.
  2. A 30-minute call, freeI ask about your business, customers and budget. Beforehand I review your website and ads.
  3. A proposal with a price, in writingWhat I’ll do, by when and for how much. You decide with no pressure.
MarketingStep 1 of 9

What do you need most?