Services

Website accessibility and AODA compliance, built to WCAG 2.2 AA

Website accessibility means people who use a keyboard, a screen reader or zoom can use your site as easily as anyone else. We build new sites to WCAG 2.2 AA, audit and fix the site you already have, and set your editors up to keep it accessible after launch. That covers the AODA in Ontario and the Accessible Canada Act for federally regulated organizations. We don't use overlays.

Rated 5.0 out of 5,72 Google reviewsBuilt for YWCA Calgary, RDCK, CHF Canada and AKBLG

Public-sector and nonprofit sites we've built

  • YWCA Calgary
  • Regional District of Central Kootenay
  • CHF Canada
  • AKBLG
  • CHF BC
  • ERP-One

What AODA and WCAG compliance mean for your website

WCAG is the standard. The AODA and the Accessible Canada Act are the laws that point to it.

The Web Content Accessibility Guidelines (WCAG) are a technical standard from the W3C. A website conforms to WCAG and complies with the laws that name it. Canadian laws and most RFPs ask for Level AA. Version 2.2 is the newest, and a site built to 2.2 AA also meets 2.1 AA and 2.0 AA.

Ontario (AODA): since January 1, 2021, public-sector organizations, and businesses and nonprofits with 50 or more employees in Ontario, have had to make their websites conform to WCAG 2.0 AA. Live captions and pre-recorded audio descriptions are exempt. Checked against Ontario Regulation 191/11, section 14 on November 15, 2026.

Federal (Accessible Canada Act): federal departments, Crown corporations and federally regulated businesses such as banks, telecoms and airlines will have to meet CAN/ASC-EN 301 549, whose web requirements match WCAG 2.1 AA. It applies to new and updated web pages: in the federal public sector from December 5, 2027, and at businesses with 100 or more employees from December 5, 2028. Checked against the Canada Gazette (SOR/2025-255) on November 15, 2026.

Everywhere else: Manitoba requires WCAG 2.1 AA from every organization. Alberta and British Columbia have no web standard yet, so public bodies write WCAG 2.1 or 2.2 AA into their RFPs. Our guide to website accessibility laws in Canada covers every province, with dates and sources. Checked against Accessibility Manitoba and the provincial sources in that guide on November 14, 2026. This is a summary, not legal advice.

Accessibility audits, fixes or a rebuild

Three different jobs get sold as "accessibility", and they cost very different amounts.

An accessibility audit tells you where the site stands. We run automated tests across every page, then test a sample of your templates and key tasks by hand (donating, applying, paying, getting in touch) with the keyboard, zoom and, when scoped, a screen reader. You get a list of failures ranked by how badly each one blocks people, with the WCAG criterion, the page and the fix. An audit changes no code.

Remediation fixes what the audit found. We start with templates, because one template fix repairs every page built on it, then move to content: headings, alt text, link text, tables and PDFs. We fix sites on WordPress, Shopify, Webflow and Sanity. If the platform and theme are sound, this costs far less than a rebuild.

Building it in makes sense when the site is due for a redesign anyway, or when the theme or page builder is the problem. Accessibility designed into a component system costs little extra at build time. Retrofitting it later costs far more.

A formal audit or conformance report for procurement, such as a VPAT or an Accessibility Conformance Report reviewed by an independent specialist, is separate work with its own cost. We'll scope it with the project and fix what it finds. We never call a site "certified".

Overlays don't count. We don't install accessibility widgets or overlays. They leave the underlying code as it was, so the barriers stay, and they can clash with the screen readers and browser settings people already rely on.

How an accessibility project runs

A review and fix project usually runs four to eight weeks, depending on how many templates and documents the site has. On a new build, automated and keyboard checks run throughout, and the rest is scoped with the project.

  1. Scope (week 1)

    We agree which law and WCAG level apply to you, pick the templates and key tasks to test, and list your documents. You give us access to the site, your analytics and any complaints or RFP requirements.

    You keep: a written scope that names the standard and the pages tested.

  2. Test (weeks 1 to 3)

    Automated checks run across the whole site. Then we test the sample by hand: keyboard and focus, zoom and reflow, contrast as it renders, forms and errors, and screen readers when scoped. You give us test accounts and tell us which tasks matter most.

    You keep: findings ranked by impact, each with its WCAG criterion, page and fix.

  3. Fix the templates (weeks 3 to 6)

    We fix the shared code first: navigation, forms, components and colours. You review each fix on a staging site before it goes live.

    You keep: the fixed code in your repository or theme, and a change log.

  4. Fix content and documents (weeks 5 to 8)

    We correct headings, alt text, link text and tables, and list every PDF that fails. You decide which documents become web pages and which get fixed or retired.

    You keep: the document list and what happened to each one.

  5. Retest and hand over (final week)

    We retest the sample, draft your accessibility statement and feedback contact, and train your editors. You publish the statement.

    You keep: the retest results, the statement and an editor guide.

Numbers from sites we built, and from our own

These figures come from our published case studies, our own accessibility statement and Deque's research.

  • 51

    Blocks YWCA Calgary's team uses to build pages without a developer

    Source
  • 90+

    Mobile PageSpeed on ERP-One's rebuild, with WCAG AA out of the box

    Source
  • 2

    Official languages on CHF Canada's site, translated down to every slug

    Source
  • 15

    Issues we found and fixed on our own site in our August 2026 WCAG 2.2 AA audit

    Source
  • 57%

    Share of issues automated testing caught in Deque's audits. The rest needed a person to find.

    Source

