Accessibility
Accessibility statement
How we design, test and improve access to Roadworthy Guide.
01
Our commitment
Roadworthy Guide aims to make its publication usable by people with diverse visual, motor, hearing and cognitive access needs. Accessibility is part of editorial quality, not an optional layer.
We work toward WCAG 2.1 Level AA principles and improve the site as practical issues are identified. This statement describes the current static website.
02
Design and content practices
Pages use semantic landmarks, a logical heading order, visible keyboard focus, sufficient contrast and a skip link. Controls have comfortable target sizes and text can reflow at narrow widths.
Meaningful photographs have descriptive alternative text. Decoration is not given distracting descriptions, and information is not communicated by colour alone.
03
Compatibility
The site is designed for current standards-based browsers, keyboard navigation, screen readers and browser zoom. Core navigation remains available without JavaScript through ordinary links and native disclosure controls.
Motion is limited and is removed when the user requests reduced motion. Layouts are responsive from small mobile screens to wide desktop displays.
04
Known limitations
Generated editorial photographs may not communicate every visual detail through concise alternative text. Legal and technical language can also remain demanding despite editing for clarity.
Third-party software used to read email, telephone links or external pages is outside our control. We welcome specific reports that help us prioritise improvements.
05
Requesting assistance
If a page, image description or navigation path prevents access, email contact@roadworthyguide.online or phone +61 8 8956 7873. Tell us the page, device and barrier if you can.
We can discuss providing the relevant information in a simpler email format. Do not include disability or health details that are unnecessary to explain the access barrier.
06
Feedback and review
Accessibility feedback is reviewed alongside content and technical maintenance. We test keyboard operation, reflow and common responsive widths when material changes are made.
This statement will be revised when practices or known limitations materially change. Our goal is a practical response, even where immediate remediation is not possible.