Potential Checklist Items for Guidelines 1.1 and 1.3
The following is an attempt to list all of the potential checklist items
relevant to guidelines 1.1 and 1.3. In order to make the 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.
Guidelines
At the guideline level, checklist items would include:
- Text alternatives are provided for all non-text content. (Guideline 1.1)
- Information, functionality, and structure are separable from
presentation. (Guideline
1.3)
Success Criteria
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
upcoming October 8, 2004 guidelines draft - some criteria are not linked
since they have not yet been incorporated into an updated working draft.)
- For all 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 SC1)
- For all non-text content that is used to convey information, text
alternatives convey the same information. (1.1 L1 SC2)
- 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 SC3)
- For multimedia and time-dependent interactive content, text
alternatives identify the content and media alternatives are provided as
described in guideline 1.2. (1.1 L1 SC4)
- Non-text content that does not provide information, functionality,
sensory experience and is neither multimedia nor time-dependent
interactive content, is marked such that it can be ignored by assistive
technology. (1.1 L1 SC5)
- Text alternatives are explicitly associated with non-text content (1.1
L1 SC6)
- 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)
Techniques
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 October 8, 2004 techniques drafts.)
General
HTML
- Text alternatives for images used as links describe the function (or
destination?) of the link (HTML
9.2) [A]
- Adjacent image and text links that point to the same resource are
combined. (HTML
9.3) [good advice? AAA? - not always easy to combine them -resolved:
@@ michael remove mapping to guideline 1.1 (also maps to 3.2)]
- The alt attribute is used on each image element. (HTML
10.1) [A - change "used" to "is present" or exists? match html
spec?]
- The body of each object element includes a text alternative. (HTML
10.5) [many user agent/AT issues that render this technique ineffective - ok to include a link to alternative or include
alternative in body of page? label as future technique - add a technique
describing what is in use today?]
- HTML and CSS are used in place of text in images. (HTML
10.12) [issue: is there a level at which we are effectively requiring CSS for
conformance? Optional? AA? AAA? (no resolution)]
- Client-side image maps are used when regions can be defined with a
geometric shape. (HTML
11.1) [A - "or relationship" with 11.2]
- Redundant text links are provided for each region of server-side image
maps. (HTML
11.2) [A -- question: if regions can't be defined with a geometric shape (per HTML 11.1, is it possible to provide alternatives at all?]
- Reduntant text links are provided for each active region of client-side
image maps (deprecated) (HTML
11.3) [Optional]
- Each area element includes a text alternative. (HTML
11.4) [A]
- Programmatic objects have text-equivelants. (HTML
12.4) [A issue: depends whether programmatic objects are included in def. of non-text content - req. label of function at minimum]
- Content rendered in frames includes a noframes element. (HTML
14.4) [A]
- A text alternative is provided for each object element. (HTML
12.5) [A - user agent issues related to how and explicit association - noted in ednote under HTML 12.4]
- Non-text content rendered using the embed element includes a noembed
element. (HTML
12.8) [A - UA issues may require altnative techniques or strategies (ex. d-link or elsewhere on the page strategies)]
- The alt attribute is used on each embed element. (HTML
12.9) [A - UA issues may require altnative techniques or strategies (ex. d-link or elsewhere on the page strategies)]
- Images used as submit buttons include a text equivalent. (HTML
15.8) [A]
- 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.6) [A - "or" relationship with d-link 10.8 or in the same document 10.9?]
- 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.7) [A - "or" programmatic object is directly accessible? meets baseline?]
- d-link technique (deprecated) (HTML
10.8) [A - "or" relationship with longdesc 10.6 or described in the same document 10.9?]
- Non-text content is described in the document (HTML
10.9) [A - "or" relationship with longdesc 10.6 or d-link 10.8?]
- Links to frames that load inaccessible formats are sufficiently
descriptive. (HTML
14.6) [A - UA Issues? issue: task talks about links but description talks about longdesc attribute on frames]
- Accessible alternatives are provided for each iframe element. (HTML
14.7) [A - UA Issues? issue: task talks about links but description talks about longdesc attribute on frames]
- The longdesc attribute is not used on iframe. (HTML
14.8) [Optional? - maps to a level 1 criterion, but doesn't do any harm when used]
- The noscript element is used to provide alternatives for each script
element (HTML
16.1) [A - issue: unclear whether noscript should be required in each case]
- The address element is used to define a page's author (HTML
1.3) [Optional - maps to L1 criterion, but not clear whether there is a specific accessibility issue here.]
- Header elements (H1 through H6) are used, in order, to define the
structure of documents. (HTML
3.1) [A - open issues on this include use of H1 first on the page, and using heading levels out of order]
- The strong and em elements are used to denote emphasis. (HTML
5.1) [A - maps to a L1 criterion, are there exceptions?]
- Future technique: short quotations (HTML
5.6) [Optional]
- The blockquote element is used to mark up block quotations. (HTML
5.7) [A]
- Markup, rather than images, is used to convey information wherever
possible (HTML
12.2) [Optional - issue: how do we define when something like this is possible?]
- Structural elements are used to identify structure (HTML
5.13) [Optional? issue: many of the items in this list are not supported by user agents and AT - label as future technique?]
- Ordered lists are formatted so that items can be followed logically (HTML
6.1) [A? UA support?]
- The caption element is used to describe the nature of data tables (HTML
7.1) [Optional]
- 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)
- The colgroup and col elements are used to group columns (HTML
7.6) [Optional]
- The scope attribute is used to specify the set of data cells for which
each header cell provides header information (HTML
7.7) [A "or" with 7.8 and 7.9]
- The headers attribute is used on each data call to associate a list of
header cells that provide header information (HTML
7.8) [A "or" with 7.7 and 7.9]
- The axis attribute is used to place a cell into a conceptual category.
(HTML
7.9) [A "or" with 7.7 and 7.8]
- The th element indicates which cells contain header information. (HTML
7.11) [A]
- CSS, not HTML is used to style documents (HTML
13.1) [Optional? issue: another item that raises the question of requiring CSS at some level]
CSS
- A text alternative is available for all non-text content generated by
style sheets. (CSS
6.1) [A]
- em or % are used for properties that need to change. (CSS
1.1) [AA - issue: would this be true if alternate CSS were available on the page?]
- px is used for properties that do not need to change. (CSS
1.2) [AA - issue: do we mean to exclude other measurements (ex. pt)?]
- 'text-indent', 'text-align', 'word-spacing', 'font-stretch' are used to
control spacing and 'text-align: center' is used instead of the
deprecated html:center element. (CSS
5.2) [AA? issue: what are the fallbacks if CSS is not used? (ex. <p|div align="center">]
- Style sheets are used to style text. (CSS
1.11) [? closely related to HTML 10.12, should this be part of checklist? included only if CSS is not part of checklist?]
- font-family, font-size, font-size-adjust, font-stretch, font-style,
font-variant, and font-weight are used to control font characteristics.
(CSS
8.2) [AA - should this be "modify" or "vary" font characterstics? issue: in example, how does end user or AT user know the difference between "primary" and "secondary" classes?]
- 'color,' 'background-color,' 'border-color,' 'outline-color,' and
dynamic pseudo-classes are used to specify colors (CSS
7.2) [A - if CSS, then A?]
- text-transform is used to change case (CSS
9.4) [Optional? - maps to level 1, but is this an accessibility issue?]
- text-indent is used to indent text (CSS
9.2) [Optional? and relationship with using structure - accessibility issue?]
Test Suites
Additionally, there may be some checklist items that are included from the
draft
test suites.
@@ sort into required tests and optional tests in techniques to tests mapping?
Guideline 1.1
Guideline 1.3