What we check

Automated tools catch some of these. The rest need manual testing.

  • Keyboard and focus

    Every menu, form, dialog and control works without a mouse, in a sensible order, with a focus outline you can always see, even under a sticky header.

  • Screen readers

    Headings, landmarks, labels and status messages make sense read aloud. We test with NVDA, JAWS or VoiceOver when it's scoped.

  • Contrast as it renders

    Text, icons and focus outlines are measured in the browser, over real images and backgrounds, not only in the design file.

  • Zoom and reflow

    Pages stay usable at 200% text size and 320 pixels wide, with nothing cut off and no sideways scrolling.

  • Forms and errors

    Every field has a label, errors say what went wrong and how to fix it, people don't type the same thing twice, and signing in doesn't need a puzzle.

  • Tap targets and motion

    Buttons and links are big enough to hit, and animation respects the reduced-motion setting.

  • Documents and media

    PDFs are tagged or replaced with pages, and videos have captions and transcripts.

Keeping a site accessible after launch

After launch, accessibility mostly slips through content changes.

An image goes up without alt text, a heading gets picked for its size, a scanned PDF goes out at 11 p.m. We build editor blocks that make the accessible choice the easy one: heading levels set by the block, alt text asked for on upload, buttons that need real link text. Your editors get training at handover. YWCA Calgary's team builds pages from 51 blocks and hasn't needed a developer call since launch.

After launch, a maintenance plan can include a scheduled re-check and fixes when someone reports a barrier.

We hold our own site to this. Our accessibility statement says papercrane.ca is partially conformant with WCAG 2.2 AA and names the gaps we haven't closed yet, and our conformance report is public.

What clients say about working with us

  • 5 out of 5 stars.

    We recently wrapped up a large website project with Paper Crane, and I cannot say enough good things about this team. They are so wonderful to work with, detail oriented, helpful, and of course their team's expertise is unmatched. Would recommend them to anyone considering working with them :)

    Allison Wheeler · Google ·
  • 5 out of 5 stars.

    Working with Paper Crane has been a really great experience. The team has been really communicative and enthusiastic. Our non-profit worked with them to redesign and update our website and we're really happy with our new look. They've also saved us money by helping us get a non-profit discount from our new web host and by helping us make better use of the host's integrated applications, so that we're not paying for duplicate services. Looking forward to working with them again.

    HiVE Operations · Google ·
  • 5 out of 5 stars.

    We had a complete website overhaul last year, and Rob has been an absolute star ever since. He’s been incredibly responsive and helpful with every change we've needed, making sure that the site is user-friendly for our customers and easy to manage on the backend for our team. It's been a long journey, and Rob has been a huge factor in the site's success. Many thanks for all your support!

    Evelyn Whicher · Google ·
  • 5 out of 5 stars.

    Paper Crane has been a great partner for web development and support. Their turnaround times are excellent, communication is clear, and they consistently find practical solutions to issues quickly. It's reassuring to know they're just an email away when something urgent comes up.

    Jenn Geiger · Google ·

Questions about website accessibility and AODA compliance

What does AODA compliance mean for a website?

In Ontario, public-sector organizations and businesses and nonprofits with 50 or more employees in Ontario must make their websites conform to WCAG 2.0 AA. Building to WCAG 2.2 AA clears that bar. Our guide to accessibility laws in Canada has the details and sources.

Is WCAG compliance a legal requirement?

WCAG itself is a standard, not a law. Laws such as the AODA, the Accessible Canada Act and Manitoba's act require you to conform to it. Where no law names it, human rights law still applies, and most public-sector RFPs ask for WCAG 2.1 or 2.2 AA.

What's included in an accessibility audit?

Automated tests across the site, then manual testing of your main templates and tasks with the keyboard, zoom and, when scoped, a screen reader. You get a ranked list of failures with the WCAG criterion, page and fix for each.

Can you certify our website as accessible?

No, and be wary of anyone who offers. Ontario doesn't certify websites under the AODA. We build and fix to WCAG 2.2 AA, and when you need a formal report for procurement we scope an independent review with its own cost.

Will an accessibility overlay or widget make our site compliant?

No. Overlays don't fix the underlying code, so the barriers stay, and they can interfere with the assistive technology people already use. We don't install them.

Can you fix a website you didn't build?

Yes. We audit it first. If the platform and theme are sound we fix it in place; if the theme is the problem, we'll tell you when a rebuild costs less than the fixes.

Do you test with screen readers?

Every build gets automated and keyboard testing. Screen-reader testing with NVDA, JAWS or VoiceOver happens when scoped, usually because your project or RFP asks for it.

What's a VPAT or Accessibility Conformance Report, and do we need one?

A VPAT is a template, and once filled in it becomes an Accessibility Conformance Report: a criterion-by-criterion account of how a product meets WCAG. Procurement teams ask for them. If nobody is asking you for one, you probably don't need it yet.

Can you work as an accessibility consultant for our team?

Yes. We review designs before they're built, check your developers' work, help write the accessibility section of an RFP, and train editors.

How do we keep the site accessible after launch?

Editor blocks that make accessible choices the default, training at handover, and a scheduled re-check. Under a maintenance plan, we fix barriers when someone reports one.

Not sure where your site stands?

Run a page through our free accessibility checker, then book a 30-minute call with our Calgary team. We'll tell you which rules apply to you and whether to fix the site or rebuild it.

Book a call