Integrate feedback from accessibility audit #37

Open
opened 2025-09-18 07:30:47 +00:00 by utopiah · 7 comments
Owner
No description provided.
utopiah added the Process audits from NLNet network label 2025-09-18 07:30:47 +00:00
utopiah added this to the NGI0 Commons Fund 2025-04 milestone 2025-09-18 12:00:10 +00:00
Author
Owner

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.

image.png
  1. green volume is where the interactable content must be in most cases
  2. larger white volume is where some secondary content could be, but ideally avoided
  3. largest red volume is where only visual content should be, otherwise it might be out of reach
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. <img width="903" alt="image.png" src="attachments/459c7635-23bb-486b-80bf-87f63334fe48"> 1. green volume is where the interactable content must be in most cases 2. larger white volume is where some secondary content could be, but ideally avoided 3. largest red volume is where only visual content should be, otherwise it might be out of reach
717 KiB
Author
Owner

let el = document.createElement("a-box"); el.setAttribute("wireframe", true); el.setAttribute("color", "red"); el.setAttribute("scale", "2 2 2"); el.setAttribute("position", "0 .5 0"); document.querySelector("a-scene").appendChild(el)
el = document.createElement("a-box"); el.setAttribute("wireframe", true); el.setAttribute("color", "orange"); el.setAttribute("scale", "1.5 1.5 1.5"); el.setAttribute("position", "0 .5 0"); document.querySelector("a-scene").appendChild(el)
el = document.createElement("a-box"); el.setAttribute("wireframe", true); el.setAttribute("color", "green"); el.setAttribute("scale", "1 1 1"); el.setAttribute("position", "0 .5 0"); document.querySelector("a-scene").appendChild(el)

```javascript let el = document.createElement("a-box"); el.setAttribute("wireframe", true); el.setAttribute("color", "red"); el.setAttribute("scale", "2 2 2"); el.setAttribute("position", "0 .5 0"); document.querySelector("a-scene").appendChild(el) el = document.createElement("a-box"); el.setAttribute("wireframe", true); el.setAttribute("color", "orange"); el.setAttribute("scale", "1.5 1.5 1.5"); el.setAttribute("position", "0 .5 0"); document.querySelector("a-scene").appendChild(el) el = document.createElement("a-box"); el.setAttribute("wireframe", true); el.setAttribute("color", "green"); el.setAttribute("scale", "1 1 1"); el.setAttribute("position", "0 .5 0"); document.querySelector("a-scene").appendChild(el) ```
utopiah added the Review pending label 2026-04-13 12:47:01 +00:00
utopiah removed the Review pending label 2026-04-16 12:11:33 +00:00
Author
Owner

Consider also #75

Consider also https://git.benetou.fr/utopiah/biggu_s_gate/issues/75
Author
Owner
See also https://www.w3.org/WAI/ and https://www.w3.org/WAI/APA/wiki/WebXR_Standards_and_Accessibility_Architecture_Issues
Author
Owner

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 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.
Author
Owner

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, see pages/remixes/remix__accessibility_example.json.

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, see `pages/remixes/remix__accessibility_example.json`.
Author
Owner
[HAN Accessibility Report - Iterative Explorations SCS.pdf](/attachments/4d2566ce-e240-4292-97c2-5b899a80c1af) Including 19 findings with matching https://www.w3.org/WAI/WCAG22 links
Sign in to join this conversation.