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

New CSS Techniques draft

From: Wendy A Chisholm <wendy@w3.org>
Date: Tue, 17 Jul 2001 15:41:56 -0400
Message-Id: <4.2.0.58.20010717152623.00cca560@localhost>
To: w3c-wai-gl@w3.org
Hello,

A new CSS Techniques draft is available at:
http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-CSS-TECHS-20010716/

The open issues and list of to do's is at:
http://www.w3.org/WAI/GL/WCAG20/css-tech-issues.html

The change log, which is not terribly detailed, is at:
http://www.w3.org/WAI/GL/WCAG20/css-techs-change-history.html

Note that instead of creating "checkpoint solutions" or 
"technology-specific checkpoints" or "evaluation criteria" I created an 
assessment section that will provide tests to perform (it's not yet 
complete).  I wrestled with writing evaluation criteria.  There was so much 
to update in this document, that I just began at the beginning.  There is 
still much to update, but it's a start.

This took much longer than I had expected because I ran into several issues 
with presenting the info - trying to find the most effective way.  I 
decided to take a more pedigogical approach.  I'm not sure if it works and 
I know that it doesn't yet meet all of the needs we are trying to 
address.  I also haven't completed the overhaul, but I wanted to get 
something out there for people to begin thinking about.

Primarily, I wanted to begin thinking about the differences between CSS for 
HTML and CSS for XML.  I want to make sure that the WCAG 2.0 checkpoints 
can handle the differences.

This process has raised a few questions:

1. Who wants to work with me on this? Should we start a sub-group and 
report results back to the list?  Kind of like what Katie and Loretta are 
doing with PDF?  However, I would like to publicly archive discussions, and 
tehrefore keep them on wai-gl, but with a subject heading of "[CSS-TECHS] 
subject X".

2. Linking between techniques documents will be interesting.

3. WCAG 2.0 currently says, "4.4 Design content so that when presentation 
effects are turned off or not supported the content is still usable. 
"  Which is still basically saying, "make sure the page is usable when CSS 
is turned off."  As we've discussed, this won't work for XML 
applications.  Is this an HTML-specific checkpoint?


I would like to give credit to a few key places that I found info and 
inspiration:
1. the wai-ig list, particularly comments from Charles Munat and David Woolley
2. the css1 and css2 specs
3. The National Cancer Institute's 508 Tutorial for style sheets: 
http://oc.nci.nih.gov/web508/tut-d.html
4. IBM's Accessibility Center info on style sheets: 
http://www-3.ibm.com/able/css.html


I look forward to comments.

--wendy
--
wendy a chisholm
world wide web consortium
web accessibility initiative
seattle, wa usa
tel: +1 206.706.5263
/--
Received on Tuesday, 17 July 2001 15:35:39 GMT

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