Announce tabledrag warning message to Assistive tech

Created on 10 May 2022, over 2 years ago
Updated 28 June 2024, 6 months ago

Problem/Motivation

The is a follow up to #1272990: Make tabledrag warning message show when row weights are enabled, and add WAI-ARIA live region β†’ which was committed to Drupal 8.0.

It was then re-opened in #1272990-22: Make tabledrag warning message show when row weights are enabled, and add WAI-ARIA live region β†’ to consider the use of Drupal.announce instead of role="alert". Refer to that comment and the following discussions for more information.

Steps to reproduce

Proposed resolution

Drupal announce is overkill as adding role="alert" to the element displaying accomplishes the same thing.

Remaining tasks

TBD

User interface changes

TBD

API changes

TBD

Data model changes

TBD

Release notes snippet

TBD

πŸ› Bug report
Status

Closed: works as designed

Version

11.0 πŸ”₯

Component
JavascriptΒ  β†’

Last updated 1 day ago

Created by

πŸ‡³πŸ‡ΏNew Zealand quietone

Live updates comments and jobs are added and updated live.
  • Accessibility

    It affects the ability of people with disabilities or special needs (such as blindness or color-blindness) to use Drupal.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡ΊπŸ‡ΈUnited States bnjmnm Ann Arbor, MI

    I previously tested all my Mac browsers with Voiceover (FF, Opera, Chrome, Safari), and I just tested Edge/Firefox/Chrome in Windows using Narrator/Jaws/NVDA. Adding the alert role functions identically to aria-live="assertive" (and thus works identically to Drupal.announce() set to assertive), so a role="alert" can be added to the element displaying the warning and it is accessible. Go ahead and change the role. It sounds like there were issues at some point with role="alert" when it was mentioned in that other issue in but as one would hope things improved in the decade that followed.

  • πŸ‡¨πŸ‡¦Canada mgifford Ottawa, Ontario

    Looks like an error identification error handling issue to me https://www.w3.org/WAI/WCAG21/Understanding/error-identification

  • Status changed to Needs work 6 months ago
  • πŸ‡³πŸ‡±Netherlands Lendude Amsterdam

    Thanks for the feedback, pretty clear on the next steps! Moving this to needs work.

  • πŸ‡¬πŸ‡§United Kingdom nlisgo

    @Lendude, since you marked this issue as postponed in #3 the only comment that possibly calls for any next steps are in #7. And the next steps are not clear to me, could you perhaps update the issue summary?

  • Status changed to Closed: works as designed 6 months ago
  • πŸ‡³πŸ‡±Netherlands Lendude Amsterdam

    @nlisgo ha! good point, I miss read/remembered what needed to be done here.

    So the conclusion in #6 was that role='alert' is fine, I thought the next step was to add that, but we already add that, so we don't need to do anything here, I think. So closing this. Please feel free to reopen this is you think there is still work that needs to be done here

  • πŸ‡¬πŸ‡§United Kingdom nlisgo

    @Lendude. Thanks for the quick followup. I was scratching my head on what the obvious next step was. I agree with outcome.

  • πŸ‡¬πŸ‡§United Kingdom nlisgo

    @mgifford I see you have tagged this issue wcag331 are you happy with this outcome?

Production build 0.71.5 2024