w3c-wai-gl@w3.org from January to March 2000 by author

1investmentfinder@4-charity.org

• invest smart dvdt (Wednesday, 5 January)

Al Gilman

• graphics generally complement, not replace, text (Friday, 17 March)
• Re: text equivalents for multimedia (Thursday, 2 March)
• Re: Reviewer role for WCAG (Wednesday, 1 March)
• Re: is this the best approach? (Thursday, 24 February)
• Re: Labelling web page functionality for blind users (Monday, 14 February)
• Re: Does the user know for sure whether the page is dynamic or static? (Monday, 24 January)
• Re: Does the user know for sure whether the page is dynamic or static? (Monday, 24 January)
• Re: XML and accessibility (Monday, 24 January)
• Re: Does the user know for sure whether the page is dynamic or static? (Sunday, 23 January)
• Re: URI correction Re: minutes posted (Friday, 21 January)
• RE: clarification of table linearization (Wednesday, 19 January)

Alan J. Flavell

• RE: New York Times web site (Friday, 11 February)
• Re: New subsection in techniques doc: Accessibility Reviewed Technologies (Wednesday, 2 February)
• Re: attributes, software architecture, CC/PP and accessibility (Wednesday, 2 February)
• Re: screen readers, browsers, & the reporting of ALT on & in image maps (Wednesday, 12 January)

andisnow@us.ibm.com

• Request to join (Thursday, 2 March)

Anne Pemberton

• RE: Some thoughts and Possible Action Steps for CD (Monday, 27 March)
• Re: Some thoughts and Possible Action Steps for CD (Monday, 27 March)
• Re: Notes from the face2face (Wednesday, 22 March)
• Re: Some thoughts and Possible Action Steps for CD (Wednesday, 22 March)
• Re: graphics generally complement, not replace, text (Saturday, 18 March)
• Re: Please Help me understand (Friday, 17 March)
• Re: GL's acceptance of the necessity of graphics on the web (Friday, 17 March)
• Re: Text equivalents and cognitive considerations (Thursday, 16 March)
• Front Page and Publisher (Thursday, 16 March)
• RE: Text equivalents (Wednesday, 15 March)
• Re: Text equivalents (Wednesday, 15 March)
• Re: Text equivalents and cognitive considerations (Wednesday, 15 March)
• Re: Text equivalents (Wednesday, 15 March)
• Re: Text equivalents (Tuesday, 14 March)
• Text equivalents (Monday, 13 March)
• RE: A proposal for changing the guidelines (Monday, 13 March)
• Re: text equivalents for multimedia (Monday, 6 March)
• Re: text equivalents for multimedia (Monday, 6 March)
• Re: text equivalents for multimedia (Friday, 3 March)
• Re: Steps in developing technology (Wednesday, 1 March)
• Re: Reviewer role for WCAG (Wednesday, 1 March)
• Re: text equivalents for multimedia (Wednesday, 1 March)
• Re: Request to Join (Monday, 7 February)
• RE: An article about Yahoo's simplicity of design (Saturday, 5 February)
• RE: An article about Yahoo's simplicity of design (Thursday, 3 February)
• Re: Does the user know for sure whether the page is dynamic or (Friday, 28 January)
• Re: Does the user know for sure whether the page is dynamic or static? (Thursday, 27 January)

bps11@ureach.com

• laser printer toner advertisement (Monday, 22 March)

Bruce Bailey

• RE: Defining the needs of people with CD (Friday, 17 March)
• RE: Text equivalents (Friday, 17 March)
• RE: Text equivalents (Thursday, 16 March)
• RE: Text equivalents (Wednesday, 15 March)
• RE: linearized tables (Tuesday, 14 March)
• RE: text equivalents for multimedia (Thursday, 2 March)
• RE: [Fwd: Addition to the Record of the House Judiciary Subcommittee Hearing on Internet and ADA by Gregg Vanderheiden] (Wednesday, 16 February)
• RE: A "one size fits all" personalized web page? (Thursday, 20 January)

bugs5@birdmail.com

• Email Advertising Special--Ends Friday (Saturday, 25 March)

Burbidge Don (UO-Ch/TEF1.3)

• Dalcho Information (Saturday, 18 March)

cebit@internum.com

• Use YOUR Software to update YOUR users (Saturday, 8 January)

Charles McCathieNevile

