Note: Items in square brackets indicate success criteria numbering in the April 29 Draft.
Guideline 1 PERCEIVABLE.
Make Content Perceivable
Group One Checkpoints – Minimum
1-M1 [1.1] All non-text content that can be expressed in words
has a text equivalent of the function or information that the non-text content
was intended to convey.
Success Criteria – Required [All minimum level success
criteria from checkpoint 1.1.]
Recommended [All level 2 success criteria from checkpoint 1.1.]
1-M2 [1.2] Synchronized media equivalents are provided for
time-dependent presentations.
Success Criteria – Required [All minimum level success criteria
from checkpoint 1.2.]
Recommended [All level 2 success criteria from checkpoint 1.2.]
Listed below are items from group two which relate to this
checkpoint:
[All level 3 success criteria from checkpoint 1.2]
1-M3 [1.3] All content and structure are [separate or
separable from] available independently of presentation.
Success Criteria – Required [Item 2, minimum level from
checkpoint 1.3. (Number 1 is actually technique for achieving number 2 and/or is
redundant with number 2)]
[An example for color coding and an example of forms and labels should
be added to the informative information here.]
1-M4 [1.6] All characters and words in the content
can be unambiguously decoded.
Success Criteria – Required [All minimum level success criteria
from checkpoint 1.6]
Note: If a standard format for doing it can be achieved, we might require
that linkages to glossaries for all abbreviations and acronyms that are created
by the author or site be provided. We could also recommend that linkages
to any abbreviations, acronyms, etc. used by the authors also be provided.
We could also have a weaker recommendation for acronyms and abbreviations
appearing on the site that linkages to glossaries explaining all abbreviations
acronyms, etc. that appear in any documents on the site be
provided.
Recommended [Items 2 and 3 from level 2 of checkpoint 1.6.]
Group Two Checkpoints
1-E1 [1.4] Structure has been made
perceivable to more people through presentation(s), positioning, and
labels.
Success Criteria – Required [All minimum level success criteria
from checkpoint 1.4.]
Recommended [All level 2 and 3 success criteria from checkpoint
1.4]
1-E2 [1.5] Foreground content is easily
differentiable from background for both auditory and visual presentations
[required].
Success Criteria – Required [All minimum level success criteria
from checkpoint 1.5.]
Recommended [All level 2 and 3 items from checkpoint 1.5.]
Guideline 2 OPERABLE
Ensure that Interface Elements in the Content are Operable by Any User
Group One Checkpoints – Minimum
2-M1 [2.1] Ensure that all of the functionality is
operable at a minimum through a keyboard or a keyboard interface.
Success Criteria – Required [All minimum level success criteria
from checkpoint 2.1.]
Recommended [All level 2 and 3 items from
checkpoint 2.1. (there is only one)]
[Informative information. Add a definition of operable as meaning not using
mouse keys or an infinite tabbing on a long doc or other unreasonably
inefficient keyboard access. Add another definition that says something to the
effect that access is efficient. That is, mouse keys can’t be used as a
way to provide access via keyboard and if a document has a very large number of
links, some mechanism other than tabbing through them one at a time needs to be
provided]
2-M2 [2.2] Allow users to control any time limits on their
reading, interaction, or responses unless control is not possible due to nature
of real time events or competition.
Success Criteria – Required [All minimum level success criteria
from checkpoint 2.2]
Related group two items -- It is recommended , but not
required that, wherever possible, activities be designed so that time limits are
not an essential part of the activity. (e.g. alternate forms of
competition, testing, etc. that are not time based.)
Group Two Checkpoints
2-E1 [2.3] User can prevent screen
flicker.
Success Criteria – Required [All minimum level success criteria
from checkpoint 2.3]
Recommended [All level 2 and 3 items from checkpoint 2.3.]
Note: Because this checkpoint impacts on and limits types of
presentation, it is not included in group one. However, it is very
strongly recommended that anyone creating accessibility guidelines or
regulations consider this checkpoint for their required set.
2-E2 [3.1 and 3.2] Structure and/or alternate navigation
mechanisms have been added to facilitate orientation and movement in
content.
Success Criteria – Required In documents greater than 50,000
words or sites larger than 50 perceived pages, the following are provided.
- Additional hierarchical structure mark up
- Table of contents (or site map)
- Alternate display orders (or alternate site navigation mechanisms)
- (Items currently listed under Success Criteria for 3.1 and 3.2 should be
considered for here, but many/most of them should actually be moved to the
techniques document???)
Note: One of the reasons for combining these two is that they both get
at the same issue. Also, on many sites, it is becoming increasingly
difficult to tell when you are navigating within a site and when you are
navigating within a document. This will only increase over time.
Since the title of this thing is web content, it is recommended that these two
items be combined so that we are talking about web content versus separating
content from sites.
2-E3 [3.5] Methods are provided to minimize error and
provide graceful recovery.
Success Criteria – Required [All minimum level success criteria
from checkpoint 3.5.]
Recommended [All level 2 and 3 items from checkpoint 3.5.]
Guideline Three: UNDERSTANDABLE
Make it as easy
as possible to understand the content and controls
Group One Checkpoints
3-M1 [1.6 partial] Language of content can be
unambiguously determined.
Success Criteria – Required [Items 1 from level 2 and Level 3
success criteria from checkpoint 1.6.]
Changes in the language within a document are marked.
Recommended If the document as a whole is written in one
language, a tool can generally determine the language. If there is a
document on a site which is mostly all in one language, then the single document
in one language could be indicated.
3-M2 [4.3] The meaning of words, abbreviations, and
acronyms can be unambiguously determined.
Success Criteria – Required [ All one item from Level 1 of
4.3]
Recommended [All items from level 2 of 4.3 plus “cascading
dictionaries”]
Group Two Checkpoints
3-E1 [4.1 and 4.2] Content is written to be no more
complex than is necessary and/or supplement with simpler forms of the
content.
Success Criteria – Required [All minimum level success criteria
from checkpoint 4.1 and 4.2]
Recommended [All level 2 and 3 items from checkpoint 4.1 and
4.2]
3-E2 [3.3 and 3.4] Layout and behavior of content is
consistent but not identical.
Success Criteria – Required [All L1 items from Checkpoint 3.3
and 3.4]
Recommended [All level 2 and 3 items from checkpoint 3.3 and
3.4]
Guideline 4 ROBUST
Use web technologies that maximize the ability
of the content to work with current and future accessibility technologies
and user agents.
Group One Checkpoints
4-M1 [5.1] Technologies are used according to
specification
Success Criteria – Required [All minimum level success criteria
from checkpoint 5.1]
Recommended [Same as first Success Criteria above, except that
the exceptions for backward compatibility are removed.]
4-M2 [5.2] Ensure that technologies relied upon by
the content are declared and widely available.
Success Criteria – Required [All minimum level success criteria
from checkpoint 5.2]
Recommendation [All level 2 items from checkpoint 5.2.]
[In the definitions add a definition of “widely available” to include
something which is low cost and available in many?/most?
countries/languages.]
4-M3 [5.3 and 5.4] Technologies used for
presentation and user interface support accessibility or alternate versions of
the content are provided which do support accessibility.
Success Criteria - Required [All items in L1 of Checkpoint 5.3
and 5.4]
[Note: Many of the items listed in 5.3 are ambiguous and/or not
actually required for accessibility. We should carefully examine this
one. For example:
- What does device independence mean besides the items that are already
required in these guidelines?
- What does “include accessibility features” mean besides what is included
in this set of guidelines?
- Having interfaces for interoperability publicly documented simply means
that they have been posted on a website, it doesn’t necessarily mean that it
follows any standards or that anybody supports it and it doesn’t necessarily
make something accessible to anyone.
- Unless these operating system features are all listed specifically in this
standard, they should not be at a “required” level in the standard.
Cynthia
has re-written this section and we should look at her recommendations
carefully. These notes are based off our current post it draft.
Recommended [All level 2 and level 3 items from checkpoint 5.3
and 5.4 and perhaps some of the L1 items as well.]
Group Two Checkpoints
{NONE}