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.

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.

What we measured, and when

Measured 9 September 2026 in Chrome, driven by Playwright, at 1280×1000 and on an iPhone 14 profile, across the landing page, the journey builder, the ledger, the register and this section:

Focus is visible on every control. A focused primary button computes a two-layer ring — a 2 px white halo and a 2 px ring in #087871, which is 4.81:1 against the page background and 5.34:1 against a card. WCAG 2.1 SC 1.4.11 asks for 3:1.
Body text contrast. Running text is 8.57:1, headings 15.52:1, quiet sub-lines 5.71:1, white on the dark band 14.88:1. SC 1.4.3 asks for 4.5:1 for normal text.
Nothing runs off the side of a phone. Horizontal overflow measured 0 px on the pages above at 390 px wide, and no text is set below 12 px anywhere.
Touch targets. On the ledger at phone width, no control is smaller than 24×24 px (WCAG 2.2 SC 2.5.8). Twenty-one of twenty-three are smaller than the 44×44 px comfort target we would prefer — see below.
No console or page errors on any route we walked, on either profile.
A skip link is the first thing in the tab order; the page declares lang="en"; animation and scrolling are switched off for prefers-reduced-motion: reduce; a forced-colours (high contrast) mode gets a solid outline instead of a shadow ring.

What is not conformant yet

Touch targets below 44×44 px. Most navigation and footer links on a phone are about 36 px tall. They meet the 24×24 px minimum in WCAG 2.2 and the inline-link exception covers links inside a sentence, but a bigger target is easier for a hand that shakes, and we are raising them.
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.
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.

If something blocks you

Write to bo@precisionfederal.com. 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.

Statement first published 9 September 2026 by Precision Federal, Ames, Iowa. Related: privacy, how the count is kept honest, security contact.