- From: John M Slatin <john_slatin@austin.utexas.edu>
- Date: Wed, 10 May 2006 15:31:18 -0500
- To: <public-wcag-teamb@w3.org>
- Message-ID: <6EED8F7006A883459D4818686BCE3B3B03A8F4F4@MAIL01.austin.utexas.edu>
Hello, and welcome to the newly reconstituted Team B! Just when you thought Thursday was safe this week... I'd like to call a short Team B meeting for Thursday, 11 May, from 5:00-6:00 PM US Eastern. This will be anorganizational meeting-- we'll take a quick liik at the comments submitted so far against the components that we've been assigned (Introduction, GL 2.4, GL 3.1, GL 3.2, GL 4.2), so that we understand how the process will work and see what questions we have about the work and how to organize it. Gregg's message (below) includes a link to a spreadsheet that we can use as a temporary issue tracker. I'll send the passcode and other meeting ifnromation later today or first thing in the morning. John "Good design is accessible design." John Slatin, Ph.D. Director, Accessibility Institute University of Texas at Austin FAC 248C 1 University Station G9600 Austin, TX 78712 ph 512-495-4288, f 512-495-4524 email jslatin@mail.utexas.edu web http://www.utexas.edu/research/accessibility/ <http://www.utexas.edu/research/accessibility/> ________________________________ From: public-wcag-teamb-request@w3.org [mailto:public-wcag-teamb-request@w3.org] On Behalf Of Gregg Vanderheiden Sent: Wednesday, May 10, 2006 8:18 am To: public-wcag-teama@w3.org; public-wcag-teamb@w3.org; public-wcag-teamc@w3.org Subject: New Teams and Topic areas Hi All, Here are the new lineups for Teams A, B, and C The TEAM MAIL-LISTS have all been updated to reflect these new teams. We do not have our database up yet. It should be soon but please use the following document link which will take you to a summary of comments to date. It will be continually updated. http://tinyurl.com/ryd2f Look at the items that relate to your group and start locating the past issues that relate to them. For now - please pass your links etc to your leader (or whomever they designate) for each group (via the maillist). They will get them entered into the list. So that the groups don't collide - I have created a copy for each group starting with your group letter - use that copy for your group. I will combine the three groups later (and send new items as a separate list you can add to the end). Use of this list should be for only a week or less. A - Gregg B - John C - Andi So 1 - look at the list of issues and find ones that relate to your areas 2 - look up items from bugzilla or other places that relate to solving the comment (ok to suggest items on others but do yours first) 3 - try to suggest wording that would resolve the comment (ok to suggest resolutions on others but do yours first) 4 - send 2 and 3 to your TEAM LIST - your lead will pick them up from there. Thanks Gregg -- ------------------------------ Gregg C Vanderheiden Ph.D. Professor - Ind. Engr. & BioMed Engr. Director - Trace R & D Center University of Wisconsin-Madison The Player for my DSS sound file is at http://tinyurl.com/dho6b <http://tinyurl.com/cmfd9> TEAM A * Conformance * 1.2 [A] Provide synchronized alternatives for multimedia <http://www.w3.org/TR/WCAG20/guidelines.html#media-equiv> * 1.4 [A] Make it easy to distinguish foreground information from its background <http://www.w3.org/TR/WCAG20/guidelines.html#visual-audio-contrast> * 2.1 [A] Make all functionality operable via a keyboard interface <http://www.w3.org/TR/WCAG20/guidelines.html#keyboard-operation> * 4.1 [A] Support compatibility with current and future user agents (including assistive technologies) <http://www.w3.org/TR/WCAG20/guidelines.html#ensure-compat> * 2.3 [G] Allow users to avoid content that could cause seizures due to photosensitivity <http://www.w3.org/TR/WCAG20/guidelines.html#seizure> * Gregg Vanderheiden * Ben Caldwell * David MacDonald * Bruce Bailey * Alex Li * Bengt Farre' * Yvette Hoitink TEAM B * Intro * 2.4 [B] Provide mechanisms to help users find content, orient themselves within it, and navigate through it <http://www.w3.org/TR/WCAG20/guidelines.html#navigation-mechanisms> * 3.1 [B] Make text content readable and understandable. <http://www.w3.org/TR/WCAG20/guidelines.html#meaning> * 3.2 [B] Make the placement and functionality of content predictable. <http://www.w3.org/TR/WCAG20/guidelines.html#consistent-behavior> * 4.2 [B] Ensure that content is accessible or provide an accessible alternative <http://www.w3.org/TR/WCAG20/guidelines.html#accessible-alternatives> * John Slatin 1 * Loretta GuarinoReid * Wendy * Makoto UeKi * Katie Haritos-Shea * Tim Boland * Sorcha Moore TEAM C * 1.1 [C] Provide text alternatives for all non-text content <http://www.w3.org/TR/WCAG20/guidelines.html#text-equiv> * 1.3 [C] Ensure that information and structure can be separated from presentation <http://www.w3.org/TR/WCAG20/guidelines.html#content-structure-separatio n> * 2.5 [C]Help users avoid mistakes and make it easy to correct mistakes that do occur <http://www.w3.org/TR/WCAG20/guidelines.html#minimize-error> * 2.2 [C] Allow users to control time limits on their reading or interaction <http://www.w3.org/TR/WCAG20/guidelines.html#time-limits> * Andi Snow-Weaver * Christophe Strobbe * Cynthia Shelly * Michael Cooper * Sofia Celic * Becky Gibson * Kerstin Goldsmith Group Assignment BY GUIDELINE * 1.1 [C] Provide text alternatives for all non-text content <http://www.w3.org/TR/WCAG20/guidelines.html#text-equiv> * 1.2 [A] Provide synchronized alternatives for multimedia <http://www.w3.org/TR/WCAG20/guidelines.html#media-equiv> * 1.3 [C] Ensure that information and structure can be separated from presentation <http://www.w3.org/TR/WCAG20/guidelines.html#content-structure-separatio n> * 1.4 [A] Make it easy to distinguish foreground information from its background <http://www.w3.org/TR/WCAG20/guidelines.html#visual-audio-contrast> * 2.1 [A] Make all functionality operable via a keyboard interface <http://www.w3.org/TR/WCAG20/guidelines.html#keyboard-operation> * 2.2 [C] Allow users to control time limits on their reading or interaction <http://www.w3.org/TR/WCAG20/guidelines.html#time-limits> * 2.3 [G] Allow users to avoid content that could cause seizures due to photosensitivity <http://www.w3.org/TR/WCAG20/guidelines.html#seizure> * 2.4 [B] Provide mechanisms to help users find content, orient themselves within it, and navigate through it <http://www.w3.org/TR/WCAG20/guidelines.html#navigation-mechanisms> * 2.5 [C]Help users avoid mistakes and make it easy to correct mistakes that do occur <http://www.w3.org/TR/WCAG20/guidelines.html#minimize-error> * 3.1 [B] Make text content readable and understandable. <http://www.w3.org/TR/WCAG20/guidelines.html#meaning> * 3.2 [B] Make the placement and functionality of content predictable. <http://www.w3.org/TR/WCAG20/guidelines.html#consistent-behavior> * 4.1 [A] Support compatibility with current and future user agents (including assistive technologies) <http://www.w3.org/TR/WCAG20/guidelines.html#ensure-compat> * 4.2 [B] Ensure that content is accessible or provide an accessible alternative <http://www.w3.org/TR/WCAG20/guidelines.html#accessible-alternatives>
Received on Wednesday, 10 May 2006 20:31:35 UTC