Edit comment LC-1410 for Accessibility Guidelines Working Group

Quick access to

Previous: LC-856 Next: LC-483

Comment LC-1410: Comment Shortname:; Commenter: David Keech <david.keech@bsi-global.com> on behalf of British Standards Instution, London, UK; Message-id:; Section of the document concerned:

or; Refinement of the section concerned:; Status:
assigned to; Type:; Resolution status:
Response drafted Resolution implemented Reply sent to commenter; Response status:
No response from Commenter yet Commenter approved disposition Commenter objected to disposition
Commenter's response (URI):; Comment:
3. WCAG defines a "web unit" as "one or more resources, intended to be rendered together, and identified by a single Uniform Resource Identifier ". Resources can in addition consist of moving images, or pages where part of the material is rendered through links into Web Services (such as with AJAX technology). The example given in the definition is static in nature - however in many situations in today's web the end result is not static, or defined solely by a single URI.

This appears to be clarified for a web unit in the section "Conformance claims" - where it states that it "can also take the form of a fully interactive and immersive environment"

However the situation becomes confused by later referring to "Aggregated content" and giving, as an example of this, "a web unit which is assembled from multiple sources that may or may not have their own levels of conformance". In a traditional web page, containing graphics, (as is given as an example in the definition of a "web unit"), this is conventionally exactly how images etc are rendered using the <IMG> tag.

Statements such as "The conformance level for a Web unit that contains authored units is equal to the lowest conformance level claimed for the Web unit content and any of the authored units it contains â€“ including any claims pertaining to aggregated authored units" are extremely unclear, and indeed may be recursive following the unclear distinction apparently made between "web units" and "aggregated content". A "web page" on the other hand is fairly well understood. BSI recommend(s) a closer look at an accurately defined and understood syntax which is not open to misinterpretation and clearly conveys the ideas being communicated.; Related issues: 878
(space separated ids); WG Notes: [EDITORZ] 878 IS PARENT Issue: If a claim can only be for a Web page, how can a claim for aggregated content exist? This section may need additional work. Discussed in the 08 February 2007 telecon: Accepted by unanimous consent. http://www.w3.org/WAI/GL/2007/02/08-wai-wcag-minutes.html; Resolution: {accept} Respond with: We have replaced the term "Web unit" with "Web page" and have modified the conformance section to clarify these concerns.; (Please make sure the resolution is adapted for public consumption)