Summit access commitment
Design for
many bodies.
Access is part of program quality, safety, and dignity. The current registry collects minimal functional input; an announced edition must publish confirmed services and known barriers.
In this standard
01Access is part of the event02Ask for function, not diagnosis03Physical and mobility access04Communication access05Sensory and digital access06Care, food, faith, and financial access07Publish what is confirmedAccess is part of the event
Before an edition can be announced, it needs an accessibility lead, budget, venue and digital review, request process, response timeline, and contingency plan. Compliance is the floor, not the goal.
Ask for function, not diagnosis
The interest form asks only for an optional note about the access feature or communication format a person needs and whether private follow-up is wanted. Medical records and diagnoses are not required; access notes are not published or used for promotion.
Physical and mobility access
The event plan must address step-free routes, seating choice, rest areas, accessible restrooms and stages, service-animal relief, transit and parking information, weather, emergency exits, and distances between spaces.
Communication access
Plans consider live captions, transcripts, sign-language interpretation, assistive listening, microphones for audience speech, readable wayfinding, plain-language pre-arrival information, and accessible presentation materials.
Sensory and digital access
Plans consider quiet space, lighting and sound disclosures, scent guidance, remote participation, keyboard and screen-reader access, contrast, reduced motion, recording availability, and accessible sign-in and ticketing.
Care, food, faith, and financial access
Scheduling and budget should consider caregiving, lactation, prayer, dietary information, hydration, rest, scholarships or lower-cost access, and the real cost of travel and participation without promising benefits before they are funded.
Publish what is confirmed
When an edition is announced, the site must name confirmed features, known barriers, request deadlines, response channels, and limitations. Goals must be labeled as goals until the relevant service is confirmed.
Continue