E-mail List Archives
Thread: rely on a browser's high contrast mode
Number of posts in this thread: 7 (In chronological order)
From: Mike Warner
Date: Wed, Jul 31 2019 9:28AM
Subject: rely on a browser's high contrast mode
No previous message | Next message →
Hi all,
we've got a website redesign in process and when I pointed out contrast
issues where we're not completely AA complaint, I was asked this:
"To what degree can we rely on a browser's high contrast mode? When I turn
on chrome's high contrast mode, it solves any contrast issues the pages may
have had. Do we need a policy for such a thing? "
I'd prefer to be at least AA as a minimum, but wanted to get expert
opinions. I couldn't find anything that directly answered the question in
my searches on the google.
Thank you,
Mike
Mike Warner
Director of IT Services
MindEdge, Inc.
From: Patrick H. Lauke
Date: Wed, Jul 31 2019 10:06AM
Subject: Re: rely on a browser's high contrast mode
← Previous message | Next message →
On 31/07/2019 16:28, Mike Warner wrote:
> Hi all,
>
> we've got a website redesign in process and when I pointed out contrast
> issues where we're not completely AA complaint, I was asked this:
>
> "To what degree can we rely on a browser's high contrast mode? When I turn
> on chrome's high contrast mode, it solves any contrast issues the pages may
> have had. Do we need a policy for such a thing? "
>
> I'd prefer to be at least AA as a minimum, but wanted to get expert
> opinions. I couldn't find anything that directly answered the question in
> my searches on the google.
The short answer is no, you can't rely on high contrast mode, as it may
not be available to all users.
For what it's worth, Chrome itself doesn't have a high contrast mode, it
only has an extension that would need to be separately installed.
Not all operating systems provide the same level/type of high contrast
mode. Windows' High Contrast mode is fairly unique in that it completely
overrides colors (in IE/Edge/Firefox). On other platforms like Android,
iOS, MacOS OS-level high contrast mostly (last time I looked anyway)
increase the contrast, which can actually lead to text being harder to
read (as it can wash out, say, light text on light background even further)
P
--
Patrick H. Lauke
www.splintered.co.uk | https://github.com/patrickhlauke
http://flickr.com/photos/redux/ | http://redux.deviantart.com
twitter: @patrick_h_lauke | skype: patrick_h_lauke
From: Farough, David (CFP/PSC)
Date: Wed, Jul 31 2019 12:58PM
Subject: Re: rely on a browser's high contrast mode
← Previous message | Next message →
Check out the following article from Scott O'Hara on other high contrast issues.
https://www.scottohara.me/blog/2019/02/12/high-contrast-aria-and-images.html
From: Birkir R. Gunnarsson
Date: Wed, Jul 31 2019 2:10PM
Subject: Re: rely on a browser's high contrast mode
← Previous message | Next message →
For the purpose of achieving absolutely minimal conformance to WCAG
2.0 this is an interesting question.
I invite you to peruse the wonderfully complex document that is the
WCAG 2.0 conformance requirements
https://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance.html
particularly the "conforming alternate version" and "accessibility
supported" sections.
Note 7 under "understanding conforming alternate versions" says:
"Setting user preferences within the content to produce a conforming
version is an acceptable mechanism for reaching another version as
long as the method used to set the preferences is accessibility
supported."
As long as you can open your browser menu and turn on high contrast
mode (which you can with most assistive technology browser
combinations I aware of) this sounds like making certain features
accessible in high contrast mode would pass the minimalist definition,
much to my disappointment.
Forpractical reasons you wouldn't want to rely on this:
As already mentioned, high contrast mode differs between browsers and
operating systems and while it can fix one area of the page it could
render other parts amost totally impossible to read (and for the page
to pass WCAG the entire page ust be accessible in the chosen mode, not
a page that requires you to switch between multiple modes to achieve
full conformance). In other words, and in my understanding, the page
must fully pass color contrast requirements in high contrast mode,
notjust the sections of it that fail in normal mode.
Even if high contrast mode is available, would users know about it
(would you be able to tell your grandma to just turn it on), similar
arguments can be made for text resizing etc. but it is still a valid
usability argument.
That designer should just make the page color scheme accessible, it
will save major headaches, complications and sleepless nights in the
long-run. ;)
On 7/31/19, Farough, David (CFP/PSC) < = EMAIL ADDRESS REMOVED = > wrote:
> Check out the following article from Scott O'Hara on other high contrast
> issues.
> https://www.scottohara.me/blog/2019/02/12/high-contrast-aria-and-images.html
>
> > > > >
--
Work hard. Have fun. Make history.
From: Jonathan Avila
Date: Wed, Jul 31 2019 2:56PM
Subject: Re: rely on a browser's high contrast mode
← Previous message | Next message →
In my experience the Chrome high contrast mode extension applies a filter to the page and while it makes some text higher contrast it can also make other text lower contrast. I find it unlikely for all of the pages that it wouldn't break something else bringing some other text lower than the threshold. Browser extensions also are not available on mobile browsers. While mobile platforms have some accessibility settings to invert colors or increase contrast again I don't think you could safely rely on these assistive technologies for a public site -- although strictly speaking only one combination is needed to claim conformance. From a functionality standpoint -- an argument under the ADA could be made that if content functionally works with assistive technology even if not conforming to WCAG that it can be used. For example, a screen reader that guesses form labels for form fields could be relied upon instead of marking up your form fields with explicit labels. This is risky.
In addition, the contrast requirements under WCAG are minimums. They are not high contrast values and are not meant to address needs of people who need high contrast -- they are meant to provide a minimum level of contrast for users. Forcing a user who only needs a minimum to use a high contrast mode does not make sense. A better option if the page colors absolutely can't be changed is to add a switch that provides an increased contrast option to meat the minimum. This option would be available to all users including those with platforms and browsers without contrast options. The argument that changing a gray line to be slightly darker will cause an organizations customers to leave is often used but is likely just someone defending their style decisions rather than based on actual data. Brand colors are important but most customers will find that you can get appealing brand colors with sufficient palette options that have sufficient contrast or that small modifications can be m
ade with a switch control allowing user preference before rebranding is done with inclusive design taken into account.
Jonathan
From: WebAIM-Forum < = EMAIL ADDRESS REMOVED = > On Behalf Of Birkir R. Gunnarsson
Sent: Wednesday, July 31, 2019 4:10 PM
To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
Subject: Re: [WebAIM] rely on a browser's high contrast mode
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
For the purpose of achieving absolutely minimal conformance to WCAG
2.0 this is an interesting question.
I invite you to peruse the wonderfully complex document that is the WCAG 2.0 conformance requirements https://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance.html
particularly the "conforming alternate version" and "accessibility supported" sections.
Note 7 under "understanding conforming alternate versions" says:
"Setting user preferences within the content to produce a conforming version is an acceptable mechanism for reaching another version as long as the method used to set the preferences is accessibility supported."
As long as you can open your browser menu and turn on high contrast mode (which you can with most assistive technology browser combinations I aware of) this sounds like making certain features accessible in high contrast mode would pass the minimalist definition, much to my disappointment.
Forpractical reasons you wouldn't want to rely on this:
As already mentioned, high contrast mode differs between browsers and operating systems and while it can fix one area of the page it could render other parts amost totally impossible to read (and for the page to pass WCAG the entire page ust be accessible in the chosen mode, not a page that requires you to switch between multiple modes to achieve full conformance). In other words, and in my understanding, the page must fully pass color contrast requirements in high contrast mode, notjust the sections of it that fail in normal mode.
Even if high contrast mode is available, would users know about it (would you be able to tell your grandma to just turn it on), similar arguments can be made for text resizing etc. but it is still a valid usability argument.
That designer should just make the page color scheme accessible, it will save major headaches, complications and sleepless nights in the long-run. ;)
On 7/31/19, Farough, David (CFP/PSC) < = EMAIL ADDRESS REMOVED = > wrote:
> Check out the following article from Scott O'Hara on other high
> contrast issues.
> https://www.scottohara.me/blog/2019/02/12/high-contrast-aria-and-image
> s.html
>
> > > archives at http://webaim.org/discussion/archives
> >
--
Work hard. Have fun. Make history.
From: Steve Green
Date: Wed, Jul 31 2019 6:58PM
Subject: Re: rely on a browser's high contrast mode
← Previous message | Next message →
My interpretation of "Setting user preferences within the content" is that the style switcher needs to be built into the website, not the browser. That means it is available in every user agent.
This view is reinforced by the phrase "as long as the method used to set the preferences is accessibility supported", which only makes sense if the style switcher is in the website.
So the bottom line is that you can't rely on the style switcher in the browser.
Steve Green
Managing Director
Test Partners Ltd
-----Original Message-----
From: WebAIM-Forum < = EMAIL ADDRESS REMOVED = > On Behalf Of Birkir R. Gunnarsson
Sent: 31 July 2019 21:10
To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
Subject: Re: [WebAIM] rely on a browser's high contrast mode
For the purpose of achieving absolutely minimal conformance to WCAG
2.0 this is an interesting question.
I invite you to peruse the wonderfully complex document that is the WCAG 2.0 conformance requirements https://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance.html
particularly the "conforming alternate version" and "accessibility supported" sections.
Note 7 under "understanding conforming alternate versions" says:
"Setting user preferences within the content to produce a conforming version is an acceptable mechanism for reaching another version as long as the method used to set the preferences is accessibility supported."
As long as you can open your browser menu and turn on high contrast mode (which you can with most assistive technology browser combinations I aware of) this sounds like making certain features accessible in high contrast mode would pass the minimalist definition, much to my disappointment.
Forpractical reasons you wouldn't want to rely on this:
As already mentioned, high contrast mode differs between browsers and operating systems and while it can fix one area of the page it could render other parts amost totally impossible to read (and for the page to pass WCAG the entire page ust be accessible in the chosen mode, not a page that requires you to switch between multiple modes to achieve full conformance). In other words, and in my understanding, the page must fully pass color contrast requirements in high contrast mode, notjust the sections of it that fail in normal mode.
Even if high contrast mode is available, would users know about it (would you be able to tell your grandma to just turn it on), similar arguments can be made for text resizing etc. but it is still a valid usability argument.
That designer should just make the page color scheme accessible, it will save major headaches, complications and sleepless nights in the long-run. ;)
On 7/31/19, Farough, David (CFP/PSC) < = EMAIL ADDRESS REMOVED = > wrote:
> Check out the following article from Scott O'Hara on other high
> contrast issues.
> https://www.scottohara.me/blog/2019/02/12/high-contrast-aria-and-image
> s.html
>
> > > archives at http://webaim.org/discussion/archives
> >
--
Work hard. Have fun. Make history.
From: Patrick H. Lauke
Date: Thu, Aug 01 2019 4:48AM
Subject: Re: rely on a browser's high contrast mode
← Previous message | No next message
On 01/08/2019 01:58, Steve Green wrote:
> My interpretation of "Setting user preferences within the content" is that the style switcher needs to be built into the website, not the browser. That means it is available in every user agent.
>
> This view is reinforced by the phrase "as long as the method used to set the preferences is accessibility supported", which only makes sense if the style switcher is in the website.
>
> So the bottom line is that you can't rely on the style switcher in the browser.
FWIW I concur with Steve on this one.
P
--
Patrick H. Lauke
www.splintered.co.uk | https://github.com/patrickhlauke
http://flickr.com/photos/redux/ | http://redux.deviantart.com
twitter: @patrick_h_lauke | skype: patrick_h_lauke