Everyone gets through the door.

01 · Commitment

Our commitment

Blend is committed to making its events platform usable by everyone, including people with disabilities. We want anyone to be able to discover an event, buy a ticket and reach that ticket: regardless of how they navigate the web.

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. Those guidelines explain how to make web content more accessible to people with a wide range of disabilities, including visual, auditory, motor and cognitive needs.

02 · Conformance

Where we stand today

Blend’s conversion-critical surfaces: event pages, the booking flow, event discovery and your tickets: are partially conformant with WCAG 2.1 Level AA. Partially conformant means most of the platform meets the standard and some content does not yet fully conform. We treat accessibility as ongoing work and prioritise fixes by real user impact.

03 · Shipped

What we have done

• A visible keyboard focus indicator across interactive controls.
• Semantic landmarks and a single main heading per page.
• Accessible names on icon-only buttons: search, share, quantity steppers, wallet and download controls.
• Text alternatives for meaningful images and QR codes.
• Labels associated with checkout form fields, with errors announced to assistive technology.
• Respect for the operating-system “reduce motion” preference.
• Support for browser zoom up to 500% without loss of content.

04 · Assistive technology

What we test against

We test against, and aim to support, recent versions of:

• VoiceOver on macOS (Safari) and iOS
• NVDA on Windows (Chrome and Firefox)
• Keyboard-only navigation
• Browser zoom and OS text-scaling
• “Reduce motion” and high-contrast / forced-colors modes

05 · Known gaps

What is not there yet

These are the areas we know about and are working on:

• Some secondary text and captions may not yet meet the 4.5:1 contrast minimum.
• A small number of interactive components still need refined keyboard and screen-reader patterns.
• Third-party embeds: seat maps and payment widgets among them: may have accessibility behaviour we do not control directly.

06 · Feedback

Tell us what we missed

If you hit an accessibility barrier on Blend, tell us: what you report is what gets prioritised. Describe the page, what you were trying to do, and the assistive technology you were using if you can.