Accessibility
Built to be reachable.
We build Clarity Systems to work with keyboards, screen readers, and contrast-sensitive eyes. If something is not working for you, tell us and we will fix it.
- Keyboard
- Screen readers
- Reduced motion
- AA contrast
- External audit to come
What we have built for
- Keyboard navigation throughout the diagnostic, results, and proposal viewer. Every clickable element has a visible focus ring, 2px green at a 3px offset, and a skip link at the top of every public page jumps past the navigation.
- Screen readers. Headings are structured semantically, form fields have explicit labels, dialogs declare
role=“dialog”witharia-modalandaria-labelledby, and live-updating regions (autosave status, unread comments) announce changes viaaria-live. - Reduced motion. Every animation honours
prefers-reduced-motion. With it on, the calculating screen holds its status phrases instead of crossfading, the dial holds still, and the finished state of every screen is what renders. - Contrast. Body text meets WCAG AA (4.5:1) on every primary surface. Each accent comes in one tier for light grounds and one for dark, so a coloured word or figure holds AA wherever it sits.
- Text size. Body copy is 16px in the application and 19px on the public pages, and the page can be zoomed to 500% without losing anything.
- Australian English. The site is tagged
lang=“en-AU”so screen readers pronounce “organise”, “colour” and “centre” correctly.
What we are 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.