Inclusive Queues: Rest Areas, Virtual Queuing and Clear Information

Why an inclusive queue is really three systems, not one

A queue excludes people not because they 'cannot wait', but because the wait is designed for one averaged visitor profile. Some people cannot stand for long or tolerate a crowded line, some will not hear a call, and some cannot follow what is happening next. Each of these limitations is removed by a different mechanism, so there is no single universal 'accessible line'.

A workable approach combines three systems. First, rest areas and seating reachable from the queue, so a person can sit down without losing their place. Second, virtual queuing, which lets someone wait somewhere else and return at an appointed time. Third, clear information: displays, announcements, and wayfinding that can be perceived by sight and hearing and understood across languages. Lean on only one and you help one group at the expense of others.

• Physical access to the line — for people with mobility limits and those who are blind.
• The ability to wait off the line — for people who cannot stand in one place for long.
• Clear information — for people who are deaf, hard of hearing, blind, cognitively diverse, or do not share the operator's language.

Rest areas and seating that preserve your place

Even a short wait is exhausting without a seat, and for someone with limited mobility or fast fatigue the absence of one makes a venue effectively inaccessible. A useful baseline appears in accessible-service rules such as Ontario's AODA standard (a jurisdiction-specific reference): accessible seating should include at least one space in every waiting area and a proportion of spaces where a mobility device fits, placed among the general seating rather than segregated elsewhere.

Make the seating mix varied: some chairs with armrests, some without, plus room beside a seated companion so a wheelchair user and a friend can sit together without blocking a corridor. The essential rule is that a seated person must not lose their place: if someone rests or steps away, there needs to be a clear way back — a call, a pager, or a note with a staff member. Otherwise an 'accessible bench' simply means starting over.

• Place accessible seats among the general ones, not in a far corner.
• Leave space for a wheelchair beside a seated companion.
• Provide a mechanism to return to the queue after resting — a call or staff help.
• For long lines, distribute seating along the whole route, not only at the front.

Make the line itself navigable

For a blind person a queue is usually an invisible ribbon across an open floor. Canadian blindness-design guidance (CNIB's Clearing Our Path) recommends queuing lanes around 1.2 m wide with clear floor space of roughly 1.5 by 1.5 m at the entry, exit, and wherever the line changes direction. It favours fixed, high-contrast guides that a white cane can detect over floor-only rope 'switchbacks', which are hard to find and give no clue where the line starts or whether it is moving.

The same reasoning underpins universal-design codes such as Russia's building-code family for people with reduced mobility (SP 59.13330): travel paths wide enough for wheelchair users to pass, firm non-slip surfaces, and tactile, high-contrast marking at turns and hazards. Where soft guides are unavoidable, make them contrast with the floor, put members at two levels so a cane finds them and a guide dog does not pass underneath, and add a detectable path of contrasting or textured surface through the area.

A call button at the start and end of the queue lets a blind visitor request assistance, and in busy areas a paging or announcement system can call a person forward and say where to go. Tight spots, turnstiles, and pockets where two wheelchairs cannot pass should be removed or bypassed by an accessible route.

Virtual queuing: wait elsewhere, return on time

Virtual queuing solves the core problem for people who cannot stand in one place: they join the line remotely, move freely, and return when their turn approaches. Theme parks have used exactly this idea, giving a guest a return time equal to the current standby wait instead of standing in the physical line. Some operators now run this digitally; Alton Towers, for example, moved guests with accessibility passes to the Merlin Ride Access Pass app with its own virtual-queue system from late November 2025.

The key to an accessible virtual queue is offering many ways to join it. Queue-management platforms let customers enter by QR code, an SMS link, or a website, check in on an on-site kiosk, or be signed in by front-desk staff. That matters because a meaningful share of visitors have no smartphone, limited data, or little confidence with apps — a purely digital path would exclude precisely the people who need help most.

Displays in the waiting area should show the current number and an estimated wait so people know how much time they have. Where a queue stays virtual but presence matters, a fair return-time model is not 'skipping the wait': it is an equal-length wait spent in a comfortable place. The system then removes the physical and sensory cost of standing rather than creating a privilege.

• Equal wait time, different place: return time mirrors the current wait.
• Multiple join channels: app or QR, SMS/web, kiosk, and staff sign-in.
• Real-time position and estimated wait shown where people actually wait.
• A published, fair basis for who qualifies, reviewed case by case.

Tell people their turn through every channel they can perceive

A person who is deaf will not hear a voice call, and a person who is blind will not see a number on a board, so the turn notification must travel through at least two complementary channels. Established queue-management practice pairs a waiting-area display showing current and previously called numbers with synchronised voice announcements, and adds text or email in the customer's preferred language — reassurance and wayfinding for visitors with hearing loss, and a lifeline for those who cannot read the screen.

For digital interfaces, the practical benchmark is conformance to WCAG 2.1 Level AA: full keyboard operation, screen-reader support, sufficient text size and contrast. Voice announcements can be multilingual — the language chosen at booking or check-in carries through to the call. Some systems detect the customer's browser language and translate two-way messages automatically. Physical wayfinding can lean on high-contrast, cane-detectable signs and smart codes readable from a distance that speak the information aloud in the user's language — the European intellectual-property office in Alicante, for instance, deploys such codes so visitors hear, in their own language, what is in front of them.

Complement the technology with plain language and clear pictograms in signage and service texts: short 'what happens next' steps — where to stand, where to walk, what to bring — support people with cognitive disabilities and anyone facing a language barrier. Comprehension is not decoration; it is what lets a person actually reach their turn.

• Pair a visual board with a voice announcement and an optional message in the preferred language.
• Aim for WCAG 2.1 AA in any app or display: keyboard, screen reader, contrast.
• Use plain language and pictograms for 'what happens next' cues.
• Consider distance-readable smart signage that reads aloud in the user's language for wayfinding.

Run it fairly: eligibility, evidence, and staff

Access passes for people with non-apparent conditions — for example autism or anxiety that makes conventional waiting harmful — are better determined per application than by a claimed label alone. Operators using return-time schemes review each request individually, often over a video registration call, and frame the service around people who cannot stand in a conventional queue for an extended period rather than as a way around ordinary waiting.

Criteria should be published and applied consistently, and visitors told well in advance when a program needs pre-registration or an app installed before the visit — as Alton Towers did when it moved its Ride Access Pass to an app-based virtual queue from 28 November 2025. Anyone who cannot or will not use an app needs a fallback: a counter, a phone line, or a paper ticket. Note also that pass criteria can change over time, so check the operator's current page before advising a guest.

Staff are part of the system: an agent should see flagged needs (notes on a profile, a priority marker), answer an assist button promptly, and record response times. When an organisation measures how fast help requests are answered and where queues stall, inclusion stops being a statement and becomes a managed process. Treat queue data as evidence for where to add seating, widen a lane, or retrain staff.