• Re: Printing using CSS (Saturday, 25 March)
• Re: Accessible Design / JAWS (Saturday, 25 March)
• Re: Some thoughts and Possible Action Steps for CD (Thursday, 23 March)
• Re: Front Page and Publisher (Thursday, 16 March)
• Re: concerns with the Web Content guidelines (Thursday, 16 March)
• Re: A proposal for changing the guidelines (Thursday, 16 March)
• Re: A proposal for changing the guidelines (Thursday, 16 March)
• Re: A proposal for changing the guidelines (Thursday, 16 March)
• Re: Text equivalents and cognitive considerations (Wednesday, 15 March)
• Re: Feelings was: Text equivalents and cognitive considerations (Wednesday, 15 March)
• Re: Text equivalents and cognitive considerations (Wednesday, 15 March)
• RE: linearized tables (Wednesday, 15 March)
• Regulation and implementability Re: A proposal for changing the guidelines (Tuesday, 14 March)
• Re: A proposal for changing the guidelines (Monday, 13 March)
• Re: A proposal for changing the guidelines (Monday, 13 March)
• Re: A proposal for changing the guidelines (Monday, 13 March)
• RE: A proposal for changing the guidelines (Monday, 13 March)
• RE: A proposal for changing the guidelines (Monday, 13 March)
• RE: A proposal for changing the guidelines (Monday, 13 March)
• Re: Request for Review (Monday, 13 March)
• Audience (long) was Re: A proposal for changing the guidelines (Monday, 13 March)
• Re: A proposal for changing the guidelines (Monday, 13 March)
• Re: Fwd: linearized tables (Saturday, 11 March)
• Re: A proposal for changing the guidelines (Saturday, 11 March)
• Re: Request for Review (Thursday, 9 March)
• Simplifying the guidelines (Thursday, 9 March)
• Request for Review (Thursday, 9 March)
• Re: text equivalents for multimedia (Tuesday, 7 March)
• Re: text equivalents for multimedia (Sunday, 5 March)
• RE: text equivalents for multimedia (Thursday, 2 March)
• Re: text equivalents for multimedia (Thursday, 2 March)
• Re: An example of a form with linked error messages (Thursday, 2 March)
• Re: Reviewer role for WCAG (Wednesday, 1 March)
• Re: Reviewer role for WCAG (Wednesday, 1 March)
• SVG techniques (Sunday, 27 February)
• Re: Steps in developing technology (Thursday, 24 February)
• Re: text equivalents for multimedia (Wednesday, 23 February)
• Re: text equivalents for multimedia (Wednesday, 23 February)
• RE: alt for applets (Wednesday, 23 February)
• RE: alt for applets (Wednesday, 23 February)
• Re: Some Comments on the Latest Techniques Draft an WCAG Minutes (Tuesday, 22 February)
• alt for applets (Monday, 21 February)
• Re: An RDF conformance scheme (Thursday, 17 February)
• Re: Web examples for visually imparied (Thursday, 17 February)
• techniques draft (Wednesday, 16 February)
• Re: Agenda for Thursday's meeting (Wednesday, 16 February)
• Re: keystrokes (Monday, 14 February)
• Re: Labelling web page functionality for blind users (Sunday, 13 February)
• Re: New York Times web site (Friday, 11 February)
• Re: FW: Browser 'back' is_a Undo (fwd) (Friday, 11 February)
• Re: An article about Yahoo's simplicity of design (Saturday, 5 February)
• Re: New subsection in techniques doc: Accessibility Reviewed Technologies (Tuesday, 1 February)
• Re: attributes, software architecture, CC/PP and accessibility (Tuesday, 1 February)
• Re: CSS and implementation (Tuesday, 1 February)
• Re: CSS and implementation (Monday, 31 January)
• Re: Does the user know for sure whether the page is dynamic or static? (Monday, 24 January)
• Re: flickering / animations (Sunday, 23 January)
• Re: XML and accessibility (Sunday, 23 January)
• Re: XML and accessibility (Sunday, 23 January)
• Re: face-to-face (Saturday, 22 January)
• Re: Dating conformance Re: URI correction Re: minutes posted (Friday, 21 January)
• Dating conformance Re: URI correction Re: minutes posted (Friday, 21 January)
• URI correction Re: minutes posted (Thursday, 20 January)
• Re: A "one size fits all" personalized web page? (Wednesday, 19 January)
• An RDF conformance scheme (Monday, 17 January)
• Re: Test: tabindex-test (fwd) (Monday, 17 January)
• Re: flickering / animations (Sunday, 16 January)
• Re: noframes & Content Guidelines (Sunday, 16 January)
• Scripts on the web Re: Does CSUN Care About Web Accessibility (Sunday, 16 January)
• Re: form submission practices by authors (Friday, 14 January)
• Re: About tabindex and bypassing link (Thursday, 13 January)
• Re: A "one size fits all" personalized web page? (Thursday, 13 January)
• Re: Second Browser Window Question (Wednesday, 12 January)
• RE: A "one size fits all" personalized web page? (Wednesday, 12 January)
• flickering / animations (Wednesday, 12 January)
• RE: A "one size fits all" personalized web page? (Wednesday, 12 January)
• RE: A "one size fits all" personalized web page? (Wednesday, 12 January)
• Re: FW: UI Design Update newsletter - December, 1999 (Tuesday, 4 January)
• Re: UI Design Update newsletter - December, 1999 (Tuesday, 4 January)
• Re: A "one size fits all" personalized web page? (Tuesday, 4 January)
• Re: Rolls of interfaces in your favorite colors (was Re: Terminology) (Sunday, 2 January)
• RE: A "one size fits all" personalized web page? (Saturday, 1 January)

