Authoring Tools Working Groupcontents:
This page describes the method used to create the Authoring Tool Accessibility Guidelines and the Techniques for Authoring Tool Accessibility. Note that the process itself is in something of an overhaul mode.
This page is provided as an aid to those who are working on parts of the documents as editors, or translators, or are interested in doing so.
Last updated $Date: 2001/04/06 15:02:52 $ by Charles McCathieNevile
The main source document includes the information that is in the techniques and guidelines documents. A handful of simple transformations are used to
xsl:key to do it)The fundamental source is an XHTML document that uses various classes to mark up which documents various fragments will or won't end up in the result document. For example, there are status sections included for each result document, but all except the relevant one are removed. The default styles are included in a local stylesheet, which is removed from generated versions. Note that at the moment there are two source documents - the source that has more of the XSLT-oriented features, and the source that has more up-to-date content
tocdiv element with id toc is replaced by an
auto-generated table of contents. I would like to have a version of the
toc left in the source normally. Todo: make this happen
with the references and definitions (partially done already)sources - default style is { color:red }techniques - default style is { color:purple }guidelines - default style is { color:green }toc and notoch1 elements are not included in the table of contents -
it is expected that there is only one, for the human-readable document
title. For h2 and h3 elements, the default is
to include them in the contents - to bypass them give them a class of
notoc. This is reversed for h4,
h5, and h6 - to make these appear in the
contents they must have a class of toc.There is an XSL stylesheet to produce drafts of guidelines.
There are several XSL stylesheets that transform the main source to produce drafts of the Techniques for Authoring Tool Accessibility. They each use an XSL stylesheet that consists only of variable declarations, as a makefile. The "main techniques transformation" produces a document that includes all techniques, and there are additional transformations that are used to produce documents that only contain techniques relevant to a specific type of tool. (at the moment the only one of these that sort of exists is the Audio Video Tools transformation)
head section for a real one.guidelines and source.One of the goals in shifting to XSLT for producing the documents was to easily enable the production of specific views of the techniques document, which only contained information relevant to a particular topic. The first that has been created is a view for Audio and Video tools - including image editing or processing software as well as more tools for more complex multimedia. Other views have been identified by the group as desirable:
Each transformation works much like the main techniques transformation (they are based on it), but has additional selection based on the subclasses for specific views described above. In future, it may prove better to write these transforamtions in such a way that they can be selected with a parameter and included in the main techniques transformation. They work as follows:
head section for a real one.guidelines and source, and subclasses
specific to views as described above.There are some transformations that are used as components by the major transformations. These are included or imported by the XSL relevant rtansformation - some are specific to a particular transformation and some are more general.
There is an XSL stylesheet that creates a table of contents.
id attribute
it uses that to generate an a element with identical
name and id attribute values. Otherwise it
generates them automatically.div with the id of toc. It
replaces this with a table of contents generated as follows:
h2 elements. for each one found, copy the text
as a link, unless it has class="notoc".h3 elements that come before any
more h2 elements. For each one, add a reference (a bit
more indented) and a newline (<br/>), unless it has
class="notoc".h4 elements until the next h3
element, as above, but only including those that have
class="toc".h6. Then provide the reference for
the next h2 element, as above...There is a transformation to include relevant
definitions for the glossary. It replaces a div which has
id="glossary" with a glossary selected as follows:
rel="glossary"dt element with
subsequent dd elements.There are makefiles for each techniques transformation that consist of variable declarations. It may prove better to include some more transformations (especially basic include-or-remove ones) and have a single techniques transformation that includes the relevant makefile based on a parameter.
Revision: $Revision: 1.18 $
Copyright © 2000 W3C® (MIT, INRIA, Keio ), All Rights Reserved. W3C liability, trademark, document useand software licensingrules apply. Your interactions with this site are in accordance with our public and Member privacy statements.