Share via

Playbook for Accessible Gaming Events Guideline 106: Web Content and Applications

  • Article

Increasingly, events are starting to create their own websites and applications whose purpose goes beyond just registering. These sites might provide schedules of speakers, maps of the venue, the ability to set up meetings with other guests, and more. However, these sites and applications are often forgotten about from an accessibility perspective.

Before your event, it's important to ensure that accessibility is thought about at the concept phase of such sites and apps. If using a third-party provided app or web service, connect with them early to confirm that their experiences are accessible (you may ask for a Voluntary Product Accessibility Template or "VPAT" that shows their conformance with WCAG guidelines).

It can take a while to create and validate accessible digital experiences; don't get caught waiting until it's too late to make them more inclusive for those with disabilities.

Scoping questions

If you answer "Yes" to any of the following questions, this guideline applies to your event:

  • Does your event have a website?

  • Does your event utilize a specific app?

Implementation guidelines

Consider implementing the following guidelines for your event.

Websites

  • Web Content Accessibility Guidelines (WCAG)

  • Alternative Methods

    • An alternative method of accessing materials from the site should be provided, such as printed handouts or brochures. As an example, maps on websites should be printed out and available physically as well.

    • If the site offers functionality such as setting up meetings between guests, sending messages to guests, etc. there should be alternative ways provided to do so, such as doing so from an information desk with assistance from staff.

Applications

  • Web Content Accessibility Guidelines (WCAG)

    • Apps, where applicable, should follow WCAG 2.1 AA) standards.

  • Alternative Methods

    • An alternative method of accessing materials from the app should be provided, such as printed handouts or brochures. As an example, maps in applications should be printed out and available physically as well.

    • If the site offers functionality such as setting up meetings between guests, sending messages to guests, etc. there should be alternative ways provided to do so, such as doing so from an information desk with assistance from staff.

Resources and tools

Article | Building Accessible Apps | android.com

Article | Building Accessible Apps | apple.com

Article | Developing inclusive Windows apps | microsoft.com

Article | How to create an accessible app and why you should | medium.com

Tool | Voluntary Product Accessibility Template (VPAT) | section508.gov

Website | Web Content Accessibility Guidelines (WCAG) 2.1 | w3.org