Accessibility

We aim to meet WCAG 2.1 AA across the marketplace — sufficient colour contrast, full keyboard navigation, semantic structure for screen readers, visible focus, and respect for reduced-motion preferences. Accessibility isn't a one-off audit for us; it's part of how we build and review every new surface.

Interactive components keep their accessible labels and roles, and we don't strip them for visual reasons. Motion is dialled back for anyone who prefers it. Text resizes without breaking layout, and the marketplace works without a mouse. We test the core flows — browse, checkout, and ticket retrieval — with a keyboard and a screen reader, not just by eye.

The accessibility of a venue and an event — step-free access, accessible seating, companion tickets, sign-language interpretation — is set by the organiser. Where an organiser provides those details, we surface them on the event page. If the information you need isn't there, contact the organiser through the event page before you buy, and tell us if you hit a wall.

We don't claim to be perfect. Some older flows and third-party embeds haven't yet reached the bar we hold for the rest of the platform, and we're working through them. If you tell us where the gaps are, you help us prioritise the fixes that matter most.

If something is hard to use, we want to know — it helps us fix it for everyone. Email access@263tickets.com with what you ran into, the page or event it happened on, and the device or assistive tech you were using. We aim to acknowledge access reports within two business days.