choeppner@hypertech.yk.ca

• Develop Your Mind, Research The Truth. (Tuesday, 29 February)

Chris Kreussling

• Re: New subsection in techniques doc: Accessibility Reviewed Technologies (Wednesday, 2 February)

Chuck Letourneau

• Re: Canadian Government Web Accessibility Test Facility (Friday, 7 January)
• Canadian Government Web Accessibility Test Facility (Friday, 7 January)

Cynthia Shelly

• request to join (Wednesday, 8 March)

Dan Brickley

• Re: An RDF conformance scheme (Thursday, 17 February)

Daniel Dardailler

• Re: XML and accessibility (Sunday, 23 January)

David M Clark

• RE: alt for applets (Wednesday, 23 February)
• RE: alt for applets (Wednesday, 23 February)
• Reuest to join (Sunday, 13 February)

David Tanner

• Request to Join (Sunday, 27 February)

Dick Brown

• RE: Text equivalents (Wednesday, 15 March)
• RE: New York Times web site (Friday, 11 February)
• RE: Request to Join (Monday, 7 February)
• RE: An article about Yahoo's simplicity of design (Friday, 4 February)
• RE: An article about Yahoo's simplicity of design (Wednesday, 2 February)
• RE: acronym for Web Content Accessibility Guidelines working grou p (Friday, 7 January)

eCampaign

• Romance Enhancement Site (Wednesday, 15 March)

Frank Torrey

• Request to Join (Wednesday, 29 March)

Gary & Betty Borton

• HI,IM,GARY L BORTON (Saturday, 22 January)

geoff freed

• Re: text equivalents for multimedia (Monday, 6 March)
• Re: text equivalents for multimedia (Wednesday, 23 February)
• Re: text equivalents for multimedia (Wednesday, 23 February)

Greg Lowney

• RE: linearized tables (Monday, 13 March)

Greg Rosenberg

• RE: Research questions - the underlying issue? (Thursday, 27 January)
• Request to Join (Monday, 24 January)

Gregg Vanderheiden

• RE: Some thoughts and Possible Action Steps for CD (Friday, 4 January)
• Some thoughts and Possible Action Steps for CD (Sunday, 19 March)
• Regarding proposals for changes to the guidelines (Friday, 17 March)
• Thought for the day (Thursday, 16 March)
• WOAW now. Lets all shake hands and come out talking (Thursday, 16 March)
• Text equivalents and cognitive considerations (Wednesday, 15 March)
• RE: A proposal for changing the guidelines (Tuesday, 14 March)
• RE: linearized tables (Tuesday, 14 March)
• RE: A proposal for changing the guidelines (Monday, 13 March)
• RE: A proposal for changing the guidelines (Sunday, 12 March)
• RE: is this the best approach? (Friday, 10 March)
• New FCC NOI (Tuesday, 22 February)
• FW: comments to House Subcommitee (Tuesday, 22 February)
• FW: Browser 'back' is_a Undo (fwd) (Thursday, 10 February)
• RE: GL SIGNUP - What if i already signed up in last few weeks? (Sunday, 6 February)
• Invitation to Join the NEW GL working Group (Sunday, 6 February)
• RE: clarification of table linearization (Wednesday, 19 January)
• RE: Children (Monday, 17 January)

Gregory J. Rosmaita

• Re: form orientation, navigation, and submission techniques (Friday, 17 March)
• form orientation, navigation, and submission techniques (Friday, 17 March)
• GL's acceptance of the necessity of graphics on the web (Friday, 17 March)
• RE: Text equivalents (Wednesday, 15 March)
• Re: Text equivalents (Wednesday, 15 March)
• Re: A proposal for changing the guidelines (Wednesday, 15 March)
• Re: Text equivalents (Wednesday, 15 March)
• Re: A proposal for changing the guidelines (Tuesday, 14 March)
• Re: problem with phone line (Monday, 13 March)
• problem with phone line (Monday, 13 March)
• Re: A proposal for changing the guidelines (Monday, 13 March)
• Re: is this the best approach? (Thursday, 24 February)
• Re: Labelling web page functionality for blind users (Thursday, 17 February)
• RE: New York Times web site (Friday, 11 February)
• Re: New York Times web site (Thursday, 10 February)
• Re: Invitation to Join the NEW GL working Group (Sunday, 6 February)
• Re: minutes posted (Friday, 4 February)
• request to re-join (Wednesday, 2 February)
• NOFRAMES, WCAG, & UAAG (was Re: noframes & Content Guidelines) (Wednesday, 19 January)
• Re: agenda for tomorrow's WCAG meeting (Thursday, 13 January)
• screen readers, browsers, & the reporting of ALT on & in image maps (Wednesday, 12 January)
• Re: acronym for Web Content Accessibility Guidelines working group (Friday, 7 January)

