Measures in the current interface
- semantic headings, landmarks and a skip-to-content link;
- visible keyboard focus and labelled form controls;
- errors linked to the affected step and moved into focus when appropriate;
- content and status that do not rely on colour alone;
- responsive layouts designed to avoid horizontal overflow at high zoom;
- editorial alternative text and explicit image dimensions;
- no autoplay, complex gesture requirement or time limit.
How the candidate is checked
Functional browser journeys cover navigation, the planner, crop and guide pages, the 404 response and critical responsive widths. Automated accessibility analysis runs on representative pages. Those checks find only some barriers; language clarity, screen reader behaviour and real task completion still need human review for this locale.
Australian context
The Australian Human Rights Commission publishesguidelines on equal access to digital goods and services. The project uses that guidance alongside WCAG as context. It does not claim external certification or a final legal conclusion while legal review is pending.
Known limits
External websites, email applications and browser tools are outside the project’s control. Every new language and market must review terminology, alternative text, messages, reading order and task behaviour; it cannot inherit another locale’s linguistic or human accessibility assessment automatically.
Report a barrier
Send the URL, task, browser or assistive technology and a short description of the barrier to newshell13@gmail.com. You do not need to disclose a diagnosis, identity document or other sensitive data.
The responsible person will use the report to reproduce and correct the problem. If an immediate fix is not possible, a reasonable alternative format can be requested.
Last updated
Statement prepared 2 August 2026 for the en-AU technical candidate.