This is a piece of a draft for the WAI Authoring Tools techniques document. It is provided here for the WCAG group to look at differnt icons used, and to try to identify why a particular group of icons might be more accessible. There are several different icons each associated with the categories proposed for authoring tools.There is a piece of the techniques document to show how the images are used. There is also a collection of the icons we have in a table.
Last modified $Date: 2001/12/08 08:56:09 $ - this needs work, like making it accessible (long descriptions for the images).
Note: For the purposes of these techniques, authoring tools may fall into one or more of the following categories. For example, an HTML authoring tool that allows the user to create JavaScripts will fall under two categories, Markup Editing Tools and Programming Tools. A SMIL editor that includes a text-only view of the markup and a preview mode would be considered both a Markup Editing Tool and a Multimedia Creation Tool.
I have included some combinations from the different icon sets for comparison
Set 1: Help the author create structured content and separate information from its presentation. Because this ATAG checkpoint has a relative priority, it is the priority of the relevant WCAG checkpoints that determines the level of conformance of the tool to the ATAG checkpoint:
Set 3: , , , ((WCAG 2.1, P1) Ensure that all information conveyed with color is also available without color.
Set 4: , , , Ensure that something very useful happens when you are checking how good icons are
Set 5: , , , , Ensure that something very useful happens when you are checking how good icons are
Set 1s: (WCAG 7.5, P2) Until user agents provide the ability to stop auto-redirect, do not use markup to redirect pages automatically. Instead, configure the server to perform redirects.
Set 4s: , , , There are various techniques for implementing things in authoring tools, and they really are a good diea to make sure that the Web actually works for everyone.