RE: [w3c/wcag] Technique G183 not applicable to touch/inputs that lack hover/focus (#201)

I am not 100% sure that this is broken. It may be related to some of the contrast algorithms or research done at Trace and elsewhere.

 

Don’t throw out the bathwater yet, let’s get some more feedback on where this came from……….:-)

 

​​​​​

 

 

 

* katie *

 

Katie Haritos-Shea 
Principal ICT Accessibility Architect (WCAG/Section 508/ADA/AODA)

 

Cell: 703-371-5545 |  <mailto:ryladog@gmail.com> ryladog@gmail.com | Oakton, VA |  <http://www.linkedin.com/in/katieharitosshea/> LinkedIn Profile | Office: 703-371-5545 |  <https://twitter.com/Ryladog> @ryladog

 

From: Patrick H. Lauke [mailto:notifications@github.com] 
Sent: Monday, July 11, 2016 8:07 PM
To: w3c/wcag <wcag@noreply.github.com>
Subject: Re: [w3c/wcag] Technique G183 not applicable to touch/inputs that lack hover/focus (#201)

 

What I love about WCAG is that once you peel away one aspect that seems broken, you find 5 more bits that it's built on that also seem broken...

So F73 makes a distinction between hue and lightness. Leaving aside the fact that I would guess most people don't indeed make that distinction (and I'd guess that if you showed people two swatches, one fire engine red and one bright pink, they wouldn't say "it's the same color"), I wonder: what about saturation (if we use the classic HSL model)? This distinction seems already quite flawed (and it's enshrined in a non-normative note to a non-normative technique). Also, you can achieve a different color contrast by changing hue and saturation, not just lightness, so regular color contrast calculations wouldn't be enough to determine the 3:1 ratio...you'd have to also ensure that the hue (and saturation?) are the same, otherwise you're using a different color (in the restrictive "hue" sense).

Long story short: agree that F73's note 1 also needs to be chopped.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <https://github.com/w3c/wcag/issues/201#issuecomment-231901891> , or mute the thread <https://github.com/notifications/unsubscribe/AFfqyuc2UbRFjGb73LNAwxmEDhvjiynYks5qUtqkgaJpZM4JJQGy> .  <https://github.com/notifications/beacon/AFfqyiAS99IwYdZSOdpWaUc5bSXVfjjxks5qUtqkgaJpZM4JJQGy.gif>