W3C home > Mailing lists > Public > public-comments-wcag20@w3.org > August 2006

WCAG 2.0 Comment Submission

From: WCAG 2.0 Comment Form <nobody@w3.org>
Date: Thu, 17 Aug 2006 17:04:52 +0000 (UTC)
To: public-comments-wcag20@w3.org
Message-Id: <20060817170452.F420113AB0@seamus.w3.org>


Name: Christophe Strobbe
Email: christophe.strobbe@esat.kuleuven.be
Affiliation: Katholieke Universiteit Leuven
Document: W2
Item Number: glossary
Part of Item: 
Comment Type: technical
Comment (Including rationale for any proposed change):
The definition of Web unit is still ambiguous.



(1) If an HTML document (home.htm) has various linked stylesheets (one for screen, one for print, one for projection, ...), these are not all intended to be rendered together. I think the the following would all count as Web units:

- home.htm with the CSS for \'screen\',

- home.htm with the CSS for \'projection\',

- home.htm with the CSS for \'braille\',

- home.htm with the CSS for \'aural\',

- ...

However, this is not clear from the definition. If these are all different web units, it is also impossible to identify them with a URL, because the URL is the same for each.



(2) If an HTML page uses an object element with one or more fallbacks nested inside it (see the example slightly below http://www.w3.org/TR/1999/REC-html401-19991224/struct/objects.html#idx-object-5), I think the Web unit you claim conformance for is the HTML document with the outermost object element (with the TheEarth.py applet). However, the content of each of the nested object elements is not meant to be rendered together with the content of all the other object elements. Does that mean that there is a different web unit per fallback/nested object element?



(3) If a web page uses frames, the content of some of the frames depends on the user\'s interaction: e.g. clicking a link in the navigation frame opens a different document in the content frame. So the URL that identifies the frameset document does not always identify the same Web unit, unless the Web unit is limited to what is loaded by default.



(4) If user agent X requests URL http://www.example.com/ with MIME type aaa/bbb and user agent Y requests the same URL with MIME type ccc/ddd, and they get different web units because of the different MIME type, the URL cannot be used to differentiate between the two web units. Does that mean these are different Web  units according to the current definition?



Most of this was previously discussed on the ERT mailing list in the context of conformance claims (see http://lists.w3.org/Archives/Public/public-wai-ert/2006May/0029.html and next messages in the same thread) and forwarded to the GL list (http://lists.w3.org/Archives/Public/w3c-wai-gl/2006AprJun/0181.html).

Proposed Change:
Received on Thursday, 17 August 2006 17:04:57 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 17 July 2011 06:13:20 GMT