Integrate feedback from accessibility audit #37

New Issue

utopiah · 2025-09-18T07:30:47Z

utopiah commented

2025-09-18 07:30:47 +00:00

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

utopiah commented

2026-03-11 14:15:50 +00:00

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.

green volume is where the interactable content must be in most cases
larger white volume is where some secondary content could be, but ideally avoided
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

image.png

717 KiB

utopiah referenced this issue

2026-03-11 14:21:30 +00:00

Integrate feedback from security audit #36

utopiah referenced this issue

2026-03-11 14:37:49 +00:00

Clarify scaffolding as the core pedagogical principle #48

utopiah commented

2026-03-11 14:42:24 +00:00


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 referenced this issue

2026-03-11 14:51:48 +00:00

Allow local customization example for accessibility #7

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

utopiah commented

2026-05-07 11:30:38 +00:00

Consider also #75

Consider also https://git.benetou.fr/utopiah/biggu_s_gate/issues/75

utopiah commented

2026-05-07 14:21:40 +00:00

See also https://www.w3.org/WAI/ and https://www.w3.org/WAI/APA/wiki/WebXR_Standards_and_Accessibility_Architecture_Issues

utopiah commented

2026-05-07 14:23:53 +00:00

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.

utopiah referenced this issue

2026-05-21 08:24:19 +00:00

Cross media collaboration #98

utopiah commented

