question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Department colours are not always accessible

See original GitHub issue

Several department colours do not have sufficient contrast, and are being used for text.

Example: Defra org page

Departments with issues:

  • DEFRA
  • HMRC
  • Any child orgs that inherit Defra or HMRC colours.

Note I think there’s several issues:

  • All departments should have a contrast-safe or text-contrast-safe colour.
  • All departments should use these colours for text.
  • We currently have web-safe colour variants to mean contrast safe, but this does not communicate the purpose of the variant, and has led to some being deleted - such as #249. Web-safe means something different.

Update: The issue with web-safe is that it has a specific meaning. It’s also been used to refer to a hex version of another named colour. Such as when an org has a Pantone colour as their brand colour, and a ‘web version’ for internet use.

For our use, all the hex colours can be used on the web, but only some will have suitable contrast for text.

We must meet WCAG 2.0 AA, which requires a contrast against the background of 4.5:1 or greater.

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Comments:23 (22 by maintainers)

github_iconTop GitHub Comments

1reaction
voxpellicommented, Jan 17, 2017

@fofr You need to add a new loadPathin the grunt-contrib-sass settings: https://github.com/alphagov/govuk_frontend_toolkit/blob/ef06147803755152f8796c57e4493cd5c1f933a6/Gruntfile.js#L49

Adding eg. ./node_modules should make the sass-color-helpers file load if you remove the node_modules prefix from their paths.

Also: I just released a new patch version that fixes https://github.com/voxpelli/sass-color-helpers/issues/5, so a good idea to upgrade to version 2.0.3.

1reaction
NickColleycommented, Jan 13, 2017

@accessiblewebuk definitely worth making a note in the implementation that we’re testing against the background colour due to how we’re currently using the department colours (which as far as I know is always against our background color)

Read more comments on GitHub >

github_iconTop Results From Across the Web

Here's What You Need to Know About Color Accessibility in ...
Color accessibility is important because it enables people with visual impairments or color vision deficiencies to interact with digital ...
Read more >
Accessibility: Don't use color alone to convey content
Non-visual and visual users who cannot access color must be taken into account when using color to emphasize elements. Information conveyed with ...
Read more >
Accessible Color Best Practices | UCSF IT
Making colors accessible means color combinations with enough contrast so the content is clearly distinguishable from the surrounding page.
Read more >
Color and contrast accessibility - web.dev
The WebAIM checklist states in section 1.4.1 that "color should not be used as the sole method of conveying content or distinguishing visual ......
Read more >
Color accessibility: tools and resources to help you design ...
All the tools, tips and resources your need to build and check the color accessibility and color constrast of digital products!
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found