Guideline / Success Criterion
|
Category 1 Issues
|
Sufficient Techniques Completed?
|
Tests completed for sufficient
techniques?
|
Suggested Techniques to develop
(including tests)
|
Guideline 1.3
|
1605 - suggest removing
funtionality from GL text
|
|
|
|
1.3.1
|
- 1309 - definition of
programmatically determined
- 1795 - asks, "
Which structures, then, are "perceivable" for purposes of this
criterion"?
- 1863 - questions the current definition of structure.
|
yes
- Using
label elements to associate text labels with form fields.
- Using
title attributes to label form controls that can't be individually
labeled.
- Using headings.
- Absolute
positioning based on structural markup.
|
No - some draft tests avail. for
some HTML techniques 1,and 3 from the previous column but tests
need to be incorporated into technique document.
Items 2 and 4 have no tests yet.
.
|
- General technique - Using standard text
formatting conventions to allow structure in a simple text document to
be programmatically determined.
|
1.3.2
|
- 1309 - definition of programmatically determined
- #1607 and 1608 - Yvette and Gregg took an action item at
the December 15
meeting that should address both issues. ACTION: Yvette and Gregg
to
review 1.3.2 and 1.3.4 to address programmatically determined,
guaranteeing visual access at level 2 and making the working
consistent.
- 1879 - suggests an update to the intent section
|
|
Draft includes test information
|
- Situation A:
- Using text and text formatting (e.g. Unicode text with
color styling) AND
- Using the same colored text in the legend or instructions
introducing the use of color are probably the most appropriate.
*Depends upon outcome of issues 1607 and 1608.
- situation B - Using color and pattern
- situation C - Using features of the technology to
ensure that color attributes are available via the accessibility API.
|
1.3.3
|
#1766. Missing glossary entries
- variations in presentation of text
should be defined. Proposal at http://lists.w3.org/Archives/Public/public-wcag-teamb/2005Dec/0003.html
|
Yes
- Using em and strong for
emphasis.
- Using blockquote for quotations.
- draft general technique available at: http://lists.w3.org/Archives/Public/public-wcag-teamb/2005Dec/0004.html
|
No
|
|
1.3.4
|
#1607 and 1608 - Yvette and
Gregg took an action item at the December 15
meeting that should address both issues. ACTION: Yvette and Gregg
to
review 1.3.2 and 1.3.4 to address programmatically determined,
guaranteeing visual access at level 2 and making the wording
consistent. |
|
Draft includes test information
|
- Situation A: Including
a character cue whenever color cues are used (e.g. asterisk next to red
items).
- Situation B: Color and pattern technique created for 1.3.2
|
1.3.5
|
- 1309 - definition of programmatically determined
<>#1767 and 1789 which suggest that this SC should be at a
higher level. See research and proposal at:
http://lists.w3.org/Archives/Public/public-wcag-teamb/2005Dec/0010.html
|
No
|
No
|
- Including meaning-critical sequences in the
programmatically determined reading order AND
- preserving meaning-critical sequences in alternate
presentations.
|
1.3.6
|
- 1851 - proposal to promote this to level 1 to better map
with 508 req. for accessible forms
|
No
|
No
|
- Providing
textual identification of items that otherwise rely only on shape
and/or position to be understood.
|
|
|
|
|
|