You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
segedyjr opened this issue
May 9, 2016
· 2 comments
Labels
Abandonedrequested reports or updates are missing since more than 1 year, author or users are not available.p4https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority
If I make a simple modification to the tree and remove the tabindex property, the keyboard controls no longer work. See this modification: http://jsbin.com/conelahaxo/1/edit?html,output
My guess is that the treeitem needs to be focusable to work, and so spans and divs without tabindex set to -1 wouldn't get caught (MSHTML.py > _get_isFocusable).
The text was updated successfully, but these errors were encountered:
nvaccessAuto
added
the
p4
https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority
label
Jul 5, 2016
Support for IE has completely ended in 2022 and the browser is being automatically removed from machines that still have it after an Edge update in February 2023. I am closing this issue as abandoned since I don't expect further accessibility updates to IE or to IE mode in Edge.
Abandonedrequested reports or updates are missing since more than 1 year, author or users are not available.p4https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority
Tree controls implemented using aria-activedescendant do not work in IE11 unless the tabindex property is set on the tree nodes. Here's an example tree control that works: http://accessibleculture.org/research-files/aria-tree-views/treeviewD.html.
If I make a simple modification to the tree and remove the tabindex property, the keyboard controls no longer work. See this modification: http://jsbin.com/conelahaxo/1/edit?html,output
My guess is that the treeitem needs to be focusable to work, and so spans and divs without tabindex set to -1 wouldn't get caught (MSHTML.py > _get_isFocusable).
The text was updated successfully, but these errors were encountered: