Filed issue monorail:2635 for the bug wizard missing Blink>Accessibility.  Thanks!

Tested the issue on Mac 10.12.4 using chrome latest stable version #58.0.3029.110.

Following are the steps followed to reproduce the issue.
------------
1. Added chromevox extension to chrome.
2. Opened the attached ariamodel.html file.
3. Clicked all the 3 buttons and also navigated out of the modal.
4. Observed that the chromevox spelled sentences as in the dialog box.

Attaching screen cast for reference.

Reporter@ - Could you please verify the screencast and please let us know if anything missed from our side. If possible please provide an expected behaviour screen cast explaining about the issue.

Thanks...!!

Deleted: 716592.mp4 3.6 MB

	716592.mp4 3.6 MB View Download

According to the spec:

> The aria-modal attribute is used to indicate that the presence of a "modal" element precludes usage of other content on the page.

When a modal is open, user *should not* be able to interact with content outside of the modal using assistive softwares.

From your screencast it looks like aria-modal is not supported at all with ChromeVox. 

As mentioned, I tested with VoiceOver on Mac. See the attached screencast.

- I navigated solely with VoiceOver keys.

- Expected behavior: when I open the first modal, I was not able to navigate out of the modal to focus on the buttons. When I attempted to navigate out, my focus stayed on "aria-modal works here" and "Close button", and there's an error sound effect.

- Unexpected behavior: when I open the second and third modal, I was able to navigate out of the modal, onto the buttons before modal and the text box after the modal.

---

I also attached another screencast to show that all 3 modals work in Safari.

Deleted: ariamodal.mov 12.8 MB

ariamodal.mov 12.8 MB Download

Deleted: ariamodal-safari.mov 7.8 MB

ariamodal-safari.mov 7.8 MB Download

Thank you for providing more feedback. Adding requester "krajshree@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Tested this issue using latest chrome #58.0.3029.110 on Mac as per the steps mentioned in comment #0

@muanchiou: Could you please find the attached screen cast and let us know that's the you're facing?

It would help us for further triaging of the issue.

Thanks,

Deleted: May 12 2017 12-09 PM.webm 1.2 MB

	May 12 2017 12-09 PM.webm 1.2 MB View Download

> @muanchiou: Could you please find the attached screen cast and let us know that's the you're facing?

Unfortunately no. From the screencast it looks like you might be navigating with tab keys? It is not supposed to work. 

To reproduce the issue, navigate using solely with VoiceOver keys — control + option + left arrow/right arrow.

Thank you for providing more feedback. Adding requester "sandeepkumars@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Please find the below attached screen cast and let us know the behavior, is the same issue you're facing?

If possible please share a expected screen cast and try upgrading your Chrome to the latest version and check if you still face the issue?

Thanks,

Deleted: May 29 2017 4-55 PM.webm 2.5 MB

	May 29 2017 4-55 PM.webm 2.5 MB View Download

Thanks @sandeepkumars, yes that screen cast shows that Chrome is not working correctly. As mentioned in the original bug report, if you try the same page in Safari it behaves correctly, so this is definitely our bug.

No more information is needed here. Thanks me@muanchiou.com for the bug report.

The label actually has little bearing on this; it's actually just it ensures the dialog is treated as a group by VO. We need to implement aria-modal properly on Mac as specced (and as previously discussed on https://codereview.chromium.org/2684543002).

Any ETA for this? Looks like no movement in quite a while.

I just tried out the attached file in the latest stable version of Safari with VoiceOver and Safari/VoiceOver seems pretty broken to me. By pressing "Stop interacting with" I can land on the dialog itself and then use linear navigation to reach the rest of the page. Visually it shows me highlighting other content in the page, but VoiceOver doesn't actually read it.

I also tried this example, same issue:

https://www.w3.org/TR/2017/NOTE-wai-aria-practices-1.1-20171214/examples/dialog-modal/dialog.html

Can anyone else confirm this behavior?

If so, it seems like Safari/VoiceOver has pretty poor support for aria-modal and I'm not sure if we want to try to copy Safari's support.

+1 to just making aria-modal work and ignoring how Safari works (or doesn't).

Interestingly, Safari keeps my VoiceOver focus from navigating outside at all in the attached HTML file, but not in the example you linked to, so it definitely has something broken there.

Deleted: alertdialog-modal.html 5.0 KB

alertdialog-modal.html 5.0 KB View Download

Any other information I can provide to help move this along?

Any other information I can provide to help move this along?

Chrome: 69.0.3497.81 (Official build) (64-bit)
Chrome: 71.0.3548.0 (Official build) Canary (64-bit)
MacOS:  10.13.3

I can stop interacting with the modal and activate another modal while the first modal is still open.

In Safari, I am restricted to the first modal until closed.

We should check in Mojave and see if there are updates to Safari+VoiceOver's support of aria-modal.