What the statement should promise
Promise a process the team can actually operate: a monitored contact, a private request route, a response expectation, an assisted option, and notice that late requests will still be reviewed even when provider availability becomes constrained.
What the statement should not promise
Avoid blanket venue-accessibility claims, guaranteed provider availability, automatic approval language, or a suggestion that the form makes legal or medical determinations.
Place it where people make decisions
Use the statement on the event page, registration form, confirmation email, agenda or mobile guide, and attendee instructions. Keep the wording and contact route consistent.
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
Where should an event accessibility statement appear?
Place it before and during registration, on the event information page, and in confirmation communications so attendees can find it without completing a purchase or registration step.
Should a cutoff be described as a hard deadline?
Describe it as the date that gives the team the best chance to arrange service. Explain how later requests will be handled rather than implying they cannot be submitted.
Can I publish the generated copy unchanged?
Review it first. Names, channels, dates, response times, venue facts, and operational promises must match your actual event.