Accessibility

We design and test tiveo against the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. We don’t claim full conformance yet: the known gaps are listed below.

• Everything works from the keyboard, with a visible focus ring and a logical order. Escape closes menus, lists and dialogs, and focus goes back to what opened them.
• Dialogs, such as Your Privacy Choices, photos and policies, keep focus inside until they close.
• Text, field edges and switches meet WCAG contrast targets.
• Buttons and links are at least 44 px tall on phones, and fields don’t make phones zoom in.
• Form fields have labels, and each error says what’s wrong next to the field it’s about.
• Pages work at 320 px wide and when zoomed, without scrolling sideways.

• Some photos from hosts don’t have descriptions yet, so a screen reader can’t say what they show.
• The card fields come from Stripe or Square, in their own frames, and the driver checks run on the host’s provider’s pages (Stripe Identity or Vouched). We can’t change how those work.
• Maps and date calendars can be hard to use with a screen reader. Places can be typed or chosen from a list, and the calendar works from the keyboard (arrow keys, Home and End, Page Up and Page Down), but a date can’t be typed yet.
• Hosts write their own descriptions, rental terms and policies.

If something on tiveo is hard or impossible to use, email us with the page and what happened, and we’ll work on it. If you can’t finish a booking because of it, we’ll help you book with the host another way.