W3C home > Mailing lists > Public > public-wcag-teama@w3.org > May 2006

New Teams and Topic areas

From: Gregg Vanderheiden <gv@trace.wisc.edu>
Date: Wed, 10 May 2006 08:17:52 -0500
To: <public-wcag-teama@w3.org>, <public-wcag-teamb@w3.org>, <public-wcag-teamc@w3.org>
Message-ID: <000601c67434$262f8e10$ee8cfea9@NC6000BAK>
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
<http://www.w3.org/TR/WCAG20/guidelines.html#media-equiv>  synchronized
alternatives for multimedia 

*         1.4 [A] Make it
<http://www.w3.org/TR/WCAG20/guidelines.html#visual-audio-contrast>  easy to
distinguish foreground information from its background 

*         2.1 [A] Make all
<http://www.w3.org/TR/WCAG20/guidelines.html#keyboard-operation>
functionality operable via a keyboard interface 

*         4.1 [A] Support
<http://www.w3.org/TR/WCAG20/guidelines.html#ensure-compat>  compatibility
with current and future user agents (including assistive technologies) 

*         2.3 [G] Allow users to avoid
<http://www.w3.org/TR/WCAG20/guidelines.html#seizure>  content that could
cause seizures due to photosensitivity 

*         Gregg Vanderheiden                     

*         Ben Caldwell                   

*         David MacDonald     

*         Bruce  Bailey 

*         Alex Li     

*         Bengt Farre'  

*         Yvette Hoitink    

 

 


TEAM B


*         Intro

*         2.4 [B] Provide
<http://www.w3.org/TR/WCAG20/guidelines.html#navigation-mechanisms>
mechanisms to help users find content, orient themselves within it, and
navigate through it 

*         3.1 [B] Make text content readable
<http://www.w3.org/TR/WCAG20/guidelines.html#meaning>  and understandable. 

*         3.2 [B] Make the
<http://www.w3.org/TR/WCAG20/guidelines.html#consistent-behavior>  placement
and functionality of content predictable. 

*         4.2  [B] Ensure
<http://www.w3.org/TR/WCAG20/guidelines.html#accessible-alternatives>  that
content is accessible or provide an accessible alternative 

*         John Slatin   1

*         Loretta GuarinoReid    

*         Wendy    

*         Makoto   UeKi       

*         Katie Haritos-Shea 

*         Tim   Boland   

*         Sorcha Moore 


 


TEAM C


*         1.1 [C]  Provide text
<http://www.w3.org/TR/WCAG20/guidelines.html#text-equiv>  alternatives for
all non-text content 

*         1.3 [C] Ensure
<http://www.w3.org/TR/WCAG20/guidelines.html#content-structure-separation>
that information and structure can be separated from presentation 

*         2.5  [C]Help users
<http://www.w3.org/TR/WCAG20/guidelines.html#minimize-error>  avoid mistakes
and make it easy to correct mistakes that do occur 

*         2.2 [C] Allow users to
<http://www.w3.org/TR/WCAG20/guidelines.html#time-limits>  control time
limits on their reading or interaction 

*         Andi Snow-Weaver             

*         Christophe Strobbe        

*         Cynthia Shelly      

*         Michael Cooper        

*         Sofia Celic   

*         Becky Gibson    

*         Kerstin Goldsmith 

 

 


Group Assignment BY GUIDELINE 


*         1.1 [C]  Provide text
<http://www.w3.org/TR/WCAG20/guidelines.html#text-equiv>  alternatives for
all non-text content 

*         1.2 [A] Provide
<http://www.w3.org/TR/WCAG20/guidelines.html#media-equiv>  synchronized
alternatives for multimedia 

*         1.3 [C] Ensure
<http://www.w3.org/TR/WCAG20/guidelines.html#content-structure-separation>
that information and structure can be separated from presentation 

*         1.4 [A] Make
<http://www.w3.org/TR/WCAG20/guidelines.html#visual-audio-contrast>  it easy
to distinguish foreground information from its background 

*         2.1 [A] Make all
<http://www.w3.org/TR/WCAG20/guidelines.html#keyboard-operation>
functionality operable via a keyboard interface 

*         2.2 [C] Allow users to
<http://www.w3.org/TR/WCAG20/guidelines.html#time-limits>  control time
limits on their reading or interaction 

*         2.3 [G] Allow users to avoid
<http://www.w3.org/TR/WCAG20/guidelines.html#seizure>  content that could
cause seizures due to photosensitivity 

*         2.4 [B] Provide
<http://www.w3.org/TR/WCAG20/guidelines.html#navigation-mechanisms>
mechanisms to help users find content, orient themselves within it, and
navigate through it 

*         2.5 [C]Help users
<http://www.w3.org/TR/WCAG20/guidelines.html#minimize-error>  avoid mistakes
and make it easy to correct mistakes that do occur 

*         3.1 [B] Make text content
<http://www.w3.org/TR/WCAG20/guidelines.html#meaning>  readable and
understandable. 

*         3.2 [B] Make the
<http://www.w3.org/TR/WCAG20/guidelines.html#consistent-behavior>  placement
and functionality of content predictable. 

*         4.1 [A] Support
<http://www.w3.org/TR/WCAG20/guidelines.html#ensure-compat>  compatibility
with current and future user agents (including assistive technologies) 

*         4.2 [B] Ensure
<http://www.w3.org/TR/WCAG20/guidelines.html#accessible-alternatives>  that
content is accessible or provide an accessible alternative 

 

 

 
Received on Wednesday, 10 May 2006 13:17:29 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:40 GMT