Affects Version/s: 3.0.6
Fix Version/s: 3.0.15
Sprint:UI - 2022-8, UI - 2022-9, UI COOLDOWN - 2022-08
Related to WCAG 2.1 level AA criteria 4.1.3: status messages
Status message is not automatically announced by the screen reader.
- "Some of the assets could not be uploaded. Assets cannot be created without properties. Hitting "Create" or "Add properties" will ignore failed assets." error message in the "Import" tab that appears upon activating the "Create" button without providing properties to the attached files
Recommendation to fix
Status messages MUST be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus.
HOW TO FIX:
Fix this issue by using ONE of the following techniques:
1. Set focus to the interstitial message: https://dequeuniversity.com/class/dynamic-updates2/notify-users/move-focus
2. Announce the interstitial message via an ARIA live region: https://dequeuniversity.com/class/dynamic-updates2/notify-users/aria-live
Deque University: https://dequeuniversity.com/class/dynamic-updates2/ajax/interstitial
WCAG Understanding document: https://www.w3.org/WAI/WCAG21/Understanding/status-messages
When the user requests an action that will take a long time to complete, such as searching for airline tickets, it is common to present an interstitial or intermediate page to users as a way to confirm that the link worked, and that the results are coming if they wait. Screen reader and other assistive technology users need that same kind of confirmation. Moving focus to the interstitial message benefits both screen reader users and screen magnification users.
ELEMENTS-1538 Make suggestion loading / no results found information announced by the screen reader