Accommodation Request Forms for Inclusive Events in 2026: What to Ask, What Not to Ask, and How to Follow Through

An accommodation request form is not just an extra field on a registration page.

It is an invitation.

It tells attendees: we know people participate in different ways, we planned for that, and we have a real person who will follow up.

But many event forms get this wrong. They ask vague questions, collect sensitive information they do not need, bury access requests in tiny text, or ask attendees to disclose personal details without explaining who will see them.

An inclusive event accommodation request form should be simple, respectful, and useful. It should help the event team prepare without forcing attendees to overexplain their disability, medical history, family situation, religion, gender identity, or personal life.

This guide explains how to build an event accommodation request process in 2026 that is practical, privacy-aware, and actually connected to event operations.

Important note: This guide is educational, not legal advice. Event organizers should consult qualified counsel about legal obligations, especially for public accommodations, workplaces, schools, government events, youth events, and events receiving public funding.

What is an event accommodation request form?

An event accommodation request form is a way for attendees, speakers, vendors, staff, or volunteers to tell the event team what they need to participate.

Requests may involve:

• Wheelchair-accessible routes and seating
• ASL interpretation
• Live captioning or CART
• Accessible digital materials
• Reserved seating
• Dietary needs or allergy information
• Quiet rooms or sensory break spaces
• Service animal space
• Personal care attendant registration
• Gender-neutral restrooms
• Prayer or lactation space
• Fragrance-reduced areas
• Accessible parking or drop-off information
• Extra time during registration or check-in
• Hybrid participation or remote access

The form is only the start. The real test is whether the event team follows through.

Why the wording matters

Bad wording can make people feel like a burden.

Better wording makes access normal.

Weak wording	Better wording
Do you have any special needs?	Do you have any accessibility needs or accommodation requests that would help you participate?
List your disability.	Please tell us what support or access arrangement you are requesting. You do not need to share a diagnosis.
We cannot guarantee accommodations.	We will make reasonable efforts to support requests and may contact you if we need more information.
Dietary restrictions?	Do you have any food allergies, dietary needs, or religious/cultural food requirements we should know about?
Need help?	For access questions, contact [name/role] at [email/phone].

People should not have to decode whether they are allowed to ask.

Ask for needs, not diagnoses

In most event contexts, the event team does not need a diagnosis.

It needs to know what to arrange.

Instead of asking:

• “What disability do you have?”
• “What is your medical condition?”
• “Why do you need this?”

Ask:

• “What accommodation or access support would help you participate?”
• “Do you need accessible seating, captioning, interpretation, materials in another format, or another support?”
• “Is there anything we should know about timing, seating, communication, food, or environment to support your participation?”

If the event has legal or workplace-specific documentation requirements, handle that in a separate process with appropriate privacy protections. Do not make the public registration form collect unnecessary sensitive information.

A strong accommodation request field

Here is a simple version that works for many events:

Accessibility and accommodation requests

We want this event to be accessible and welcoming. Please tell us about any accommodations or access needs that would help you participate, such as seating, mobility access, captioning, ASL interpretation, dietary needs, quiet space, service animal space, accessible materials, or another support. You do not need to share a diagnosis.

Request: [open text field]

May our accessibility contact follow up with you if needed? [Yes / No]

Preferred contact method: [Email / Phone / Text]

This is better than a checkbox-only system because people’s needs rarely fit a perfect menu.

When to use checkboxes

Checkboxes can help attendees think of needs they might forget to mention.

Use them as prompts, not limits.

Checkbox option	Why it helps
Wheelchair-accessible route or seating	Helps plan room layout and venue navigation
Accessible parking/drop-off information	Helps with arrival details
ASL interpretation	Requires advance vendor coordination
Live captioning/CART	Requires advance vendor coordination
Accessible digital materials	Helps prepare slides, PDFs, and agendas
Reserved seating	Helps with sightlines, hearing, mobility, or anxiety needs
Quiet room/sensory break area	Helps plan low-stimulation space
Dietary need or allergy	Helps catering and labeling
Service animal space	Helps seating and venue planning
Personal care attendant/support person	Helps registration and badge planning
Lactation/private care space	Helps room planning
Prayer/quiet reflection space	Helps room planning
Other request	Prevents the list from becoming limiting

Always include “other request” and an open text field.

Recommended form structure

A clean event accommodation section can look like this:

1. Accessibility statement
2. Accommodation checklist
3. Open request field
4. Food/allergy section
5. Optional privacy note
6. Follow-up permission
7. Deadline guidance
8. Contact person

Here is a full example.

Accessibility and accommodations

We want this event to be accessible and welcoming. Please tell us about any accommodations or access needs that would help you participate. You do not need to share a diagnosis.

Which of the following would help you participate? Select all that apply.

• Wheelchair-accessible route or seating
• Accessible parking or drop-off information
• ASL interpretation
• Live captioning/CART
• Accessible digital materials
• Reserved seating
• Quiet room or sensory break space
• Food allergy or dietary support
• Service animal space
• Support person or personal care attendant registration
• Lactation/private care space
• Prayer or quiet reflection space
• Other access request

Please share any details we need to plan well: [open field]

Do you have food allergies, dietary needs, or religious/cultural food requirements? [open field]

May our accessibility contact follow up with you if needed? [Yes / No]

Preferred contact method: [Email / Text / Phone]

To help us coordinate vendors and venue logistics, please submit requests by [date]. We will still do our best to support requests received after that date.

Questions? Contact [name/role] at [email/phone].

The deadline should not become a wall

Events often need deadlines for interpreters, captioners, food orders, room layouts, transportation, or printed materials.

