Issue metadata
Sign in to add a comment
|
VoiceOver landmark menu announcing all text content for landmark elements with tabindex |
||||||||||||||||||||||
Issue descriptionChrome Version: 63.0.3235.0 (Official Build) canary (64-bit) OS: macOS Sierra 10.12.6 What steps will reproduce the problem? (1) Create a landmark element like <main> and give it a tabindex=-1 (2) (3) What is the expected result? The VoiceOver web rotor landmarks menu would report "main" What happens instead? The VoiceOver web rotor landmarks menu reads all of the content of the main element, and also says "main" Here is a sample Codepen to test: https://codepen.io/fstorr/full/pWbJjx/ In Safari with VoiceOver it will just say 'main', whereas Chrome is reading all of the content.
,
Oct 30 2017
I know why we do this. It turns out that if you do <div tabindex=-1>Foo</div> and focus it, VoiceOver gets really mad if it doesn't have an "interesting" role and doesn't have a name either. So we have a rule that we always get text from the descendants in that case. It sounds like we don't need that rule for role=main and probably some other roles too. Still, I'm not sure making <main> is good authoring. Can you explain the use case? If the goal is to move the user focus there programmatically, would using a url fragment work instead?
,
Oct 31
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by fst...@gmail.com
, Oct 18 2017