Accessibility Statement

Our commitment

We want this site to work for everyone, on any device, with any assistive technology. We're targeting WCAG 2.1 Level AA across pacesolutions.au, and treat accessibility as an ongoing practice rather than a one-off checkbox.

What's implemented

• Semantic HTML throughout: headings, landmarks and lists that describe what they are, not just how they look.
• Full keyboard navigation: every interactive element (navigation, menus, forms, the Nexus door) is reachable and operable without a mouse, with a visible focus state.
• Reduced-motion support everywhere: scroll reveals, meteor effects and canvas animation are disabled or simplified when a visitor has prefers-reduced-motion switched on.
• Measured colour contrast: every text colour on the site is verified against the surface behind it at the 4.5:1 AA threshold, not judged by eye.
• A skip-to-content link at the top of every page.
• Touch targets sized for mobile and layouts that reflow to a single column on small screens without horizontal scrolling.

How we test

Accessibility is checked automatically on every build rather than reviewed occasionally. The audit runs axe-core against the WCAG 2.0, 2.1 and 2.2 A and AA rulesets across every page at both a desktop and a mobile viewport, and adds four checks that automated tooling doesn't cover on its own: that the skip link actually moves focus, that touch targets meet our size rule, that nothing keeps animating when prefers-reduced-motion is set, and that every focusable element shows a visible focus indicator.

The site currently passes that audit with no A or AA violations. The suite is committed to the repository and runs against the built site, so a regression fails the build rather than quietly shipping.

Known limitations

Automated testing is not the whole picture. It reliably catches contrast, markup, focus and target-size problems, but it cannot tell you whether a page actually makes sense read aloud. We have not yet completed a manual audit with real screen-reader software, and that is the next thing on this list.

The hero and section canvas animations (the constellation, particle fields) are decorative, they carry no information, are marked aria-hidden, and are gated behind prefers-reduced-motion. If that setting is on, they simply don't run. Other small flourishes (blade-cut corners, meteor seams) are decorative-only for the same reason.

We're a small team and continue to test as the site grows. If you hit a barrier we haven't caught, we want to know, see below.