Closed (fixed)
Project:
Drupal core
Version:
8.7.x-dev
Component:
layout_builder.module
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
20 Nov 2018 at 09:21 UTC
Updated:
6 Dec 2018 at 15:04 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
andrewmacpherson commentedComment #3
tedbowPatch. Followed instructions in #3013770: Distinguish between the repeated text of buttons in Layout Builder UI
Comment #5
tedbow#4 was unrelated failure. Passed on retest.
Comment #6
andrewmacpherson commentedWe don't need the
span.visually-hiddenhere for the section number, because the entire text "remove section" is already visually hidden by.layout-section .remove-section { text-indent: -9999px; }.Comment #7
tim.plunkettThat's a design choice which could always change. Unless there's a problem from those two conflicting, I'd rather be clear about which part should always be visually hidden vs the whole thing happening to be hidden for now.
Comment #8
tedbowAlso a front-end theme could choose to show the labels
Comment #9
andrewmacpherson commentedThere isn't a conflict, it's just overkill to hide something, then hide it again. I thought this was excess code that could do with being tidied up. Patch #3 is safe. Happy to say RTBC.
Are we planning to change it? A visible text label has several benefits over an icon only, but we can do that in a follow-up.
The problem addressed in this issue is: make the purpose clear to screen reader users who don't perceive the visual/spatial relationship of the button to the section.
Ah, now there's a misconception. Basically, that's framing it the wrong way around. There's no part of the accessible name which "should always" be visually hidden. Anyone can benefit from the whole name.
Visually hidden text is a common accessibility practice, but it's not a desirable thing in it's own right. Rather, it's an awkward compromise to meet the needs of screen reader users, while aiming for brevity in the visual UI design. Done badly, it can make things worse for speech control users, and it can somtimes pose challenges for translators too. If you can satisfy the needs of screen reader users without resorting to visually hidden text, so much the better.
Comment #10
alexpottCommitted and pushed 23d304ffd8 to 8.7.x and 83dfb0a02c to 8.6.x. Thanks!
This feels like an accessibility bug rather than a task.