Needs review
Project:
Drupal core
Version:
main
Component:
contextual.module
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
24 Sep 2020 at 14:37 UTC
Updated:
17 Aug 2026 at 02:45 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
bnjmnmThis adds+implements the theme function
Comment #3
bnjmnmComment #6
andrewmacpherson commentedI haven't really grokked the need for this yet, however...
This isn't true!
The contextual trigger text is just visually hidden, which means it's rendered on the page in a way that can be accessed with other kinds of assistive technology, and likely without using any assistive technology at all.
Look what happens when you say "configuration" to Android Speech Access. Here we see the homepage after installing Standard profile, logged-in as an administrator, with the "manage" toolbar tray open. There are 10 numbers visible on screen, which are controls whose name matches "configuration". One is the visible text in the toolbar tray, and there's a column of numbers running down the right-hand side; these are the visually-hidden contextual buttons for each block.
Also, there's no reason why a custom theme can't do away with either the visually-hidden class and/or the text indent. I can imagine either of these variations being useful...
<button type="button" class="trigger visually-hidden focusable">Configure<span class="visually-hidden"> toolbar block</span></button><button type="button" class="trigger">Edit<span class="visually-hidden"> toolbar block</span></button>Comment #7
andrewmacpherson commentedSo, we can ditch the comment about screen readers.
Comment #9
larowlanAll that remains here is to refactor the comment to remove mention of screen-readers
Comment #13
smustgrave commentedBelieve novice tag can remain but this issue should be considered fair game for anyone.
Comment #17
kieran.cottRemoved reference to screen-readers and implemented patch from #2 as an MR.
Comment #18
needs-review-queue-bot commentedThe Needs Review Queue Bot tested this issue. It fails the Drupal core commit checks. Therefore, this issue status is now "Needs work".
This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.
Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.
Comment #19
kieran.cottPipelines now pass.