Heather Swayne

• concerns with the Web Content guidelines (Thursday, 16 March)

hellocorp1@yahoo.com

• Save 50-80% on International Calls and Win $500 in Free phone calls! (Thursday, 20 January)

Henry, Shawn Lawton

• RE: Accessible Web Designing (Monday, 13 March)

hifiber7@compuserve.com

• AD:Family Reunion T Shirts & More (Sunday, 13 February)

Ian Jacobs

• Re: Questions regarding compliance and alternative pages (Tuesday, 28 March)
• Re: Printing using CSS (Friday, 24 March)
• Re: Some thoughts and Possible Action Steps for CD (Thursday, 23 March)
• Re: Notes from the face2face (Wednesday, 22 March)
• Re: A proposal for changing the guidelines (Friday, 17 March)
• Re: Thought for the day (Thursday, 16 March)
• Re: A proposal for changing the guidelines (Thursday, 16 March)
• Re: WCAG face to face meeting agenda (Wednesday, 15 March)
• Re: A proposal for changing the guidelines (Wednesday, 15 March)
• Proposal for GL mailing list posting privileges change (Monday, 13 March)
• Re: A proposal for changing the guidelines (Monday, 13 March)
• Re: A proposal for changing the guidelines (Monday, 13 March)
• Re: more table tricks (Wednesday, 8 March)
• Re: Labelling web page functionality for blind users (Friday, 11 February)
• Re: face-to-face (Saturday, 22 January)
• Re: Dating conformance Re: URI correction Re: minutes posted (Friday, 21 January)
• Re: Text needs to be written for a reader. A little longer than my usual... (Monday, 17 January)
• Proposal for unified conformance scheme (Wednesday, 12 January)
• Re: UI Design Update newsletter - December, 1999 (Tuesday, 4 January)
• Re: UI Design Update newsletter - December, 1999 (Monday, 3 January)

info17640@babit.com

• WE FIND MISSING PEOPLE for YOU.....Or it's FREE!!_ (7856) (Thursday, 27 January)

info5454@babit.com

• WE FIND MISSING PEOPLE for YOU.....Or it's FREE!!_ (8460) (Wednesday, 26 January)

Jason Hinkin

• How far? (Thursday, 24 February)

Jason White

• Invitation to review Evaluation and Repair Techniques document (Thursday, 30 March)
• Working group meeting schedule (Thursday, 30 March)
• Re: Text equivalents and cognitive considerations (Thursday, 16 March)
• Re: Text equivalents and cognitive considerations (Wednesday, 15 March)
• WCAG face to face meeting agenda (Wednesday, 15 March)
• Re: A proposal for changing the guidelines (Friday, 10 March)
• Agenda for Thursday's meeting (Wednesday, 8 March)
• Agenda for Thursday's meeting (Tuesday, 29 February)
• Re: text equivalents for multimedia (Thursday, 24 February)
• Agenda for Thursday's meeting (Tuesday, 22 February)
• Agenda for Thursday's meeting (Wednesday, 16 February)
• Meeting cancellation and draft of Techniques document (Wednesday, 9 February)
• Review of Techniques Document and Agenda for Thursday's meeting (Wednesday, 2 February)
• Re: proposed clarification of TABLE caption, title, and summary for the techniques document (Friday, 28 January)
• Re: proposed clarification of TABLE caption, title, and summary for the techniques document (Friday, 28 January)
• Cross-references in guidelines (Thursday, 27 January)
• Re: agenda for tomorrow's meeting (Wednesday, 26 January)
• RE: clarification of table linearization (Wednesday, 19 January)
• Agenda for Thursday's meeting (Wednesday, 19 January)
• RE: A "one size fits all" personalized web page? (Friday, 14 January)

Jerry Richer

• Request to Join (Thursday, 3 February)

jesica@web.com

• Email Advertising Special--Ends Friday (Thursday, 30 March)

Jon Gunderson

• User Agent Guidelines (Thursday, 16 March)
• Re: A proposal for changing the guidelines (Wednesday, 15 March)
• Markup to Support Navigation (Tuesday, 14 March)
• RE: linearized tables (Tuesday, 14 March)
• RE: linearized tables (Tuesday, 14 March)
• RE: A proposal for changing the guidelines (Monday, 13 March)
• Re: Request for Review (Monday, 13 March)
• Re: Reviewer role for WCAG (Wednesday, 1 March)
• Re: Department of Defence Advanced Distributed Learning Network (Monday, 21 February)
• Department of Defence Advanced Distributed Learning Network (Monday, 21 February)
• Request to Join (Monday, 7 February)
• Re: agenda for tomorrow's WCAG meeting (Wednesday, 12 January)

Jonathan Chetwynd

