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

Re: Should we drop the color bullet for now?

From: Jim Allan <jimallan@tsbvi.edu>
Date: Thu, 27 Apr 2017 21:12:33 -0500
Message-ID: <CA+=z1Wn5iThGZvuocCrs-xQdy1_zewG=f+wEDz2tQcMV12RJaQ@mail.gmail.com>
To: Wayne Dick <wayneedick@gmail.com>
Cc: Alastair Campbell <acampbell@nomensa.com>, public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>, Jonathan Avila <jon.avila@ssbbartgroup.com>
This is a process. I don't think anyone disagrees that the ability to
change color is important. We are taking some time to get the wording
right. Writing these is hard. There will be lots of discussion. Color will
not go away.

On Apr 27, 2017 8:06 PM, "Wayne Dick" <wayneedick@gmail.com> wrote:

The ability to change color is essential to my use of web pages.


An icon that depends on background color to be visible is using color to
convey meaning.

Agree. We talked about that in todays meeting and agreed to do more on this
topic. I created a wiki page with reference to the minutes.

A presentation that depends on a background image to make font visible is
using color to convey meaning.

Agree. See above

Background images were never created to act as cashes for icons. Using
sprites in background images is like using a heading because you like the
style of the element.


We are being blocked from accessibility because of an identifiable list of
practices that are kludges.

I think you started a good list. We need to expand the list. Get examples.
Build the case. Write the SC. It takes time. We have 15 months to go.

Testability of color substitution is trivial.  Setting save  color choices
with a wide domain of choice is trivial.  There is not reason to deny users
access to the color of their choice.

If color is taken off the table I will prepare an appeal to the AC. I have
enough data to prove my case.

We are NOT removing color forever. We are rethinking the approach and
wording of the SC to approach the issue from the authors side rather than
the user need side.
I think the group made progress on the differt approach to the color SC
Please give the group time to think and the process (which is slow and
frustrating) to work, so we can craft a solid SC to address color.



On Thu, Apr 27, 2017 at 1:39 AM, Alastair Campbell <acampbell@nomensa.com>

> Ach, I shouldn’t reply from my phone, I had meant the test should be:
> “Change the colours to black and white. Where the foreground text is dark
> use white on black, or if the foreground text is light use black on white.”
> This would be a test to find issues as a proxy of what the user does, it
> is not the user requirement. I think that would highlight any issues people
> encounter?
> I can’t think how to get that into SC text as a bullet though… perhaps:
> * Colours can be adapted to a high-contrast colour scheme such as black
> and white.
> Although not everyone wants high-contrast the ability to change it is
> there, easy to test, and clear on the requirement… I hope.
> -Alastair
Received on Friday, 28 April 2017 02:13:08 UTC

This archive was generated by hypermail 2.3.1 : Friday, 28 April 2017 02:13:09 UTC