Accessibility
trailbuzz317 should work for everyone who uses the trails, including people who use a screen reader, zoom or larger text, a keyboard or switch control.
Our target
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, on this website and in the app. We don’t meet it everywhere yet. This page says what we tested, what passed and what doesn’t work well yet.
What we tested
On November 11, 2026 we checked this website and the app against WCAG 2.2 AA:
- Website: the home page, trail, town, county and event pages, search, Ride videos and this page.
- App: Explore (the riding screen), the Map tab with its pins, place cards, layers and search, Route and its results, Nearby, Settings and Your page.
- How: automated checks (axe-core), then by hand. We used a keyboard alone, and checked what a screen reader is told about each control. We also checked colour contrast in day and night mode, focus in pop-ups and dialogs, and text made larger: up to the largest size the iPhone app uses, and to double size on the web.
We haven’t yet tested with VoiceOver on a real iPhone, or with Switch Control or Voice Control.
What works
- The website’s pages passed the automated checks with no failures. They work with a keyboard alone. They have a “Skip to content” link, a visible focus outline, one main heading, headings in order and labelled page regions.
- Contrast. Text and controls we checked meet AA contrast, in light and dark mode. The app also has a night mode for riding after dark.
- Labels. The app’s buttons, including those that show only an icon, have names a screen reader can say. Map pins say what they are (“Garfield Park, park”), and groups of pins say how many places they hold.
- Keyboard. Map pins and groups of pins open with Enter or Space. Pop-up cards and dialogs keep focus inside them, close with Escape where they can be closed, and return focus to where you were.
- Spoken updates. While you follow a route, each new turn and your arrival are announced to a screen reader. The app speaks them itself if you turn on spoken directions. Search tells you how many results it found.
- Targets. Buttons and links meet the WCAG 2.2 minimum target size: 24 pixels, or enough space around a smaller link. Most are 44 pixels or more, for gloves and a phone on the handlebars.
- Less motion. When your device is set to reduce motion, moving tickers stop and most animations are turned off. Tickers also have a pause button.
- Text that grows. On the web, pages follow your browser’s zoom and text size. In the iPhone app, text follows your iPhone’s Text Size setting.
- Plain pages. Every trail, town, county and event has a page on this site that works without the app or the map.
Known gaps
- The map. Moving around the map is hard with a screen reader or keyboard, and trail lines can’t be picked from the keyboard. To find a trail or place, use search, or use the app’s Nearby tab, which lists places and events. The trail, town and event pages have the same information as text.
- Hazard pins. A hazard pin opens with Enter, but focus doesn’t move into the details it shows.
- Ride videos have no captions or audio description. They have music but no speech. The speed, distance and nearby places shown over the video aren’t read out as it plays.
- Colour alone. On the map, some layers, such as closures and road work, are told apart mainly by colour. The highlight on a selected trail can be hard to see.
- The largest text sizes. In the iPhone app, text grows to about one and a third times its usual size, so the riding screen still fits on one screen. It doesn’t reach the largest sizes iOS offers. The tab bar’s labels stay the same size.
- Some smaller targets. A few chips and buttons are 40 to 42 pixels tall, under the 44 we aim for. A map pin can sit partly under the map’s own buttons or search box until you move the map.
- Testing. We haven’t yet checked the app with VoiceOver on a real iPhone, or the admin console at all.
Report a barrier
If something on this site or in the app is hard or impossible to use, write to admin@trailbuzz317.com. Tell us the page or screen, what you were trying to do, and your device and any assistive technology you use. We read every message and will tell you what we can fix.