RE: Baseline description -- HERE IS WHAT I AM SENDING LATER THIS AM. LET ME KNOW IF YOU SEE ANY PROBLEMS WITH IT

Gregg,
 
I'm not sure about the phrase "established list of Web technologies,"
since it immediately raises the question "by whom?" I'd suggest deleting
the word "established." The idea that baselines can be established and
public comes in a little later under the point that only those who
understand accessibility, AT support, etc., should be developing
baselines.
 
 
Here's a slightly shorter version of the elevator speech:
 
 
<proposed>
Baseline is a new concept introduced in WCAG 2.0.  A baseline is a list
of Web technologies (HTML, CSS, etc.) that are supported in most
browsers,assistive technologies, and other user agents in a way that
meets the needs of people with disabilities.  Authors may use these
technologies in creating accessible Web content.

Baselines should only be created by those who understand accessibility
and Assistive Technology support.  Others should use established,
recognized baselines.      

</proposed>

 

About further notes:

#5 reads:

<blockquote>

5.                             Baselines should be specified by the same
entity that required conformance to WCAG.  If the author is required to
conform
to WCAG by a customer or government agency, then that same agency would
specify the baseline to be used.  


</blockquote>

 

This is good, but we may want to make it clear that the specified
baseline could be one that was created by some other entity that has the
necessary knowledge and understanding.

 

John

 

 

"Good design is accessible design"
John Slatin, Director
Accessibility Institute University of Texas at Austin 1 University
station Stop G9600
Austin, TX 78712, USA
Phone +1.512.495.4288 Fax +1.512.495.4524 cell +1.512.784.7533
email jslatin@austin.utexas.edu
www.utexas.edu/research/accessibility/ 

	-----Original Message-----
	From: w3c-wai-gl-request@w3.org
[mailto:w3c-wai-gl-request@w3.org] On Behalf Of Gregg Vanderheiden
	Sent: Wednesday, September 06, 2006 3:42 PM
	To: w3c-wai-gl@w3.org
	Subject: Baseline description -- HERE IS WHAT I AM SENDING LATER
THIS AM. LET ME KNOW IF YOU SEE ANY PROBLEMS WITH IT
	
	

	We have been working on a better short description of the
baseline concept.  Here is a version to comment on.

	 

	Easier to understand?    Harder to misunderstand?

	 

	Thanks

	
	Gregg

	 

	 


	Baseline basics 


	One sentence version:


	A Baseline is an established list of technologies (HTML, CSS,
etc.) that are accessible and that an author can choose from when
creating accessible Web content.

	 


	Elevator version (also to be used in Introduction): 


	Baseline is a new concept introduced in WCAG 2.0.  A baseline is
a list of Web technologies (HTML, CSS, etc.) that are supported in most
user agents (browsers, assistive technologies, etc.) in a way that meets
the needs of people with disabilities. Baselines should only be created
by those who understand accessibility and Assistive Technology support.
Others should use established, recognized baselines.     One way to
think about baselines is:  An established list of technologies (HTML,
CSS, etc.) that are accessible and that an author can choose from when
creating accessible Web content (because it has been determined that
there is sufficient accessibility support for them).

	 

	(PS the elevator version is something so short you can say it on
an elevator ride to give someone a rough idea of what you are talking
about)  

	 


	 


	Further notes on baselines 


	1.                             " Baselines" is an important new
concept to allow WCAG 2.0 that allow it to remain relevant over time and
adapt as new technologies come out and are supported by AT. 

	 

	2.                             A baseline is a list of Web
technologies (e.g. HTML, CSS, PDF etc.)

	*           NOTE: a baseline is NEVER a list of user agents or
AT (i.e. a baseline NEVER includes things like IE or Firefox or Jaws or
Home Page Reader)

	 

	3.                             To conform to WCAG, a Web Unit
(e.g. Web Page) must 

	*           1) conform to WCAG when all non-baseline
technologies used in the Web Unit are turned off in the browser; and
also 

	*           2) conform to WCAG when they are turned on in the
browser (i.e. the technologies not in the baseline should not interfere
with use of the accessibility of the (full) content that is implemented
with baseline technologies).  

	*         FOR EXAMPLE:   If Flash is not in the baseline - then
the Web Content must conform when Flash is turned off - and also when
FLASH is turned on.   (the Flash content does not have to be accessible
in either condition but the accessible alternatives must be able to be
accessed in both conditions).   

	 

	4.                             Baselines should only be created
by those who understand accessibility and Assistive Technology support.
Others should use established baselines.

	5.                             Baselines should be specified by
the same entity that required conformance to WCAG.  If the author is
required to conform to WCAG by a customer or government agency, then
that same agency would specify the baseline to be used.  

	 

	6.                             Baselines should be chosen to
represent the technologies that are currently supported on a widespread
basis by the user agents and especially Assistive Technologies. 

	 

	7.                             Baselines will evolve over time
as new technologies are supported by user agents and AT.  The Baselines
will evolve in ways that maintain access and increase user and author
options and flexibility over time.  They will also be backward
compatible as a result so changing baselines would not require old
content to be reworked. It would only provide new options for new
content. 

	 

	8.                             WAI will be creating guidelines
for creating baselines - as well as creating sample Baselines for 2007.