Outline and background for techniques for making content easier to
understand
Background
Augmentative and alternative communication (AAC)
http://212.187.34.208/wwaac/project/symbols.asp
Web Content Accessibility Guidelines (WCAG) 2.0
- WCAG 2.0 checkpoints that are most relevant:
- Checkpoint
4.1 Write as clearly and simply as is [appropriate / possible]
for the purpose of the content.
- Checkpoint
4.2 Supplement text with non-text content.
- Checkpoint
4.3 Annotate complex, abbreviated, or unfamiliar information with
summaries and definitions.
WWAAC
work packages,
most relevant:
Plain language
One method to satisfy checkpoint 4.1 is to use a "controlled language" or
a reduced word vocabulary. Many industries have controlled languages. For
example the aerospace industry uses controlled languages to write technical
manuals. Avi Arditti selected the following resources for introduction to
this topic.
Concept codes
The WWAAC has been working on the idea of standardizing concept codes to
facilitate translation of text into symbols. Lisa Seeman is also interested
in this and has produced an example schema.
W3C Annotea work
If text was annotated with concept codes, then a browser could request the
annotations (concept codes) for a web page display the appropriate symbols
instead of or alongside text. The Annotea project is W3C work to create an
annotation client (in Amaya) and methods to store and retrieve
annotations.
Contributors
- Avi Arditti - Voice of America
- Jonathan Chetwynd
- Lisa Seeman - Unbounded Access
- WWAAC folks
- Doeko Hekstra - Handicom
- Mike Clarke, Andrew Lysley, Mark Saville, David Colven - ACE Centre
Advisory Trust
- Colette Nicolle - Loughborough University
- Bengt Farre - Femtio Procent Data
- SWAD-E folks
- Charles McCathieNevile, Dan Brickley - W3C
- Libby Miller - ILRT/University of Bristol
$Date: 2002/07/11 20:59:12 $ Wendy
Chisholm