Accessibility Statement

1. 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 access 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. These guidelines explain how to make web content more accessible to people with a wide range of disabilities, including visual, auditory, motor, and cognitive needs.

2. Conformance status

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 that while most of the platform meets the standard, some content does not yet fully conform. We treat accessibility as ongoing work and prioritise fixes by real user impact.

3. What we've done

• A "Skip to main content" link so keyboard users can bypass navigation.
• 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.

4. Supported assistive technology

We test 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

5. Known limitations

We are actively working on the following areas:

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

6. Feedback and contact

If you encounter an accessibility barrier on Blend, please tell us — your feedback directly shapes our priorities. Describe the page, what you were trying to do, and the assistive technology you were using if you can.

Email us at Info@blendapp.ae. We aim to respond within five business days.