Accessibility
Help articles may not be fully accurate — they can lag behind the app due to frequent updates and automated translation. If in doubt, please contact support.
On this page
- 1. The settings
- 2. Built into the platform
- 3. Known limitations
- 4. Report a problem
- 5. Good to know
- 6. Troubleshooting
- 7. Related
EventMann has four settings you can adjust for yourself, and a set of accessibility features that are built into the pages. This article says what is there today and how to report something that does not work for you. The settings page is linked as Accessibility Settings from the Sign-in & access card on your profile page, and is also at /accessibility/settings, which works without signing in.

The settings
- High Contrast Mode ① — increases the contrast between text and background colours.
- Reduce Animations ② — minimises motion effects and transitions. Nothing stops working; only the movement around it is removed.
- Screen Reader Optimised — shows clearer focus outlines and keeps the skip links visible when they get keyboard focus.
- Font Size ③ — a slider from Small to Extra Large (the default is Medium) that changes the text size across the platform.
- Open Accessibility Settings from your profile page, or go to
/accessibility/settings. - Switch on what you need and move the slider.
- Press Save Settings ④. The page confirms and the setting applies on every page.
When you are signed in, your choices are saved to your account and follow you to other devices. When you are signed out, they are kept for your current browser session only. They are separate from the light and dark theme, so you can combine both.
Built into the platform
- Keyboard use — interactive elements can be reached and used without a mouse, and focus is visible.
- Structure — semantic page structure and landmarks so screen readers can move through a page.
- Forms — inputs have labels, and errors are described in text next to the field, not only in colour.
- Accessible seating — organizers can mark seats and whole sections as wheelchair-accessible. Those seats carry a wheelchair symbol on the seat map and in the seat list, and you can filter to show only accessible seats. The organizer enters this information, so ask them if it matters for your booking.
- Keyboard seat choice — every seat map has a seat list of real buttons that announce section, row, price, accessibility and availability. The picture of the map itself is pointer-only; the list is the full equivalent.
Known limitations
- Images and descriptions added by organizers may lack alternative text or structure; that depends on the organizer.
- PDF tickets contain text but are not optimised for every screen reader. The ticket page in the browser shows the same information.
- Content from other providers, such as maps and payment forms, is outside our direct control.
Our aim is to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA. The page Accessibility Statement, linked from the settings page, describes our approach and these limits.
Report a problem
If you meet a barrier, such as a control you cannot reach by keyboard, text that does not resize or something a screen reader mishandles, open a support ticket or use the contact details on the Accessibility Statement. Name the page and describe what happened. Accessibility reports are treated as faults, not as feature requests.
Good to know
- The settings page works signed out as well, so you can adjust the site before you create an account.
- Your browser’s own zoom works as usual; the settings here are in addition to it.
Troubleshooting
- I cannot find the accessibility menu — it is not in the top menu; open it from the Sign-in & access card on your profile page, or go to
/accessibility/settingsdirectly. - My font size did not stick — press Save Settings. When signed out, the choice lasts only for the browser session.
- The seat map cannot be used with my keyboard — use the seat list beside it.