Accessibility

Accessibility statement

Vandrer wants everyone to be able to read about the project, explore the Route Lab, and take part in Field Notes and route voting, regardless of how they browse the web.

Our commitment

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, in both the dark and the light reading contexts of this site. This is an aim we test against on every change, not a certification — see “Known limitations” for what we have not finished.

What is built in

  • Keyboard access to every action — nothing requires a mouse, and nothing requires hovering.
  • A visible focus outline on every interactive element.
  • A skip link to jump straight past navigation to the main content.
  • Labels on every form field, and error messages a screen reader announces.
  • Colour is never the only way status is shown — route momentum, for example, is also spelled out in words.
  • Reduced-motion support: turning on your system's reduced-motion setting turns off the animated map lines and fade-in reveals.
  • Touch targets of at least 44 pixels for buttons, menu items and form controls, and text that reflows without horizontal scrolling at 200% and 400% zoom.
  • Core content, navigation and the status line are readable with JavaScript switched off; forms that need it say so and offer an email alternative.

How we test

Every page is checked with automated accessibility scanning (axe, WCAG 2.x A and AA) at phone and desktop sizes, in both languages, plus keyboard-only passes, reduced-motion checks and reflow checks at 320 to 1440 pixels, before publication. Manual screen-reader testing is being introduced as a regular practice and is not yet run on every change.

Known limitations

The living route map is a visual, spatial feature; a full list-view alternative sits alongside it, but we know a map is never as effortless as a list for every reader, and we keep improving it. If you find anything else, please tell us.

Tell us about a problem

If you hit an accessibility barrier anywhere on this site, contact us at info@flyvandrer.com and describe the page and the problem. We read every message and treat accessibility reports as a priority, though as a small team in development we cannot yet promise a fixed response time.

Vandrer is a project in development; a governing legal entity has not yet been registered, so this statement is published by the project team rather than under a registered company name.