W3C home > Mailing lists > Public > public-low-vision-a11y-tf@w3.org > November 2016

RE: Text Color is Ready.

From: Jonathan Avila <jon.avila@ssbbartgroup.com>
Date: Wed, 16 Nov 2016 23:27:25 +0000
To: public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>
Message-ID: <DM5PR03MB27804E30A46A36D5494AB40E9BBE0@DM5PR03MB2780.namprd03.prod.outlook.com>
> Given that people can use their browsers or OS to change colours,

I am not aware of how to change colors of content in the browser on an iOS device.  Using the invert color features or darken color features in the OS is not the same as it provides a filter which does not always have the intended consequences.  To my knowledge while there are options to be able to change the color, font, etc. of captions for video the same is not true of web content.


-----Original Message-----
From: Alastair Campbell [mailto:acampbell@nomensa.com] 
Sent: Wednesday, November 16, 2016 6:19 PM
To: Wayne Dick; public-low-vision-a11y-tf
Subject: Re: Text Color is Ready.

Hi Wayne,

I wonder if this one needs re-framing a little. As stated it implies that site owners should provide colour choices.

Given that people can use their browsers or OS to change colours, is the intent to enable users to do that without the website screwing it up for them?

In which case, should it be framed as something like this:

Web pages maintain contrast and functionality when foreground or background color changes are made in the user agent.

The rest seems fine. I'd forgotten about technique C22, that seems to be the key one and for this SC.

I added a little bit at the top of the description to say "these are the things that prevent it from working" with a few examples, are there others?


Received on Wednesday, 16 November 2016 23:27:59 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:23:23 UTC