Paper Crane / legal / accessibility
( Scroll to explore ↓ )
Paper Crane builds websites for a living, so we hold our own site to the standard we ask clients to meet. This page says where papercrane.ca currently stands, what we know is still wrong, and how to tell us when we have missed something.
Conformance status
The Web Content Accessibility Guidelines (WCAG) set out how to make web content usable by people with disabilities. They define three levels: A, AA, and AAA.
papercrane.ca is partially conformant with WCAG 2.2 Level AA. Partially conformant means most of the site meets the standard, but some parts do not yet.
Two things fall short, and we would rather name them than round up:
The main heading on a few pages, including the homepage, is an editorial phrase rather than a description of what the page is about. Someone navigating by headings gets less useful information than they should. We are rewriting that copy.
We have not yet run a full test with a screen reader such as NVDA, JAWS, or VoiceOver. We checked the underlying code, the accessibility information the browser exposes, and how the page reads when the layout is stripped away, but that is not the same as listening to it. Until we do that pass, treat any claim about how the site sounds as unverified.
What we fixed most recently
We audited the site against WCAG 2.2 Level AA on 23 August 2026 and fixed fifteen issues. The ones most likely to have affected you:
Two of the three case studies in the homepage slider could not be reached with a keyboard at all. There are now previous and next buttons, and the section stacks into a plain vertical list if you have reduced motion turned on.
The contact form accepted submissions with required fields left empty and gave no error when an email address was malformed. Every field is now checked, and each error says what to do about it.
Looping videos on case study pages had no pause control. They do now.
The client logos at the bottom of the homepage were invisible to screen readers, because the code asked for the wrong field and got nothing back. All 48 client names are now announced.
Text that was too faint to read has been darkened in several places, pages no longer scroll sideways on a narrow phone, and the focus outline is now visible on dark backgrounds as well as light ones.
Telling us about a problem
If you hit a barrier on this site, we want to know. Email hello@papercrane.ca and describe what you were trying to do and where it went wrong. A link to the page helps. So does telling us what browser or assistive technology you were using, if you know.
We aim to reply within five business days.
If something is blocking you right now and you need the information another way, say so in the email and we will send it to you directly.
Compatibility with browsers and assistive technology
The site is built to work with current versions of Chrome, Edge, Firefox, and Safari, and with screen readers, screen magnification, speech recognition, and keyboard-only navigation. It may not work properly in browsers more than two versions old.
Technical specifications
Accessibility on this site depends on HTML, WAI-ARIA, CSS, and JavaScript. If JavaScript is turned off, some pages will not display correctly.
How we assessed the site
Paper Crane assessed papercrane.ca ourselves. We are the developer, so this is a self-assessment and has not been reviewed by an independent accessibility specialist.
We tested sixteen pages, chosen to cover every page template the site uses. We ran automated checks with axe-core against the fully rendered page, then scripted tests for keyboard order, focus visibility, colour contrast measured as it actually renders, tap target size, layout at 320 pixels wide, and increased text spacing. A person then worked through twelve checks by hand on the live site, covering the things no tool can judge, such as whether a video can be paused and whether an error message is actually helpful.
The full audit and a detailed conformance report are available if you want them. Email us and we will send them over.
Date
This statement was written on 23 August 2026 and describes the site as it was on that date.