Accessibility statement

We want everyone to be able to discover events, buy tickets and take part in the soundr community, regardless of ability or the technology they use. Accessibility is treated as a requirement of every screen we build, not an afterthought.

This statement applies to the soundr web application at soundr.social. Our iOS and Android companion apps are covered by their own platform accessibility support and are improved on the same ongoing basis.

soundr.social aims to conform to the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA, which also underpins the European standard EN 301 549 and the European Accessibility Act. “Aims to conform” means we target the AA bar across the product and treat any shortfall as a defect to fix.

The web app is substantially conformant with WCAG 2.2 AA: the great majority of content meets the standard, with the limited, documented exceptions in the section below.

Accessibility is built into how we design, build and test soundr:

• Colour & contrast — our design tokens are audited against the WCAG contrast ratios (4.5:1 for text, 3:1 for large text and UI components), and the audit runs as an automated test so a regression fails the build.
• Keyboard — every interactive control is operable by keyboard with a visible focus indicator; dialogs and menus trap and restore focus; a “skip to content” link bypasses repeated navigation; and gesture-only surfaces (such as the swipe feed) have a full keyboard alternative.
• Screen readers — we use semantic HTML and landmarks, label every control, associate form fields with their labels and errors, and announce asynchronous updates (loading, results, errors and notifications) through live regions.
• Motion — animations and smooth scrolling are suppressed when you ask your device to reduce motion.
• Automated & manual testing — we run per-component accessibility checks (axe), an automated page-level axe gate across core pages in our continuous integration pipeline, and a manual keyboard and screen-reader review before shipping new screens.

soundr.social is designed to work with current versions of major browsers (Chrome, Firefox, Safari and Edge) together with their built-in or commonly used assistive technologies, including VoiceOver (macOS/iOS), NVDA (Windows) and TalkBack (Android). The site is responsive and remains usable when text is enlarged and at high zoom levels.

Despite our efforts, some content may not yet be fully accessible. We are aware of the following and are working to address them:

• User-generated content — media uploaded by organizers and fans (photos, videos and external links) may lack text alternatives or captions that we do not control. We encourage meaningful descriptions and moderate reported content.
• Third-party components — some embedded or third-party flows (for example, the payment provider’s hosted checkout) are outside our direct control, though we choose partners with accessibility in mind.
• Maps & rich media — interactive maps and some data visualisations provide text equivalents but may not expose every detail to assistive technology.

If you hit a barrier that isn’t listed here, please tell us — it helps us prioritise.

We welcome your feedback on the accessibility of soundr. If you encounter a barrier, or need information in a different format, contact us and we’ll help:

If you contact us about an accessibility problem and are not satisfied with our response, you may be entitled to escalate to the relevant accessibility regulator or consumer-protection body in your country. This does not affect any other rights you have.

This statement is based on a combination of automated testing (token contrast checks, per-component and page-level axe scans) and manual keyboard and screen-reader evaluation of the core user journeys against WCAG 2.2 AA. It is reviewed as the product evolves. It should be read together with our Terms of Service and Privacy Policy.