Accessibility
What we have done to make this site usable for everyone, what is still outstanding, and how to tell us when something gets in your way.
Klarite Pty Ltd wants this website to be usable by as many people as possible, including people who use a screen reader, navigate by keyboard alone, rely on voice control, or need to enlarge the text. This page records how far we have got, tested rather than assumed, and what we already know is not right yet.
01Our commitment
Accessibility is treated here as a defect class rather than a preference. Where a design decision and an accessibility requirement have conflicted on this site, the accessibility requirement has won and the design has been changed to match.
We are also subject to the Disability Discrimination Act 1992 (Cth), which applies to services provided online in Australia.
02The standard we aim for
We aim to meet WCAG 2.1 Level AA — the Web Content Accessibility Guidelines published by the World Wide Web Consortium, and the benchmark the Australian Human Rights Commission points to.
03How the site measures up
This website is partially conformant with WCAG 2.1 Level AA. Partially conformant means some parts of the standard have been verified and others have not yet been assessed. It does not mean we know of failures we have chosen to leave; the ones we do know about are listed in the next section.
Verified as of 1 September 2026, across every public page at both a 375px and a 1280px viewport:
- Text contrast meets AA everywhere. Fourteen failures were found and all fourteen were fixed. The brand teal caused most of them, and the palette was changed rather than the standard relaxed.
- Every form field has a label that assistive technology can read, not just one printed next to it.
- Buttons can be operated by voice.Where a control’s spoken name did not contain the words written on it, the name was corrected.
- Pages can be read without JavaScript. Every page is delivered as complete HTML.
- The keyboard focus indicator is visible against every background the site uses.
- Content that scrolls sideways can be reached and moved by keyboard.
- There is no audio or video anywhere on this site, so no captions or transcripts are required.
- Nothing moves or plays on its own, and no content flashes.
04What we know is not right yet
Listing these is the point of this page. Each was reproduced before it was written down.
| Issue | What it means for you | Guideline |
|---|---|---|
| Headings inside some Insights articles skip a level | A few older posts move from a third-level heading straight to a sixth. Screen reader users navigating by heading get a structure that does not match the article. The posts are authored in WordPress, so this is fixed post by post rather than in code. | 1.3.1 Info and Relationships (A) |
| Pop-up forms and the ProveSUITE detail panels are not fully tested | The enquiry pop-ups and the product panels on the ProveSUITE page have not been through a keyboard-only or screen reader pass. We have not found a fault in them; we have not yet confirmed there is none. | Not yet assessed |
| No screen reader testing has been done | Nobody has yet worked through this site with NVDA, JAWS or VoiceOver. Everything in "How we tested it" below is either automated or sighted keyboard checking. | Not yet assessed |
Automated testing reaches roughly a third of WCAG. A clean automated result is a floor, not a pass, and we have not claimed more than it supports.
05How we tested it
Last full review 1 September 2026.
- Automated:axe-core 4.10 against every public page, at a 375×812 and a 1280×900 viewport, checking WCAG 2.0 and 2.1 at Levels A and AA.
- Manual: sighted checks of colour contrast against the rendered pixels, keyboard focus order through the main pages, and the reading order of the page source.
- Not yet done: testing with a screen reader, and a keyboard-only pass through the pop-up forms and the ProveSUITE product panels.
This site is built with Next.js and served by Vercel. Insights articles are authored in WordPress, so an article’s own structure depends on how it was written as well as on the code.
06Tell us if something blocks you
If any part of this site stops you doing what you came to do, please tell us — including anything not listed above. Say which page and what happened, and we will come back to you. If reaching us is itself the problem, an email with nothing in it but the page address is enough.
Accessibility feedback
We aim to respond within five business days.
If you are not satisfied with our response, you can contact the Australian Human Rights Commission, which handles complaints under the Disability Discrimination Act 1992.
07Updates
This statement is reviewed whenever the site changes in a way that affects it, and the date it was last reviewed is shown at the top of this page. It describes the site as it actually is on that date, not as we intend it to become.