• $$$---$150 for an icon of a man with trolley (Tuesday, 28 March)
• 2 WOWs and Re: Some thoughts and Possible Action Steps for CD (Tuesday, 28 March)
• Re: Some thoughts and Possible Action Steps for CD (Thursday, 23 March)
• Re: Some thoughts and Possible Action Steps for CD (Thursday, 23 March)
• Re: Some thoughts and Possible Action Steps for CD (Sunday, 19 March)
• Re: Text equivalents (Saturday, 18 March)
• Re: Please Help me understand (Friday, 17 March)
• Re: Text equivalents (Friday, 17 March)
• Defining the needs of people with CD (Friday, 17 March)
• Cognitiver Disability + Participation at CSUN WWW9 ..... (Friday, 17 March)
• Re: Feelings was: Text equivalents and cognitive considerations (Friday, 17 March)
• Feelings was: Text equivalents and cognitive considerations (Wednesday, 15 March)
• Re: Text equivalents (Wednesday, 15 March)
• Re: Text equivalents (Wednesday, 15 March)
• Re: A proposal for changing the guidelines (Monday, 13 March)
• Re: text equivalents for multimedia (Thursday, 2 March)
• Re: accessibility and its meaning. (Wednesday, 1 March)
• accessibility and its meaning. (Sunday, 27 February)
• Re: New York Times web site (Friday, 11 February)
• Re: An article about Yahoo's simplicity of design (Saturday, 5 February)
• Re: An article about Yahoo's simplicity of design (Friday, 4 February)
• online Dictionary..... (Thursday, 3 February)
• Re: An article about Yahoo's simplicity of design (Thursday, 3 February)
• Re: An article about Yahoo's simplicity of design (Tuesday, 1 February)
• Re: some references on user need assessment (Friday, 28 January)
• Cognitive difficulties (Friday, 28 January)
• Re: some references on user need assessment (Wednesday, 26 January)
• Re: some references on user need assessment (Wednesday, 26 January)
• Re: some references on user need assessment (Wednesday, 26 January)
• Re: some references on user need assessment (Wednesday, 26 January)
• Re: HI,IM,GARY L BORTON (Wednesday, 26 January)
• Re: Does the user know for sure whether the page is dynamic or static? (Monday, 24 January)
• Re: Does the user know for sure whether the page is dynamic or static? (Monday, 24 January)
• Re: Does the user know for sure whether the page is dynamic or static? (Monday, 24 January)
• Re: Does the user know for sure whether the page is dynamic or static? (Monday, 24 January)
• Re: some references on user need assessment (Monday, 24 January)
• Re: Does the user know for sure whether the page is dynamic or static? (Sunday, 23 January)
• Re: Does the user know for sure whether the page is dynamic or static? (Sunday, 23 January)
• Re: Does the user know for sure whether the page is dynamic or static? (Sunday, 23 January)
• Re: some references on user need assessment (Sunday, 23 January)
• Re: Request to Join (Sunday, 23 January)
• Text needs to be written for a reader. A little longer than my usual... (Monday, 17 January)
• Children: was Re: A "one size fits all" personalized web page? (Friday, 14 January)
• Re: A "one size fits all" personalized web page? (Tuesday, 4 January)
• Re: UI Design Update newsletter - December, 1999 (Tuesday, 4 January)
• Re: UI Design Update newsletter - December, 1999 (Monday, 3 January)
• father xmas was Re: UI Design Update newsletter - December, 1999 (Monday, 3 January)
• Re: UI Design Update newsletter - December, 1999 (Monday, 3 January)
• Re: A "one size fits all" personalized web page? (Monday, 3 January)
• Re: UI Design Update newsletter - December, 1999 (Saturday, 1 January)

Judy Brewer

• US Sec. 508 [was: Re: FW: ADA/ABA Accessibility Guidelines Notice of Proposed Rulemakin g] (Friday, 31 March)
• WAI at CSUN 2000! (Friday, 17 March)
• Registration pages available for WAI meetings before and after CSUN (Wednesday, 16 February)
• WAI Meetings around CSUN, Confirmed Schedule (Friday, 4 February)
• WAI Meetings around CSUN, Tentative Schedule (Saturday, 22 January)

julie23@smallbizmail.com

• Email Advertising Special--Ends Friday (Monday, 27 March)

Kelly Ford

• Re: screen readers, browsers, & the reporting of ALT on & in image maps (Wednesday, 12 January)

Kynn Bartlett

• RE: Some thoughts and Possible Action Steps for CD (Monday, 27 March)
• Re: Some thoughts and Possible Action Steps for CD (Monday, 27 March)
• RE: New York Times web site (Friday, 11 February)
• RE: New York Times web site (Friday, 11 February)

Leonard R. Kasday

• Re: Questions regarding compliance and alternative pages (Tuesday, 28 March)
• Questions regarding compliance and alternative pages (Monday, 27 March)
• RE: linearized tables (Friday, 17 March)
• RE: linearized tables (Friday, 17 March)
• RE: linearized tables (Thursday, 16 March)
• RE: linearized tables (Wednesday, 15 March)
• Re: screen readers, browsers, & the reporting of ALT on & in image maps (Wednesday, 12 January)

