Accessibility statement

Built to be read.

Last reviewed 2026-08-12 · applies to praetu.com

A site about verification should be honest about its own state. Our working target is WCAG 2.2 level AA. Here is where we stand, including the gaps.

What's in place

• Full keyboard operability: skip-to-content link, visible focus outlines, no keyboard traps, and disclosure widgets (FAQ, data tables) using native elements.
• Every chart has a table-view twin: no value on this site is reachable only by hovering a graphic. Chart tooltips supplement; they never gate.
• Chart colors are validated programmatically for color-vision-deficiency separation and contrast against our background, and class identity is never carried by color alone (legends and tables carry it too).
• Text contrast meets or exceeds AA on all body and UI text.
• prefers-reduced-motion is honored: scroll reveals, shimmer, and animated bars all become static.
• Semantic structure throughout: landmarks, one h1 per page, ordered heading levels, labeled form fields with explicit error messages, breadcrumbs.
• Images and graphics carry alt text or are marked decorative; charts carry descriptive aria-labels plus their table equivalents.
• The site works without JavaScript for all written content; charts degrade to their data downloads.
• A light theme (the "Light" toggle in the navigation) for readers who find light-on-dark text harder to read. Both themes are contrast-checked independently (the chart palettes are separately validated against each background) and your choice is remembered on this device.

Known gaps

• Term-definition tooltips are hover/focus-based on desktop; on touch devices the same definitions live in the FAQ rather than inline. We're evaluating a tap-to-toggle pattern.
• The scatter chart's nearest-point hover is mouse/touch-oriented; keyboard users get the full table view instead. Per-point keyboard traversal is under consideration.

Found a barrier?

Tell us and we'll fix it: accessibility reports get the same two-business-day response promise as everything else, and fixes to real barriers ship ahead of feature work. Contact us or email hello@praetu.com with the page and what got in the way. If you need any published result in another format (the weekly data, for instance), ask; the underlying JSON is freely downloadable and we're happy to help convert it.