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

Re: Text Color is Ready.

From: Wayne Dick <wayneedick@gmail.com>
Date: Wed, 16 Nov 2016 15:48:19 -0800
Message-ID: <CAJeQ8SDnAMd5feFR-fTficgULAMZDrDRbWFJNx+VteaYX892Kg@mail.gmail.com>
To: Alastair Campbell <acampbell@nomensa.com>
Cc: public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>
The intent is this. If the browser has a mechanisms for full color
then the cannot block this access. The problem is that WCAG WG wants
it all stated positively.


On Wed, Nov 16, 2016 at 3:18 PM, Alastair Campbell
<acampbell@nomensa.com> wrote:
> 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?
> Cheers,
> -Alastair
Received on Wednesday, 16 November 2016 23:49:33 UTC

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