[BlinkOn17] Accessible name computation update
0 likes15 views
Jacobo Aragunde Pérez gave an update on accessible name computation at BlinkOn 17 in November 2022. He discussed landing new tests for the W3C spec, fixing bugs, and cleaning up Chrome's implementation. He also covered updates to the spec regarding how hidden content is handled in name computation. The spec was updated to clarify that if the current node is hidden and not directly referenced by aria attributes, the empty string should be returned.
![Name from hidden content
Spec version 1.1. “If the current node is hidden and is not directly referenced by
aria-labelledby or aria-describedby [...], return the empty string.”
Otherwise, continue name computation!
Update on accessible name computation
Jacobo Aragunde Pérez, BlinkOn 17 November 2022](https://image.slidesharecdn.com/blinkon17accessiblenamecomputationupdate-lightningtalk-221212161737-ad34224d/85/BlinkOn17-Accessible-name-computation-update-5-320.jpg)
![Update the spec
Discussion: https://github.com/w3c/accname/issues/57
Several proposals: reuse innerText property, hide/show aria-hidden…
Spec update: https://github.com/w3c/accname/pull/150
New text:“If the current node is hidden and is not part of an aria-labelledby or
aria-describedby traversal, where the node directly referenced by that relation was
hidden [...], return the empty string.”
…and lots of comments and examples.
Update on accessible name computation
Jacobo Aragunde Pérez, BlinkOn 17 November 2022](https://image.slidesharecdn.com/blinkon17accessiblenamecomputationupdate-lightningtalk-221212161737-ad34224d/85/BlinkOn17-Accessible-name-computation-update-7-320.jpg)
![[BlinkOn17] Accessible name computation update](https://image.slidesharecdn.com/blinkon17accessiblenamecomputationupdate-lightningtalk-221212161737-ad34224d/85/BlinkOn17-Accessible-name-computation-update-15-320.jpg)
[BlinkOn17] Accessible name computation update
- 1. Update on accessible name computation Jacobo Aragunde Pérez BlinkOn 17, November 2022
- 2. Accessible name and description computation W3C spec: https://www.w3.org/TR/accname-1.2/ “describes how user agents determine the names and descriptions of accessible objects from web content languages” Update on accessible name computation Jacobo Aragunde Pérez, BlinkOn 17 November 2022
- 3. Previously, on BlinkOn 15… Update on accessible name computation Jacobo Aragunde Pérez, BlinkOn 17 November 2022 land around 300 new tests file issues in the spec about corner cases and ambiguity fix bugs clean up implementation in Chrome
- 4. Name from hidden content Update on accessible name computation Jacobo Aragunde Pérez, BlinkOn 17 November 2022
- 5. Name from hidden content Spec version 1.1. “If the current node is hidden and is not directly referenced by aria-labelledby or aria-describedby [...], return the empty string.” Otherwise, continue name computation! Update on accessible name computation Jacobo Aragunde Pérez, BlinkOn 17 November 2022
- 6. Directly referenced? <input type=”text” aria-labelledby=”label”> <div id=”label” hidden>Directly referenced <span>Not directly referenced</span> </div> Expected name: “Directly referenced” Actual name: “Directly referenced Not directly referenced” Update on accessible name computation Jacobo Aragunde Pérez, BlinkOn 17 November 2022
- 7. Update the spec Discussion: https://github.com/w3c/accname/issues/57 Several proposals: reuse innerText property, hide/show aria-hidden… Spec update: https://github.com/w3c/accname/pull/150 New text:“If the current node is hidden and is not part of an aria-labelledby or aria-describedby traversal, where the node directly referenced by that relation was hidden [...], return the empty string.” …and lots of comments and examples. Update on accessible name computation Jacobo Aragunde Pérez, BlinkOn 17 November 2022
- 8. To know more Blog post: https://blogs.igalia.com/jaragunde/2022/10/accessible-name-computation-in-chromi um-chapter-i-introduction Update on accessible name computation Jacobo Aragunde Pérez, BlinkOn 17 November 2022
- 9. “There are only two hard things in Computer Science: cache invalidation and naming things.” Phil Karlton Update on accessible name computation Jacobo Aragunde Pérez, BlinkOn 17 November 2022
- 10. Directly referenced? <input type=”text” aria-labelledby=”label”> <div id=”label” style=”visibility:hidden”>Directly referenced <span>Not directly referenced</span> </div> Chrome and Firefox: “Directly referenced Not directly referenced” WebKit: “Directly referenced” Slide Deck Title Presenter(s), Presentation Date
- 11. Update on accessible name computation Jacobo Aragunde Pérez, BlinkOn17 November 2022
- 12. Update on accessible name computation Jacobo Aragunde Pérez, BlinkOn17 November 2022 button, name: close heading, name: find and replace text entry, name: replace with text entry, name: find
- 13. .tooltip { visibility: hidden; border: 1px solid; position: relative; right: 20px; bottom: -20px; background: yellow; } div:hover .tooltip { visibility: visible; } Slide Deck Title Presenter(s), Presentation Date <div>Hover over me <span class="tooltip">Tooltip text</span> </div>
- 14. Thank you! Update on accessible name computation Jacobo Aragunde Pérez, BlinkOn17 November 2022