Skip to main content
Events increasingly build their own websites and apps for schedules, maps, and networking. These often get overlooked from an accessibility perspective. Bake accessibility in during concept phase and, when using a third party, confirm their conformance early — ask for a VPAT. Accessible digital experiences take time to build and validate. Don’t wait until it’s too late.

​
Scoping questions

This guideline applies if you answer yes to either:
  • Does your event have a website?
  • Does your event use a companion app?

​
Implementation guidelines

​
Websites

Web Content Accessibility Guidelines (WCAG) Alternative methods
  • Provide an alternative way to access the site’s materials — printed handouts, brochures, or physical maps.
  • If the site includes functionality like scheduling meetings or messaging guests, offer alternative channels such as staff-assisted service at an information desk.

​
Applications

Web Content Accessibility Guidelines (WCAG) Alternative methods
  • Provide alternative access to the app’s materials — printed handouts, maps, brochures.
  • If the app includes networking or messaging features, offer staff-assisted alternatives.

​
Resources and tools

Last modified on August 4, 2026

Related topics

Web Content Test Application (CTA) overviewPAGE 101 · Accessible event registration guidelinesSetting up PlayFab authentication using Kongregate and UnitySetting up PlayFab authentication using Kongregate and HTML5PAGE 108 · Accessible attractions and activations