Accessibility
A guide is only useful if you can read it. Cleo aims to meet WCAG 2.2 level AA on every page, for every one of its places — and to say plainly where it doesn't yet.
What we commit to
- Everything is readable without the map.Every place is in the list as text — name, write-up, address, who recommends it, open or closed. The map is an extra; if it fails to load, nothing is lost.
- Everything is readable without a network or script.Pages are plain HTML with system-font fallbacks; search, saving and filters add to it but are never needed to read a guide.
- Contrast at AA, in both editions.Text and controls meet the AA contrast minimums in the day edition and the night edition. Colour is never the only signal: closed places say “Closed” in words, tiers have a name next to the glyph.
- Targets you can hit.Every button and link outside running prose is at least 44 by 44 pixels.
- Keyboard all the way.A skip link goes straight to the content; focus is always visible; dialogs (place details, filters, search) keep focus inside, close with Esc or Back, and return focus to where you were. In search results, the arrow keys move between results.
- Landmarks and names.Each page has a header, navigation, main content and footer; every control has an accessible name.
- Motion only if you want it.With “reduce motion” set on your device, nothing animates.
- Storage is optional.If your browser blocks storage, your list still works for the session and the page tells you so.
How it is measured
Each build is checked by an automated harness at a phone size (390 × 844) and a desktop size (1440 × 900) across every page: contrast in both editions, tap-target size, overflow, visible focus, landmarks, skip link, accessible names, and that every place can be reached by scrolling, by deep link, by search and with scripts off. The latest results are kept in the project's QA log alongside the evidence.
Known gaps
These are open today. We list them instead of claiming conformance we haven't measured.
- Map pins are not a keyboard list.Pins on the map can be reached with a pointer; with a keyboard or screen reader, use the list, which carries every place the map shows, in the same order and numbering.
- The biggest guides are long pages.Tokyo and New York hold close to 500 places each on one page, which can be slow to move through with a screen reader. Use the area links, the filters or search to jump. Lighter progressive loading is being built.
- Native-script names are not yet language-tagged.Names such as 浅草寺 are shown beside the English name but are not yet marked as Japanese, so some screen readers may mispronounce them.
- English only.The interface is in English. Place names stay in their own script.
- Not yet audited by a person.The checks above are automated. A manual audit with assistive-technology users has not been done yet.
Tell us about a barrier
If something on Cleo is hard to use, please tell us on the feedback form with the page and what happened. You don't need to know the technical cause — “I couldn't reach the Close button with the keyboard on the Tokyo page” is exactly the kind of report we need.