RE: WebGL experiences & accessibility

Generally folks take an approach where you have invisible HTML components overlay the controls or you use an ARIA live region and keyboard handler to accept input and feed content of the focused elements to screen readers.  An ARIA live region approach has a number of drawbacks for assistive technology such as speech recognition and braille displays.  The Unity Accessibility Plug-in has an implementation.
https://assetstore.unity.com/packages/tools/gui/ui-accessibility-plugin-uap-87935


The PHET simulators also have some accessible examples: https://phet.colorado.edu/en/accessibility/prototypes


Jonathan

From: Iulia Brehuescu <iulia.brehuescu@mediamonks.com>
Sent: Monday, July 26, 2021 5:00 AM
To: w3c-wai-ig@w3.org
Subject: WebGL experiences & accessibility

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

Hello,

I am looking for some thoughts on how to address accessibility on webgl experiences. For reference, what I mean by a webgl experience is something similar with what Netflix did for The Witcher<https://witchernetflix.com/en-gb>.

What would be the best/impactful approach:

  *   Provide a separate more linear/simpler experience while maintaining the main user flows?
  *   Or provide "Accessibility Settings" where users can change font style or enable/disable animations etc? (this idea I took from games & accessibility)
Any feedback would be appreciated!