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

[CSS-TECHS] goals and audience of this document

From: Wendy A Chisholm <wendy@w3.org>
Date: Thu, 19 Jul 2001 13:38:16 -0400
Message-Id: <>
To: Jo Miller <jo@bendingline.com>, w3c-wai-gl@w3.org

>Before I suggest any wording, though, I should make sure I'm on the same 
>page as the rest of the group. I'm interested in knowing the set of 
>specific needs that the CSS Techniques document aims to address (and also 
>what it does not aim to address, i.e., things that are more appropriately 
>covered elsewhere).

Good question.
We haven't discussed this for the technology-specific stuff, but for the 
higher level guidelines/checkpoints.  Therefore, my initial thoughts, and I 
think we can apply these thoughts to all of the technology-specific documents:

We have several audiences:
content developers,
policy makers, managers, and disability community advocates,
authoring tool developers,
Testers and evaluators,
developers of evaluation tools

The goals of the CSS-TECHS for content developers (I'd say this is our 
primary audience):
1. To give developers a good idea of what accessible CSS looks like.  We 
will do this through prose, examples, screen shots, and links to live 
2. To help developers evaluate if their use of CSS is accessible.  They can 
do this by comparing their results with the examples, screen shots, etc. 
but also through the assessment sections (which are still need a lot of work).

Overall, developers need to understand what makes a site accessible.  We 
hope they do this by reading the Guidelines and Checkpoints in the top 
layer.  Then, when they begin looking at using CSS and how to do it such 
that it satisfies the Guidelines and Checkpoints, it will be clear from the 
CSS Techniques doc.

The goal of the CSS-techs (for policy makers, managers, and disability 
community advocates):
Is to help them understand the high-level issues with CSS:  the possible 
accessibility issues, but also the benefits.

The goal of the CSS-techs (for authoring tool developers) is similar to 
content developers: understand what makes accessible CSS so that their 
tools will generate accessible code.

The goal for users is to be able to create their own style sheets if they 
want to (the last appendix) and understand the issues so that they can make 
suggestions to developers (advocate for accessibility).

Testers and evaluators of content have similar needs to the content 
developers, just as developers of evaluation tools have similar needs to 
authoring tool developers.

Have I missed any body?  Is this trying to tackle too much? Does this 
answer your question?

>>Would you like to begin working on the reasoning for each item?
>Sure, at least for items for which I know the reasoning. In some cases I 
>don't. (I'm definitely not the world's greatest CSS expert.)

any bit helps.  I and others can help fill in the gaps.

wendy a chisholm
world wide web consortium
web accessibility initiative
seattle, wa usa
tel: +1 206.706.5263
Received on Thursday, 19 July 2001 13:27:28 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 16 January 2018 15:33:38 UTC