Accessibility

8nOut is the map of the European One Pocket community — and plenty of you reach us from an iPad or a computer, not an iPhone. The native 8nOut app is iPhone-only, so on any other device, the website at 8nout.com — including the full web app — is how you use 8nOut. This page sets out what we’ve built to make that experience accessible, and where we know we still have work to do.

On iPad and desktop

The web app isn’t a cut-down version of 8nOut — it’s the map, connections, chat, groups, City Ladder, and calls, laid out to fit whatever screen you’re on. It runs in Safari on iPad the same way it runs in any desktop browser. Nothing about using 8nOut requires an iPhone.

What’s supported today

• Follows your system’s light or dark setting, automatically, and remembers a manual choice if you’ve made one in Profile → Appearance.
• Respects reduced motion. If you’ve turned on Reduce Motion (iPad: Settings → Accessibility → Motion; desktop browsers and operating systems have an equivalent), 8nOut turns off its decorative animations — spinners, pulsing dots, fade transitions — across chat, connections, and your profile. Anything that’s actually information, rather than decoration, stays exactly as long as it needs to.
• Works with your own text size and zoom. 8nOut’s text is set in sizes that scale with your browser’s font size and zoom settings, not fixed pixel sizes, so increasing your default text size — or pinching to zoom on iPad — makes 8nOut’s text bigger too. We never disable pinch-to-zoom on any 8nOut page.
• Screen reader labelling on the map and beyond. Player pins, availability markers, and venue markers on the map carry descriptive labels for VoiceOver and other screen readers, and purely decorative icons are hidden from them. The same pattern — labelled controls, hidden decoration — carries into chat, connections, and calls. A QR code gets a real description; an avatar sitting next to a name that’s already on screen doesn’t repeat it.
• Keyboard support. Every custom control built to act like a button — a list row, a player card, a chat thread — also responds to a keyboard Enter press, and shows a visible outline when it’s focused.
• A responsive layout, across phone, tablet, and desktop widths, including iPad’s portrait and landscape sizes.

Still working on

• We haven’t run a professional accessibility audit or tested 8nOut against a specific standard like WCAG, so we won’t claim a compliance level we haven’t verified. What’s above is what we know we’ve built and can point to directly in the code.
• Longer pages, like the map, don’t yet have a “skip to content” shortcut past the header for keyboard and screen-reader users. We know it’s missing.
• The homepage’s main heading isn’t marked up as an actual heading yet — screen reader users scanning by heading level skip past it. We know it’s missing.
• Labelling is most complete on the map, chat, and connections; some newer or smaller screens haven’t had the same close attention yet.
• A handful of small text elements — mostly compact tags and labels — are set to a fixed size rather than one that scales with your text settings. Most of the app scales; that handful doesn’t yet.

Report an accessibility problem

If something on 8nOut’s website is hard to use with a screen reader, keyboard, or larger text size, tell us: email us at gethelp@8nout.com with the page, your device and browser, and what happened. A real person reads and replies to everything sent there.

If you’re signed in, there’s also a Send feedback link on your Profile page. It’s a fine place to leave a quick note, but it’s a one-way queue — nobody replies to it there. For something you want an actual answer to, email is the way.

Last updated 12 September 2026