Ticketing & Events

October 1, 2025 · Last updated on March 16, 2026

Recipe: Capture Access Needs

# accessibility

# ticketing operations

# recipes for success

Makes: An online booking journey that empowers access for everyone

Inclusivity begins with the booking journey. Ensuring that all customers can self-identify access needs online helps you make the experience equitable and welcoming for everyone.

This recipe helps you record access needs clearly, use that data to highlight relevant seats, and communicate more effectively with your audience.

What you need

Access to Tag Groups and web-visible Tags in Spektrix

Ability to configure Custom Website Messages

(Optional) Integration with the Nimbus Access Card (UK only)

Time required

15 minutes

What will this help me achieve?

Let customers self-identify their access needs

Create targeted segments for communication and seat availability

Build a more inclusive and supportive booking experience

Concepts we’ll be using

Normal Tags (web-visible): Manually applied labels that customers can select themselves

Tag Groups: Group tags together for better organisation and visibility

Custom Website Messages: Add messaging during booking that encourages account login or self-identification

Nimbus Access Card (UK only): A third-party tool for centralised access identification

Prep

Decide which access needs your organisation wants to support and communicate. This could include wheelchair access, captioning, step-free routes, or sensory-friendly performances.

Draft clear, audience-friendly labels for your Tags so customers can easily understand and self-select.

Review your existing Tag Groups and Custom Website Messages to see if updates are needed before you create new ones.

If you're UK-based and planning to use the Nimbus Access Card, reach out to Nimbus Disability to get set up and understand their recommended access categories.

Activate

Create a Tag Group named “Access” and mark it as visible on the web.

Add Tags within that group for specific access needs (e.g. “Wheelchair access,” “Captioned performance,” “Assistance dog welcome”).

Add a Custom Website Message to the chooseseats.aspx iframe prompting users to log in or create an account to share their access needs or link a Nimbus Access Card (if in the UK).

Optional – Use the Nimbus Access Card

For organisations based in the UK, the Nimbus Access Card helps reduce the need for repetitive documentation. Customers manage their access requirements centrally, and your system reads those needs directly.

Tags would not be visible on the web if you are using this method.

More to explore

↗️Creating and Managing User Accounts

Guidance on how to set up, control, and assign permissions for user accounts in your system — useful if multiple staff will manage tags or settings.

↗️How to Request Help with Reports

Tips on submitting report requests and getting support when you want to analyze how well your access tags and strategies are working.

Comments (0)

Popular

Table Of Contents