bug(MatMenu): With NVDA enabled, keyboard focus doesn't show up #21947
Labels
Accessibility
This issue is related to accessibility (a11y)
area: material/menu
G
This is is related to a Google internal issue
P2
The issue is important to a large percentage of users, with a workaround
Comments
jelbourn
added
Accessibility
|
@calebegg I just tried this with NVDA 2020.3 and Firefox 85 and I don't see any difference between the focus treatment with and without NVDA enabled. Could have been an issue with an older browser + screen-reader combination? |
|
Still repros consistently for me with those versions (2020.3 and 85.0.2). My specific repro steps
I have video if it would help? Github won't let me upload it here. |
|
I just tried it with NVDA + Firefox and I wasn't able to reproduce it either. |
|
Could I trouble one of you for a video call to see if we can figure out what we're doing differently then? Our a11y tester and I are having trouble with this and it's going to block a launch if I can't figure it out. |
|
Sure, are you on the Angular Slack? |
|
Yep. I'm calebegg on there too. |
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
Feb 23, 2021
We currently have handling for the case where a `mousedown` event is thrown off by a fake `mousedown` listener that may be dispatched by a screen reader when an element is activated. It turns out that if the device has touch support, screen readers may dispatch a fake `touchstart` event instead of a fake `mousedown`. These changes add another utility function that allows us to distinguish the fake events and fix some issues where keyboard focus wasn't being shown because of the fake `touchstart` events. Fixes angular#21947.
crisbeto
added
has pr
P2
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
Feb 23, 2021
We currently have handling for the case where a `mousedown` event is thrown off by a fake `mousedown` listener that may be dispatched by a screen reader when an element is activated. It turns out that if the device has touch support, screen readers may dispatch a fake `touchstart` event instead of a fake `mousedown`. These changes add another utility function that allows us to distinguish the fake events and fix some issues where keyboard focus wasn't being shown because of the fake `touchstart` events. Fixes angular#21947.
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
Feb 23, 2021
We currently have handling for the case where a `mousedown` event is thrown off by a fake `mousedown` listener that may be dispatched by a screen reader when an element is activated. It turns out that if the device has touch support, screen readers may dispatch a fake `touchstart` event instead of a fake `mousedown`. These changes add another utility function that allows us to distinguish the fake events and fix some issues where keyboard focus wasn't being shown because of the fake `touchstart` events. Fixes angular#21947.
andrewseguin
pushed a commit
that referenced
this issue
Feb 25, 2021
) We currently have handling for the case where a `mousedown` event is thrown off by a fake `mousedown` listener that may be dispatched by a screen reader when an element is activated. It turns out that if the device has touch support, screen readers may dispatch a fake `touchstart` event instead of a fake `mousedown`. These changes add another utility function that allows us to distinguish the fake events and fix some issues where keyboard focus wasn't being shown because of the fake `touchstart` events. Fixes #21947.
andrewseguin
pushed a commit
that referenced
this issue
Feb 25, 2021
) We currently have handling for the case where a `mousedown` event is thrown off by a fake `mousedown` listener that may be dispatched by a screen reader when an element is activated. It turns out that if the device has touch support, screen readers may dispatch a fake `touchstart` event instead of a fake `mousedown`. These changes add another utility function that allows us to distinguish the fake events and fix some issues where keyboard focus wasn't being shown because of the fake `touchstart` events. Fixes #21947. (cherry picked from commit c7edf03)
This was referenced Mar 6, 2021
This was referenced Mar 18, 2021
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Repros on https://material.angular.io/components/menu/overview
Everything works fine when NVDA is disabled
Environment: NVDA version - 2019.2.1 - Firefox Version 83.0 - Windows 10 Enterprise (64-bit)
The text was updated successfully, but these errors were encountered: