174667 2017-07-19 21:58:37 -0700 When aria-modal is set to true VoiceOver does not read the static content in the popupAX: 2023-06-09 13:07:20 -0700 1 1 1 Unclassified WebKit Accessibility WebKit Nightly Build iPhone / iPad iOS 10.3 NEW InRadar P1 Critical --- 1 mohith.ckm49 webkit-unassigned achintamkarmakar alilikoi ap bailhard bell621iran Carolyn_MacLeod catt.communications cfleizach finleyreo graham.armfield henryjonesuk147 jcraig klh marvelson ntim pamijiv595 simon.fraser stephen vovep92957 webkit-bug-importer whiteadam102 wohay98163 oldest_to_newest 1330550 0 mohith.ckm49 2017-07-19 21:58:37 -0700 When aria-modal=”true” the static content in the modal popup / dialog is not read by the VoiceOver at all. This causes the following issues: 1. If there is any static text running more than a line user cannot read and understand. We can make it announce with aria-describedby but users cannot check the spelling, punctuation, etc. 2. Error messages displayed next to the form control are no longer read by the VO while correcting the mistakes. If the aria-modal property is removed from the popup, the static text and the error messages displayed next to the form controls are properly read by VoiceOver. However removing the aria-modal makes the VoiceOver read the content out of the popup which is a frustrating user experience. 1330551 1 webkit-bug-importer 2017-07-19 21:58:56 -0700 <rdar://problem/33420351> 1606170 14 jcraig 2020-01-13 17:48:14 -0800 So that we're all on the same page, are you able to attach a reduced test case? I could create one, but I'd be making some assumptions about what you intend. For example, some people use "popup" to mean fly out menus similar to html:select. Others use "popup" to mean contextual dialogs similar to what is called a "popover" on iOS. 1649660 15 catt.communications 2020-05-06 09:29:45 -0700 (In reply to James Craig from comment #14) > So that we're all on the same page, are you able to attach a reduced test > case? I could create one, but I'd be making some assumptions about what you > intend. For example, some people use "popup" to mean fly out menus similar > to html:select. Others use "popup" to mean contextual dialogs similar to > what is called a "popover" on iOS. This refers to dialogs, not selects. More info is available here: https://developer.paciellogroup.com/blog/2018/06/the-current-state-of-modal-dialog-accessibility/ And you should be able to reproduce this issue with the sample dialog here: https://www.w3.org/TR/wai-aria-practices-1.1/examples/dialog-modal/dialog.html 1649663 16 catt.communications 2020-05-06 09:32:19 -0700 PS: note that this issue has been reported to exist on both MacOS and iOS. 1790692 17 klh 2021-09-06 06:48:44 -0700 I can confirm that this is broken across osx and iOS, reduced testcase here: https://codepen.io/pen?&editors=100&prefill_data_id=ed12545a-9bee-4190-87c2-1ce003ae34e8 virtual cursor cannot move past the headline (you can kinda get there by trying to move up and outside, with single words and the arrow key navigate upwards however this wasn't the intention) - you should disable this implementation in future releases until the behaviour is fixed, Current best practice is to add both aria-modal="true" and aria-role="dialog" (for future compatibility) however the buggy implementation actually renders the modal unreadable by screenreader... I'd consider this a high priority for a11y 1960765 18 alilikoi 2023-06-09 09:31:45 -0700 Any updates on this issue? It is a huge blocker for making dialogs fully accessible.