Accessibility

Our goal

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA across the planner, the shared trip page and the rest of the site. capy is in early testing, so we treat accessibility problems as bugs and fix them as they're found.

What we do and test

• Automated checks (axe) on every main screen before each test build: the home page, planning, a stop's details, flights, review, save and share, the friend view, my trips, and these pages.
• Every control works with a keyboard, with a visible focus ring, and dialogs close with Escape.
• Text and controls meet AA color contrast. Touch targets are sized for fingers on phones.
• Pages reflow to phone widths, and animations calm down when your device asks for reduced motion.
• Screens are tested in Chromium and Safari's engine (WebKit), on desktop and phone sizes.

Known gaps

• Maps can't be fully used with a screen reader. Everything on a map is also in the day list next to it, with times and places.
• Dragging stops in the desktop calendar needs a mouse. You can make the same change by asking in the chat (for example, “move the museum to Friday morning”).
• Photos are decorative and hidden from screen readers; the place name next to each one says what it shows.
• Partner sites you book on (airlines, hotels, tours) aren't run by capy, and their accessibility may differ.

Tell us about a problem

If something in capy doesn't work for you, please tell us: email [contact email], or use Send feedback at the top of any page. Say which page and what happened, and what device or assistive technology you use if you're happy to. We aim to reply within 5 working days, and we'll help you get what you need from the plan in the meantime.