Accessibility
Accessibility statement
Last updated 19 November 2026
We want everyone on a trail crew to be able to use TrailVector: in the forest on an old phone with gloves on, with a screen reader, with large text or by keyboard. This statement covers the TrailVector app (each association's own, and the demo at demo.trailvector.app, with its help page and admin screen) and this website, trailvector.app.
What you can do
- Zoom the page up to 400% with no text running off the side or overlapping
- Make the text bigger in your browser or phone's settings
- Use the app in light or dark mode (Settings → Appearance), whichever is easier to read in the sun
- Fill in every form with a keyboard alone, with focus always shown
- Use a screen reader: every button and field has a name, and pages have headings and landmarks
- Turn the phone sideways: every screen works in landscape
- Watch the walkthrough video with captions, and jump to a chapter
Buttons and other things to tap are large, for cold fingers and gloves, and the app doesn't rely on colour alone: a priority, for example, is also written out.
How accessible it is
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. As far as we know, the app and this website meet it, apart from the content described below. We checked them ourselves; they haven't yet been audited by an independent accessibility specialist.
What we can't make fully accessible
- Maps. The forest map and the lines drawn for trails are pictures, which a screen reader can't describe. Everything they show is also in the app as text: each inspection lists its issues and where they are, and each trail has its own page.
- What people add. Photos that leads take don't have descriptions, and notes and Ask Vector's answers are written by people or by AI, not by us.
- Other companies' content. Map pictures come from OpenStreetMap and others, and trail details from Trailforks. We can't change how accessible those are.
How we checked
On 19 November 2026 we checked every screen of the app, its help page and admin screen, and every page of this website:
- with the axe accessibility checker against WCAG 2.2 A and AA, in both light and dark mode, at phone and computer sizes
- for colour contrast on every piece of text, including over the faint contour lines behind the top of each screen
- at 320 pixels wide (the same as zooming to 400%), in landscape, with WCAG's wider text spacing, and with text at twice its size
- for size of tap targets, and for using forms with a keyboard alone
We fixed what these checks found, and the app's automated tests run the same accessibility, width and keyboard checks on every screen before each release. We haven't yet tested with people who use screen readers or other assistive technology, and we'd like to: if that's you, please get in touch.
Tell us about a problem
If something in TrailVector is hard to use, or you need information in a different format, email ppa.rotcevliart@olleh or use Send feedback in the app. Tell us the page and what happened. We'll reply within 5 working days.
Associations can share this statement with their councils, landowners and funders.