Web and Software:December 20

Miscellanous

• Minutes from December 13, 2006 were approved.

Review of action Items from December 13th

1. IN PROCESS: Judy Brewer to send requirements for W3C copyright notices. WCAG working group is documenting how to reference WCAG standards.
2. Andi to check with Access Board staff to confirm that we can quote provisions in other standards.
3. Unassigned: Need a presentation on where graphical applications are going.
4. COMPLETE: Sean Hayes to write a proposal for a default minimum contrast.
   • Testing that luminosity meets a certain criteria (n:1) is easy and clear and can be applied to Web, Software, PDF, Java, and more.
   • Concern that a requirement for a certain luminosity ratio it is not testable due to dynamic content where you don't always know what the text is being rendered on.
   • Issue of glare mentioned but not discussed.
   • Need to determine how to handle the fringe cases where the contrast ratio may not be testable.
   • Documented in subcommittee deliverable for 21(j).
5. ONGOING: Gregg Vanderheiden to do some research with the low vision community to see what they want with regard to color and contrast.
6. COMPLETE: Randy Marsden to poll AT vendors to determine if 21(e) (consistent labeling of bitmap images) is still necessary for AT interoperability.
   • 21(e) Recommend removing 21(e) as a requirement, but list it as a sufficient technique if 21(d) is not implemented.
7. IN PROCESS: Jim Thatcher to write a proposal for a requirement on structure and/or reading order.
   • Proposal accepted
     1. Delete 1194.22(d) (Readable without style sheets)
     2. Add: (Meaningful sequence) When the sequence in which content is presented affects its meaning, a correct reading sequence is programmatically determinable.
   • programmatically determinable: can be determined by software from data provided in a user-agent-supported manner such that various user agents including assistive tecnologies can extract and present this information to users in different modalities
   • This definition and its connection to assitive technologies needs further discussion.

Discussion of valid and well-formed code

• Some think this should be removed. While writing valid code is important, many do not view this as an accessibility issue. Need specific examples where invalid code impacted accessibility.
• Some think we do need this requirement. Tools that generate invalid code can impact accessibility.
• WCAG "recommends" validity checking but requires only that the code parse correctly which is definitely an accessibility issue.
• No consensus to adopt WCAG language because of the concern that the language used ("unambiguous parsing") is in fact ambiguous.
• Continue discussion at the next meeting.

Summary of New Action Items

• Add a discussion topic on "programmatically determinable and the relationship with assistive technology".

Attendees

1. Jim Thatcher
2. Peter Korn, Sun Microsystems, Inc.
3. Nick Truesdell (IRS)
4. Chuck Letourneau (Industry Canada)
5. Shannon Rapuano (IBM)
6. Captioner
7. Robert Baker (SSA)
8. Mike Fratkin (SSA)
9. Eric Damery, Freedom Scientific
10. Andrew Kirkpatrick (Adobe)
11. Barbara Lybarger, Mass. Office on Disability
12. Sean Hayes (Microsoft)
13. Dana Simberkoff, HiSoftware
14. Jim Allan (W3C)
15. Curtis Chong
16. Kate Walser (SRA)
17. Dewi Gani
18. Michael Burks
19. Luke Kowalski (Oracle)
20. Amy Chen (Oracle)
21. Michael Cooper, W3C
22. Blene Bekure (LMIT)
23. Alex Li (SAP)
24. Jessica Brodey (ATIA)
25. David Oyola (Ricoh Corporation)
26. tom brett
27. Don Barrett
28. Carl Schmidt
29. Terry Weaver - GSA
30. Gregg - Trace