Allgenda

Accessibility

Accessibility at Allgenda.

If you can't use part of Allgenda, that's a bug, and I want to hear about it. Here's what we build toward and how to flag a gap.

Last reviewed September 28, 2026.

Our target

Allgenda targets WCAG 2.2 Level AA. Color is never the only thing carrying meaning. The app is built to be keyboard-operable end to end, and we test it with prefers-reduced-motion turned on so motion never gets in your way. If the map is hard to use, the same places are in a list in the directory.

Color isn't the only signal

Verification tiers always pair the color with a shape and a label, so the meaning holds even when the colors don't read as distinct. Here's the actual component you'll see on listings and map pins.

Verified. Confirmed by the owner, a moderator, a phone call or an attributed source.Community-reported. Reported by the community, or checked with medium confidence. Not confirmed yet.Low confidence. The latest check came back with low confidence, so treat the details with caution.Not checked yet. No check is on record for this listing yet.

We also check the UI in deuteranopia, protanopia, and tritanopia simulations as part of design review, so a warning triangle and a green check never come down to hue alone.

Physical accessibility in listings

Every listing has a Wheelchair accessline. It says “ADA accessible” only when a source recorded that, and “Not on record” otherwise, so a gap in our data never reads as a yes. We plan to record more concrete facts, like door width and grab-bar locations, each with a source and a date.

Report a gap

If any part of Allgenda blocks you, tell me through the contact form(pick the "Accessibility" topic) and a real person reads it. For anything urgent, email trust@allgenda.comand we'll prioritize it.