Accessibility
Accessibility Statement
The standard we build to, what we have actually tested, where we fall short, and how to tell us if something blocks you.
Updated
- Standard
- WCAG 2.1 Level AA
- Tested
- Automatically, on every change, in our build
- Keyboard
- Fully operable, with visible focus
- Reduced motion
- All animation disabled on request
- Not yet done
- A human audit or screen-reader testing
- Found a barrier?
- Email us — we reply within 5 business days
Our commitment
WCAG 2.1 AA, the standard referenced for the Disability Discrimination Act
We aim to meet WCAG 2.1 Level AA — the standard the Australian Human Rights Commission references for compliance with the Disability Discrimination Act 1992 (Cth), and the level required of Australian government websites.
We build software for a living. A website that excludes people is a defect, and we treat it as one.
What we have done
Keyboard access, contrast, reduced motion, and proper structure
- Keyboard. Everything interactive is reachable and operable, a skip link is the first stop, and focus indicators are never suppressed.
- Contrast and colour. All text meets 4.5:1, and nothing is communicated by colour alone.
- Motion. Every animation is disabled when your system asks for reduced motion, and no content is hidden behind one.
- Structure. Proper headings and landmarks, labelled form fields, alt text on meaningful images, and content that reflows to 320px.
How we test
axe-core runs against every page on every change; a violation fails the build
Automated accessibility checks run against every page on every change, as part of our build pipeline, using axe-core against the WCAG 2.0 and 2.1 A/AA rules. A change that introduces a violation fails the build.
Keyboard navigation and reduced-motion behaviour are covered by the same suite.
Known limitations
Automated tools catch about a third of real problems — we have not had a human audit
We would rather tell you where we fall short than claim more than we verified.
- Automated testing is not enough. Tools catch roughly a third of real accessibility problems. This site has not had a human audit, and has not been tested systematically with screen readers or with people who use them.
- Two ORYX interface screenshots convey detailed information. They carry descriptive alt text, but a complex screenshot is never fully equivalent to what it shows. Ask us and we will describe it.
Tell us if something blocks you
Email the page and what went wrong; we reply within 5 business days
If any part of this site is difficult or impossible for you to use, email hello@vectriontechnologies.com.au with the page and what went wrong. We acknowledge within 5 business days and tell you what we intend to do.
If something is stopping you contacting us at all, that is the most serious kind of failure and we treat it that way. Need information in another format? Ask.
If we do not resolve your concern, you can complain to the Australian Human Rights Commission at humanrights.gov.au.