- From: John M Slatin <john_slatin@austin.utexas.edu>
- Date: Mon, 9 Jan 2006 16:16:40 -0600
- To: <public-wcag-teamb@w3.org>
Meeting information Date: Wednesday, 11 January 2006 Time: 10:00 AM-12:00 noon US Eastern, 7:00-9:00 AM US Pacific, 16:00-18:00 Central Europe Phone: +1.617.761.6200 Passcode: 92248 IRC: irc.w3.org port 6665, channel #wcag-teamb This is a full agenda! Please note that the most recent draft of WCAG 2.0 (the Guidelines doc) is actually the Editors' Draft dated 16 December 2005; techniques drafts (or portions) that haven't yet been approved by the full Working Group are in the WIKI. Overview of agenda - Clear remaining items related to 1.3 and put out a new survey on those items - Draft techniques for and clear category 1 issues for 2.4 and put out a survey Updated techniques for GL 1.3 (15 minutes) Review changes based on the 05 January call, approve for new survey to WG 1. Updated technique for SC 1.3.2 (http://lists.w3.org/Archives/Public/public-wcag-teamb/2006Jan/0032.html #start32) a. Updated technique for SC 1.3.3 (http://lists.w3.org/Archives/Public/public-wcag-teamb/2006Jan/0034.html ) 2. Updated technique for SC 1.3.6 (http://lists.w3.org/Archives/Public/public-wcag-teamb/2006Jan/0035.html ) Other items related to GL 1.3 (15 minutes) 3. Perceivable structures (issues 1795 and 1863), http://lists.w3.org/Archives/Public/public-wcag-teamb/2006Jan/0028.htmll 4. Accessible diagrams, http://lists.w3.org/Archives/Public/public-wcag-teamb/2006Jan/0033.html Guideline 2.4 (90 minutes) 5. Techniques and category 1 issues for GL 2.4 a. Loretta's list of tasks, http://lists.w3.org/Archives/Public/public-wcag-teamb/2006Jan/0031.html# start31 6. Proposed wording for SC 2.4.5 (meaningful link text, issue 1649); see end of this message for details 7. Proposed definition for "programmatic reference" (2.4.5); see end of this message for details a. The following proposals are related to SC 2.4.5. I've extracted them from the list discussion for convenience' sake, but read the threads on "meaningful link text" and bug 1649 to get the full context. Proposed wording for SC 2.4.5 David Macdonald's proposal, with a modification suggested by Andrew Kirkpatrick and supported by David <blockquote cite=http://lists.w3.org/Archives/Public/w3c-wai-gl/2006JanMar/0034.html #start34> <current> Each programmatic reference to another delivery unit or to another location in the same delivery unit, is associated with text describing the destination. </current> <proposed> Each hyperlink or other programmatic reference to another delivery unit or to another location in the same delivery unit, is programmatically associated with text describing the destination, unless the hyperlink or programmatic reference is part of an array of programmatic references to different versions (or views) of the same information. </proposed> </blockquote> Proposed definition for programmatic reference David Macdonald, with modifications suggested by Christophe and accepted by David <blockquote cite=http://lists.w3.org/Archives/Public/w3c-wai-gl/2006JanMar/0048.html #start48> programmatic reference <proposed> A relationship that enables the retrieval of a specified delivery unit or movement to another part of the same delivery unit. A function or control that can be used to cause a contextual transition. </proposed> </blockquote> "Good design is accessible design." Dr. John M. Slatin, Director Accessibility Institute University of Texas at Austin FAC 248C 1 University Station G9600 Austin, TX 78712 ph 512-495-4288, fax 512-495-4524 email jslatin@mail.utexas.edu Web http://www.utexas.edu/research/accessibility
Received on Monday, 9 January 2006 22:16:51 UTC