- 🇨🇦Canada mgifford Ottawa, Ontario
This doesn't tie to status messages, but if the content isn't provided to the AT I'd put it under a failure of WCAG 4.1.2
https://www.w3.org/WAI/WCAG21/Understanding/name-role-value
Updated: Comment #1
The content translation settings UI is a really complex and, most of all, dynamic UI. Enabling a checkbox, for instance, can make a new table in a different place show up (e.g. enabling translation for a certain entity type) or simply make other table rows show up (e.g. enabling translation for a certain entity bundle make its field translation settings show up in the same table).. Vice-versa, disabling checkboxes make the same elements hidden to the user.
These are really dynamic changes and we should inform screen reader users about them, otherwise they will have a lot of troubles understanding how the UI works. Luckily, we have a Javascript utility that has been created exactly for this purpose: informing screen reader users of dynamic content changes. It is the Drupal.announce() → utility and the Content translation settings UI should leverage it whenever the UI changes dynamically.
TBD
Yes. Screenreader interface changes to announce parts that are live, when they change.
No.
Active
11.0 🔥
It affects the ability of people with disabilities or special needs (such as blindness or color-blindness) to use Drupal.
(Drupal 8 Multilingual Initiative) is the tag used by the multilingual initiative to mark core issues (and some contributed module issues). For versions other than Drupal 8, use the i18n (Internationalization) tag on issues which involve or affect multilingual / multinational support. That is preferred over Translation.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
This doesn't tie to status messages, but if the content isn't provided to the AT I'd put it under a failure of WCAG 4.1.2
https://www.w3.org/WAI/WCAG21/Understanding/name-role-value