Accessibility

The site should support different ways of reading and navigating

Accessibility is treated as an ongoing product requirement, not a one-time automated score or an unsupported statement of legal conformity.

Measures in the current interface

The candidate includes the following design and implementation measures:

  • semantic headings, landmarks and a skip-to-content link;
  • visible keyboard focus and labelled form controls;
  • errors linked to the affected step and focused when appropriate;
  • status that does not rely on colour alone;
  • responsive layouts intended 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

Automated accessibility checks, keyboard navigation, multiple viewports and core planner flows are included in QA. Automated tools cannot assess every reading, cognitive, language or assistive-technology barrier.

New Zealand context

The New Zealand Government Web Accessibility Standard provides public-sector context and points to WCAG 2.2 AA. This private Spain-based technical candidate follows accessible engineering practices without claiming that the standard applies or that legal conformity is established. The project records this as context rather than claiming categorical legal compliance before specialist review.

Known limits

The complete New Zealand English review, real assistive-technology feedback and final domain/provider configuration remain pending. Third-party source pages are outside project control.

Report a barrier

Use the contact channel and include the page, task, browser or assistive technology if relevant, what happened and the result expected. Do not send sensitive or unnecessary personal information.

Statement prepared 3 August 2026 for the non-public nz-en technical candidate.