That is reasonable.

But the wording matters.

Avoid:

Accommodation requests must be submitted by May 1. No requests accepted after that date.

Use:

Please submit accommodation requests by May 1 so we have time to coordinate vendors, materials, and venue logistics. We will still do our best to support requests received after that date.

This sets expectations without shutting people out.

Privacy and data handling

Accommodation requests can reveal sensitive information.

Treat them as private operational information, not marketing data.

Privacy question	Better practice
Who can see the request?	Limit access to the event lead, accessibility contact, and staff/vendors who need the information to fulfill the request
Is the data used for marketing?	No, not unless the attendee separately consents
Are requests shown on badges?	No, unless the attendee chooses a visible marker for a specific reason
Are dietary needs shared with caterers?	Share only necessary information, not unrelated personal details
Are disability details stored forever?	Avoid long-term storage unless needed; delete or anonymize after the event according to your policy
Is AI used to summarize requests?	Avoid sending sensitive access requests into tools without a clear privacy basis and vendor review

A simple privacy note can help:

We use accommodation information only to plan and support event access. We limit access to people who need the information to respond to your request.

Do not make identity fields required unless truly necessary

Some inclusive event forms overcorrect by asking many identity questions.

Be careful.

A registration form may ask optional demographic questions for reporting, scholarships, or community programming. But do not make sensitive identity questions mandatory unless there is a clear reason.

Examples:

Field	Recommended approach
Pronouns	Optional, with “Prefer not to say” or blank allowed
Chosen name	Allow people to enter the name they want on badge/materials
Legal name	Ask only if needed for payment, travel, security, or credentialing
Disability status	Usually not needed for event registration; ask for access needs instead
Race/ethnicity	Optional only, explain why if collecting
Gender identity	Optional only, explain why if collecting
Dietary restrictions	Optional but visible and easy to find
Accessibility needs	Optional but encouraged and clearly supported

Inclusive forms give people control.

Food allergy and dietary request section

Food can determine whether someone can safely attend.

A strong food section asks clearly and avoids treating dietary needs as a preference problem.

Suggested wording:

Food allergies and dietary needs

If food will be served, please tell us about any food allergies, dietary needs, or religious/cultural food requirements we should know about. We will work with the venue/caterer to label food and support requests where possible.

Details: [open field]

For larger events, ask caterers about:

• Ingredient lists
• Allergen labeling
• Cross-contact risks
• Separate serving utensils
• Packaged options
• Staff knowledge
• Whether attendees may bring outside food for medical/religious needs

FARE explains that cross-contact can occur when an allergen is accidentally transferred from one food to another, and even small amounts can matter for people with food allergies.

Operational workflow

The form is only useful if someone reviews it.

Create a simple workflow:

Step	Owner	Timing
Review new requests	Accessibility/event lead	At least twice weekly before event; daily near event
Categorize request	Event lead	Within 2 business days
Confirm receipt	Event lead	Within 2 business days when possible
Contact vendors	Event/operations team	As early as possible
Update room layout	Operations/venue lead	Before final floor plan
Prepare check-in notes	Registration lead	Before event day
Confirm with attendee	Accessibility contact	When arrangement is ready or if options are limited
Debrief after event	Event lead	Within 1 week

A spreadsheet can work for small events. Larger events should use a secure event management system with restricted access.

What to do if you cannot provide exactly what was requested

Sometimes the exact request cannot be fulfilled, especially if it arrives late or the event has venue limitations.

Do not ignore it.

Respond respectfully:

Thank you for sharing this request. We are checking what we can arrange with the venue and vendors. If the exact setup is not available, we will follow up with the closest available options so you can decide what works for you.

Offer alternatives when possible.

Examples:

Requested	Possible alternatives if exact request is not available
ASL interpreter	Remote interpreter, captioning, transcript, reserved front seating, future recording with captions
Quiet room	Reserved low-traffic area, nearby private room, re-entry permission, sensory kit
Specific meal	Packaged safe meal, ingredient list, outside food permission, nearby food options
Accessible parking	Drop-off route, reserved space request, shuttle details, nearby accessible parking map
Printed large-print materials	Digital accessible copy, enlarged agenda, screen-reader-friendly PDF

The key is to communicate, not disappear.

FAQ

Should an accommodation request form ask for documentation?

Most public event registration forms should not ask for medical documentation. Ask what support the attendee needs to participate. Legal, school, workplace, or specialized programs may have different requirements and should use a separate process.

How early should we ask for accommodation requests?

Ask during registration, not after ticket purchase. Include the request field on the main registration form and repeat it in confirmation emails.

Should we include a phone number?

Yes, if possible. Some people may not be able to explain an access request comfortably in a form field. Offer email and phone/text when you can.

What if no one requests accommodations?

Still make the event accessible by default. Accessible routes, readable signage, captions on videos, plain-language instructions, and accessible materials should not depend only on requests.

Should we ask about pronouns in the same section?

You can ask optional pronouns elsewhere on the registration form, especially for badge printing. Keep accommodation requests focused on participation needs.

Sources

• ADA.gov: Effective Communication — https://www.ada.gov/resources/effective-communication/
• CDC: Disability Inclusion Strategies — https://www.cdc.gov/disability-inclusion/strategies/index.html
• W3C WAI: Making Events Accessible — https://www.w3.org/WAI/teach-advocate/accessible-presentations/
• FARE: Avoiding Cross-Contact — https://www.foodallergy.org/resources/avoiding-cross-contact
• Section508.gov: Accessible Meetings — https://www.section508.gov/create/accessible-meetings/