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

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

From: Gregg Vanderheiden <gv@trace.wisc.edu>
Date: Fri, 8 Sep 2006 00:03:51 -0500
To: "'Makoto Ueki'" <makoto.ueki@gmail.com>
Cc: <w3c-wai-gl@w3.org>
Message-ID: <008601c6d304$2ddf0bc0$066fa8c0@NC6000BAK>

They will be Sample Baselines.  And we will also be doing a document to
discuss how to make them.  Others can then make them to fit other contexts. 

Gregg

 -- ------------------------------ 
Gregg C Vanderheiden Ph.D. 
Professor - Ind. Engr. & BioMed Engr.
Director - Trace R & D Center 
University of Wisconsin-Madison 
The Player for my DSS sound file is at http://tinyurl.com/dho6b 
 

> -----Original Message-----
> From: w3c-wai-gl-request@w3.org 
> [mailto:w3c-wai-gl-request@w3.org] On Behalf Of Makoto Ueki
> Sent: Thursday, September 07, 2006 11:00 PM
> To: Gregg Vanderheiden
> Cc: w3c-wai-gl@w3.org
> Subject: Re: Baseline description -- HERE IS WHAT I AM 
> SENDING LATER THIS AM. LET ME KNOW IF YOU SEE ANY PROBLEMS WITH IT
> 
> 
> Hi Gregg,
> 
> <blockquote>
> > 8.                             WAI will be creating 
> guidelines for creating
> > baselines - as well as creating sample Baselines for 2007.
> </blockquote>
> 
> I have a question on this. Will WAI also do that for 
> Japanese? What about the other languages than English? The 
> user agents' support would be different among the languages.
> 
> - Makoto
> 
> 
> 2006/9/7, Gregg Vanderheiden <gv@trace.wisc.edu>:
> >
> >
> >
> > 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.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> 
> 
> 
Received on Friday, 8 September 2006 05:03:51 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:46 GMT