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

Re: CSS Parsed Unambiguously

From: Chris Ridpath <chris.ridpath@utoronto.ca>
Date: Mon, 12 Jun 2006 11:44:15 -0400
Message-ID: <00ba01c68e37$0f5d3530$e29a968e@WILDDOG>
To: "Gregg Vanderheiden" <gv@trace.wisc.edu>, <w3c-wai-gl@w3.org>

Here's an example of a real world problem:

body {
 background: black 10;
 color: yellow;
}

CSS Grammar is correct and looks fine in IE (tested on version 6). However 
it's almost impossible to read in Firefox (tested on 1.5.0.4).

This is an accessibility problem for people with low vision and this product 
could ship.

So I agree with Tina:
>   So, basically, we /do/ have a case of what I asked last week: a 
> stylesheet
>   can pass SC 4.1.1 and be harmful to accessibility - both at the same 
> time.

Also, it's possible that content can fail SC 4.1.1 and have no harmful 
effects on accessibility.

Chris


----- Original Message ----- 
From: "Gregg Vanderheiden" <gv@trace.wisc.edu>
To: <w3c-wai-gl@w3.org>
Sent: Monday, June 12, 2006 11:10 AM
Subject: RE: CSS Parsed Unambiguously


>
> No
>
> Actually it would be a page that was accessible ONLY to people with
> disabilities (who use screen reader or don't use style sheets).
>
> If we can restrict ourselves to problem that actually occur in pages on 
> the
> web it would be helpful.
>
> Black text on black background is not going to ship.   And is not an
> accessibility problem.  People with disabilities and using AT are actually
> at an advantage, not disadvantage.
>
> Gregg
>
Received on Monday, 12 June 2006 15:44:58 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:46 GMT