Closed (fixed)
Project:
Advanced Content Feedback (aka admin_feedback)
Version:
8.x-2.6
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
11 Sep 2024 at 09:12 UTC
Updated:
17 Feb 2025 at 15:44 UTC
Jump to comment: Most recent
Comments
Comment #2
tgoeg commentedComment #3
bserem commentedComment #4
gkffzs commentedComment #6
gkffzs commentedComment #7
tgoeg commentedLooks good to me, perfect!
You chose "visually-hidden" and it seems to work well on a bootstrap-based theme. I wonder if this is universally applicable to all templates? It seems to be inherited from the "stable" theme in my case. I am not 100% we can rely on this to exist anywhere?
Comment #9
bserem commentedMerging following the "looks perfect" review. Thanks both of you.
Should the need arise for further improvements we can open a new issue in the future.
Comment #10
briangon commentedWhy not just remove the label element entirely and use an aria-label on the button?
That's how I've got it patched. If you go that route I won't need to patch it anymore.
The label markup appears replicated when rendering, which might be another issue that this solves too.
Comment #11
tgoeg commentedI am not an a11y pro - my initial description stems from an a11y certification authority that suggested to solve it that way.
https://stackoverflow.com/questions/22039910/what-is-aria-label-and-how-... mentions bad support for aria-label. The referenced page seems quite dated. Do you know whether things have changed to the better in the meantime?
The description of `aria-label` indeed seems to fit better than adding a label that has to be hidden anyway.