Integrate feedback from accessibility audit #37
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Partly clarified during a call on the prototyping aspect. Constraints are different than on a release that's nearly a product.
Most effort can be shifted to #20 then #23
Some assumptions also have to explicit, e.g reliance on hand tracking and some mobility (small size roomscale, standing up).
Testing also showcased some limitations, e.g. player height. A typical risk is a parent or teacher designing a game, placing assets too high which becomes unreachable by children. A good template could provide a volume wireframe, i.e. a 3D equivalent of cinematic framing, where the content must typically remain at the center of the frame.
Consider also #75
See also https://www.w3.org/WAI/ and https://www.w3.org/WAI/APA/wiki/WebXR_Standards_and_Accessibility_Architecture_Issues
See https://xraccessibility.github.io/#webxr with https://github.com/rdub80/aframe-binary-controls and past collaborations with Roland Dubois.
A most promising path is to respect W3C WAI, namely not "just" have a
<a-entity>semantic entity which becomes a 3D object that must then been seen but rather also have enough information that can be read.See also past work on hand switching, e.g.
switchSide()in https://git.benetou.fr/utopiah/biggu_s_gate/src/branch/main/pages/jxr-core.js#L757 available already as remix, seepages/remixes/remix__accessibility_example.json.HAN Accessibility Report - Iterative Explorations SCS.pdf
Including 19 findings with matching https://www.w3.org/WAI/WCAG22 links