Last updated: 5th October 2025
Next update due: 5th January 2025
We’ve made significant progress on our accessibility roadmap following a full WCAG 2.1 AA audit of our website platform at the end of 2024. The audit confirmed that our platform already meets many key accessibility criteria, making us partially compliant, with several areas fully compliant.
Our focus now is on closing the remaining gaps — we’re already over 30% through the identified improvements, meeting 30 out of 50 criteria so far. Many of these are quick wins that will be resolved in upcoming releases, while broader improvements are being addressed through our regular development cycle.
It’s important to note that achieving full WCAG compliance also depends on the content and design choices made on each individual website. Our platform provides the technical foundation, and we support clients in ensuring their sites remain accessible in practice.
To learn more about our accessibility approach and the support available for your own website, read our full article here.
The details below highlight the current status of our accessibility roadmap.
✅ Passed Criteria (30)
The following criteria have no outstanding issues and are considered compliant:
- 1.2.1 Audio Only and Video Only (Pre-Made)
- 1.2.2 Captions (Pre-recorded)
- 1.2.3 Audio description or media alternative (Pre-recorded)
- 1.2.4 Captions (Live)
- 1.2.5 Audio description (Pre-recorded)
- 1.3.3 Sensory Characteristics
- 1.3.4 Orientation
- 1.3.5 Identify Input Purpose
- 1.4.2 Audio Control
- 1.4.5 Images of text
- 1.4.13 Content on Hover or Focus
- 2.1.2 No Keyboard Trap
- 2.1.4 Character Key Shortcuts
- 2.2.1 Timing Adjustable
- 2.3.1 Three Flashes or Below Threshold
- 2.4.1 Bypass Blocks
- 2.4.2 Page Titled
- 2.4.5 Multiple Ways
- 2.4.6 Headings and Labels
- 2.5.1 Pointer Gestures
- 2.5.2 Pointer Cancellation
- 2.5.3 Label in Name
- 2.5.4 Motion Actuation
- 3.1.1 Language of Page
- 3.2.1 On Focus
- 3.2.2 Input elements
- 3.2.3 Consistent Navigation
- 3.3.3 Error suggestion
- 3.3.4 Error Prevention (Legal, Financial, Data)
- 4.1.1 Parsing
❌ Criteria with room for improvement (20)
1.1.1 Non-text Content
Videos without titles
Embedded videos (YouTube, Vimeo) lack proper titles for screen readers
Affected areas: Production pages with video embeds, showcase banners
Solution: We are working on adding title fields for embedded videos.
Decorative images not properly marked
Card overview images are not marked as decorative
Affected areas: Agenda/event listing pages
Solution: We are looking at a new solution to cards overall and have standardised most already to fix this, this will allow for dedicated alt text fields so users can decide based on context.
1.3.1 Info and Relationships
Seat selection inaccessible
The seatmap lacks programmatic structure for screen readers
Affected areas: Seatmap
Solution: We are looking at a completely new Seatmap experience as part of our new order flow.
Headings not properly structured
FAQ headings and some content headings such as pricing lists lack proper semantic markup
Affected areas: FAQ sections, content pages
Solution: We are looking at improved approaches to our headings in context of other parts.
Fieldsets without legends
Radio buttons and checkboxes lack proper grouping labels
Affected areas: Contact forms
Solution: We are working on adding proper fieldset legends to form elements.
Definition lists improperly formatted
Price information and team credits not using proper definition list markup
Affected areas: Price tooltips on agenda pages, production team credits
Solution: We are updating these to use proper definition list markup.
1.3.2 Meaningful Sequence
Modal dialog focus management
Focus can leave modals while they remain open
Affected areas: Shopping cart dialog, calendar picker
Solution: We are looking at new datepicker controls and a global solution to handling modals in general and rolling this out by context.
Background content accessible behind dialogs
Screen readers can access content behind modal overlays
Affected areas: Shopping cart, modal windows
Solution: We are looking at a global solution to handling modals in general and rolling this out by context.
Illogical reading order
Event cards read name before date/time
Affected areas: Agenda listings
Solution: We are looking at revising the ordering of content here, this should be delivered in the coming sprints.
1.4.1 Use of Colour
Seat ranking by colour only
Different seat categories distinguished solely by colour
Affected areas: Seatmap
Solution: We are looking at a completely new Seatmap experience as part of our new order flow that will include additional indicators beyond colour.
1.4.3 Contrast (Minimum)
Text over images
Insufficient contrast for text overlaid on background images
Affected areas: Showcase banners, Hero sections
Solution: This is mostly a stylistic choice by our users. We recommend using the flat layout here or increasing the contrast of any overlays. We are rolling out a more compliant "default".
Error messages
Red error text has insufficient contrast
Affected areas: Form validation messages
Solution: We are looking to a global solution for error messages platform wide.
1.4.4 Resize text
Loss of functionality at 200% zoom
Content becomes inaccessible when text is resized
Affected areas: Main navigation, list views
Solution: We are looking into an improved agenda layout to reduce the density of these views.
1.4.10 Reflow
Process bar disappears
Checkout steps not visible in reflow
Affected areas: Reservation/checkout flow
Solution: Will be resolved in the new order flow.
Navigation issues
"Go directly to" menu items read when collapsed
Affected areas: Mobile navigation
Solution: We are looking at wider improvements to navigation as a whole.
1.4.11 Non-text Contrast
Seatmap seats
Available seats have insufficient contrast (1.2:1) with background
Affected areas: Seatmap
Solution: We are looking at a completely new seatmap experience as part of our new order flow.
Focus indicators
Focus state lacks sufficient contrast across various backgrounds
Affected areas: Various components
Solution: We are looking towards better defaults for focus states across the platform, instead using the browser defaults for now.
1.4.12 Text Spacing
Content loss with text spacing
Layout breaks when user-defined text spacing is applied
Affected areas: Agenda list view, general layouts
Solution: We are looking into an improved agenda layout to reduce the density of these views.
2.1.1 Keyboard
Date-picker not keyboard accessible
Calendar widget cannot be operated via keyboard
Affected areas: Event filtering, date selection
Solution: There are little-to-no solutions for an accessible date-picker that offers the features we require, therefore we have designed our own, which will be developed for use across the CMS and the website.
Seat selection not keyboard operable
Cannot select seats using keyboard only
Affected areas: Seatmap
Solution: We are looking at a completely new Seatmap experience as part of our new order flow. In the interim, users can opt for the select seats for me journey, or we suggest adding copy to contact the box office should end-users need support.
Tooltips not keyboard accessible
Price and information tooltips cannot be accessed via keyboard
Affected areas: Agenda pages, price displays
Solution: These will be improved with wider modal/popup improvements and rolling this out by context.
2.2.2 Pause, Stop, Hide
Automatic timer cannot be hidden
Cart countdown timer continuously visible and cannot be paused
Affected areas: All pages when items in cart
Solution: Will be resolved within the new order flow.
Auto-rotating content
Videos and slideshows cannot be paused
Affected areas: Homepage banners, showcase sections
Solution: We have introduced pauses for video content, but this should apply to auto-rotating carousels too, we suggest turning this option off in the Dashboard.
2.4.3 Focus Order
Focus leaves intended areas
Tab order moves outside modals and menus
Affected areas: Modal dialogs, dropdown menus
Solution: Will be improved with wider modal/popup improvements and rolling this out by context.
2.4.4 Link Purpose (In Context)
Generic link text
SVG/icons without accessible names
Affected areas: Content pages, article listings
Solution: We are looking at reclassifying these as programmatically clickable links.
2.4.7 Focus Visible
Inconsistent focus indicators
Some interactive elements lack visible focus states
Affected areas: Custom UI components
Solution: We are looking towards better defaults for focus states across the platform, instead using the browser defaults for now.
3.1.2 Language of Parts
Language switching not properly marked
Multi-language content within a page lacks proper language attributes
Affected areas: Part specific languages not part of the language switcher buttons
Solution: We are looking at how we can add language flags for content within a page.
3.2.4 Consistent Identification
Inconsistent UI patterns
Similar functions use different naming conventions
Affected areas: Various navigational items
Solution: We are looking at standardising the naming and structure of these components site-wide.
3.3.1 Error Identification
Missing error messages
Form validation doesn't provide text-based error identification
Affected areas: Profile management, contact forms
Solution: We are looking at a validation system that works site-wide for this. If you are using custom forms, please reach out on helpdesk and we can assist you with manual fixes for this.
3.3.2 Labels or Instructions
Mandatory field marking
Asterisk (*) for required fields not explained before form
Affected areas: All forms
Solution: We are working through this to create a solution given the vast usage of forms across the platform (and custom forms built on those).
4.1.2 Name, Role, Value
iFrames without names
Modal windows lack accessible names
Affected areas: iFrames
Solution: We are looking at a title field for these, but you can use a description field and title to help advise visitors of this.
Unnamed interactive elements
Seats and remove buttons lack proper labels
Affected areas: Seatmap, clickable icons
Solution: We are looking at giving names and appropriate context to all icons, including the new seatmap in the order flow.
4.1.3 Status Messages
Status updates not announced
Dynamic content changes not communicated to screen readers
Affected areas: Form submissions, cart updates
Solution: We are looking at a site-wide announcement feature to cover situations like this across contexts.
Feedback and support
If you have any suggestions or questions, please create a ticket in our service desk.