Thoughts on Issues 24 and 25

Thoughts on Issues 24 and 25

These are similar to issues that Gregg V. addresssed in #LC-494 (for W2 - 2.3.2) and 
somewhat the Conformance issue #LC-464  (for W2 - Conformance, Aggregated Content).
 
It all comes back to conformance. If we decide to use 'web units' or 'content' 
(instead of web unit) it should be done consistantly throughout. I think that the use 
of content vs. web units has been explorer laboriously and web unit was chosen by the 
Working Group as most appropriate for all technologies. Personally I think we should 
resist that urge to change all 'web unit' instances to 'content'.
 
Using 'web units' instead of 'web unit' will be confusing in these two instances 
(3.1.1 and 3.1.2), but if we think 'web units' is favored, we should switch to it 
throughout.
 
This should be discussed.
 
 
SUGGESTED RESPONSES.............

#LC- Issue 24      
Jason White  5/5/2006   
W2       
3.1.1                 
ED       

Comment:
The content (i.e., everything within the scope of conformance), can and in many 
instances will consist of multiple Web units.

Proposed Change:  
Change \"the Web unit\" to \"every Web unit\", or \"every Web unit within the 
content\".
            
Proposed Resolution (– from Team B): 
 
Accept Partial 
 
Proposed Response ( – from Team B):
Response to reviewer:
The discussion of web unit versus content was a topic that was explorer laboriously 
by the working group over the years. Eventually, the working group decided to replace 
content with web unit in @@ ??. 'Web unit' will be replaced with 'web units' where 
appropriate in WCAG 2.0. 

 
Definition of Web Unit:
 
a collection of information, consisting of one or more resources, intended to be 
rendered together, and identified by a single Uniform Resource Identifier (such as 
URLs)
 
Note: This definition is based on the definition of Web page in Web Characterization 
Terminology & Definitions Sheet. The concept of simultaneity was removed to allow the 
term to cover interactive and scripted content.
 
Example 1: An interactive movie-like shopping environment where the user navigates 
about and activates products to have them demonstrated, and moves them to a cart to 
buy them.
 
Example 2: A Web page including all embedded images and media.
          

Definition of Content:
 
information to be communicated to the user by means of a user agent 
 
Note: This includes the code and markup that define the structure, presentation, and 
interaction, as well as text, images, and sounds that convey information to the 
end-user.
 
 
 
 
 
#LC- Issue 25      
Jason White  5/5/2006   
W2       
3.1.2                 
ED       

Comment:
The content (i.e., everything within the scope of conformance), can and in many 
instances will consist of multiple Web units.

Proposed Change:  
Change \"the Web unit\" to \"every Web unit\", or \"every Web unit within the 
content\".

            
Proposed Resolution (– from Team B): 
 
Accept Partial 
 

Proposed Response ( – from Team B):
Response to reviewer:
The discussion of web unit versus content was a topic that was explorer laboriously 
by the working group over the years. Eventually, the working group decided to replace 
content with web unit in @@ ??. 'Web unit' will be replaced with 'web units' where 
appropriate in WCAG 2.0. 
 
Definition of Web Unit:
 
a collection of information, consisting of one or more resources, intended to be 
rendered together, and identified by a single Uniform Resource Identifier (such as 
URLs)
 
Note: This definition is based on the definition of Web page in Web Characterization 
Terminology & Definitions Sheet. The concept of simultaneity was removed to allow the 
term to cover interactive and scripted content.
 
Example 1: An interactive movie-like shopping environment where the user navigates 
about and activates products to have them demonstrated, and moves them to a cart to 
buy them.
 
Example 2: A Web page including all embedded images and media.
          

Definition of Content:
 
information to be communicated to the user by means of a user agent 
 
Note: This includes the code and markup that define the structure, presentation, and 
interaction, as well as text, images, and sounds that convey information to the 
end-user.
 
* katie *

Katie Haritos-Shea

Section 508 Technical Policy Analyst

Communications Resource, Inc. (CRI)
CRI Email: kharitos-shea@cri-solutions.com

U.S. Department of Treasury - Financial Management Service
Information Resources - IT Policies & Standards Branch
Section 508 Support

Phone: 202-874-3203
FMS Email: mailto:Katie.Haritos-Shea@fms.treas.gov
Location: 10E24


CRI Headquarters
8280 Greensboro Drive, Suite 400
McLean, Virginia 22102
CRI Email: mailto:kharitos-shea@cri-solutions.com

Received on Wednesday, 17 May 2006 22:18:05 UTC