Accessibility
Accessibility statement
This tool is for people who are often exhausted, often in pain, and often reading on a phone in a waiting room. If any part of it keeps you out, that is a defect, and we want the report.
- WCAG 2.1 AAthe standard the Revised Section 508 rules point to for federal use
- 15.93:1running text on the page background, light theme, measured Sep 30, 2026 (SC 1.4.3 asks for 4.5:1)
- 5.80:1the focus ring against the page background, light theme (SC 1.4.11 asks for 3:1)
- 0 pxhorizontal overflow at 390 px wide on the eleven pages measured
What we aim at
WCAG 2.1 Level AA, which is the standard the Revised Section 508 rules point to for federal use. We build to it deliberately rather than testing for it afterwards: one h1 per page, real headings in order, labels tied to their controls, a skip link, a visible focus indicator, no colour used as the only carrier of meaning, no motion for anyone whose system asks for less of it.
If something blocks you
Write to us through Contact. Tell us the page, what you were using (browser, screen reader, phone), and what happened. We answer every message, we will send you the information another way if you need it now, and what we change because of you gets published on the register with the date.
ContactWhat we measured, and when
Measured Sep 30, 2026 in Chrome, driven by Playwright, at 1440×900 and at 390×844 with touch, across the landing page, the journey builder, the ledger, the live register, the survey, the method page and the privacy, adoption, developer, account and accessibility pages:
Every colour pair in the light theme, measured
Ten pairs, each drawn against the ratio WCAG 2.1 asks for
| Pair | Sample and measured against the rule | Ratio | Asks for |
|---|---|---|---|
| Running text on the page | 15.93:1 | 4.5:1 | |
| Running text on a card | 17.22:1 | 4.5:1 | |
| Secondary text | 9.36:1 | 4.5:1 | |
| Quiet sub-lines | 5.83:1 | 4.5:1 | |
| Links and teal labels | 5.80:1 | 4.5:1 | |
| White on the primary button | 16.42:1 | 4.5:1 | |
| Focus ring, against the page | 5.80:1 | 3:1 | |
| Focus ring, against a card | 6.28:1 | 3:1 | |
| Text box edge, against a card | 3.26:1 | 3:1 | |
| Text box edge, against the page | 3.02:1 | 3:1 |
Every colour pair in the dark theme, measured
The same ten pairs, computed from the dark theme's own colours
| Pair | Sample and measured against the rule | Ratio | Asks for |
|---|---|---|---|
| Running text on the page | 17.86:1 | 4.5:1 | |
| Running text on a card | 14.61:1 | 4.5:1 | |
| Secondary text | 13.65:1 | 4.5:1 | |
| Quiet sub-lines | 9.51:1 | 4.5:1 | |
| Links and teal labels | 12.61:1 | 4.5:1 | |
| Dark text on the primary button | 8.27:1 | 4.5:1 | |
| Focus ring, against the page | 11.56:1 | 3:1 | |
| Focus ring, against a card | 9.45:1 | 3:1 | |
| Text box edge, against a card | 4.54:1 | 3:1 | |
| Text box edge, against the page | 5.55:1 | 3:1 |
The ratios in the cards below are for the light theme. The dark theme’s are in the second table, computed the same way from its own colours: running text is 17.86:1 on the page and the focus ring 11.56:1.
- Meets SC 1.4.11
5.80:1against the page, light theme
Focus is visible on every control.
In the light theme, a focused button computes a two-layer ring: a 2 px white halo and a 2 px ring in
#0a6c65, which is 5.80:1 against the page background and 6.28:1 against a card. WCAG 2.1 SC 1.4.11 asks for 3:1. - Meets SC 1.4.3
15.93:1running text, light theme
Text contrast.
In the light theme, running text is 15.93:1 on the page and 17.22:1 on a card, secondary text 9.36:1, quiet sub-lines 5.83:1, links and teal labels 5.80:1, and white on the primary button 16.42:1. SC 1.4.3 asks for 4.5:1 for normal text.
- Measured
0 pxoverflow at 390 px
Nothing runs off the side of a phone.
Horizontal overflow measured 0 px on every page above at 390 px wide, and no text is set below 12 px anywhere (the smallest is 12.25 px, in code samples).
- Measured
44 pxsmallest target outside a sentence
Touch targets.
On the pages above at phone width, every control outside a sentence has a target at least 44 px tall (on the survey, the whole 52 px answer row is the target; at the foot of every page, the information toggle’s 22 px circle has a 44×44 px target). Links inside a sentence are covered by the inline exception in WCAG 2.2 SC 2.5.8.
- axe-core
0WCAG 2.1 A or AA violations
An automated check
axe-core found no WCAG 2.1 A or AA violation on the privacy, adoption, developer, account and accessibility pages, at either size, with every folded section open.
- In place
Skip link, language, motion, high contrast
A skip link is the first thing in the tab order (on the home page the story box takes focus when the page opens, so the skip link is one Shift+Tab back from it); every page declares
lang="en"; animation and scrolling are switched off forprefers-reduced-motion: reduce; a forced-colours (high contrast) mode gets a solid outline instead of a shadow ring.
Checked and fixed on Sep 30, 2026
Three findings of this re-measure. Two were fixed the same day; the third already met the rule once the whole target was measured. Each was measured again on the rendered pages.
- Fixed Sep 30
Text box edges
In the light theme, the outline of a text box was
#e1e5ea, 1.27:1 against white, where SC 1.4.11 asks for 3:1. It is now#878f9b: 3.26:1 against white and 3.02:1 against the page background. - Fixed Sep 30
Information toggle
The toggle at the foot of every page was a 22 px target, under the 24×24 px minimum in WCAG 2.2. It keeps its 22 px circle and now has a 44×44 px target, centred on it.
- Already met
Survey answers
Each answer’s 18 px circle sits inside a label that is the whole target: 52 px tall, measured 324×52 px on a 390 px phone.
What is not conformant yet
- Not yet
No screen-reader pass yet
We have not completed a VoiceOver, NVDA or JAWS walk of the whole flow. Until we have, we will not claim it works well with one: we will only say the markup was built for it.
- Not yet
No independent audit
Everything above is our own measurement, and you can reproduce it: the site is open source under Apache-2.0 and the numbers come from the browser, not from us.
Statement first published Sep 9, 2026 by Precision Federal, Ames, Iowa, and re-measured Sep 30, 2026. Related: