Skip to content
← back home
legal · 04

Accessibility.

Queer-safe should also mean access-safe. Here's what we're doing, and where we still fall short.

last updated · · 16 may 2026reading time ≈ 8 min
§01

Our commitment

We treat accessibility as a baseline, not a feature. Every interactive element should be reachable by keyboard, perceivable by screen readers, and usable at standard zoom and contrast. If it isn't, that's a bug.

§02

Standards we target

  • WCAG 2.2 Level AA across the directory, submission, and profile flows.
  • European Accessibility Act readiness ahead of enforcement dates.
§03

What we're doing right

  • Discreet theme — muted palette for sensitive contexts (buses, waiting rooms, shared screens).
  • Light / dark / system color modes — pick what your eyes need.
  • Respects prefers-reduced-motion — if you have animations off at the OS level, we disable the flashy stuff automatically.
  • Keyboard navigation throughout, with visible focus rings.
  • Semantic HTML and ARIA labels on icon-only controls so screen readers can make sense of the layout.
§04

Known limitations

We're a small team and haven't paid an agency for a formal WCAG audit. There are blind spots:

  • The interactive map is mouse-first. A fully keyboard-equivalent list view shows the same spaces — use that if the map gives you trouble.
  • User-submitted content (space photos, descriptions, notes) may lack alt text or sufficient color contrast. We can't guarantee what other people upload.
  • Map tiles are served by OpenStreetMap — their rendering isn't something we control.
§05

Report a barrier

If something blocks you, tell us — don't assume we did it on purpose, we probably just missed it. Write to hello@questry.app with the page, what broke, and what assistive tech you're using (screen reader, browser, etc). We treat accessibility regressions as P1 bugs.