Tour operators must anticipate disabled customers' needs and make reasonable adjustments to their services. That duty applies to services provided on a website, so consider both the booking journey and the experience itself. Source: EHRC services code
No UK law requires private businesses to meet a specific web accessibility standard. WCAG 2.2 AA is the standard required for UK public sector sites and the usual benchmark for other organisations. Use the standard to guide testing rather than assuming a checklist alone settles every accessibility issue. Sources: GOV.UK and W3C
Check that a customer can use the booking form without a mouse, understand labels and errors, and select dates without relying on a dragging gesture. WCAG 2.2 also addresses target size, obscured focus, repeated information and accessible authentication, with criteria and exceptions set out in the standard. Source: W3C
Provide an alternative way to book and make the contact route easy to find. Describe relevant features of the activity, meeting point and facilities, and invite customers to discuss requirements without making assumptions about what they can do.
- Use clear headings, readable text and meaningful form labels.
- Test links, date selection and payment steps with a keyboard.
- Check that a fixed booking bar does not hide the field being used.
- Give customers a way to select dates without dragging.
- Explain practical access details and provide a contact route.
- Review any booking countdown against WCAG's timing requirements, including applicable exceptions.
If a booking uses a countdown, WCAG requires users to be able to turn it off, adjust it or extend it, unless an exception applies, such as an essential limit. Source: W3C