While editing a WYSIWYG field, when the user changes the selection within the “Text format” combo box, a “Change text format?” popup window appears and JAWS announces, “Continue button”. Instead, JAWS is expected to announce the popup window e.g., “Change text format? Dialog Changing the text format to … Continue button”.
Expected result: All dynamically appearing popup windows are expected to be announced by JAWS. In this instance, JAWS is expected to announce the popup window e.g., “Change text format? Dialog Changing the text format to … Continue button”.
Reference: Section 508, 1.3.1 - Information and Relationships.
For more information, visit: http://www.w3.org/TR/UNDERSTANDING-WCAG20/content-structure-separation-p...
Active
11.0 🔥
It affects the ability of people with disabilities or special needs (such as blindness or color-blindness) to use Drupal.
Involves an in-browser What-You-See-Is-What-You-Get content editor.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Ok, this is still an issue.
I can confirm that this definitely requires aria-live to alert users about the change on the UI.
@mgifford So all this needs is a Drupal.announce()? When? AFAICT:
Can you confirm that? Would be happy to write this code, should be easy 👍