See #15293 from the WPCampus accessibility audit. Although it specifically refers to notices in the media views, the base principle applies for all the notices / warnings and the like that appear in a page.
Previously: #9442 and #9425.
All notice / warning messages that appear on a page need to be exposed to assistive technologies.
They also need to be visible to screen magnification users if they appear outside their current view.
For the notices created via withNotices see #9442.
However, there are also other messages that appear on the page and need to be exposed wither with an alert role or via a speak() message.
For example, the warning for the Video "loop" setting added in #13550
Gutenberg should also make sure these messages are still visible at very high magnification levels.
Splitting this out from https://github.com/WordPress/gutenberg/issues/13550#issuecomment-491850649
See #15293 from the WPCampus accessibility audit. Although it specifically refers to notices in the media views, the base principle applies for all the notices / warnings and the like that appear in a page.
Previously: #9442 and #9425.
All notice / warning messages that appear on a page need to be exposed to assistive technologies.
They also need to be visible to screen magnification users if they appear outside their current view.
For the notices created via
withNotices
see #9442.However, there are also other messages that appear on the page and need to be exposed wither with an
alert
role or via aspeak()
message. For example, the warning for the Video "loop" setting added in #13550Gutenberg should also make sure these messages are still visible at very high magnification levels.