Accessibility

Using Papilo With Assistive Technology

Last updated November 3, 2026

Papilo should be usable whether you navigate with a mouse, a keyboard, a screen reader, voice control, or at a zoom level that makes the text readable for you. This page says what we aim for, what we have checked, and what we know is still wrong.

The standard we work to

We aim to meet WCAG 2.1 Level AA. We are not claiming full conformance — no one should claim that without an audit to back it, and we have not had one. We treat it as the bar to be measured against, and we re-check pages when we change them.

What we've done

  • Interactive controls are at least 44×44 pixels, so they can be hit reliably on a phone. Where a control looks smaller, its tap area is still 44 pixels.
  • Every form field has a visible label tied to the input, rather than a placeholder that disappears as soon as you type.
  • Filters, time selectors, and voting controls are real buttons that announce their state, so a screen reader says which option is selected.
  • Dialogs trap focus while open, close on Escape, and return focus to the control that opened them.
  • Pages work without horizontal scrolling at phone widths and at increased zoom.
  • Images that carry meaning have alternative text; decorative ones are hidden from screen readers rather than described.

What we know is still wrong

This list is deliberately specific. If you hit something that is not on it, we would genuinely like to know.

  • The map. Explore and shared plans use an interactive map whose zoom controls are smaller than our own 44-pixel minimum, and whose pins are not fully reachable by keyboard. Every place shown on the map is also in the list beside it, and the list is the accessible path — but the map itself is not yet up to standard.
  • Screen-reader testing is partial. We have tested the main flows structurally but have not completed a full pass with VoiceOver and NVDA across every page.
  • Colour contrast. Secondary and tertiary text is checked against the 4.5:1 ratio, but we have not audited every state of every component, particularly hover and disabled states.
  • No formal audit. Nothing here has been reviewed by an external accessibility auditor.

We don't use an accessibility overlay

We have deliberately not installed one of the widgets that promises to fix accessibility automatically. They tend to sit on top of the underlying problems rather than remove them, and they can interfere with the assistive technology you already use and have configured. We would rather fix the markup.

Telling us about a problem

Email team@papilonyc.com with the page, what you were trying to do, and the browser or assistive technology you were using. That last detail is usually what makes a report reproducible.

If something on Papilo is blocking you, say so in the subject line and we will treat it as a bug rather than a suggestion.