Ensure that when the Media Library disables media items so that they cannot be selected, that they are also disabled for screenreader access

Created on 29 September 2019, almost 5 years ago
Updated 30 January 2023, over 1 year ago


Problem/Motivation

When @cboyden's team did an assistive tech walkthrough of Media Library for #2834729: [META] Roadmap to stabilize Media Library β†’ using NVDA on Firefox, we discovered that, when making selections of items in the library, if you have met the max and remaining items are grayed out (disabled), a screenreader user is still able to select the disabled items, hearing them as "clickable".

This problem is only present if you are using a screenreader (tested with NVDA). This is not something that a mouse user will encounter because the disabled items cannot be clicked by the mouse to select. Keyboard-only users cannot select the items either.

This problem becomes especially confusing because the screenreader user is not given any kind of warning or alert that they have made selections beyond what is possible. Once they select more than the limit, the remaining items are no longer disabled and grayed out, so they might select an unlimited number. The system does not show an error message in the modal when more than the limit are selected.

After activating "Insert selected" button, the system announces "Added X media items," but the field is actually empty. If they go so far as to save the node, then it saves, but no media is added. The error that should have appeared on the modal displays on the node page, but is not announced.

This interaction can be viewed on the video recording of the September 29, 2019 walkthrough of Media Library starting at around minute 6:30 and continuing to minute 9:45..

Proposed resolution

TBD

Remaining tasks

  • Determine resolution and implement.

User interface changes

The way that the Media Library presents each selectable media item may need to be adjusted slightly so that the entire element, including the image and the checkbox, are only available through keyboard access as a single element.

API changes

None anticipated.

Data model changes

None anticipated.

Release notes snippet

TBD

πŸ› Bug report
Status

Needs work

Version

10.1 ✨

Component
MediaΒ  β†’

Last updated about 10 hours ago

Created by

πŸ‡ΊπŸ‡ΈUnited States rainbreaw

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.

  • Usability

    Makes Drupal easier to use. Preferred over UX, D7UX, etc.

  • Needs accessibility review

    Used to alert the accessibility topic maintainer(s) that an issue significantly affects (or has the potential to affect) the accessibility of Drupal, and their signoff is needed (see the governance policy draft for more information). Useful links: Drupal's accessibility standards, the Drupal Core accessibility gate.

  • Needs manual testing

    The change/bugfix cannot be fully demonstrated by automated testing, and thus requires manual testing in a variety of environments.

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.

  • The Needs Review Queue Bot β†’ tested this issue. It either no longer applies to Drupal core, or fails the Drupal core commit checks. Therefore, this issue status is now "Needs work".

    Apart from a re-roll or rebase, this issue may need more work to address feedback in the issue or MR comments. To progress an issue, incorporate this feedback as part of the process of updating the issue. This helps other contributors to know what is outstanding.

    Consult the Drupal Contributor Guide β†’ to find step-by-step guides for working with issues.

Production build 0.71.5 2024