Web and Software:January 3

Miscellaneous

• Minutes from December 20, 2006 approved.
• Plan to have a face to face meeting during the TEITAC meeting February 6 - 8th.
• Calendar - January 31st meeting rescheduled to January 30th at 1 PM Eastern time.
• Plan for deliverables to February TEITAC meeting
  • Remaining topics to address:
    • API proposal and gaps in Web requirements - today
    • Other General Issues
    • Content
  • Deliverables on recommended changes to 1194.21 and 1194.22 - draft available by January 17th, resolve issues by January 31st.

Review of action items from December 20th

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. ONGOING: Gregg Vanderheiden to do some research with the low vision community to see what they want with regard to color and contrast.
5. COMPLETE: Add a discussion topic on "programmatically determinable and the relationship with assistive technology". This has been added to the General Issues page.

Disussion on the API proposal

• We discussed whether the proposal will address emerging converging devices (e.g. newer telecomm devices with their own OS. some work with AT, but in a different manner). It was felt the proposal would address these technologies.
• We should recommend more frequent updates to 508 in the future.
• Concern that proposal is not organized like the ISO standard. Expect European countries to adopt ISO or something very similar to ISO. Since the proposal builds on what is in ISO, it should be organized the same way to make reporting to both standards easier.
• Discussion about why the issues with ISO were not covered in the ISO committee versus raising the issues here in the 508 committee. Some of the companies raising issues (Sun, Adobe, etc) were not on the ISO committee.
• Discussion about why ISO didn't consider some of the extensions like the API proposal. Only one person attended the call who participated in the ISO standard. He said that by the time he joined, they were only accepting minor changes.
• Some feel that the extensions could be covered in sufficient techniques. Others disagree but think the sufficient techniques might describe specific APIs that are known to meet the requirements.
• Disagreement about whether or not this is even needed in 508.
• SUMMARY: Reorganize the API proposal to a more ISO-like format/framework and then add more detail on the gaps in ISO. This leads to better harmonization with 508 and ISO since European countries are expected to adopt ISO.
  • Sean Hayes and Rich Schwerdtfeger will join this work group with Peter Korn, Andrew Kirkpatrick, and Luke Kowalski. Eric Damery will get the right person from Freedom Scientific to work with the team as well so we have representation from ATIA.
  • Structure will harmonize with the ISO standard - similar structure and strengthen to address gaps. New proposal to include a clear summary of the differences in the API proposal vs ISO. It may be too late to work the enhancements back into the ISO standard since the final ISO draft is expected in February.

Discussion on gaps in Web requirements

Valid and well-formed code

• WCAG definition of parsed unambiguously provided.
• Tabled until next week due to absence of person raising the issue.

Keyboard operation

• WCAG 2.0 has keyboard requirement. Support for idea in general.
• Concern raised about the efficiency of keyboard actions. More complicated for Web vs software since application on browser on many different underlying platforms and those platforms have different keyboard 'gestures'.
• Concern raised about systems that don't have a keyboard.
• Action:Andi will develop a proposal that builds on WCAG keyboard requirement (2.1.1) but includes "when software is designed to run on a system that has a keyboard" to address concerns about keyboard interaction for voice/phone applications.

Page and element refresh

• Related to the API discussion and API proposal addresses this issue.
• No further action planned.

Hidden elements

• AT now handles "hidden" styles. so no need to add a new requirement for hidden elements.

Error handling techniques

• WCAG 2.5.1 requires that errors be identified to the user.
• Don't want to prescribe how error handling should be done. WCAG 2.0 sufficient techniques provide alternative strategies from which authors can choose.
• Action: Andi to post WCAG 2.5.1 for error handling as a base proposal including a pointer to the sufficient techniques.

Summary of new action items

• Andi to develop proposal for keyboard requirement for Web.
• Andi to post WCAG 2.5.1 for error handling as a base proposal including a pointer to the sufficient techniques.

Attendees

1. Dewi Gani - SAP
2. Tom Brett
3. Peter Korn - Sun Microsystems, Inc.
4. Curtis Chong - National Federation of the Blind
5. Andi Snow-Weaver - IBM
6. Don Barrett - Department of Education
7. Nick Truesdell - IRS
8. Captioner
9. Barbara Lybarger, Mass. Office on Disability
10. Shannon Rapuano - IBM
11. Eric Damery, Freedom Scientific
12. Sean Hayes - Microsoft
13. Rex Lint - ITAA
14. Luke Kowalski - Oracle
15. Dana Simberkoff - HiSoftware
16. Laura Ruby - Microsoft
17. Andrew Kirkpatrick - Adobe
18. Randy Marsden - ATIA
19. Ken Kipnes - Oracle
20. Amy Chen - Oracle
21. Rich Schwerdtfeger (IBM)
22. Jessica Brodey - ATIA
23. Earl Johnson - Sun
24. Michael Cooper - W3C
25. David Oyola - Ricoh Corporation
26. Blene Bekure - LMIT
27. Donald Evans - AOL LLC
28. Terry Weaver - GSA
29. Jessica Brodey - ATIA
30. Judy Brewer - W3C/WAI