Make the route easy to find and use
Place accessibility information in the main event and registration journey. Use native form controls, logical headings, associated instructions and errors, keyboard operation, screen-reader semantics, visible focus, reflow, and an assisted alternative.
Explain what happens next
Tell attendees who receives the request, when to expect a response, how information may be shared, how to update the request, and where to ask a question. Send a receipt with a reference and contact.
Create a dependable back-office handoff
Route the request to an accountable coordinator. Preserve the original submission, record clarifications separately, and keep the human organizer decision distinct from the fulfillment plan.
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 accessibility fields should event registration include?
A clear request invitation, affected dates or sessions, functional need, communication preference, contact and consent choices, plus a route for private follow-up.
Should the request be public to event staff?
No. The full request should remain private. Event, provider, finance, and onsite roles receive only the fields needed for their task.
How do late requests work?
Keep the route open, respond promptly, document provider or logistics constraints, and record the organizer’s human decision and any proposed alternative.