Text on the front page is failing clolr contrast testing. Testing was conducted using the Color Contrast Analyzer plugin for Chrome.
Recipe page breadcrumbs a11y issue

Comments

jollysolutions created an issue. See original summary.

mgifford’s picture

This is important for backgrounds with CSS gradients & images.

bn_code’s picture

Assigned: Unassigned » bn_code
bn_code’s picture

Assigned: bn_code » Unassigned
shaal’s picture

Priority: Major » Normal
Issue summary: View changes
Status: Active » Needs work
Issue tags: -Accessibility +accessibility
StatusFileSize
new190.28 KB

I tested the pages for a11y issues (color contrast) using Firefox Nightly.
After 8.7.x already includes the darker background to hero text, the only 1 issue I found was the contrast Home link in the breadcrumbs.

andrewmacpherson’s picture

More infio please. Which text is it? What contrast does it report? the issue summary doesn't say. I'm reviewing this on a phone and I can't make out what's in the screenshot.

shaal’s picture

StatusFileSize
new25.38 KB

In /articles and /recipes pages,
Below the Umami logo there are breadcrumb links.
It also sits on top of background-color: #fbf5ee.

The Home link in the breadcrumbs has

color: #00836d /* rgb(0, 131, 109) */
font-size: 16px

Firefox A11y inspector shows Contrast: 4.34 with an exclamation mark.

Here's a close-up of the screenshot:

andrewmacpherson’s picture

Good catch. I think this slipped past us on other accessibility reviews. This foreground/background combination isn't used in many places.

#00836d text against white background - contrast 4.7:1 - pass.
#00836d text against #fbf5ee background - contrast 4.34:1 - fail.

So let's review where else the latter combination is seen:

  • breadcrumb text
  • "search help" link text on /search/node
  • Anywhere else...?

Note the contact form buttons use the green as a background colour, on a #fbf5ee page background. (This is fine, the ratio required for WCAG Non-text contrast is 3:1)

To fix this, it can be darkened. An good way to do this is to treat it as a HSV, and change the V component only.

Before:
#00836d - hsv(169,255,131)

After:
#008068 - hsv(169,255,128) - same hue and saturation

#008068 on #fbf5ee has contrast 4.52:1

I think we can change this colour everywhere it is used.

shaal’s picture

Status: Needs work » Needs review
StatusFileSize
new151.58 KB
new8.3 KB

I created a patch that change the colour #00836d to #008068.
It affects 3 CSS files, and 4 SVG icons.

Here's the result of Firefox Nightly a11y contrast testing tool (4.52:1 - passed!)
Umami with Firefox Nightly a11y contrast testing tool

andrewmacpherson’s picture

Title: Text failing contrast » Umami green link text fails WCAG contrast on peach background.

Clearer title, better for the commit log.

I dunno what we call this colour. Peach, salmon, or whatever.

Will review patch when I'm on a big computer.

andrewmacpherson’s picture

Good stuff, no instances of the old colour left. RTBC, assuming the designer/maintainer are OK with it.

This is how little difference it makes to keep the WCAG threshold gods happy: https://contrast-ratio.com/#%23008068-on-%2300836d

andrewmacpherson’s picture

Status: Needs review » Reviewed & tested by the community

Status: Reviewed & tested by the community » Needs work

The last submitted patch, 9: umami-darker-deep-sea-3001683-9.patch, failed testing. View results

andrewmacpherson’s picture

Status: Needs work » Reviewed & tested by the community

The test failure is unrelatrd to the changes in the patch. Lots of CSS patches are running into this bug in our test framework. #2990645: "Build Successful" is treated as a test failure.

kjay’s picture

From the design perspective, this looks good to me and is slight enough to make little difference to the design.

  • lauriii committed d4fa72e on 8.7.x
    Issue #3001683 by shaal, jollysolutions, andrewmacpherson, kjay: Umami...
lauriii’s picture

Status: Reviewed & tested by the community » Fixed

Thank you for the confirmation @kjay! Committed d4fa72e and pushed to 8.7.x. Thanks!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

andrewmacpherson’s picture

Issue tags: -accessibility (duplicate tag) +Accessibility

fixing accessibility tag