E-mail List Archives

Search E-mail List Archives for

Number of posts in this thread: 2 (In chronological order)

From: Sudheer Babu
Date: Fri, Aug 13 2021 2:10AM
Subject: Mapping WCAG Success Criteria High Contrast Mode Testing on Windows
No previous message | Next message →

Hi All,

Hope everyone is doing well and staying safe!

I have my team find out few defects on Chrome browser when some of the UI
elements (radio buttons in the selected state) are not rendered as expected
when High contrast black and white settings are applied.
Can someone please explain how these high contrast mode testing can be
mapped to WCAG 2.1 Criteria (1.4.11 perhaps??),
and also any information on the HCM testing process and best practices for
fixing such issues.

Thanks in advance!
Sudheer

From: Patrick H. Lauke
Date: Fri, Aug 13 2021 2:45AM
Subject: Re: Mapping WCAG Success Criteria High Contrast Mode Testing on Windows
← Previous message | No next message

On 13/08/2021 09:10, Sudheer Babu wrote:
> Hi All,
>
> Hope everyone is doing well and staying safe!
>
> I have my team find out few defects on Chrome browser when some of the UI
> elements (radio buttons in the selected state) are not rendered as expected
> when High contrast black and white settings are applied.
> Can someone please explain how these high contrast mode testing can be
> mapped to WCAG 2.1 Criteria (1.4.11 perhaps??),
> and also any information on the HCM testing process and best practices for
> fixing such issues.

At a very high level, the answer is that normatively, HCM is not taken
into consideration for WCAG (as it effectively counts as the user
explicitly overriding the presentation defined by the author, which the
author often has limited control over).

There are various discussion threads here
https://github.com/w3c/wcag/issues?q=is%3Aissue+is%3Aopen+high+contrast
and https://github.com/w3c/wcag/issues?q=is%3Aissue+is%3Aopen+HCM and
so far that seems to be the consensus.

Of course, this doesn't stop you testing and reporting on bugs that crop
up in HCM anyway, but these would be above and beyond what is required
for a WCAG pass/fail evaluation (i.e. if something doesn't work in HCM,
it's not a normative failure of WCAG at the moment).

P
--
Patrick H. Lauke

https://www.splintered.co.uk/ | https://github.com/patrickhlauke
https://flickr.com/photos/redux/ | https://www.deviantart.com/redux
twitter: @patrick_h_lauke | skype: patrick_h_lauke