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.As a mildly colorblind person the available updates page provided by the update module is really annoyingly low contrast.
There isn't enough contrast in the background-colors of .color-success and .color-warning that are used to indicate wether a module should be updated or not. It's probably because Seven wants a light, pastel kind of color pallet but just a tiny bump in contrast would make a huge difference.
/**
* Reusable colors.
*/
.color-success {
color: #325e1c;
background-color: #f3faef;
}
.color-warning {
color: #734c00;
background-color: #fdf8ed;
}
.color-error {
color: #a51b00;
background-color: #fcf4f2;
}I suggest that the least drastic change would be to make .color-warning a bit darker. For instance #fbeed3 instead of #fdf8ed.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | patch.diff | 427 bytes | JanLaureys |
| Screenshot 2016-07-06 14.51.27.png | 173.36 KB | JanLaureys | |
| Screenshot 2016-07-06 14.50.10.png | 173.75 KB | JanLaureys | |
Comments
Comment #2
JanLaureys CreditAttribution: JanLaureys commentedAttached a patch for the color change.
Comment #3
cilefen CreditAttribution: cilefen commentedComment #4
cilefen CreditAttribution: cilefen commentedI do not know the Drupal standards but there are some online verifications.
Comment #5
JanLaureys CreditAttribution: JanLaureys commentedComment #6
Bojhan CreditAttribution: Bojhan as a volunteer and commentedThese are ornamental colours. We use images to explain the errors. Making these match contrast guidelines is not required by WCAG 2.0 AA, therefore we do not comply. This is an intentional design choice.
Comment #7
mgiffordSorry Bojhan, where does it say that "ornamental colours" are excluded from WCAG?
https://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contras...
We're talking about the color of the foreground text & background, right?
Comment #8
Bojhan CreditAttribution: Bojhan as a volunteer and commentedAh, my bad. The design used here is pretty poor - sadly :( We actually have a redesign issue.
Comment #9
mgiffordCool. What's the issue number?
Comment #10
mgiffordComment #13
andrewmacpherson CreditAttribution: andrewmacpherson as a volunteer and at Annertech commentedTag clean up: "accessibility" is the preferred one. The "a11y" tag doesn't have many issues so I'm moving them all to "accessibility".
Comment #14
wturrell CreditAttribution: wturrell as a volunteer commentedUsing the WebAIM checker cilefen mentioned:
Current:
#734c00 on #fdf8ed
passes WCAG AA and AAA normal and large text.
Proposed:
#734c00 on #fbeed3
fails WCAG AAA normal size.
Also the Issue Summary mentions both .color-success and .color-warning, but the patch only includes the latter.
Comment #15
mgiffordIt looks like we are getting a request for AAA contrast on this vs AA. @JanLaureys am I missing something?
.color-warning #325e1c on #f3faef is OK.
.color-warning #734c00 on #fdf8ed is OK.
.color-error #a51b00 on #fcf4f2 is OK.
Btw, I love that http://contrast-finder.tanaguru.com gives suggestions if it doesn't meet the required contrast.
Comment #16
Bojhan CreditAttribution: Bojhan as a volunteer and commentedWe have AA contrast compliance across core.
Comment #17
mgifford@Bojhan agreed. AAA is always nice, but not required. I might be missing something, but marking this as postponed for now.
Comment #22
pameeela CreditAttribution: pameeela commentedThanks for reporting this issue. We rely on issue reports like this one to resolve bugs and improve Drupal core.
As part of the Bug Smash Initiative, we are triaging issues that are marked "Postponed (maintainer needs more info)". Given that, as noted previously, the page meets AA standards, this is in line with the official Drupal accessibility policy so I am going to mark it Closed (works as designed).
I think that raising the topic of meeting AAA standards would be a feature request and would require discussion and consideration.