FW: [w3c/wcag] Does SC 1.4.11 require comparing focused and non-focused states (#541)

Hi Group Issue #541 is something that this group should weigh in on.  If we think that the current WCAG 2.1 SC allows low contrast to be the only differentiator between focused and non-focused states then we might want to propose plugging this hole in any proposed WCAG 2.2 SC.  If we think this was not the intention of 2.1 then we should speak up now.

Jonathan

From: Patrick H. Lauke <notifications@github.com>
Sent: Friday, November 30, 2018 8:31 AM
To: w3c/wcag <wcag@noreply.github.com>
Cc: Jonathan Avila <jon.avila@levelaccess.com>; Author <author@noreply.github.com>
Subject: Re: [w3c/wcag] Does SC 1.4.11 require comparing focused and non-focused states (#541)


to expand my previous: 1.4.11 defines that the focus indication itself needs to satisfy the contrast requirement...in isolation. as long as the focus indication has sufficient contrast, it would pass 1.4.11. but nothing says how distinguishable focus indication needs to be, normatively, from non-focused state.

for instance, i could have a control that has a border of #666 against #FFF, and when focused its border changes to #665. in both cases, both color values for the borders amply pass 1.4.11, and nominally this passes focus visible (as there is a "visible" change between #666 and #665). and nothing normatively anywhere says otherwise?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<https://github.com/w3c/wcag/issues/541#issuecomment-443203792>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AFYSM2UQyaAiuLV8zc4Te-dUs0j7JaONks5u0TL_gaJpZM4YzWGx>.