search

immersive-web / model-element

Repository for the <model> tag. Feature leads: Marcos Cáceres and Laszlo Gombos
https://immersive-web.github.io/model-element/
Other
62 stars 11 forks source link

Accessibility: ARIA integration and HTML Accessibility API Mappings #39

Open marcoscaceres opened 1 year ago

marcoscaceres commented 1 year ago

We need to define how what the ARIA semantics are and what is exposed (application probably). We need to coordinate with the accessibility folks + get this added to the HTML Accessibility API Mappings.

svinkle commented 1 year ago

I conducted thorough accessibility testing of Google's <model-viewer> web component several years ago. My research and findings are documented in my blog post, 3D Model Accessibility.

In particular, you may be interested in the section where I attempt an ARIA Authoring Practices Guide style outline. This includes keyboard and aria-* expectations.

Please note: I've not sent these recommendations for any type of usability testing for confirmation. This is due to <model-viewer> issues preventing the use of the component altogether with some AT.

If you're interested, here's some links to GitHub issues regarding 3D model accessibility:

In my opinion, here's the main concerns preventing usability and perceivability of a 3D model component while using assistive technology:

  1. Semantic meaning. When discovered, how do we describe what the user is interacting with? What semantics are available to convey this content type?
  2. Input modalities. Touch, swipe, keyboard, mouse, voice, and many more input methods exist. How do we ensure people with various methods of input are able to interact with the model?
  3. Text alternatives. Web authors provide context for an image via alt attribute. Authors provide context for video via aria-label or other means. A 3D model is an incredibly visual medium. How do we ensure what's displayed visually is described to the end user who cannot see the model?

These are a few questions worth exploring. However this is approached, it must include feedback by people with disabilities throughout.

marcoscaceres commented 1 year ago

This is amazing @svinkle! I'll give all that a read. I filed a more general issue for a11y: #50. I'm hoping we can put together some ideas and then bring in the W3C a11y folks to help us.

cookiecrook commented 1 year ago

Discussion of this topic at TPAC 2022 is embedded in the ARIA minutes for Sept 16th: https://www.w3.org/2022/09/16-aria-minutes.html#x465

jnurthen commented 1 year ago

we missed adding a new topic but discussion starts halfway through - https://www.w3.org/2022/09/16-aria-minutes.html#t05 (search for "hi everyone please join our meeting once again?")

cookiecrook commented 1 year ago

TIL every line of the RRSAgent-generated minutes has a hash ID. https://www.w3.org/2022/09/16-aria-minutes.html#x465