What we test for, how, and where we know we fall short.

1Our commitment

We are working to make this site usable by everybody, including people using a screen reader, a keyboard alone, magnification, a high-contrast mode, or a browser with motion or scripting turned off.

This is not only a matter of principle for us. PermitX is sold to Ontario municipalities and building departments, and the Accessibility for Ontarians with Disabilities Act makes WCAG Level AA a legal requirement of those organisations and of what they buy. A tool a department cannot procure is not a tool.

2Standard and current status

Target standard: Web Content Accessibility Guidelines 2.1, Level AA. This is a superset of the WCAG 2.0 Level AA that the AODA's Information and Communications Standard requires.

Status: partially conformant. We use that phrase in the sense WCAG uses it. Most of the site meets the standard, and clause 5 names what does not. We have not commissioned an independent third-party audit, and we say so rather than implying one. If you need one for a procurement file, ask us and we will tell you honestly where we are with it.

3How this is measured

3.1 On every build, automatically

The repository carries an audit that drives a real browser over every page at nine viewport widths, the widths phones and tablets actually report rather than round numbers, and measures:

• Text contrast against the surface it is actually on. The backdrop is composited through the whole ancestor chain rather than assumed, because on this site almost every element's own background is transparent and the bands are semi-opaque. The large-text threshold follows WCAG's own definition. Anything under its floor fails the build rather than printing a warning.
• Content running past the edge of the viewport, or scrolling the page sideways.
• Text cut off by its own box instead of wrapping.
• Tap targets smaller than the 44px floor.

That contrast gate exists because of a real failure rather than as a precaution. One colour token used for the site's smallest type, which is the form field labels, the billing period under each price and the excluded rows in the pricing table, sat at 3.3:1 against white for months and survived every visual review, because a token failure looks intentional at all 110 of its usages at once. It is now measured, and the number it has to clear is measured against the darkest surface it appears on rather than against the page.

3.2 By hand

Keyboard traversal of every page including the mobile navigation drawer, which traps and restores focus and closes on Escape; the site with JavaScript disabled; the site with reduced motion requested; and screen reader behaviour on the interactive and drawn content. Automated tools cannot judge whether a heading structure makes sense or whether alternative text says the useful thing, and we do not pretend otherwise.

4What is built in

• It works without JavaScript. Every page is a static file and every scroll-triggered reveal is visible by default. The hiding is only ever added by script once it can guarantee it will also un-hide. With scripting off you get all of the content, laid out, immediately.
• Motion is opt-out and it is honoured everywhere. The animated scenes, the reveals and the hero footage all stop under prefers-reduced-motion. The background video is not even requested on a narrow viewport, a metered connection, or when reduced motion is set.
• Every illustration is vector and scales cleanly. There are no screenshots of the product anywhere on this site; the drawings, panels and maps are drawn in the site's own colour tokens, so they follow a zoom to any magnification without blurring and they respond to the surface they are on.
• Decoration is marked as decoration. Animated scenes and drawn ornament are hidden from assistive technology, so a screen reader is not read a list of graphical elements it can do nothing with, and the meaning they illustrate is in the surrounding text.
• Landmarks, headings and labels. One h1 per page, a heading structure that descends without skipping, real label elements on every form field, and errors announced rather than only coloured.
• Visible focus. Focus is never removed, and the focus ring is drawn to be visible on both the light surfaces and the black bands.

5Known limitations

Stated rather than omitted, because a statement with no limitations in it is a statement nobody believes.

5.1 The hero background on a narrow screen

The home page opens on aerial footage of Toronto behind the headline. On a phone the copy fills the frame, so there is no quiet corner of the image to spend legibility in: either the photograph is invisible or the small type over it sits below a 4.5:1 composite. We chose to keep the photograph visible and to give the small copy its own darkened plate behind the glyphs, which is measured and documented in the source.

The headline itself is large text and clears its 3:1 floor several times over. The two lines that fall short are the eyebrow above it and the standfirst below it, and both restate content that appears again in plain text further down the same page, so no information is available only through them. This is the one place on the site that makes that trade, and it is a decorative background rather than content.

5.2 Drawn technical illustrations

Several pages carry drawn permit drawings, elevations and measurement scenes. These are illustrations of a process, and the argument each one makes is always also written in the prose beside it. They are not offered as an accessible substitute for the drawing content itself, and a lettered dimension on a drawn sheet is not exposed as text to a screen reader.

5.3 Third-party content

Typefaces are loaded from Google Fonts and the contact form is delivered by Web3Forms. We do not control their infrastructure, and the site is built to degrade to a system typeface and a plain email link if either is unavailable.

5.4 The product is a separate assessment

This statement covers this website. PermitX itself runs inside Quoto Build, which is a different application with a different interface, and its conformance is assessed separately. If you are evaluating PermitX for a public sector procurement, ask us about the application specifically, and do not read this page as covering it.

6Feedback, and how to reach a person

If any part of this site is a barrier to you, tell us. Write to contactus@permitx.io or call 905 965 0323 and quote PX-ACCS-001. Tell us the page and what happened; you do not need to know which guideline it is.

We aim to reply within two business days. If you need something on this site in another format, whether that is large print, plain text, or read to you over the phone, ask and we will provide it at no cost. That is an AODA obligation and it is also just the right way to answer.

This is version 1.0 of this statement, effective 10 August 2026. It is reviewed when the design system changes and at least once a year.