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

Re: EOWG work for this week: Baseline docs

From: Justin Thorp <justin@mycapitalweb.com>
Date: Thu, 4 May 2006 17:21:32 -0400
Message-Id: <6A78F7E0-AB39-4953-8062-9C710370B06A@mycapitalweb.com>
To: w3c-wai-eo@w3.org

Hi all,

I get this mixed idea of baselines from reading all of this.   
Baselines can be a list of things you must support  in order to be  
able to view this site.

This makes sense for things like javascript or flash.  You have to  
have a flash plug-in to be able at the baseline understand flash.   
JavaScript has to be turned on in order to understand an AJAX/DHTML- 
heavy web site.

I also get the sense that a baseline is just a list of technologies  
used to make the site.

With this definition, it makes sense to include stuff like CSS and  
JPEGs.

With the first definition of baseline, you shouldn't have to support  
CSS in order to see a web site because CSS is just presentational. So  
is CSS a baseline web technology? Can it be?

I read this stuff again and again and I go "huh?"

Sincerely,
Justin



On May 2, 2006, at 3:12 PM, Shawn Henry wrote:

>
> EOWG,
>
> At last week's teleconference we agreed to review the documents  
> related to Baseline this week:
> - About Baselines for WCAG 2.0 at http://www.w3.org/wai/wcag20/ 
> baseline/
> - Conformance to WCAG 2.0 at http://www.w3.org/TR/WCAG20/ 
> conformance.html
>
> Note that the editors might be able to make some edits to the  
> "About Baselines" document right away; therefore, we want to focus  
> review and comments on that document first. The "Conformance"  
> document will not be edited for a while, and so comments on that  
> can be submitted later.
>
> In order to facilitate quick turn around on comments and to make  
> the best use of EOWG teleconference time, please:
> - send your comments to the EOWG list before *Thursday* 4 May  
> *12:00noon* US Eastern (as mentioned last week, so that we can plan  
> teleconference discussion for this Friday)
> - clearly distinguish and put at the top issues the that you think  
> need EOWG discussion (versus clear-cut issues that can be submitted  
> directly to the documents Editors and Working Group)
> - clearly distinguish between high and low priority issues
> - as possible, include suggestions for addressing any issues that  
> you identify
>
> If you have copyedits (typos, mis-spellings, and such), send those  
> separately to:
> 	gv@trace.wisc.edu (not the EOWG list)
> Use a clear subject line such as: About Baselines - copyedits
>
> NOTE: We agreed that this first review would be how the "About  
> Baseline" doc communicates the issues of Baseline, and that we will  
> save the discussion of the concept of Baseline itself for later.
>
> Regards,
> ~ Shawn
>
Received on Thursday, 4 May 2006 21:22:23 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 10:33:42 GMT