LuAnne Bullington

• [w3c-wai-gl] <none> (Saturday, 22 January)

lynn2121@crosswinds.net

• Email Advertising Works--Special Rates till Friday (Tuesday, 28 March)

m.thomas@ix.netcom.com

• Accessible Web Designing (Sunday, 12 March)

Marcelo de Arruda

• Re: linearized tables (Tuesday, 14 March)

Marja-Riitta Koivunen

• suggestion: site or page description (Tuesday, 28 March)
• Re: more table tricks (Wednesday, 8 March)
• Re: An RDF conformance scheme (Thursday, 17 February)
• Re: some references on user need assessment (Wednesday, 26 January)
• Re: Research questions - the underlying issue? (was Re: XML and accessibility) (Monday, 24 January)

Marti

• Re: Feelings was: Text equivalents and cognitive considerations (Friday, 17 March)
• Please Help me understand (Friday, 17 March)
• PDF Documents (Thursday, 2 March)
• Re: is this the best approach? (Thursday, 24 February)
• Re: Scripts on the web Re: Does CSUN Care About Web Accessibility (Thursday, 17 February)
• Request to Join (Monday, 24 January)

Mei Yeh-Kennedy

• Request to Join (Monday, 31 January)

Michael Burks

• RE: New York Times web site (Friday, 11 February)

Michael_Muller@lotus.com

• Re: FW: UI Design Update newsletter - December, 1999 (Monday, 3 January)

Nagaraj Balasubramanya

• Re: TABINDEX - HTML Applications (Wednesday, 22 March)

Neff, Robert

• FW: ADA/ABA Accessibility Guidelines Notice of Proposed Rulemakin g (Friday, 31 March)
• RE: drilling down on checkpoints (Saturday, 25 March)
• drilling down on checkpoints (Saturday, 25 March)
• FW: All Set With Access (Friday, 4 February)

Nir Dagan

• Re: Text equivalents (Wednesday, 15 March)
• content negotiation (was Re: A proposal for changing the guidelines) (Monday, 13 March)
• Fwd: Re: Request for Review (Thursday, 9 March)
• Re: more table tricks (Wednesday, 8 March)
• Re: attributes, software architecture, CC/PP and accessibility (Wednesday, 2 February)
• Re: XML and accessibility (Sunday, 23 January)
• Re: XML and accessibility (Saturday, 22 January)

pjenkins@us.ibm.com

• RE: linearized tables and FORMs (Tuesday, 14 March)
• Re: Markup to Support Navigation (Tuesday, 14 March)
• Re: A proposal for changing the guidelines (Monday, 13 March)
• Re: A proposal for changing the guidelines (Monday, 13 March)
• Re: minutes from today (Thursday, 2 March)
• Re: proposed clarification of TABLE caption, title, and summary for the techniques document (Friday, 28 January)
• Re: screen readers, browsers, & the reporting of ALT on & in image maps (Wednesday, 12 January)

press@webclaim.net

• Electronic Dental Claims via the Internet (Sunday, 16 January)

printz61@polbox.com

• AD:Family Reunion T Shirts & More (Sunday, 5 March)

removeitc99@netscape.net

• Commercial Unsolicited mail - Special offer from itc'99 online auction (Saturday, 26 February)

Ricardo Sanchez

• Fwd: Test: tabindex-test (Tuesday, 18 January)

Robert Neff

• Re: form orientation, navigation, and submission techniques (Sunday, 19 March)
• Re: A proposal for changing the guidelines (Thursday, 16 March)
• Re: WCAG face to face meeting agenda (Wednesday, 15 March)
• Re: A proposal for changing the guidelines (Tuesday, 14 March)
• Re: A proposal for changing the guidelines (Tuesday, 14 March)
• Re: A proposal for changing the guidelines (Monday, 13 March)
• Re: A proposal for changing the guidelines (Monday, 13 March)
• Re: A proposal for changing the guidelines (Monday, 13 March)
• Re: is this the best approach? (Sunday, 12 March)
• Re: text equivalents for multimedia (Sunday, 5 March)
• Re: CSS and implementation (Tuesday, 1 February)
• Re: CSS and implementation (Saturday, 29 January)
• Re: proposed clarification of TABLE caption, title, and summary for the techniques document (Saturday, 29 January)
• CSS and implementation (Sunday, 23 January)

Scott Luebking

