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

INTRO and conformance edits

From: Gregg Vanderheiden <gv@trace.wisc.edu>
Date: Thu, 20 Apr 2006 02:54:25 -0500
To: <w3c-wai-gl@w3.org>
Message-ID: <00ed01c6644f$a5e3edd0$ee8cfea9@NC6000BAK>

We have cleaned up the intro and conformance sections and put in all the
edits we received. 


All edits are editorial.    Most are just grammar and typos. 


There were a few (9) additions or rewordings based on comments and
suggestions.  They are listed here.  


1)       changed "resources" to "content" (we kept switching between them.
Content is what our guidelines are about so we chose that)

2)       Added the following text to the section describing the organization
"To assist readers,  there is a How to Meet link beside every success
criterion that puts readers one click away from detailed information on that
success criterion and two clicks away from the specific technique
descriptions related to the success criterion."

3)       Changed reference to ATAG 1.0 to a reference to both 1.0 and 2.0 as
"The current version at the time of WCAG 2.0's release is Authoring Tool
Accessibility Guidelines 1.0.  However version 2.0 is nearing completion and
it based on WCAG 2.0.  The latest version of Authoring Tool Accessibility
Guidelines 2.0 can be found at http://www.w3.org/TR/ATAG20"

4)       Added a paragraph on role of user agents in response to comments
from UAAG.  
The Role of User Agents.  
Web content is always rendered by a user agent. A user agent is any software
that retrieves and renders Web content for users and includes Assistive
Technologies. Web content that conforms to WCAG 2.0 is most likely to be
rendered correctly by user agents that conform to the User Agent
Accessibility Guidelines (UAAG). For more information about the relationship
between WCAG 2.0 and other WAI accessibility guidelines, see Essential
Components of Web Accessibility (http://www.w3.org/WAI/intro/components).

5)       Added the following section to the end of the INTRO:


Important New Terms Used in WCAG 2.0

WCAG 2.0 includes several important new terms. These terms are defined in
the Glossary (Appendix A), and links to the definitions are provided
whenever these and other important terms are used in the success criteria.
The terms are introduced briefly here to make this new vocabulary easier to

"Web unit" is one of these important new terms. Web pages are the most
common type of Web unit. The broader term was chosen because it covers Web
applications and other types of content to which the word "page" may not
apply. A Web unit is any collection of information, consisting of one or
more resources, intended to be rendered together, and identified by a single
Uniform Resource Identifier (such as a URL).  For example, A Web page
containing several images and a style sheet is a typical Web unit.   

Several success criteria require that content (or certain aspects of
content) can be "programmatically determined." This means that the author is
responsible for ensuring that the content is delivered in such a way that
software access it.  This is important in order to allow assistive
technologies to recognize it and present it to the user, even if the user
requires a different sensory modality than the original. For example, some
assistive technologies convert text into speech or braille. This will also
allow content in the future to be translated into simpler forms for people
with cognitive disabilities, or to allow access by other agent based
technologies. This can happen only if the content itself can be
programmatically determined.  

WCAG 2.0 also introduces the term "baseline" which allows WCAG 2.0 to adapt
to changing technologies and to the needs of different countries and
environments.  Baselines are described in more detail in the conformance
section and in Questions and Answers about
<http://www.w3.org/WAI/intro/wcag20-baseline.php>  Baseline and WCAG 2.0.



6)        Changed description of 'baseline' 


The set of such technologies that an author assumes are supported and turned
on in accessible user agents is called a baseline. Developers must ensure
that all information and functionality of the Web content conforms to WCAG
2.0 assuming:

1.      that user agents support all the technologies in the baseline, but
no other technologies and

      2. that those technologies that are listed in the baseline are all


The set of such technologies that an author assumes are supported and turned
on in accessible user agents is called a baseline. Developers must ensure
that all information and functionality of the Web content conforms to WCAG
2.0 assuming that user agents support all of the technologies in the
baseline and that they are enabled.   Non-baseline technologies can also be
used, but all information and functionality of the Web content must conform
both with all non-baseline technologies turned on and with the technologies
turned off.  Both conditions are necessary since some users many have
browsers that support them while others may not.


7)      Changed a 3 cases of "Developer" to "Author" (again we kept
switching between)

8)      Per comment from Shawn - added an intro sentence to the section on
"use of technologies outside of the baseline". It reads as follows :    
Authors may use technologies that are not in the specified baseline provided
that the authors do not rely exclusively on those technologies for conveying
any information or functionality.  Also the presence of the other
technologies must not block the ability of the users to access the content
via the technologies in the baseline.   

9)      Changed  "chosen baseline"  to "specified baseline"









Gregg C Vanderheiden Ph.D. 
Professor - Depts of Ind. Engr. & BioMed Engr.
Director - Trace R & D Center 
University of Wisconsin-Madison 
< <http://trace.wisc.edu/> http://trace.wisc.edu/> FAX 608/262-8848  
For a list of our list discussions http://trace.wisc.edu/lists/

The Player for my DSS sound file is at http://tinyurl.com/dho6b 



Received on Thursday, 20 April 2006 07:54:52 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:59:42 UTC