Accessibility Claims and Logos -- first thoughts

For discussion.

Here I set out a structure for the page about the level A claim.
--------------------------------------------

General notes
Every feature will be accompanied by a Browser-appropriate (sniffed by 
the server if possible, *not* scripted) keyboard combo where 
appropriate, plus link to full instructions.

WCAG1.0 A

+Common

1.	Alternative textual content [how to see this – details alt, title, 
longdesc]
2.	Colour vision is not required
      -	For example, links are denoted by more than just colour
3.	The document can be read without style sheets [how to do this]
4.	If there are data tables on this page, they will have row and column 
headings (and any other sets of data within the table) explicitly 
marked. [how to use these]
5.	If frames are used on this page, each frame will have a sensible 
title [how to read it]
6.	You can still use this page if you are surfing without javascript or 
any extra ‘plugins’ such as Flash

+Less common

1.	Changes of language should be dealt with gracefully
2.	Dynamic content will be accessible to devices that do not use scripting
3.	You don’t have to use imagemaps (simpler description?), the pages it 
links to will be listed more simply elsewhere on the page (usually near 
the imagemap itself)
4.	Multimedia presentations will provide an auditory description of 
important visual material. Any captions or auditory descriptions will be 
synchronised with the visual elements of the presentation

+AT-specific features
We could allow users to customise this page for their AT
JAWS (various versions)
Window Eyes (various versions)
Dolphin SuperNova (various versions)
IBM HomePage Reader (various versions)

Followed by...

Is your AT listed here? If not, email EMAILADDRESS stating its name and 
version number.




Regards

Liam
www.communis.co.uk

Received on Thursday, 7 September 2006 19:14:37 UTC