W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > April to June 2018

Re: Updates to Understanding 1.4.11 part 2

From: Laura Carlson <laura.lee.carlson@gmail.com>
Date: Thu, 14 Jun 2018 12:11:55 -0500
Message-ID: <CAOavpvfFgDa7gDAqUkhMmsDLwi7BZxCkz0eqB=U5L-fBSCQnZw@mail.gmail.com>
To: John Foliot <john.foliot@deque.com>
Cc: David MacDonald <david100@sympatico.ca>, Alastair Campbell <acampbell@nomensa.com>, WCAG group <w3c-wai-gl@w3.org>, LVTF - low-vision-a11y <public-low-vision-a11y-tf@w3.org>
Hi John and all,

On 6/13/18, John Foliot <john.foliot@deque.com> wrote:

> I can agree with that half-way: as long as the author has not modified the
> background, then yes, the native foreground is a User Agent problem.
> BUT, if the content author has modified the background, then no, native
> default colors/indication cannot be "forgiven", because at some point the
> author has intervened.

I have been thinking about this. If the WG decides to go with the wide
interpretation, authors would need tools to help them catch those

At one time the W3C CSS Validator did warn [1] [2] [3] if an author
had no background-color with their foreground color. I wonder if that
warning could be reinstated/adjusted for this use case.

Besides F24 which Jon A mentioned, there is also the old "If You Pick
One Color, Pick Them All" on W3C QA Tips [4]

Kindest Regards,

[1] https://web.archive.org/web/20160919184438/http://www.websitedev.de:80/css/validator-faq
[2] https://www.webmasterworld.com/css/3061963.htm
[3] https://lists.w3.org/Archives/Public/w3c-wai-ig/1999AprJun/0300.html
[4] https://www.w3.org/QA/Tips/color

Laura L. Carlson
Received on Thursday, 14 June 2018 17:12:21 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 21:08:26 UTC