Accessibility Statement

Our commitment

This website is designed and built to meet, as closely as practical, the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. We test new pages against accessibility checks as part of our build process and continue to refine the site over time.

What we've done

Keyboard navigation — every interactive element (links, buttons, form fields, modal, accordions, tabs) can be reached and operated using only the keyboard. A skip-to-content link is provided at the top of every page.
Visible focus states — keyboard focus is shown with a clear amber outline on every interactive element, never hidden by CSS.
Reduced motion — animations are toned down or disabled for users who have prefers-reduced-motion: reduce set in their system preferences.
Colour contrast — body text and key UI elements meet or exceed WCAG AA contrast ratios (4.5:1 for body text, 3:1 for large text and non-text elements).
Semantic HTML — pages use real <header>, <nav>, <main>, <section> and <footer> landmarks. The lead form uses a native <dialog>. FAQ accordions use native <details> and <summary>. Tabs use ARIA tablist / tab / tabpanel with keyboard arrow navigation.
Labelled forms — every input has an associated <label>. Required fields are clearly marked. Validation errors are surfaced via aria-invalid and focus management.
Touch targets — interactive elements meet a minimum 44×44 pixel target on touch devices.
Responsive design — layouts adapt to screens from 320 pixels wide up to wide desktop displays. Content reflows; nothing requires horizontal scrolling at any breakpoint.
No flashing content — there are no rapidly flashing or strobing elements that could trigger photosensitive seizures.
Decorative icons hidden — purely decorative SVG icons are marked aria-hidden="true" so they don't add noise for screen readers.

Known limitations

Some animated elements (e.g. the hero call simulation, scroll-progress bar) are decorative. They convey no information not also present in the surrounding text.
External tools (e.g. third-party integrations, embedded forms once connected) may have their own accessibility characteristics outside our direct control. Where we identify barriers, we'll work with providers or offer alternative routes.
The custom score-ring visualisation on the audit preview is also conveyed as text ("42/100") so the information isn't colour or shape-dependent.

How to use the site

Press Tab to move forward through interactive elements; Shift + Tab to move backward.
Press Enter or Space to activate buttons and links.
On the FAQ accordion, Enter expands and collapses items.
On the industry tabs (where present), ← and → move between tabs.
On open modals, Esc closes the modal.
The skip link at the top of every page jumps focus to the main content.

Reporting an accessibility issue

If something on this site isn't accessible to you — text is hard to read, a control doesn't work with your assistive technology, or anything else gets in the way — please tell us. We take these reports seriously and aim to respond within 5 business days.

Email: [email protected] with subject "Accessibility issue".
Please include the page URL, what you were trying to do, what happened, and the assistive technology or browser you were using.

Standards we follow

Web Content Accessibility Guidelines (WCAG) 2.1 — Level AA target
Disability Discrimination Act 1992 (Cth) — Australian context
HTML Living Standard for semantic structure
ARIA Authoring Practices Guide for custom interactive components

Ongoing work

Accessibility is never "done". We review the site periodically as we add features and update content. If you have suggestions for improvement, we'd genuinely like to hear them.

This statement is current as of the date above and will be updated as the site evolves.