Specify behavior when following a hidden subtree via aria-labelledby … by jaragu...
source link: https://github.com/w3c/accname/pull/150
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
…or -describedby.
This proposal tries to bring the spec closer to the actual behavior of the different user agents. In general, user agents expose hidden content when following an aria-labelledby or -describedby relation into a hidden subtree. There are differences between engines, though.
This is a summary of what user agents will need to change to comply with this text update:
- Firefox in generally compliant with the proposed wording, but it might need checking for special cases.
- Chrome would need to change the behavior for aria-hidden. Example:
Name for the input should be "hello", currently empty in Chrome.<style>.hidden {display:none;}</style> <input id="el1" role="button" aria-labelledby="el2" /> <span id="el2" class="hidden"> <span id="el3" aria-hidden="true">hello</span> </span>
- WebKit would need to unify behavior between different types of hidden, because it currently produces different names when using
display:none
andvisibility:hidden
. Example:
Name for the input should be "hello", currently empty in WebKit. It would be "hello" if<style>.hidden {visibility:hidden;}</style> <input id="el1" role="button" aria-labelledby="el2" /> <span id="el2" class="hidden"> <span id="el3" class="hidden">hello</span> </span>
display:none
was used instead.
Thanks in advance for your time and feedback.
Closes #57.
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK