Open kabsas opened 9 months ago
@kabsas Why is this a problem? It's down to the screen reader software to decide when it announces regions, it announces the dialog, then the focused element.
further discussion needed, and further test creation needed
@stevefaulkner - A navigation landmark should be announced when you enter the region. The problem is the navigation region is not announced when it is in a dialog as described in the summary. This is not an issue when the landmark is not in a dialog. We have come across several bugs in dialogs, such as https://github.com/FreedomScientific/standards-support/issues/706, that are quite problematic for our applications that contain complex content in dialogs.
@BrettLewisVispero thinks it should be working, will review
Imported into ADO as bug 79583
Summary
JAWS does not announce the navigation region in dialog. This happens in Chrome and Edge with the virtual cursor off. However, with the VPC on, the navigation region is not announced when the dialog opens if the focused element is in the region, it is only announced when you navigate away from the region then back to it. In Firefox, the navigation region is not announced with VPC off and VPC on.
Steps to reproduce:
Expected result
When the dialog opens the navigation region around the Home and About links is announced.
Actual result
When the dialog opens the navigation region is not announced.
JAWS version and build number
2023.2302.15
Operating System and version
Windows 10 Enterprise 19045.3324
Browser and version:
Chrome 116 Edge 116 Firefox 117