508 Compliance Issue - Dynamic Appearing Message

All dynamically appearing messages are expected to be announced by JAWS automatically.

Example 1: "Within the “Insert Image” window when the user selects the “Save” button without filling in the required fields, an error message appears, “Image field is required. Alternative text is required. (Only in rare cases should this be left empty. To create empty alternative text, enter “ “ – two double quotes without any content)” and JAWS announces the dynamic message incorrectly as “Image browse…Alternative text short description for the visually impaired Align None Left Center Right Save Save button”.

Expected result: All dynamically appearing messages are expected to be announced correctly by JAWS. In this instance JAWS is expected to announce, “Image field is required. Alternative text is required. (Only in rare cases should this be left empty. To create empty alternative text, enter “ “ – two double quotes without any content)”.

Example 2: When updating configurations from the Swift Mailer module, within the “Transport settings” screen, when the “Save configuration” button is selected, the dynamic message “Drupal has been configured to send all e-mails using the PHP transport type” appears and is not announced by JAWS automatically. When the message appears JAWS announces, “Save configuration”. Instead, JAWS is expected to announce “Drupal has been configured to send all e-mails using the PHP transport type”.

Expected result: All dynamically appearing messages are expected to be announced by JAWS automatically. JAWS is expected to announce as “Drupal has been configured to send all e-mails using the PHP transport types”.

Notes:
• This defect may exist elsewhere within the application.
• The defect exists in IE 11 and Google Chrome (latest versions)
Reference: Section 508, Part 1194.22, Paragraph (n).