Needs work
Project:
Drupal core
Version:
main
Component:
Olivero theme
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
26 Feb 2021 at 16:43 UTC
Updated:
20 Jan 2023 at 19:25 UTC
Jump to comment: Most recent, Most recent file

Comments
Comment #2
gauravvvv commentedHi @mherchel, Please write the steps to reproduce this issue. or Is this available on the live preview? https://tugboat-aqrmztryfqsezpvnghut1cszck2wwasr.tugboat.qa/
Comment #4
xjmThis actually sounds like a fairly serious accessibility issue to me. If there is no way to tell the control is disabled, that is very disorienting for the user.
Comment #5
xjmOops, never mind, I misunderstood the issue title. It is only the description that is lacking the styling.
However, I would still call this a normal accessibility bug because it is confusing in that the text seems disconnected from the form element.
Comment #6
kostyashupenkoComment #7
abhijith s commentedApplied path #6 and it works fine.The description text of form elements are faded out after applying this patch, which is similar to their input element.
Before patch:

After patch:

RTBC +1
Comment #11
andy-blumNeeds re-roll.
Comment #12
gauravvvv commentedRe-rolled the patch for Drupal10.1
Comment #13
gauravvvv commentedComment #14
deepalij commentedApplied patch #12 on Drupal 10.1.x-dev.
Patch applied cleanly.
The issue got fixed after applying the patch.
Screenshots are as per the #7
RTBC +1
Comment #15
Manoj Raj.R commentedApplied patch #12 on Drupal 10x
The description text of form elements are faded out after applying the patch.
RTBC +1
Comment #16
andy-blumI'm seeing the new styles apply, but they do not match the results of the screenshot in #7. I'm seeing the disabled input's label being colored with --color-gray-70, but the description with --color-gray-45.
Another thing I'm seeing that I'm not sure is an issue or not:
The code above will only add the 'is-disabled' class if the description already has an attributes object. If not, it just gets bypassed. Should we alter this portion of the code to create an attributes object if one does not already exist to make sure this class can be added if needed?
Comment #17
mgiffordThis is likely a WCAG SC 1.4.3 issue.
Longer discussion of disabled styles here https://github.com/w3c/wcag21/issues/805