Accessibility
In short
This site is built to be usable by everyone, including people who use screen readers, keyboards, magnification, or who find dense text difficult. We target WCAG 2.2 Level AA. If anything gets in your way, please tell us.
What we have done
- Dyslexia-friendly by default: the Lexend typeface, left-aligned text, generous line spacing (1.75), a restricted reading width, short sections, and no italic body text or justified text.
- Strong colour contrast for text, and status is never shown by colour alone (icons and text labels accompany it).
- Full keyboard access: every interactive element is reachable and operable by keyboard, with a visible focus outline and a \u201cskip to main content\u201d link.
- Screen-reader support: semantic HTML, proper headings and landmarks, labelled forms, descriptive links, and live-region announcements for tool results.
- Reflow and zoom: content reflows to a single column on small screens and remains usable at 200% zoom, with no loss of function.
- Reduced motion: we use very little animation, and honour the \u201creduce motion\u201d setting in your system.
- Works without JavaScript: all core content and navigation work with JavaScript turned off; the calculators are an enhancement on top.
- Meaningful text: images have appropriate alternative text (decorative icons are hidden from screen readers), and every visual explanation has a text equivalent.
Standard we aim for
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. Accessibility is tested with both automated tools and manual keyboard and screen-reader checks. No automated tool catches everything, so manual testing is part of our process.
Known limitations
We are committed to fixing accessibility barriers. If you find one, please report it (below) and we will prioritise it. Any known outstanding issues will be listed on the updates page.
Tell us about a barrier
If any part of this site is hard to use with your assistive technology or setup, please contact SupportCALL ICT Solutions via supportcall.com.au, describing the page and the problem. We treat accessibility reports as a priority.
Verified 20 July 2026