Consider focusables with tabindex="-1" to be unreachable #43
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Consider focusables with
tabindex="-1"
to be unreachableDescription
Updates LRUD to ignore focusables with
tabindex="-1"
, but still focus any focusable elements within any parent withtabindex="-1"
.Motivation and Context
Elements with a
tabindex
of-1
should only be focusable programatically and not be part of the navigational flow of the document. This is in-line with behaviour of tabbing order in a standard HTML document. See https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/tabindexThe primary driver for this change is the existence of devices which only announce
aria-live
regions if they have atabindex
, but these regions should not be focusable.How Has This Been Tested?
New
unreachable.html
layout created in tests and tests written.Manual testing with this layout.
Checklist: