Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Using media browser version 2.10 and above with jquery_update (any versions above the default drupal version).
When trying to upload a file using only the keyboard the focus is trapped on the close button. Making it impossible to complete the task.
Comments
Comment #2
andrewmacpherson CreditAttribution: andrewmacpherson as a volunteer and at Annertech commentedI saw a similarly-named issue and wondered if they were duplicates (#2914241: Focus not confined to modal Media Browser - keyboard trap). They aren't, so updating both issues titles.
Comment #3
mgiffordComment #4
Chris Matthews CreditAttribution: Chris Matthews as a volunteer commentedRecent versions of media have resolved most of peoples concerns and is compatible with entity translation, multilingual and various advanced configurations. Due to the high volume of inactive and most often irrelevant issues we are Closing this as (outdated). If for whatever reason this issue is important to you AND you still have issues after checking the media recipe documentation, then let us know and we will review your concerns.
Otherwise, see the recipe documentation for how to configure media and for troubleshooting tips OR refer to the media_dev distribution if you want to see a working media setup.
As mentioned, feel free to make some noise in this issue if you still feel it is important to you or someone else.
Thanks,
Media team
Comment #5
andrewmacpherson CreditAttribution: andrewmacpherson as a volunteer and at Annertech commentedCan you please leave all the topic-related tags in place when marking something as outdated?
It looks like lots of open media issues are getting closed as outdated, in a big purge? That's understandable, if you need to make sense of a huge queue. Removing all the topic-related tags at the same time will make it very hard to locate old issues. The core accessiblility maintainers are using these tags to keep up to date on the state of accessibility across the whole core + contrib combined ecosystem. I expect people working on other topics do too.
Comment #6
andrewmacpherson CreditAttribution: andrewmacpherson as a volunteer and at Annertech commentedThis one is definitely worth checking again - it's at WCAG level A, and is one of the most severe barriers to accessiblility that can occur. Typically the only way out of this situation for a keyboard-only user is to ask someone else to operate your computer for you (undignified), or reboot your machine (risk of data loss).
If nothing has explicitly been done to address the bug (here, or in an upstream library), then it's very likely to still be an problem. It won't have been fixed by magic, and nor will it become irrelevant.
I'm tagging this one for my todo list, to check if it's still occurring.