immersive-web
model element accessibility requirements
model element accessibility requirements...
There are already some examples in the Model Element Explainer
As for model formats, USD in particular allows the model itself to contain accessibility information... (similarly to how an SVG image can contain an accessible subtree or not) so this requirements list isn't limited to simple accessibility like a label on a leaf node.
- https://openusd.org/dev/user_guides/schemas/usdUI/AccessibilityAPI.html
<model> fallback content could be based on <video> fallback content allowing use of track alternatives like captions and text-based audio descriptions (or potentially an new vtt-based metadata variant that could delineate time-based accessibility metadata)... Some examples are called out in the explainer: https://github.com/immersive-web/model-element/blob/main/explainer.md#fallback-content
A way to indicate that the model contains its own accessibility metadata... e.g. "don't look here in the DOM for the accessibility, instead look in the model file."
This might also be useful for remotely loaded images (SVG>title or EXIF Description from raster image formats) or other include-type elements.
Related USD Announcements: (cc @zachernuk @dgovil)
- https://aousd.org/blog/announcing-openusd-v25-05-key-features-and-improvements/
- https://openusd.org/dev/api/class_usd_u_i_accessibility_a_p_i.html