New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Certain nesting of ARIA attributes causes NVDA to ignore active elements in the tab order in IE #3571
Comments
Comment 1 by mdcurran on 2013-10-18 02:00 |
Comment 2 by bgaraventa on 2013-10-18 18:08 In the case of the date picker though, using IE10, the simulated links are actually rendered, even though Applications Mode is not activated as expected. This is likely just a querk, that hopefully doesn't crop up anywhere else. I wished to file the bug so you guys would be aware of it in case this happens in other places too. Likely very low priority though. |
Comment 3 by jteh on 2013-10-22 23:05 |
@bgaraventa I am not sure if I can reproduce this issue in IE11. I am testing with NVDA las Alpha and am getting following error. As you can see, I could tab to the link and then to "show options" and the focus didn't got stuck on that region. But I am not sure if there are things ignored. Can you reproduce this issue with last NVDA Alpha?
|
Hm unfortunately the initial author is not on Github anymore. Can anyone reproduce it? |
I am closing this one as abandoned. We cannot reach to the initial author and the case is very corner. Actually I don't know exactly what is expected here. Testing with NVDA 2019.1.1, NVDA reads the dialog and application role when tabbing in focus mode in IE11. If someone has further thoughts on this, please comment on it and we can reopen it. Thanks. |
Reported by bgaraventa on 2013-10-10 20:45
It appears that, when certain ARIA attributes are nested, such as role=dialog and role=application, NVDA cannot read active elements in the tab order when viewed in IE, though it does work correctly in FF.
Here is an example:
When you attempt to press Tab to set focus to the "Test Link", it does work correctly in FF and reads both the role and state accurately.
However if you try the same in IE, it causes a dead tab stop and appears to get stuck so you can't tab past it.
I understand that this is a corner case, but the active element shouldn't be entirely invisible in the tab order regardless.
The text was updated successfully, but these errors were encountered: