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 labeled form controls;
  • errors linked to the affected step and focused when appropriate;
  • status that does not rely on color 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.

United States context

Official U.S. guidance explains that web accessibility can be relevant under the Americans with Disabilities Act, while the exact obligations depend on the organization and facts. The project records this as context rather than claiming categorical legal compliance before specialist review.

Known limits

The complete U.S. 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 August 2, 2026 for the non-public us-en technical candidate.