RE: CSS Parsed Unambiguously

I'm not sure I follow the question.

Are you saying the CSS file is broken for everyone?  If so that is not a
disability access problem. It is a broken CSS file.  There is no
disadvantage to people with disabilities beyond the problems faced by all. 

If it works for everyone but is broken so that the WCAG provisions can't be
met - then it would fail WCAG.  

Can you clarify?

Gregg

 -- ------------------------------ 
Gregg C Vanderheiden Ph.D. 
Professor - Ind. Engr. & BioMed Engr.
Director - Trace R & D Center 
University of Wisconsin-Madison 
The Player for my DSS sound file is at http://tinyurl.com/dho6b 
 

> -----Original Message-----
> From: w3c-wai-gl-request@w3.org 
> [mailto:w3c-wai-gl-request@w3.org] On Behalf Of Tina Holmboe
> Sent: Friday, June 09, 2006 5:07 PM
> To: Johannes Koch
> Cc: WAI WCAG List
> Subject: Re: CSS Parsed Unambiguously
> 
> 
> On Fri, Jun 09, 2006 at 11:49:45PM +0200, Johannes Koch wrote:
> 
> > >I think that the stylesheet can be broken in some ways and 
> still be 
> > >parsed properly as Björn suggested
> > 
> > Then the CSS will meet the SC.
> 
>   In other words: a stylesheet can be written so poorly that, 
> following
>   the error correction rules in section 4.2 of CSS 2.1, so many bits
>   and pieces are left out that contrast and other important
>   accessibility details suffer ... but as long as it can be parsed
>   properly it will still meet the SC?
> 
>   Frankly, that doesn't make sense at all. What is the
>   accessibility value of a correctly parsed, but broken, CSS
>   file?
> 
> -- 
>  -     Tina Holmboe                    Greytower Technologies 
> (UK) Ltd.
>    tina@greytower.co.uk                  http://www.greytower.co.uk
>      +46 708 557 905  
> 
>

Received on Saturday, 10 June 2006 06:37:46 UTC