Built to be reachable

Accessibility statement.

We build Clarity Systems to work with keyboards, screen readers, and contrast-sensitive eyes. If something isn't working for you, tell us and we'll fix it.

What we’ve built for

  • Keyboard navigation throughout the diagnostic, results, and proposal viewer. Every clickable element has a visible focus halo (a 3px bronze ring).
  • Screen readers. Headings are structured semantically, form fields have explicit labels, dialogs declare role=“dialog” with aria-modal + aria-labelledby, and live-updating regions (autosave status, unread comments) announce changes via aria-live.
  • Reduced motion. The calculating animation honours prefers-reduced-motion; if you have it enabled, the status phrases hold instead of crossfading.
  • Contrast. Body text targets WCAG AA (4.5:1) on every primary surface. We’ve specifically calibrated bronze-deep + bronze-light for the cream/charcoal-deep dark backgrounds we use.
  • Australian English. The site is tagged lang=“en-AU”so screen readers pronounce “organise”, “colour”, “centre” correctly.

What we’re still working on

  • A formal third-party WCAG 2.2 audit. We meet the AA bar internally today; the external audit is a 2026 Q3 commitment.
  • Mobile screen-reader testing across the proposal viewer’s comment-thread sidebar.

Tell us when something doesn’t work

If you hit a wall, a focus that doesn’t land, copy that doesn’t read aloud right, contrast that’s too low, email info@doitwithclarity.org. We’ll get back to you within 2 business days with a fix or a workaround.