- From: John Foliot <john.foliot@deque.com>
- Date: Wed, 24 Feb 2016 09:15:25 -0600
- To: "'Jonathan Avila'" <jon.avila@ssbbartgroup.com>, <josh@interaccess.ie>
- Cc: "'Paul J. Adam'" <paul.adam@deque.com>, "'Gregg Vanderheiden RTF'" <gregg@raisingthefloor.org>, <tink@tink.uk>, "'Katie Haritos-Shea'" <ryladog@gmail.com>, "'David MacDonald'" <david100@sympatico.ca>, "'Jason J White'" <jjwhite@ets.org>, "'Sailesh Panchang'" <sailesh.panchang@deque.com>, "'Andrew Kirkpatrick'" <akirkpat@adobe.com>, "'GLWAI Guidelines WG org'" <w3c-wai-gl@w3.org>, "'Jim Allan'" <jimallan@tsbvi.edu>
Jonathan Avila wrote: > > > Why do you consider it a loophole? Is it not understood that for focus > > indicators need to satisfy colour contrast/luminosity ratios? > > We seem to all agree they should but this does not seem to be directly covered > by the success criteria. +1 While we, as "experts" understand this, it is not specifically called out as part of the requirement(s) - thus the gap (I consider it more of a gap than a "loophole") is something that should be addressed going forward, either via work from one of the TFs currently working (Low Vision perhaps?) > I believe a similar missing need exists When selection and focus are indicated by > the difference in luminosity of background and not by shape. Consider a > selected page tab that was medium gray and the others a light gray. The > selected state is indicated by color difference and it's not clear if SC 1.4.1 would > apply. Even if it did apply and some other marking was added there is no > requirement that the marking have sufficient contrast. Hear, hear.... with the caveat that color alone is not the only means of providing that kind of visual feedback, so it is actually a "merging" (as it were) of both 1.4.1 AND the variant of 1.4.3 under discussion here > Future updates or extensions need to clearly address luminosity for visual > indication of keyboard focus and address color differences used for selection. +1 JF
Received on Wednesday, 24 February 2016 15:15:56 UTC