2026-06-04 10:55:50 +00:00

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`.

utopiah commented

2026-06-12 05:57:20 +00:00

HAN Accessibility Report - Iterative Explorations SCS.pdf

Including 19 findings with matching https://www.w3.org/WAI/WCAG22 links

[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

HAN Accessibility Report - Iterative Explorations SCS.pdf

459 KiB

utopiah commented

2026-06-22 08:34:47 +00:00

This table of issues is copied here to facilitate easily browsing through related issues. Some details are missing, e.g. links from the Guideline column. Please consider the PDF linked before as the reference.

Nr	Issue	Location	Guideline
1	The links in the intro have no other clear indication when hovering, pointing or clicking. Both in the browser and on the headset. In the browser, there is only the cursor pointer, but that might not be enough. On the headset, it is not sufficient as there is no indicator.	Website	1.4.1 Use of Color
2	Consider making it clearer which links open a game, and which open another webpage. This can also help users with orientation and expectation of what will happen when they interact with the options.	Website	2.4.4 Link Purpose 3.2.3 Consistent Navigation
3	The links to the games also have no clear alternate title/description or text. Leaving users to wonder what it is that the open when the click on it. Consider adding something like a title element to the link for each game for a clearer description.	Website	1.1.1 Non-text content 2.4.4 Link Purpose 1.3.1 Info and Relationships 4.1.2 Name, Role, Value
4	In the intro, it is stated that compatibility for WebXR is shown by the green or red background. Color cannot be the only way to make something clear to every type of user. Consider adding a clearer way of showing this state.	Website	1.4.1 Use of Color
5	Both on the website and with the pointer on the headset, it doesn’t seem possible to click the star rating select box for each game, as the link for opening the game seems to overlap and overwrite this. So when you click the star rating, the full game just opens. (With the keyboard, it is possible to reach these select boxes).	Website	3.2.2 On Input 3.2.3 Consistent Navigation 3.2.1 On Focus
6	There also seems to be an issue with the star ratings for some games, as some games can be rated, and some just have a list of the star options over the game.	Website	3.2.3 Consistent Navigation
7	Some games seem to have a title or text, that overlays part of the thumbnail and is difficult to read. Consider creating a higher contrast or moving this text.	Website	1.4.3 Contrast (Minimum) 3.2.4 Consistent Identification
8	When in an environment, the functions that you can use might not always be clear to every user. For example, we can understand that a certain function might make the sky blue or black. But not every user might. Consider changing the name of these “buttons”.	Game	4.1.2 Name, Role, Value 1.3.3 Sensory Characteristics
9	If you setup the audio recorder for feedback and deny access to the microphone. You still continue and can press the start button, but you cannot re-do that action to give permission for use of the microphone. Creating a possible deadlock.	Game	3.3.1 Error Identification
10	There is no directly visible feedback when using the recording options to start/stop. There is of course the console within the game, but this might not be understandable for everyone and is not always directly in the viewport. Make sure users are alerted when they press buttons and perform actions like this. For example, a status message when recording has started or stopped.	Game	4.1.3 Status Messages
11	Most buttons in the game also don’t offer clear feedback when you select them (any kind of “hover” or clear state that shows that if you pinch now, you will activate the option). Also, when performing the action, users have to spot the action (like the sky turning a different color) but aren't notified that they pressed the button and that the action was successful or unsuccessful. You get no feedback from choosing a specific button. Again, not taking into consideration that there is a log on the right, as this might not be readable for users and is not in viewport at all times.	Game	4.1.3 Status Messages 3.2.1 On Focus 3.3.1 Error Identification 2.4.7 Focus Visible
12	The instructions for a game are not always clear. The names of functions don’t help, as already discussed. But the fact that input options are different for left and right hand can also confuse users. As well as block users with hand/arm related disabilities from performing certain actions. These instructions are being shown within a game but can be missed by less experienced users.	Game	2.5.1 Pointer Gestures 3.3.2 Labels or Instructions
13	It is also not always clear which options you can drag or move, and with ones you can click. This is also being caused a bit by the names of the functions, but for example, every option has a blue circle on the left. But some do as well that can only be dragged or do nothing when pinching on them. Like “attributes”.	Game	2.5.1 Pointer Gestures 1.3.3 Sensory Characteristics 3.3.2 Labels or Instructions
14	It is pretty difficult to undo dragging or turning elements within a game. This can be increasingly difficult for texts that cannot be read upside down or turned in a weird way. Consider adding the possibility to undo or rollback specific actions.	Game	2.5.2 Pointer Cancellation
15	It might be unclear to users if there is a difference between green and red options within a game. If there even is a difference, of course.	Game	1.4.1 Use of Color 3.3.2 Labels or Instructions
16	The “123” buttons for the games can come across a bit unclear to users. From first impressions, it can seem like it is navigation for pages of games. But they all link to issues. Also, as they are so close together, it appears as though it is one button, but in fact, there are multiple.	Website	3.2.3 Consistent Navigation 1.3.1 Info and Relationships 4.1.2 Name, Role, Value
17	On the website, the button in the top left is not accessible with keyboard navigation.	Website	2.1.1 Keyboard
18	There is no title element present on the website, only smaller headers. Consider giving the website a proper structure, so users might have an easier understanding of the content when navigating through it.	Website	2.4.2 Page Titled 2.4.6 Headings and Labels
19	The select boxes on the website for ratings have no clear label or title for assistive technology like screen readers to give feedback to users about the purpose of the element. Consider adding this information.	Website	4.1.2 Name, Role, Value

This table of issues is copied here to facilitate easily browsing through related issues. Some details are missing, e.g. links from the Guideline column. Please consider the PDF linked before as the reference. Nr | Issue | Location | Guideline -- | -- | -- | -- 1 | The links in the intro have no other clear indication when hovering, pointing or clicking. Both in the browser and on the headset. In the browser, there is only the cursor pointer, but that might not be enough. On the headset, it is not sufficient as there is no indicator. | Website | [1.4.1 Use of Color](https://www.w3.org/WAI/WCAG22/Understanding/use-of-color) 2 | Consider making it clearer which links open a game, and which open another webpage. This can also help users with orientation and expectation of what will happen when they interact with the options. | Website | 2.4.4 Link Purpose 3.2.3 Consistent Navigation 3 | The links to the games also have no clear alternate title/description or text. Leaving users to wonder what it is that the open when the click on it. Consider adding something like a title element to the link for each game for a clearer description. | Website | 1.1.1 Non-text content 2.4.4 Link Purpose 1.3.1 Info and Relationships 4.1.2 Name, Role, Value 4 | In the intro, it is stated that compatibility for WebXR is shown by the green or red background. Color cannot be the only way to make something clear to every type of user. Consider adding a clearer way of showing this state. | [Website](https://git.benetou.fr/utopiah/biggu_s_gate/src/branch/main/pages/onboarding.html#L77) | 1.4.1 Use of Color 5 | Both on the website and with the pointer on the headset, it doesn’t seem possible to click the star rating select box for each game, as the link for opening the game seems to overlap and overwrite this. So when you click the star rating, the full game just opens. (With the keyboard, it is possible to reach these select boxes). | Website | 3.2.2 On Input 3.2.3 Consistent Navigation 3.2.1 On Focus 6 | There also seems to be an issue with the star ratings for some games, as some games can be rated, and some just have a list of the star options over the game. | [Website](https://git.benetou.fr/utopiah/biggu_s_gate/src/branch/main/pages/content.js#L87-L113) | 3.2.3 Consistent Navigation 7 | Some games seem to have a title or text, that overlays part of the thumbnail and is difficult to read. Consider creating a higher contrast or moving this text. | [Website](https://git.benetou.fr/utopiah/biggu_s_gate/src/branch/main/pages/content.js#L148-L195) | 1.4.3 Contrast (Minimum) 3.2.4 Consistent Identification 8 | When in an environment, the functions that you can use might not always be clear to every user. For example, we can understand that a certain function might make the sky blue or black. But not every user might. Consider changing the name of these “buttons”. | Game | 4.1.2 Name, Role, Value 1.3.3 Sensory Characteristics 9 | If you setup the audio recorder for feedback and deny access to the microphone. You still continue and can press the start button, but you cannot re-do that action to give permission for use of the microphone. Creating a possible deadlock. | [Game](https://git.benetou.fr/utopiah/biggu_s_gate/src/branch/main/pages/remixed_room.html#L321-L399) | 3.3.1 Error Identification 10 | There is no directly visible feedback when using the recording options to start/stop. There is of course the console within the game, but this might not be understandable for everyone and is not always directly in the viewport. Make sure users are alerted when they press buttons and perform actions like this. For example, a status message when recording has started or stopped. | [Game](https://git.benetou.fr/utopiah/biggu_s_gate/src/branch/main/pages/remixed_room.html#L321-L399) | 4.1.3 Status Messages 11 | Most buttons in the game also don’t offer clear feedback when you select them (any kind of “hover” or clear state that shows that if you pinch now, you will activate the option). Also, when performing the action, users have to spot the action (like the sky turning a different color) but aren't notified that they pressed the button and that the action was successful or unsuccessful. You get no feedback from choosing a specific button. Again, not taking into consideration that there is a log on the right, as this might not be readable for users and is not in viewport at all times. | Game | 4.1.3 Status Messages 3.2.1 On Focus 3.3.1 Error Identification 2.4.7 Focus Visible 12 | The instructions for a game are not always clear. The names of functions don’t help, as already discussed. But the fact that input options are different for left and right hand can also confuse users. As well as block users with hand/arm related disabilities from performing certain actions. These instructions are being shown within a game but can be missed by less experienced users. | Game | 2.5.1 Pointer Gestures 3.3.2 Labels or Instructions 13 | It is also not always clear which options you can drag or move, and with ones you can click. This is also being caused a bit by the names of the functions, but for example, every option has a blue circle on the left. But some do as well that can only be dragged or do nothing when pinching on them. Like “attributes”. | Game | 2.5.1 Pointer Gestures 1.3.3 Sensory Characteristics 3.3.2 Labels or Instructions 14 | It is pretty difficult to undo dragging or turning elements within a game. This can be increasingly difficult for texts that cannot be read upside down or turned in a weird way. Consider adding the possibility to undo or rollback specific actions. | Game | 2.5.2 Pointer Cancellation 15 | It might be unclear to users if there is a difference between green and red options within a game. If there even is a difference, of course. | Game | 1.4.1 Use of Color 3.3.2 Labels or Instructions 16 | The “123” buttons for the games can come across a bit unclear to users. From first impressions, it can seem like it is navigation for pages of games. But they all link to issues. Also, as they are so close together, it appears as though it is one button, but in fact, there are multiple. | Website | 3.2.3 Consistent Navigation 1.3.1 Info and Relationships 4.1.2 Name, Role, Value 17 | On the website, the button in the top left is not accessible with keyboard navigation. | Website | 2.1.1 Keyboard 18 | There is no title element present on the website, only smaller headers. Consider giving the website a proper structure, so users might have an easier understanding of the content when navigating through it. | Website | 2.4.2 Page Titled 2.4.6 Headings and Labels 19 | The select boxes on the website for ratings have no clear label or title for assistive technology like screen readers to give feedback to users about the purpose of the element. Consider adding this information. | Website | 4.1.2 Name, Role, Value

utopiah commented

2026-07-05 16:06:13 +00:00

Voting in XR for the current remix as the current player

Voting in XR for the current remix as the current player <img width="587" alt="image.png" src="attachments/210a0d60-902b-4a72-b429-ed9a1d680432">

image.png

202 KiB

utopiah commented

2026-07-06 13:15:07 +00:00

Scoring in XR with screenshots to facilitate selection

Scoring in XR with screenshots to facilitate selection <img width="581" alt="image.png" src="attachments/7e5703bd-ff2b-4dad-8313-b41c2b9e2bf0">

image.png

318 KiB