This example was recently added to the Element with aria-hidden has no focusable content rule:
https://act-rules.github.io/rules/6cfa84#failed-example-5
<div aria-hidden="true">
<button tabindex="-1">Some button</button>
</div>
I didn't realise this when it went in, but looking at implementing this I can't quite figure out why this would fail SC 4.1.2. This is not a button in any sort of meaningful way. The only way I can see to get to it is with VoiceOver in reading mode. But it then announces the text node, not the button. It's explicitly called "some button text".
I think the expectation needs to be adjusted to only apply to elements in sequential focus navigation that do not redirect focus.
This example was recently added to the
Element with aria-hidden has no focusable contentrule:https://act-rules.github.io/rules/6cfa84#failed-example-5
I didn't realise this when it went in, but looking at implementing this I can't quite figure out why this would fail SC 4.1.2. This is not a button in any sort of meaningful way. The only way I can see to get to it is with VoiceOver in reading mode. But it then announces the text node, not the button. It's explicitly called "some button text".
I think the expectation needs to be adjusted to only apply to elements in sequential focus navigation that do not redirect focus.