- From: Michael Cooper <michaelc@watchfire.com>
- Date: Fri, 16 Jan 2004 11:39:45 -0500
- To: "WAI GL (E-mail)" <w3c-wai-gl@w3.org>
PRESENT Jenae Andershonis Michael Cooper David MacDonald Tim Boland Ben Caldwell Chris Ridpath Lisa Seeman Wendy Chisholm Matt May David Donovan DISCUSSION Review of action items - we reviewed action items from the past couple weeks. A number of people have testing items related to potential changes to WCAG 1.0 that need to be completed soon. We also discussed our relationship to EuroAccessibility, which is we consider them participants in our process. We may wish to further work on this at the Cannes Face to Face. CSS Techniques - Tim Boland is a member of the CSS Working Group and reviewed our old CSS techniques, which have been updated in format but not content [1]. He mapped that to CSS 3 and sent that to the list [2], [3], and [4]. We talked about next steps in CSS techniques, and it seems that CSS 2.1 [5] is the version we should initially target techniques to, since that reflects current implementation. Possible next steps on the techniques are to clean the examples, address editorial notes, add missing techniques (harvest from places like Zen garden, Eric Meyers, etc.), address open issues, and go through the issues list [6], determine if they're so old they can be closed, otherwise move to Bugzilla for further tracking. Tim will get started on some of this. Supporting Technology - related to CSS techniques is the concept that some technologies, like HTML, contain content and should fully meet WCAG, while supporting technology, like CSS, cannot by itself meet the guidelines fully, but still need to follow parts of the guidelines. The relationship of technologies like HTML and SVG, either one of which can be the "host" technology and the other supporting, furthers the complexity of these relationships. How we label and deal with these technologies has been a source of confusion for some time. We ended up with three terms: "parent" technology is the main technology displaying content, "embedded" technology renders a discrete subset of the content, e.g., as an embedded SVG or movie clip, and a "style" technology affects the presentation and accessibility but does not itself play a role in content. QA framework review - we continued the review of the QA framework, Guideline 4 [7]. Checkpoint 4.1 is a requirement to provide a test framework and we spent the rest of the discussion reviewing what that might be, what we already have, what we would like to have. The HTML techniques [8] have "tasks" as well as code examples and resources. Other repositories like John Slatin's [9] and Chris Ridpath's [10] exist. We thought we should use the model from the User Agent Accessibility Guidelines [11]. Chris and Jenae will work further on this. IRC log of discussion at [12] (at time of posting this link doesn't work but should be fixed soon) ACTION ITEMS Wendy, Tim: Discuss open issues for CSS Jenae: Survey some sites for things that would go into test framework Jenae and Chris: Pull together ideas for test framework, using Guideline 1.1 for HTML as a starting point Michael, Wendy: Initial proposal of plan for Technical Plenary Jenae: Send list of ideas for test page REFERENCES [1] http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-CSS-TECHS-20031219.html [2] http://lists.w3.org/Archives/Public/w3c-wai-gl/2003OctDec/0583.html [3] http://lists.w3.org/Archives/Public/w3c-wai-gl/2003OctDec/0584.html [4] http://lists.w3.org/Archives/Public/w3c-wai-gl/2003OctDec/0585.html [5] http://www.w3.org/TR/CSS21/ [6] http://www.w3.org/WAI/GL/WCAG20/css-tech-issues.html [7] http://www.w3.org/TR/2003/WD-qaframe-test-20030516/#gl4 [8] http://www.w3.org/TR/WCAG20-HTML-TECHS/ [9] http://www.utexas.edu/research/accessibility/resource/how_to/index.html [10] http://www.aprompt.ca/oac/ [11] http://www.w3.org/WAI/UA/TS/html401/ [12] http://www.w3.org/2004/01/14-wai-wcag-irc.html --- Signature --- Michael Cooper Accessibility Product Manager, Watchfire 1 Hines Rd, Kanata, ON K2K 3C7 Canada Tel: +1 (613) 599-3888 x4019 Fax: +1 (613) 599-4661 Email: michaelc@watchfire.com Web: http://www.watchfire.com/
Received on Friday, 16 January 2004 11:37:41 UTC