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

Re: CSS Parsed Unambiguously

From: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: Fri, 09 Jun 2006 19:57:26 +0200
To: "Chris Ridpath" <chris.ridpath@utoronto.ca>
Cc: "WAI WCAG List" <w3c-wai-gl@w3.org>
Message-ID: <g5dj82l117av26oa638m7ach10oopl64po@hive.bjoern.hoehrmann.de>

* Chris Ridpath wrote:
>Success Criteria 4.1.1 requires the web unit be parsed unambiguously. The 
>conformance section specifies that all content, including secondary 
>resources, must be included for conformance. So it seems that if your CSS 
>does not validate then you'll fail SC 4.1.1 (level 1).

CSS 2.1 is close to defining parsing of style sheets for pretty much any
sequence of octets; style sheets that cannot be parsed unambiguously are
not common.

>Here's an example file that includes an invalid CSS (missing a semicolon).
>http://checker.atrc.utoronto.ca/docs/file4.html
>http://checker.atrc.utoronto.ca/docs/test1.css
>
>The W3C's validator says regarding the example file: "your CSS style sheet 
>needs a correct document parse tree".

Yes, that means about the same as "parsed unambiguously".
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de
68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 
Received on Friday, 9 June 2006 17:57:37 GMT

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