- From: Hidde de Vries <hidde@w3.org>
- Date: Sun, 17 Oct 2021 23:58:18 +0200
- To: John Foliot <john@foliot.ca>
- Cc: "Patrick H. Lauke" <redux@splintered.co.uk>, WCAG <w3c-wai-gl@w3.org>
- Message-Id: <274B1EE7-467A-4A2F-B656-CD350B8FAE2D@w3.org>
Hi John, > On 14 Oct 2021, at 15:11, John Foliot <john@foliot.ca> wrote: > (…) > > I'll also note that while the colors being used on those resource appear to be passing the WCAG Color contrast requirements, I'll pose a slightly higher-level question: given that we know that red/green color-blindness is the most prevalent form of color blindness, do we really want to be using red/green 'contrast' like this? > <image.png> > > Not a hill to die on, but I just find it curious, is all... > > JF Thanks for raising this, it is a great point. We're using an off the shelve colour scheme for this, called a11y-syntax-highlighting <https://github.comericwbailey/a11y-syntax-highlighting/blob/main/dist/prism/a11y-light.css>, also used in the W3C design system <https://design-system.w3.org/>. The reason we're seeing these colours is a little technical. Syntax highlighters usually rely on language being indicated, eg with classnames, which we don't do in the Techniques. For that reason, we are using a library <https://highlightjs.org/> that tries to detect the language, before applying colours. It seems to struggle detecting our HTML (sadly). Currently, code in Techniques is not syntax highlighted at all, so I feel adding it, even in this form, is an improvement, but it would certainly be something we could/should work on making better in a next iteration. Best, Hidde — Web Accessibility Specialist ・ https://w3.org/people/hidde <https://w3.org/people/hidde> ・ Web Accessibility Initiative (WAI) at World Wide Web Consortium (W3C)
Received on Sunday, 17 October 2021 21:58:24 UTC