Re: Contrast ration of hover state

Hi,

     There were no objective color contrast requirements in WCAG 2.0
for User Interface Components.more..
<https://lists.w3.org/Archives/Public/w3c-wai-ig/2017JanMar/0231.html>

But, in WCAG 2.1 there exist https://www.w3.org/TR/WCAG21/#non-text-contrast

 -Success Criterion 1.4.11 Non-text Contrast, might be relevant.

https://www.w3.org/WAI/WCAG21/quickref/#non-text-contrast.

Thanks


On Tue, Feb 7, 2023 at 12:33 PM anni zhai <annizhai226@gmail.com> wrote:

> Hi all,
>
> Hope everyone doing well.
>
> I have the same issue with the email in the archive with the response of Patrick, but i need a further discussion, if the state is only for hover, does the light grey color need to have a 3:1 contrast with the white background?
>
> On 07/05/2020 23:02, Kiran wrote:
> > Hi All,
> >
> > Hope you are staying safe.
> >
> > I appreciate your inputs and thoughts in clarifying color
> > contrast requirements in hover state of the dropdown element.
> >
> > As shown in an example below, on hover state: the dropdown element text
> > "Willie" passes accessibility on that light gray, which is #DbDbDb. But
> > the light gray #DBDBDB color doesn't meet accessibility on white. So my
> > question is: does the gray have to be discernible from white when next
> > to each other to pass WCAG 2.1 AA ?
>
> I'm assuming this isn't just the hover state, but the focus state as
> well? In which case I'd say that yes, the background of the currently
> focused item needs to have sufficient contrast (at least 3:1) against
> the white background (per 1.4.11, as that background color is the only
> visual indication of the focused/selected state).
>
> [image: image.png]
>
> Thanks
> Anni
>