• Notes from the face2face (Wednesday, 22 March)
• Re: form orientation, navigation, and submission techniques (Saturday, 18 March)
• Re: form orientation, navigation, and submission techniques (Friday, 17 March)
• Re: A proposal for changing the guidelines (Friday, 17 March)
• Re: A proposal for changing the guidelines (Thursday, 16 March)
• Re: A proposal for changing the guidelines (Thursday, 16 March)
• Re: A proposal for changing the guidelines (Thursday, 16 March)
• Re: A proposal for changing the guidelines (Thursday, 16 March)
• Re: A proposal for changing the guidelines (Thursday, 16 March)
• Re: A proposal for changing the guidelines (Thursday, 16 March)
• Re: A proposal for changing the guidelines (Thursday, 16 March)
• Re: A proposal for changing the guidelines (Thursday, 16 March)
• Re: A proposal for changing the guidelines (Thursday, 16 March)
• Re: A proposal for changing the guidelines (Thursday, 16 March)
• Re: A proposal for changing the guidelines (Thursday, 16 March)
• Re: A proposal for changing the guidelines (Thursday, 16 March)
• Re: A proposal for changing the guidelines (Wednesday, 15 March)
• Re: A proposal for changing the guidelines (Monday, 13 March)
• Re: A proposal for changing the guidelines (Monday, 13 March)
• Re: A proposal for changing the guidelines (Monday, 13 March)
• Re: A proposal for changing the guidelines (Monday, 13 March)
• Re: A proposal for changing the guidelines (Monday, 13 March)
• A proposal for changing the guidelines (Friday, 10 March)
• Re: Steps in developing technology (Thursday, 2 March)
• Re: An example of a form with linked error messages (Thursday, 2 March)
• Re: A poll for screen reader users (Thursday, 2 March)
• An example of a form with linked error messages (Wednesday, 1 March)
• Re: A technology gap (was Re: Steps in developing technology (Sunday, 27 February)
• Re: A technology gap (was Re: Steps in developing technology (Sunday, 27 February)
• A technology gap (was Re: Steps in developing technology (Saturday, 26 February)
• Re: Steps in developing technology (Thursday, 24 February)
• Steps in developing technology (Tuesday, 22 February)
• Re: Labelling web page functionality for blind users (Thursday, 17 February)
• Re: Labelling web page functionality for blind users (Thursday, 17 February)
• Labelling web page functionality for blind users (Friday, 11 February)
• RE: New York Times web site (Friday, 11 February)
• RE: New York Times web site (Friday, 11 February)
• Re: New York Times web site (Friday, 11 February)
• Re: New York Times web site (Thursday, 10 February)
• ISO standards (Saturday, 5 February)
• Re: attributes, software architecture, CC/PP and accessibility (Wednesday, 2 February)
• attributes, software architecture, CC/PP and accessibility (Tuesday, 1 February)
• Re: Research questions - the underlying issue? (was Re: XML (Tuesday, 1 February)
• An article about Yahoo's simplicity of design (Tuesday, 1 February)
• Another view of "One size fits all?" (Sunday, 30 January)
• Re: some references on user need assessment (Friday, 28 January)
• Re: Does the user know for sure whether the page is dynamic or (Thursday, 27 January)
• Re: some references on user need assessment (Thursday, 27 January)
• Re: Research questions - the underlying issue? (was Re: XML (Thursday, 27 January)
• Re: Does the user know for sure whether the page is dynamic or (Wednesday, 26 January)
• Re: some references on user need assessment (Wednesday, 26 January)
• Re: some references on user need assessment (Wednesday, 26 January)
• Re: some references on user need assessment (Wednesday, 26 January)
• Re: some references on user need assessment (Wednesday, 26 January)
• Re: some references on user need assessment (Tuesday, 25 January)
• Re: some references on user need assessment (Monday, 24 January)
• Re: some references on user need assessment (Monday, 24 January)
• Just wondering (Monday, 24 January)
• Re: some references on user need assessment (Sunday, 23 January)
• Re: Does the user know for sure whether the page is dynamic or static? (Sunday, 23 January)
• Re: XML and accessibility (Sunday, 23 January)
• Re: XML and accessibility (Sunday, 23 January)
• Re: XML and accessibility (Sunday, 23 January)
• Re: XML and accessibility (Saturday, 22 January)
• XML and accessibility (Saturday, 22 January)
• Dynamically generated web pages and disabled users (Thursday, 20 January)
• RE: A "one size fits all" personalized web page? (Thursday, 20 January)
• Re: A "one size fits all" personalized web page? (Thursday, 20 January)
• Re: A "one size fits all" personalized web page? (Wednesday, 19 January)
• Re: A "one size fits all" personalized web page? (Wednesday, 19 January)
• RE: A "one size fits all" personalized web page? (Thursday, 13 January)
• RE: A "one size fits all" personalized web page? (Wednesday, 12 January)
• RE: A "one size fits all" personalized web page? (Wednesday, 12 January)
• Re: A "one size fits all" personalized web page? (Wednesday, 12 January)
• RE: A "one size fits all" personalized web page? (Wednesday, 12 January)
• RE: A "one size fits all" personalized web page? (Wednesday, 12 January)

Sean Mauney

• Printing using CSS (Tuesday, 1 February)

sino123@hotmail.com

• Welcome to post your business and trade offers in sino trade Leads wwwboard! (Wednesday, 5 January)

skateboard@skateshop1.com

• skateboard (Friday, 14 January)

Steve Hall

• Web examples for visually imparied (Wednesday, 16 February)

thatch@us.ibm.com

• Re: Some thoughts and Possible Action Steps for CD (Monday, 27 March)
• RE: linearized tables (Friday, 17 March)
• RE: linearized tables (Tuesday, 14 March)
• RE: linearized tables (Tuesday, 14 March)
• IBM Accessibility Guidelines (Friday, 4 February)
• [w3c-wai-gl] <none> (Saturday, 22 January)

Tim Noonan

• Some Comments on the Latest Techniques Draft an WCAG Minutes (Monday, 21 February)
• Request to Join (Monday, 24 January)

Wendy A Chisholm

• Please review: Techniques For Evaluation And Implementation Of Web Content Accessibility Guidelines (Wednesday, 15 March)
• Fwd: server side image maps guideline 1.2 (Friday, 10 March)
• Fwd: linearized tables (Friday, 10 March)
• Re: minutes from today's call, next mtg is the face2face - 20 March. (Friday, 10 March)
• minutes from today's call, next mtg is the face2face - 20 March. (Thursday, 9 March)
• non-w3c technologies module (Thursday, 9 March)
• new draft of techniques (Thursday, 9 March)
• more table tricks (Wednesday, 8 March)
• minutes from today (Thursday, 2 March)
• Re: Reviewer role for WCAG (Wednesday, 1 March)
• Reviewer role for WCAG (Wednesday, 1 March)
• Re: xml accessibility (Tuesday, 29 February)
• Re: accessibility and its meaning. (Tuesday, 29 February)
• minutes from last thursday (Tuesday, 29 February)
• is this the best approach? (Thursday, 24 February)
• Re: text equivalents for multimedia (Wednesday, 23 February)
• Re: text equivalents for multimedia (Wednesday, 23 February)
• text equivalents for multimedia (Wednesday, 23 February)
• xml accessibility (Tuesday, 22 February)
• Reminders and Minutes from 17 February 2000 (Thursday, 17 February)
• Re: An RDF conformance scheme (Thursday, 17 February)
• Re: noframes & Content Guidelines (Thursday, 17 February)
• Re: Scripts on the web Re: Does CSUN Care About Web Accessibility (Thursday, 17 February)
• Interesting Flash and Shockwave article from WebReview (Tuesday, 15 February)
• Information and Registration for WAI meetings at CSUN (Monday, 14 February)
• Confirmed: WCAG WG weekly telecon (Friday, 28 January)
• tidied up the home page (note that it gets updated _weekly_) (Friday, 28 January)
• Re: CSS and implementation (Friday, 28 January)
• proposed clarification of TABLE caption, title, and summary for the techniques document (Friday, 28 January)
• minutes from today's call (Thursday, 27 January)
• ETA tool is available (Thursday, 27 January)
• Re: some references on user need assessment (Thursday, 27 January)
• agenda for tomorrow's meeting (Wednesday, 26 January)
• Re: some references on user need assessment (Wednesday, 26 January)
• proposed update to errata: meta data conformance schemes (Wednesday, 26 January)
• Table summary, caption, and title (Monday, 24 January)
• Research questions - the underlying issue? (was Re: XML and accessibility) (Monday, 24 January)
• face-to-face (Friday, 21 January)
• minutes posted (Thursday, 20 January)
• errata updated for checkpoint 10.2 (Thursday, 20 January)
• clarification of table linearization (Tuesday, 18 January)
• form submission practices by authors (Thursday, 13 January)
• minutes from today (Thursday, 13 January)
• agenda for tomorrow's WCAG meeting (Wednesday, 12 January)
• acronym for Web Content Accessibility Guidelines working group (Friday, 7 January)
• minutes from today (Thursday, 6 January)

Wendy Chisholm

• New Techniques Working Draft (Friday, 11 February)
• minutes posted (Thursday, 3 February)
• New subsection in techniques doc: Accessibility Reviewed Technologies (Tuesday, 1 February)
• Techniques: Document structure and metadata (Tuesday, 1 February)
• New techniques for Techniques (Tuesday, 1 February)

William Loughborough

• Re: Text equivalents (Tuesday, 14 March)
• Re: is this the best approach? (Friday, 10 March)
• Re: Agenda for Thursday's meeting (Thursday, 2 March)
• css inclusion (Thursday, 2 March)
• Re: How far? (Thursday, 24 February)
• Re: is this the best approach? (Thursday, 24 February)
• Re: xml accessibility (Wednesday, 23 February)
• Request to Join (Monday, 7 February)
• Re: Does the user know for sure whether the page is dynamic or static? (Monday, 24 January)
• Request to Join (Saturday, 22 January)
• Re: A "one size fits all" personalized web page? (Wednesday, 12 January)

Last message date: Friday, 31 March 2000 15:45:25 UTC