- From: Gregg Vanderheiden <gv@trace.wisc.edu>
- Date: Wed, 17 Sep 2003 14:48:29 -0500
- To: w3c-wai-gl@w3.org
Thursday, 18 September at 2000 UTC (4 PM US Eastern, 10 PM France, 6 AM Eastern Australia) on +1-617-761-6200, passcode 9224 IRC: irc.w3.org 6665, channel #wai-wcag Agenda: [group 1 - issues from past agendas] Checkpoint 1.1 issues: (170,322,373,401,404) [1] Questions: 1. What do we want to require and at what level in terms of accessibility for advertising which is pushed onto a web site? (Open Issue 170, from June 2002) 2. Do we require a for full text script of all movies? (Open Issue 322) Editorial and Proposals: *add “using text-to-speech synthesis” to the end of the first bullet under benefits (Open Issue 373) *simplify and clarify checkpoint text (Open Issue 401) *include examples of when, where and how to use text-equivalents (Open Issue 404) Checkpoint 2.1 Issues: (262,410,346) [2] Questions: 1. What if something is designed so that it ONLY works on a device for which there is no AT? (Open Issue 262) 2. What is meant by "minimum" in "All functionality is operable at a minimum..." (Open Issue 410) Editorial and Proposals: *Proposed Definition of Operable (Pending Issue 346) Checkpoint 3.1 Issues: (172,355,380,417) [3] Questions: 1. checkpoint about use of standard character set (Open Issue 172 – from June 2002) 2. should 3.1 be moved to extended? (Open issue 355) 3. use of the language attribute should make this checkpoint unnecessary (Open Issue 380) 4. Other mechanisms to identify primary language (Open Issue 417) [end past agenda issues] [group 2 - issues stemming from public comments] Public Comments that apply to the draft in general: These are new, unassigned issues resulting from our recent call for review period. Suggestions and comments (357, 391, 358, 362, 378, 392, 393, 399, 398) [4]: * add link at top of page to jump to TOC (Open issue 357) * [was *.*] is confusing (Open issue 391) * Decrease reliance on WCAG 1.0 (Open issue 358) * replace "Benefits" with "Who is benefited?" (Open issue 362) * wording suggestion for guideline 2 (Open issue 378) * change robust to robustness (Open issue 384) * Better definition of "audience" (Open issue 392) * Migrating from WCAG 1.0 to WCAG 2.0 (Open issue 393) * Graphical representation of document structure and conformance (Open issue 395) * Replace "cannot see" with "see well" (Open issue 399) * an icon for each design principle (Open issue 398) Questions (388, 400, 432) [5]: * focus shift from accessibility to universal access in WCAG 2.0? (Open issue 388) * What is meant by "perceivable?" (Open issue 400) * Addressing the needs of older people (Open issue 432) [end public comments issues] References used in this email: [1] <http://trace.wisc.edu/bugzilla_wcag/buglist.cgi?bug_id=170%2C322%2C373%2C40 1%2C404%2C320%2C332%2C333&bugidtype=include&order=bugs.bug_id> [2] <http://trace.wisc.edu/bugzilla_wcag/buglist.cgi?bug_id=262%2C410%2C346&bugi dtype=include&order=bugs.bug_id> [3] <http://trace.wisc.edu/bugzilla_wcag/buglist.cgi?bug_id=172%2C355%2C380%2C41 7&bugidtype=include&order=bugs.bug_id> [4] <http://trace.wisc.edu/bugzilla_wcag/buglist.cgi?bug_id=357%2C%20391%2C%2035 8%2C%20362%2C%20378%2C%20392%2C%20393%2C%20399%2C%20398&bugidtype=include&or der=bugs.bug_id> [5] <http://trace.wisc.edu/bugzilla_wcag/buglist.cgi?bug_id=388%2C%20400%2C%2043 2&bugidtype=include&order=bugs.bug_id>
Received on Wednesday, 17 September 2003 15:48:31 UTC