Checklist Prototyping Notes
I took an action item to work on prototyping checklists and have collected
some initial notes and ideas related to what information might be included in
checklists, how that information might be organized, where the issues are and
what needs to be done before we can begin discussing and developing
prototypes.
Checklist Items
As a starting point for discussion, I looked at guidelines 1.1 and 1.3 and
attempted to list all of the potential checklist items relevant to each
guideline. Note that in order to make checklist items into true/false
statements, some of the items in this list are slight variations of the
actual guidelines, success criterion or technique task.
At the guideline level, checklist items would include:
- Text alternatives are available for all non-text content. (Guideline
1.1)
- Information, functionality, and structure are separable from
presentation. (Guideline
1.3)
At the success criteria level, there are a number of additional cheklist
items to include: (note: guideline 1.1 items listed below are based on the June
24, 2004 Guideline 1.1 Revisions and are not linked since they have not
yet been incorporated into an updated working draft)
- Text alternatives are explicitly associated with non-text content (1.1
L1 SC1)
- For non-text content that is functional, such as graphical links or
buttons, text alternatives identify the purpose or function of the
non-text content. (1.1 L1 SC1a)
- For non-text content that is used to convey information, text
alternatives convey the same information. (1.1 L1 SC1b)
- For non-text content that is used to convey information, text
alternatives convey the same information. (1.1 L1 SC1c)
- For non-text content that is intended to create a specific sensory
experience, such as music or visual art, text alternatives identify and
describe the non-text content. (1.1 L1 SC1d)
- Non-text content that does not provide information or functionality is
marked such that it can be ignored by assistive technology. (1.1 L1
SC1d)
- For multimedia content, a text document (similar to a play script) is
provided that includes descriptions of all important visual information
as well as transcripts of dialogue and other important sounds. (1.1
L3 SC1)
- Structures and relationships within the content can be derived
programmatically. (1.3
L1 SC1)
- Emphasis can be derived programmatically. (1.3
L1 SC2)
- Any information presented through color is also available without color
(for example, through context or markup or coding that does not depend on
color). (1.3
L1 SC3)
- Information presented using color is also available without color and
without having to interpret markup (for example through context or text
coding). (1.3
L2 SC1)
At the techniques level, the following checklist items could be included
(note: these items are a rewrite of existing tasks as true/false statements
and are based on the list of techniques associated with guidelines 1.1 and
1.3 in the June 2
draft of success criteria to techniques mapping.)
- The alt attribute is used on each image element. (HTML
10.1)
- The body of each object element includes a text alternative. (HTML
10.4)
- HTML and CSS are used in place of text in images. (HTML
10.11)
- Client-side image maps are used when regions can be defined with a
geometric shape. (HTML
11.1)
- Redundant text links are provided for each region of server-side image
maps. (HTML
11.2)
- Deprecated Technique: (HTML
11.3) [see also?]
- Each area element includes a text alternative. (HTML
11.4)
- Content rendered in frames includes a noframes element. (HTML
13.3)
- A text alternative is provided for each object element. (HTML
12.1) [already covered by 10.4?]
- The alt attribute is used on each embed element. (HTML
12.3) [ref to use-spec? note about browser support?]
- Images used as submit buttons include a text equivalent. (HTML
14.7) [redundant with 10.1?]
- Text transcripts are provided for all audio and video content. (GATEWAY
1.1.3)
- Text transcripts of audio content allow users to (GATEWAY
1.5.2)
- Detailed information about non-text content that uses the img elemement
is available in a separate file and referenced using the longdesc
attribute. (HTML
10.5)
- Detailed information about non-text content that uses the object
elemement is available in the body of the tag, providing links to other
content where appropriate. (HTML
10.6)
- Deprecated Technique: (HTML
10.7) [see also?]
- Non-text content is described in the document (HTML
10.8)
- Non-text content rendered using the embed element includes a noembed
element. (HTML
12.2)
- Links to frames that load inaccessible formats are sufficiently
descriptive. (HTML
13.5)
- Accessible alternatives are provided for each iframe element. (HTML
13.6)
- The longdesc attribute is not used on iframe. (HTML
13.7)
- A text equivalent is available for all non-text content generated by
style sheets. (CSS
2.1)
- Header elements (H1 through H6) are used, in order, to define the
structure of documents. (HTML
3.1)
- Future technique: (HTML
5.6) [see also?]
- The blockquote element is used to mark up block quotations. (HTML
5.7)
- Markup, rather than images, is used to convey information wherever
possible (HTML
5.9)
- Structural elements are used to identify structure (HTML
5.12)
- Ordered lists are formatted so that items can be followed logically (HTML
6.1)
- The caption element is used to describe the nature of data tables (HTML
7.1) [optional technique - see also?]
- The thead element is used to group repeated table headers, the tfoot
element is used to group repeated table footers and the tbody element is
used to identify other groups of rows. (HTML
7.5) [optinoal - see also?]
- The colgroup and col elements are used to group columns (HTML
7.6) [optional technique - see also?]
- The scope attribute is used to specify the set of data cells for which
each header cell provides header information (HTML
7.7)
- The headers attribute is used on each data call to associate a list of
header cells that provide header information (HTML
7.8)
- The axis attribute is used to place a cell into a conceptual category.
(HTML
7.9)
- The th element indicates which cells contain header information. (HTML
7.11)
- The strong and em elements are used to denote emphasis. (HTML
5.1)
- Style sheets are used to style text. (CSS
1.11) [2x]
- Style sheets are used to create layout, positioning, layering and
alignment. (CSS
3.1)
- CSS properties are used to control font characteristics. (CSS
1.2)
- CSS properties are used to specify colors (CSS
1.5)
- text-transform is used to change case (CSS
1.13)
Additionally, there may be a number of checklist items that could be
incorporated into the checklists in some form. The following list comes from
OpenAccessibility
Checks:
Views and Sorting
Sorting
There are a number of different considerations related to determining the
list questions to be included in a checklist. I've listed a few of dimensions
by which checklist content might be affected below.
- technology used (HTML, CSS, etc.)
- guideline
- baseline (where baseline is set may have an impact on which techniques
you need to do)
- level - checklist content will change based on whether conformance goal
is to achieve A, AA, AAA
- scope (ex. if claim is for a single page, then techniques and questions
related to document collections fall out)
Example sorting questions:
- Does the content include non-text content? (If yes, continue to
question X, if no, continue to question y)
- Does your content include multimedia? (if no, skip all checklist items
and techniques associated with guideline 1.2)
- What level of compliance to WCAG 2.0 are you testing for?
- Which technologies do you use in your content?
- What browsers/user agents are you developing for?
- Are you making a claim for a site or for a single page?
Questions:
- How to reference informative, optional or future techniques?
- What impact will the question of normative vs. informative checklists
have on techniques? Will certain techniques become normative as a
result?
- How/where do tests/checks fit in? Should checklists include lists of
what not to do? (ex. alt text can't be a file name or placeholder
text)
- Is the list above complete? Are there techniques/concepts missing?
Action items:
- Identify sufficient techniques for each criterion. Our current
technqiues drafts include a number of types of techniques. Some are
already labeled as optional or deprecated. However, it is not currently
clear which techniques sufficient or required for conformance within a
given technology.
- Identify relationships and dependencies between techniques and include
references (see also, depends on)
- Create checlists mockups that examine how checklist items might be
grouped and organized.
- Include checklist item information in DTD (not clear whether it would
be best to store this data in the techniques DTD or in a checklist
DTD)