Accessibility statement

Our target

AdventureOS aims to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA across the web app and this marketing site.

That is a target we work toward, not a claim that we have reached it everywhere. This statement is self-assessed: no independent third party has audited AdventureOS, and we do not publish a VPAT or an Accessibility Conformance Report. The known limitations below are the honest account of where we fall short today.

How we test

Automated: every change runs an axe-core sweep in continuous integration over the public marketing and sign-in routes plus a signed-in application route, checking the WCAG 2.0, 2.1 and 2.2 A and AA rule sets. A serious or critical finding fails the build and blocks the change from shipping.

By hand: we check keyboard operability and visible focus on the surfaces we touch as we build them, and the interface is built on one shared design system rather than per-page styling, so a fix to a control fixes it everywhere that control is used.

What we do not do yet: we do not run a scheduled screen-reader test pass, and automated coverage does not reach every screen in every module. Deep application surfaces are checked less often and less thoroughly than the pages listed above.

Known limitations

These are the gaps we know about. We are working on them, and we would rather you knew than found out.

Maps. Location and route maps are interactive Leaflet maps. Panning and zooming them is a pointer interaction with no equivalent text alternative, so a member relying on a keyboard or a screen reader cannot explore the map itself. The place’s name, description, coordinates and any official notices are rendered as text on the same page and do not require the map.

Member-uploaded images. There is nowhere for a member to write alternative text when they upload a photo — avatars, gear photos, marketplace listing images and adventure photos have no author-supplied description, so a screen reader announces surrounding context rather than the image.

Motion. We do not currently honor the operating system’s reduced-motion preference. Interface transitions and animations play at full strength regardless of that setting.

Generated PDFs. The signed logbook export is generated as a laid-out document and is not tagged for assistive technology, so its reading order and table structure are not exposed. The same records are readable as ordinary pages in the app.

Third-party components. The bot challenge on the sign-in and sign-up pages is Cloudflare Turnstile, and map tiles come from OpenStreetMap. Their accessibility is theirs, not ours; we can report problems upstream but we cannot fix them here.

Coverage of newer surfaces. Module screens added recently may not have had the same keyboard and screen-reader attention as the older ones. If you hit something, telling us is the fastest route to a fix.

Tell us about a barrier

If any part of AdventureOS is difficult or impossible for you to use, email accessibility@adventureos.net. Tell us the page or URL, what you were trying to do, and what assistive technology, browser and operating system you were using if you know — but a one-line “I cannot get past the sign-up form with a keyboard” is entirely enough to act on.

If you are already signed in, the in-app feedback control sends the same report and attaches the page and app version automatically.

We aim to acknowledge every accessibility report within five business days, and to tell you what we intend to do about it and roughly when. Where a fix will take time, we will describe a way to get the task done in the meantime if one exists.

If our response does not resolve it, escalate to hello@adventureos.net.

Keeping this current

The date above is when this statement was last reviewed against the app. We update it when we close one of the limitations above, when we find a new one, or when we change how we test — and reviewing it is part of shipping accessibility work, not a separate task that waits.