Design the request path
Publish a clear accessibility statement, private request route, assisted option, contact, response expectation, and practical planning date. Ask about participation needs and affected event context rather than forcing a diagnosis.
Turn the request into an event-specific plan
Authorized people review and record the organizer’s decision. The coordinator then maps each accepted need to services, sessions, rooms, providers, equipment, materials, approvals, cutoffs, and owners.
- Keep request, organizer decision, and purchased service distinct
- Version material changes and stale prior confirmation
- Surface blocked dependencies and their owners
- Share role-specific disclosure packs
- Return a plain-language plan to the attendee
Verify delivery and learn
Record day-of state, incidents, provider attestation, organizer observation, requester feedback, discrepancies, and follow-up. Preserve useful venue and provider learning after removing restricted case content.
Keep decisions human and evidence explicit
Evencue records decisions made by authorized organizers and coordinates their event-specific consequences. It does not determine legal reasonableness, medical validity, entitlement, or venue certification. Provider and onsite views receive only the information required for their task.
What teams usually ask
What is event accessibility planning?
It is the operational work of making event information, registration, environments, materials, communication, services, and delivery usable by attendees with disabilities.
Is collecting accommodation requests enough?
No. Each request needs an owner and a path through review, fulfillment planning, confirmation, day-of delivery, and closeout.
Does Evencue certify venues?
No. Teams can record sourced, dated venue observations and evidence, but Evencue does not certify that a venue is accessible.