Open aaronbnb opened 1 year ago
I can confirm the problem. However, it occurs only when navigating with the virtual cursor immediately after opening the page. If TAB is used to navigate within the alertdialog beforehand and then the virtual cursor is used, JAWS respects the boundaries of the alertdialog and does not output the rest of the page. So very strange behavior
Summary
When focus is set to within a dialog with
role="alertdialog"
, one is still able to navigate outside the dialog. The rest of page content is not hidden from JAWS.Expected result
Rest of page content is hidden from assistive technology IF focus is set within the dialog. Do not hide other page content unless focus is programmatically set to within the dialog. Some site developers don't hide dialogs properly so do not want to hide other page content unless it is certain that the site developer has intended that the user must interact with the alert dialog's content before interacting with main page content.
Actual result
All content outside the element with
role="alertdialog"
is exposed to JAWS.Example
Go to Shop Ford website On page load, focus is set to within the cookie consent dialog.
Additional Information
JAWS version and build number
JAWS 2023
Operating System and version
Windows 10
Browser and version:
Chrome 101.xx