Skip to content
IQPayStub IQ

Accessibility statement

This site aims at WCAG 2.2 Level AA. That is a target, not a certificate. Below is what has been done and what has not, written plainly enough that you can judge it yourself.

Written and reviewed by Rocco Clayfield, Founder & DirectorLast reviewed

What has been done

  • Every page has exactly one H1, verified across every URL in the sitemap. In August 2026 the heading order was rebuilt on 21 pages — the province, Quebec and tool templates — where it jumped from H1 straight to H3.
  • Text contrast meets WCAG 2.2 SC 1.4.3 Contrast (Minimum) on every surface used on the site. The muted ink colour #64748b measured 4.34:1 on slate panels, 4.37:1 on the blue tint and 4.33:1 on the rose tint — all below the 4.5:1 threshold — and was darkened to #475569, which clears it on all of them.
  • Every input, select and file drop zone has a border at 4.76:1 against white, so the boundary of a control is visible (WCAG 1.4.11).
  • Links are underlined as well as coloured, so they are not distinguished by colour alone.
  • There is a skip link to the main content. Main carries tabindex="-1" so the skip link works in Safari, and it was verified as 153.5 by 40 pixels when focused.
  • Every standalone interactive target measured by our test harness is at least 24 by 24 CSS pixels (WCAG 2.2 SC 2.5.8). The harness deliberately excludes the skip link, which is 1 by 1 pixel at rest by design and 153.5 by 40 once focused. Links inside a sentence are exempt under the criterion’s own inline exception and are not measured.
  • Frequently asked questions use native details and summary elements, so they open with a keyboard and with JavaScript switched off.
  • Calculator results are announced with role="status" and aria-live="polite". Form errors use role="alert" with aria-invalid and aria-describedby.
  • Every element named by aria-controls exists in the DOM at all times, including when its panel is closed.
  • Tables carry a caption, column headers with scope, and row headers.
  • Page zoom is not disabled, and there is no horizontal scrolling at 390 pixels wide.
  • Diagrams are inline SVG with role="img", a title and a description, and every figure repeats its meaning in a caption in real text.
  • Scroll padding keeps the sticky header from covering a focused element or an anchor target.
  • French pages are served with lang="fr-CA" so a screen reader switches voice.
  • Every URL in the sitemap — 99 of them as at 14 August 2026 — was driven at 390 by 844 pixels in both Chromium and WebKit, including opening the mobile navigation on all 11 page templates in both engines. Pages outside the sitemap, including the 404 page, were not covered.

What has not been done

A statement that lists only successes is marketing. These are the real gaps, and they are the next things to close.

  • No automated axe-core scan has been run. The Playwright harness that already drives every page in two browser engines could carry one; it has not been wired in yet. There is no technical obstacle, only work not yet done.
  • No testing has been done with people who use assistive technology daily. Emulated testing finds structural faults; it does not find the ones that matter most.
  • No third-party accessibility audit has been commissioned.
  • Mobile testing is browser emulation, not physical hardware. It is reliable for layout, target size and navigation behaviour, and unreliable for touch feel and for the way the iOS Safari toolbar changes viewport height.
  • Desktop and tablet viewports have not been tested systematically. Only 390 CSS pixels is covered by an automated pass.
  • WCAG 2.2 SC 1.4.10 Reflow is measured at 320 CSS pixels, and we have not tested at 320. A page can pass at 390 and still scroll sideways at 320, so this is a real gap and not a technicality.
  • No 200 per cent zoom pass has been run. We can say that zoom is not disabled anywhere — there is no maximum-scale or user-scalable restriction on any URL in the sitemap — but not that text reflows cleanly at 200 per cent, because nobody has checked.
  • Firefox has not been tested. Its automation build would not install in the environment used for the other two engines.

Report a barrier

If something on this site stopped you doing what you came to do, tell us what page it was and what happened. Email hello@paystubiq.com. You will get a reply within 10 business days, and if the fix is quick it will be live before the reply.

If you need any content on this site in another format — larger text, plain text, or read aloud — ask, and it will be provided at no cost.

The legal position, stated honestly

Canada has the Accessible Canada Act, and Ontario has the Accessibility for Ontarians with Disabilities Act. This statement is a good-faith description of the current state of the site. It is not a claim of compliance, a conformance report, or a certification, and it is not legal advice. No audit has been carried out by anyone other than the publisher.

How this statement is kept honest

It is updated whenever an accessibility change ships, and every claim on it is one that was measured rather than assumed. Last reviewed August 2026.

Upload Your Pay StubDeductions