Becky's summary of work needed to complete Guideline 1.3 for the Last Call draft.


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
 yes
  1. Using label elements to associate text labels with form fields.
  2. Using title attributes to label form controls that can't be individually labeled.
  3. Using headings.
  4. 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.
.
  1. General technique - Using standard text formatting conventions to allow structure in a simple text document to be programmatically determined. 

1.3.2
  1. 1309 - definition of programmatically determined
  2. #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.

No - three situations and only 1 completed CSS technique

 No
  1. Situation A:
    1. Using text and text formatting (e.g. Unicode text with color styling) AND
    2. 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.
  2. situation B  - Using color and pattern 
  3. 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
 Yes
  1. Using em and strong for emphasis.
  2. Using blockquote for quotations.
 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 working consistent. 		No
 No
  1. Situation A: Including a character cue whenever color cues are used (e.g. asterisk next to red items).
  2. Situation B: Color and pattern technique created for 1.3.2
1.3.5
  1. 1309 - definition of programmatically determined
  2. #1767 and 1789 which suggest that this SC should be at a higher level

 No
 No
  1. Including meaning-critical sequences in the programmatically determined reading order AND
  2.  preserving meaning-critical sequences in alternate presentations.

1.3.6

No
 No
  1. Providing textual identification of items that otherwise rely only on shape and/or position to be understood.