w3c-wai-ig@w3.org from January to March 2001 by author

Lesley Armon

• unsubscrib (Wednesday, 17 January)

Aaron Leventhal

• Netscape Accessibility Job correction (Monday, 26 March)
• Netscape Accessibility Job opening (Tuesday, 27 March)
• Cross platform accesibility & Netscape effort underway (Friday, 5 January)

ADAM GUASCH-MELENDEZ

• Re: Animated GIFs and accessibility guidelines (Monday, 5 March)
• Re: Animated GIFs and accessibility guidelines (Thursday, 15 February)
• Re: Animated GIFs and accessibility guidelines (Thursday, 15 February)
• Re: Accessibility of federal statistical tables (Tuesday, 23 January)
• Re: Indicating Compliance (Friday, 12 January)

Al Gilman

• FYI: review and repair of Web interface to W3C email archives (Thursday, 22 March)
• Re: doing it right?Fw: [jfw-employment] forms accessible (Friday, 16 March)
• Re: doing it right?Fw: [jfw-employment] forms accessible (Friday, 16 March)
• Re: Forms???? (Thursday, 8 March)
• RE: Process/Procedure for Accessibility Testing of Software (Wednesday, 7 March)
• Re: Animated GIFs and accessibility guidelines (Sunday, 4 March)
• RE: (lists and) Screen Readers (Monday, 19 February)
• RE: onmouseover, onfocus, onclick (Friday, 16 February)
• RE: Section 508 Question on Javascript - Section 1194.22, Paragraph (l) (Wednesday, 14 February)
• Re: Associate Data and Header cells (Monday, 12 February)
• FYI: Re: Accessibility of "fusion" services (Monday, 12 February)
• Re: Accessibility of "fusion" services (Monday, 12 February)
• Re: ABBR vs ACRONYM, round 57894174803 (Saturday, 10 February)
• Re: A question of titles (Thursday, 1 February)
• Re: Design Question (Wednesday, 24 January)
• Re: Can the W3C HML validaor send email when the page becomes invalid (was Re: WWW: Interoperability Crisis?) (Monday, 22 January)
• RE: server side images for geographic mapping data (Thursday, 18 January)
• Re: server side images for geographic mapping data (Thursday, 18 January)
• Re: QUESTION: use of javascript to comply with Sect 508 (Thursday, 4 January)

Alice Anderson

• opinions on deprecated code plus (Saturday, 17 February)
• Re: Guideline 11 Interpretation (Monday, 8 January)

Andrew Arch

• Re: Screen Readers (Saturday, 17 February)
• Screen readers and Lists (Thursday, 15 February)

Andrew Kirkpatrick

• Access Solutions to Rich Media Project (Wednesday, 21 February)

Anirvan Basu

• [w3c-wai-ig] <none> (Friday, 16 February)

Anne Pemberton

• RE: Simplicity of Authoring and Accessibility Tools (Saturday, 20 January)
• RE: Fw: Disturbing trend in tables (Saturday, 20 January)
• RE: Simplicity of Authoring and Accessibility Tools (Friday, 19 January)
• RE: Fw: Disturbing trend in tables (Friday, 19 January)
• RE: Fw: Disturbing trend in tables (Thursday, 18 January)
• Re: Disturbing trend in tables (Friday, 19 January)
• RE: Fw: Disturbing trend in tables (Thursday, 18 January)
• RE: Fw: Disturbing trend in tables (Thursday, 18 January)
• RE: Fw: Disturbing trend in tables (Wednesday, 17 January)
• Re: Disturbing trend in tables (Wednesday, 17 January)
• RE: Fw: Disturbing trend in tables (Tuesday, 16 January)

Anthony Quinn

• RE: Text unavailable to sighted users but available to screen reader users (Friday, 9 March)
• RE: Lotus Domino and Accessible Tables (Monday, 5 March)
• question on embedded documents and screenreaders (Friday, 2 March)
• RE: Accessibility - A perfect solution? (Wednesday, 24 January)
• RE: Accessible _By_ (Friday, 19 January)
• RE: Accessible _By_ (Friday, 19 January)
• testing to ensure 508 compliance (Monday, 15 January)
• user defined stylesheets (Wednesday, 10 January)
• How closely does Windows narrator simulate JAWS (Friday, 5 January)

B.K. DeLong

• Re: Accessible chat software (Sunday, 4 February)

Bailey, Bruce

• 508 wording/intent (Tuesday, 20 February)
• Re: opinions on deprecated code plus (Tuesday, 20 February)
• OS for the LD/CD crowd? (Thursday, 15 February)
• AnyBrowser.com (Wednesday, 14 February)
• A List Apart: The Politics of Design (Friday, 9 February)
• ABBR vs ACRONYM, round 57894174803 [a tirade] (Wednesday, 7 February)
• RE: use of alt attributes in decorative images (Tuesday, 6 February)
• RE: ABBR vs ACRONYM, round 57894174803 (Monday, 5 February)
• RE: use of alt attributes in decorative images (Monday, 5 February)
• use of alt attributes in decorative images (Monday, 5 February)
• RE: wtop Let Us Hear From You (Monday, 5 February)
• RE: bobby compliant (Monday, 5 February)
• [w3c-wai-ig] <none> (Monday, 5 February)
• Re: bobby compliant (Monday, 5 February)
• Re: Accessibility of federal statistical tables (Tuesday, 23 January)
• RE: FW: Disturbing trend in tables (Tuesday, 23 January)
• RE: FW: Disturbing trend in tables (Monday, 22 January)
• RE: FW: Disturbing trend in tables (Monday, 22 January)
• Re: Disturbing trend in tables (Monday, 22 January)
• Re: Keyboard Alternatives and Vision Solutions (Monday, 22 January)
• Re: Fw: Disturbing trend in tables (Monday, 22 January)
• Trace ListServs (Friday, 19 January)
• RE: Fw: Disturbing trend in tables (Friday, 19 January)
• RE: Fw: Disturbing trend in tables (Thursday, 18 January)
• RE: Fw: Disturbing trend in tables (Wednesday, 17 January)
• RE: Fw: Disturbing trend in tables (Wednesday, 17 January)
• Re: Guideline 11 Interpretation (Tuesday, 16 January)
• RE: Fw: Disturbing trend in tables (Tuesday, 16 January)
• MacWorld at SanFrancisco (Tuesday, 9 January)

bdiamnd@ix.netcom.com

• RE: [w3c-wai-ig] side menu and screen readers (Tuesday, 6 March)

Ben Canning

• RE: Fw: Disturbing trend in tables (Friday, 12 January)
• RE: Fw: Disturbing trend in tables (Friday, 12 January)
• RE: Fw: Disturbing trend in tables (Friday, 12 January)
• RE: Fw: Disturbing trend in tables (Friday, 12 January)
• RE: Fw: Disturbing trend in tables (Thursday, 11 January)
• RE: Fw: Disturbing trend in tables (Wednesday, 10 January)

Ben Morris

• RE: Caution about Style Sheets (Wednesday, 17 January)

Bernard Silva

• [w3c-wai-ig] side menu and screen readers (Friday, 2 March)

Beth Skwarecki

• Re: QUESTION: use of javascript to comply with Sect 508 (Thursday, 4 January)
• Re: QUESTION: use of javascript to comply with Sect 508 (Thursday, 4 January)

Bill Kules

• Re: Caution about Style Sheets (Monday, 22 January)
• Re: Fw: Disturbing trend in tables (Wednesday, 10 January)

Brian Kelly

• Animated GIFs and accessibility guidelines (Thursday, 15 February)
• Re: HTML Validation from browser (Opera 5) (Monday, 12 February)
• Accessibility of "fusion" services (Monday, 12 February)
• Re: Can the W3C HML validaor send email when the page becomes invalid (was Re: WWW: Interoperability Crisis?) (Tuesday, 23 January)
• Can the W3C HML validaor send email when the page becomes invalid (was Re: WWW: Interoperability Crisis?) (Monday, 22 January)

Brown, Lorelei

• Keep the list on topic [ was RE: FW: Disturbing trend in tables] (Monday, 22 January)

Charles F. Munat

• RE: accessibility makeovers (Thursday, 29 March)
• RE: Consumers combat pop-ups with software, Tricks (Thursday, 8 February)
• RE: ABBR vs ACRONYM, round 57894174803 [a tirade] (Tuesday, 6 February)
• RE: ABBR vs ACRONYM, round 57894174803 [a tirade] (Tuesday, 6 February)
• RE: ABBR vs ACRONYM, round 57894174803 [a tirade] (Tuesday, 6 February)
• RE: ABBR vs ACRONYM, round 57894174803 [a tirade] (Tuesday, 6 February)
• RE: Fw: Disturbing trend in tables (Saturday, 20 January)
• RE: What HTML Means (Saturday, 20 January)
• RE: XHTML vs. WYSIWYG vs. Whatever? (Saturday, 20 January)
• RE: What HTML Means (Saturday, 20 January)
• RE: Simplicity of Authoring and Accessibility Tools (Saturday, 20 January)
• RE: [w3c-wai-ig] <none> (Saturday, 20 January)
• RE: Simplicity of Authoring and Accessibility Tools (Friday, 19 January)
• RE: Simplicity of Authoring and Accessibility Tools (Friday, 19 January)
• RE: Simplicity of Authoring and Accessibility Tools (Friday, 19 January)
• RE: Accessible _By_ (Friday, 19 January)
• RE: Simplicity of Authoring and Accessibility Tools (Friday, 19 January)
• RE: Simplicity of Authoring and Accessibility Tools (Friday, 19 January)
• RE: Simplicity of Authoring and Accessibility Tools (Friday, 19 January)
• RE: Simplicity of Authoring and Accessibility Tools (Friday, 19 January)
• RE: B vs Strong (Friday, 19 January)
• RE: Simplicity of Authoring and Accessibility Tools (Friday, 19 January)
• RE: B vs Strong (Friday, 19 January)
• RE: Accessible _By_ (Friday, 19 January)
• RE: Simplicity of Authoring and Accessibility Tools (Friday, 19 January)
• RE: Fw: Disturbing trend in tables (Thursday, 18 January)
• RE: Caution about Style Sheets (Wednesday, 17 January)
• RE: Fw: Disturbing trend in tables (Sunday, 14 January)
• RE: Fw: Disturbing trend in tables (Saturday, 13 January)
• RE: Fw: Disturbing trend in tables (Wednesday, 10 January)

Charles McCathieNevile

• Re: CSS - font-size (Tuesday, 27 March)
• Re: Please review: Web Content Accessibility Guidelines 2.0 Wor king Draft (Wednesday, 21 March)
• RE: Skipping navigation tactics (Tuesday, 20 March)
• Chat systems and accessibility (Friday, 16 March)
• Re: Text version of image used as a link (Monday, 12 March)
• Re: Most Web Books Ignore Accessibility and Usability (Friday, 9 March)
• Re: <HR> (Thursday, 8 March)
• Re: Other browsers, etc... (Thursday, 8 March)
• RE: Process/Procedure for Accessibility Testing of Software (Thursday, 8 March)
• Re: Text unavailable to sighted users but available to screen reader users (Thursday, 8 March)
• RE: Lotus Domino and Accessible Tables (Monday, 5 March)
• RE: Lotus Domino and Accessible Tables (Monday, 5 March)
• Re: Lotus Domino and Accessible Tables (Monday, 5 March)
• Re: Controlling headers w/ CSS (Thursday, 22 February)
• Re: ALT - TITLE - LONGDESC? (Wednesday, 21 February)
• RE: Any examples of <NOSCRIPT>? (Wednesday, 21 February)
• Re: Longdesc (Tuesday, 20 February)
• Re: Animated GIFs and accessibility guidelines (Monday, 19 February)
• RE: Animated GIFs and accessibility guidelines (Monday, 19 February)
• Re: 508 wording/intent (Monday, 19 February)
• RE: Frame Title and Screenreader Access (Monday, 19 February)
• RE: Frame Title and Screenreader Access (Sunday, 18 February)
• Re: Animated GIFs and accessibility guidelines (Saturday, 17 February)
• Re: Accessibility of "fusion" services (Monday, 12 February)
• RE: Client Side vs. Server Side Image Maps (Monday, 12 February)
• Re: A few questions (Monday, 12 February)
• Re: HTML Validation from browser (Opera 5) (Monday, 12 February)
• RE: Swedish Handicap Institute adopts WCAG 1.0 (Tuesday, 6 February)
• RE: ABBR vs ACRONYM, round 57894174803 [a tirade] (Tuesday, 6 February)
• Re: Accessible chat software (Monday, 5 February)
• Re: Accessible chat software (Monday, 5 February)
• Re: Accessible chat software (Sunday, 4 February)
• Re: A question of titles (Thursday, 1 February)
• Re: Table columns and screen readers (Thursday, 1 February)
• Re: A question of titles (Tuesday, 30 January)
• Re: Off Topic Question on Size of Market for 'Accessible Web Services' (Monday, 29 January)
• Re: Design Question (Thursday, 25 January)
• Re: use of alt attributes in decorative images (Thursday, 25 January)
• Re: Design Question (Wednesday, 24 January)
• Re: Can the W3C HML validaor send email when the page becomes invalid (was Re: WWW: Interoperability Crisis?) (Wednesday, 24 January)
• Dlinks, Re: character codes and repeated link phrase questions (Wednesday, 24 January)
• Re: Accessibility - A perfect solution? (Wednesday, 24 January)
• Re: Caution about Style Sheets (Tuesday, 23 January)
• Re: Standard Keyboard Controls? (Monday, 22 January)
• Re: Caution about Style Sheets (Sunday, 21 January)
• RE: Caution about Style Sheets (Saturday, 20 January)
• RE: Caution about Style Sheets (Saturday, 20 January)
• RE: server side images for geographic mapping data (Saturday, 20 January)
• Re: Useful authoring tools RE: Simplicity of Authoring and Accessibility Tools (Saturday, 20 January)
• Useful authoring tools RE: Simplicity of Authoring and Accessibility Tools (Friday, 19 January)
• Re: seeking information on W3C compliance for dynamically generated w eb pages (Friday, 19 January)
• RE: Simplicity of Authoring and Accessibility Tools (Friday, 19 January)
• Re: B vs Strong (Friday, 19 January)
• RE: Simplicity of Authoring and Accessibility Tools (Friday, 19 January)
• Re: B vs Strong (Friday, 19 January)
• RE: Simplicity of Authoring and Accessibility Tools (Friday, 19 January)
• Re: Disturbing trend in tables (Friday, 19 January)
• Re: Is This JavaScript Menu Accessible? (Monday, 15 January)
• Re: Examples of checkpoint 6.4? (Sunday, 14 January)
• Re: Examples of checkpoint 6.4? (Sunday, 14 January)
• RE: Indicating Compliance (Sunday, 14 January)
• Re: Fw: Disturbing trend in tables (Sunday, 14 January)
• Re: Examples of checkpoint 6.4? (Saturday, 13 January)
• Re: Somehwhat OT - Size of Accessibility Market (Friday, 12 January)
• RE: Indicating Compliance (Friday, 12 January)
• Re: Fw: Disturbing trend in tables (Friday, 12 January)
• RE: Fw: Disturbing trend in tables (Friday, 12 January)
• Re: user defined stylesheets (Friday, 12 January)
• Re: sample CSS for screen readers (Tuesday, 9 January)
• Re: Guideline 1.2 (Tuesday, 9 January)
• RE: QUESTION: use of JavaScript to comply with Sect 508 (Monday, 8 January)
• Re: QUESTION: use of javascript to comply with Sect 508 (Saturday, 6 January)
• Re: Tables and Screen reader question (Friday, 5 January)
• Re: How closely does Windows narrator simulate JAWS (Friday, 5 January)
• Re: Screen reader question: data table documentation (Friday, 5 January)
• Tables and Screen reader question (Friday, 5 January)
• Re: screen readers (Wednesday, 3 January)
• Re: screen readers (Wednesday, 3 January)
• RE: Methodology (Wednesday, 3 January)

Chris Croome

• Re: Caution about Style Sheets (Wednesday, 17 January)

Christopher Atkinson

• RE: Is This JavaScript Menu Accessible? (Tuesday, 16 January)
• Is This JavaScript Menu Accessible? (Monday, 15 January)

Chuck Letourneau

• ALT - TITLE - LONGDESC? (Tuesday, 20 February)

Constantine Stephanidis

• Call for Papers: New international journal UNIVERSAL ACCESS IN THE INFORMATION SOCIETY (Tuesday, 30 January)

Cynthia Waddell

• RE: Web Page Disability Access Design (Tuesday, 13 March)
• Face to Face? (Tuesday, 13 February)
• Swedish Handicap Institute adopts WCAG 1.0 (Monday, 5 February)
• RE: Politics: Strict Guidelines Considered Harmful (Thursday, 4 January)

Daniel Koger

• RE: Aaargh .. Whatever happened to Bobby? (Monday, 12 February)

daniel smith

• Re: XML generated "Flash" (was: A few questions) (Saturday, 10 February)
• Re: server side images for geographic mapping data (Wednesday, 24 January)
• Re: Guideline 11 Interpretation (Wednesday, 10 January)
• Ooops--Sorry. Overreaction. (Sunday, 7 January)
• VIRUS IN ABOVE HAHA MESSAGE! (Sunday, 7 January)
• Re: QUESTION: use of javascript to comply with Sect 508 (Sunday, 7 January)
• Re: Is AAA possible? (Monday, 1 January)

Davelofy@aol.com

• RE:%20My%20comments%20on%20tables%20vs%20image%20maps&In-Reply-To=<01BDBC69.992A (Thursday, 29 March)

Davey Leslie

• Re: Skipping navigation tactics (Wednesday, 21 March)
• Re: Applying the guidelines. (Wednesday, 14 March)
• Re: B vs Strong (Saturday, 20 January)
• Re: B vs Strong (Friday, 19 January)
• Re: Disturbing trend in tables (Friday, 19 January)
• Re: Disturbing trend in tables (Thursday, 18 January)
• Re: Caution about Style Sheets (Wednesday, 17 January)
• Re: Disturbing trend in tables (Wednesday, 17 January)
• Re: Disturbing trend in tables (Sunday, 14 January)

David Clark

• Controlling headers w/ CSS (Wednesday, 21 February)
• RE: bobby compliant (Monday, 5 February)
• Accessible chat software (Sunday, 4 February)
• RE: Design Question (Wednesday, 24 January)
• RE: Methodology (Wednesday, 3 January)

David Poehlman

• media: web able releases new product: (Thursday, 22 March)
• Re: Skipping navigation tactics (Tuesday, 20 March)
• doing it right?Fw: [jfw-employment] forms accessible (Friday, 16 March)
• new list:Fw: NEW: Webcreationz - News and Tips (Friday, 16 March)
• Re: ezine:Fw: The Webwriters' Tipsheet Ezine (Wednesday, 14 March)
• ezine:Fw: The Webwriters' Tipsheet Ezine (Wednesday, 14 March)
• curiouser and curiouser (Tuesday, 13 March)
• blocking enter key form submission: (Saturday, 3 March)
• Re: Any examples of <NOSCRIPT>? (Wednesday, 21 February)
• Re: Longdesc (Tuesday, 20 February)
• Re: Screen Readers (Monday, 19 February)
• Re: Screen Readers (Friday, 16 February)
• Re: Animated GIFs and accessibility guidelines (Thursday, 15 February)
• Re: [media] Making Sites Accessible Makes Sense For All Customers (Wednesday, 14 February)
• Re: [media] Making Sites Accessible Makes Sense For All Customers (Wednesday, 14 February)
• Re: [media] Making Sites Accessible Makes Sense For All Customers (Wednesday, 14 February)
• Re: A few questions (Friday, 9 February)
• talk your way through the web! (Friday, 9 February)
• Re: Screen readers and images (Friday, 9 February)
• media:Fw: Consumers combat pop-ups with software, Tricks (Wednesday, 7 February)
• Re: use of alt attributes in decorative images (Monday, 5 February)
• Re: use of alt attributes in decorative images (Monday, 5 February)
• Re: cio discusses accessibility (Friday, 2 February)
• Fw: Call for Articles: Accessibility of Web-Based Information Resourc es (Thursday, 1 February)
• Re: Acronyms... With Indistinct Spellings (Wednesday, 31 January)
• media:Fw: Fwd: Wired News :Adobe's Novel Approach to E-Books (Wednesday, 31 January)
• media: isps move forward with accessability plans (Tuesday, 30 January)
• Fw: Follow up on inquiry about Pocket Coach (Monday, 29 January)
• media:Fw: Webcast on Section 508 Regs and On-site Resources (Friday, 26 January)
• Re: use of alt attributes in decorative images (Thursday, 25 January)
• Re: use of alt attributes in decorative images (Thursday, 25 January)
• Re: What HTML Means (Sunday, 21 January)
• Re: [w3c-wai-ig] <none> (Saturday, 20 January)
• Re: Simplicity of Authoring and Accessibility Tools (Friday, 19 January)
• Re: Simplicity of Authoring and Accessibility Tools (Friday, 19 January)
• Re: Simplicity of Authoring and Accessibility Tools (Friday, 19 January)
• Re: Accessible _By_ (Friday, 19 January)
• Re: media: aaa from a f b? (Thursday, 18 January)
• media: aaa from a f b? (Thursday, 18 January)
• media:Fw: Web Usability, accessibility closely related (Friday, 12 January)
• Fw: Disturbing trend in tables (Wednesday, 10 January)
• Re: QUESTION: use of javascript to comply with Sect 508 (Saturday, 6 January)
• Re: QUESTION: use of javascript to comply with Sect 508 (Thursday, 4 January)
• javascript and 508 redux (Thursday, 4 January)
• Re: QUESTION: use of javascript to comply with Sect 508 (Thursday, 4 January)
• Re: screen readers (Wednesday, 3 January)
• info:Fw: Section 508 regs and Web Pages (Tuesday, 2 January)

David Woolley

• Re: accessibility makeovers (Thursday, 29 March)
• Re: Skipping navigation tactics (Tuesday, 20 March)
• Re: Text version of image used as a link (Monday, 12 March)
• Re: opinions on deprecated code plus (Saturday, 10 March)
• Re: Most Web Books Ignore Accessibility and Usability (Friday, 9 March)
• Re: Text unavailable to sighted users but available to screen reader users (Wednesday, 7 March)
• Re: Row and Column Headers - Only 1 Logical Level (Friday, 2 March)
• Re: [w3c-wai-ig] side menu and screen readers (Friday, 2 March)
• Re: Any examples of <NOSCRIPT>? (Wednesday, 21 February)
• Re: Controlling headers w/ CSS (Thursday, 22 February)
• Re: Any examples of <NOSCRIPT>? (Thursday, 22 February)
• Re: opinions on deprecated code plus (Wednesday, 21 February)
• Re: Frame Title and Screenreader Access (Sunday, 18 February)
• Re: 508 wording/intent (Sunday, 18 February)
• Re: opinions on deprecated code plus (Sunday, 18 February)
• Re: Frame Title and Screenreader Access (Saturday, 17 February)
• Re: "Text-Only" Versions Considered Harmful (Saturday, 17 February)
• Re: Animated GIFs and accessibility guidelines (Friday, 16 February)
• Re: Section 508 Question on Javascript - Section 1194.22, Paragraph (l) (Thursday, 15 February)
• Re: onmouseover, onfocus, onclick (Thursday, 15 February)
• Re: [media] Making Sites Accessible Makes Sense For All Customers (Wednesday, 14 February)
• Re: [media] Making Sites Accessible Makes Sense For All Customers (Wednesday, 14 February)
• Re: Client Side vs. Server Side Image Maps (Monday, 12 February)
• Re: google and pdf (Saturday, 10 February)
• XML generated "Flash" (was: A few questions) (Saturday, 10 February)
• Re: Screen readers and images (Saturday, 10 February)
• Re: Client Side vs. Server Side Image Maps (Saturday, 10 February)
• Re: ABBR vs ACRONYM, round 57894174803 (Saturday, 10 February)
• Re: Client Side vs. Server Side Image Maps (Thursday, 8 February)
• Re: ABBR vs ACRONYM, round 57894174803 (Wednesday, 7 February)
• Re: HTML validator (Sunday, 4 February)
• Re: HTML validator (Sunday, 4 February)
• Re: HTML validator (Sunday, 4 February)
• Re: Accessible chat software (Sunday, 4 February)
• Re: HTML validator (Sunday, 4 February)
• Re: Accessible chat software (Sunday, 4 February)
• Re: Accessible chat software (Sunday, 4 February)
• Re: Table columns and screen readers (Thursday, 1 February)
• Re: A question of titles (Wednesday, 31 January)
• Re: Betsie and other text only conversion applications (Sunday, 28 January)
• Re: Accessibility - A perfect solution? (Tuesday, 23 January)
• Re: Can the W3C HML validaor send email when the page becomes invalid (was Re: WWW: Interoperability Crisis?) (Monday, 22 January)
• Re: Fw: Disturbing trend in tables (Sunday, 21 January)
• Re: Simplicity of Authoring and Accessibility Tools (Sunday, 21 January)
• Re: Disturbing trend in tables (Saturday, 20 January)
• Re: Simplicity of Authoring and Accessibility Tools (Saturday, 20 January)
• Re: B vs Strong (Saturday, 20 January)
• Re: Caution about Style Sheets (Saturday, 20 January)
• Re: Caution about Style Sheets (Saturday, 20 January)
• Re: Simplicity of Authoring and Accessibility Tools (Saturday, 20 January)
• Re: Keyboard Alternatives and Vision Solutions (Saturday, 20 January)
• Re: Fw: Disturbing trend in tables (Saturday, 20 January)
• Re: Fw: Disturbing trend in tables (Saturday, 20 January)
• Re: Fw: Disturbing trend in tables (Saturday, 20 January)
• Re: Accessible _By_ (Saturday, 20 January)
• Re: [w3c-wai-ig] <none> (Saturday, 20 January)
• Re: MouseOver in Netscape (Wednesday, 17 January)
• Re: Indicating Compliance (Sunday, 14 January)
• Re: Fw: Disturbing trend in tables (Sunday, 14 January)
• Re: Fw: Disturbing trend in tables (Sunday, 14 January)
• Re: Examples of checkpoint 6.4? (Sunday, 14 January)
• Re: Fw: Disturbing trend in tables (Saturday, 13 January)
• Re: Examples of checkpoint 6.4? (Saturday, 13 January)
• Re: ISO-HTML and headers / form elements (Friday, 12 January)
• Re: Fw: Disturbing trend in tables (Wednesday, 10 January)
• Re: Fw: Disturbing trend in tables (Wednesday, 10 January)
• Re: QUESTION: use of JavaScript to comply with Sect 508 (Monday, 8 January)
• Re: QUESTION: use of JavaScript to comply with Sect 508 (Sunday, 7 January)
• Re: QUESTION: use of javascript to comply with Sect 508 (Saturday, 6 January)

Dick Brown

• RE: Caution about Style Sheets (Thursday, 18 January)

Didier Courtaud

• UIML Europe 2001 (Wednesday, 7 February)
• First European UIML conference (Friday, 12 January)

Don Saklad

• How to improve a weblog for access step by step (Monday, 5 March)
• Guide to Problematial Boston Public Library Use http://GuideToProblematicalLibraryUse.weblogs.com/stories (Friday, 2 March)

Emmanuelle Gutiérrez y Restrepo

• Applying the guidelines. (Tuesday, 13 March)
• RE: ABBR vs ACRONYM, round 57894174803 (Wednesday, 7 February)
• RE: ABBR vs ACRONYM, round 57894174803 [a tirade] (Tuesday, 6 February)
• RE: ABBR vs ACRONYM, round 57894174803 (Tuesday, 6 February)
• RE: ABBR vs ACRONYM, round 57894174803 (Monday, 5 February)

Erik Hodge

• Re: Fw: Disturbing trend in tables (Wednesday, 10 January)

Fitzgerald, Jimmie

• RE: 508 Accessibility Deadline - Accessibility Testing (Friday, 16 February)
• 508 Accessibility Deadline (Thursday, 15 February)
• RE: Section 508 Question on Javascript - Section 1194.22, Paragraph (l) (Wednesday, 14 February)
• RE: Aaargh .. Whatever happened to Bobby? (Tuesday, 13 February)
• Examples of screen reader processing (Friday, 9 February)
• RE: Consumers combat pop-ups with software, Tricks (Thursday, 8 February)
• JAWS Example (Tuesday, 6 February)
• Accessibility - A perfect solution? (Tuesday, 23 January)
• RE: FW: Disturbing trend in tables (Monday, 22 January)
• RE: Indicating Compliance (Friday, 12 January)
• Indicating Compliance (Friday, 12 January)
• RE: Fw: Disturbing trend in tables (Wednesday, 10 January)
• RE: Disturbing trend in tables (Wednesday, 10 January)
• RE: Guideline 1.2 (Tuesday, 9 January)
• RE: Guideline 11 Interpretation (Monday, 8 January)

Fox, Jamie

• RE: Caution about Style Sheets (Wednesday, 17 January)

Frank Gaine

• RE: Bobby rating over rated (Monday, 5 February)
• Guideline 1.2 (Tuesday, 9 January)

Frank Tobin

• Re: <HR> (Thursday, 8 March)
• Re: Animated GIFs and accessibility guidelines (Monday, 5 March)
• use of alt attributes in decorative images (Wednesday, 24 January)
• Re: Fw: Disturbing trend in tables (Monday, 22 January)
• RE: Fw: Disturbing trend in tables (Sunday, 14 January)
• Re: user defined stylesheets (Wednesday, 10 January)
• Re: Fw: Disturbing trend in tables (Wednesday, 10 January)
• Re: Fw: Disturbing trend in tables (Wednesday, 10 January)

Gatewood, Joy

• RE: Lotus Domino and Accessible Tables (Monday, 5 March)
• RE: Simplicity of Authoring and Accessibility Tools (Friday, 19 January)

Graham Oliver

• Re: Kynn's Soapbox: Accessibility and Usability (was: accessibility makeovers) (Thursday, 29 March)
• Re: FW: Web Page Disability Access Design (Tuesday, 13 March)
• Text version of image used as a link (Monday, 12 March)
• Re: Forms???? (Thursday, 8 March)
• Text unavailable to sighted users but available to screen reader users (Tuesday, 6 March)
• RE: Lotus Domino and Accessible Tables (Monday, 5 March)
• Row and Column Headers - Only 1 Logical Level (Friday, 2 March)
• Lotus Domino and Accessible Tables (Thursday, 1 March)
• Section 508 Question on Javascript - Section 1194.22, Paragraph (l) (Monday, 12 February)
• HTML Validation from browser (Opera 5) (Sunday, 11 February)
• New Zealand E-Government Web Guidelines - Exposure Draft (Wednesday, 7 February)
• RE: President's New Freedom Initiative on disability - Clarification Sought (Friday, 2 February)
• Off Topic Question on Size of Market for 'Accessible Web Services' (Saturday, 27 January)
• Comments on WCAG 2.0 Working Draft (Friday, 26 January)
• RE: testing to ensure 508 compliance (Tuesday, 16 January)

Gregg Vanderheiden

• RE: Section 508 Question on Javascript - Section 1194.22, Paragraph (l) (Wednesday, 14 February)

HARRIS Rachel D

• RE: Publishing Tools and accessibility guidelines (Tuesday, 20 February)
• RE: Animated GIFs and accessibility guidelines (Friday, 16 February)

Harvey Bingham

• Most Web Books Ignore Accessibility and Usability (Friday, 9 March)
• Web Accessibility Ripples Through IT (Thursday, 15 February)
• US Legal and Policy Resources Source (Monday, 5 February)
• FYI: Fulfilling America’s Promise to Americans with Disabilities (Friday, 2 February)
• Re: Congratulations, David (+Larry and Lila) (Saturday, 27 January)

Hemm, Randy [IMS]

• Forms???? (Thursday, 8 March)

Hiroshi Kawamura

• Re: Accessible chat software (Sunday, 4 February)

Ian Jacobs

• Scheduling (third) last call review for User Agent Accessibility Guidelines 1.0 (Wednesday, 28 March)

inekemaa@xs4all.nl

• accesible Websites/make-overs (Thursday, 29 March)

iris

• <HR> (was Re: Fleet Boston's...) (Wednesday, 7 March)

jacques@knowsystems.com

• Re: Most Web Books Ignore Accessibility and Usability (Friday, 9 March)

jaime-suarez@data-dimensions.com

• RE: 508 Accessibility Deadline - Accessibility Testing (Friday, 16 February)
• Re: 508 Accessibility Deadline - Accessibility Testing (Friday, 16 February)

Jamie Mackay

• Skipping navigation tactics (Tuesday, 20 March)
• RE: Betsie and other text only conversion applications (Sunday, 28 January)
• Betsie and other text only conversion applications (Thursday, 25 January)
• character codes and repeated link phrase questions (Tuesday, 23 January)

Jean Foster

• Re: Process/Procedure for Accessibility Testing of Software (Wednesday, 7 March)

Jeff Isom

• Screen readers and images (Friday, 9 February)

jeffrey Pledger

• media: AbleTV's webcast of the CSUN keynote address . . . (Tuesday, 20 March)
• media: AbleTV's webcast of the AFB event on 3/16/2001 . . . (Wednesday, 14 March)
• Re: Lotus Domino and Accessible Tables (Monday, 5 March)
• media: AbleTV's webcast of the Garrett Decision . . . (Tuesday, 27 February)

Jennifer Sutton

• some quick forms pointers, perhaps (Friday, 16 March)

Jim Thatcher

• RE: accessibility makeovers (Tuesday, 27 March)
• RE: Skipping navigation tactics (Tuesday, 20 March)
• RE: Other browsers, etc... (Thursday, 8 March)
• RE: Any examples of <NOSCRIPT>? (Wednesday, 21 February)
• RE: Any examples of <NOSCRIPT>? (Wednesday, 21 February)
• RE: Any examples of <NOSCRIPT>? (Wednesday, 21 February)
• RE: Any examples of <NOSCRIPT>? (Wednesday, 21 February)
• Any examples of <NOSCRIPT>? (Tuesday, 20 February)
• RE: Frame Title and Screenreader Access (Sunday, 18 February)
• RE: Frame Title and Screenreader Access (Sunday, 18 February)
• RE: Skipping Links (Friday, 16 February)
• RE: Section 508 Question on Javascript - Section 1194.22, Paragraph (l) (Wednesday, 14 February)
• RE: Section 508 Question on Javascript - Section 1194.22, Paragraph (l) (Wednesday, 14 February)
• A question of titles (Tuesday, 30 January)
• RE: FrontPage Wants to be FREEEEEEEE (Thursday, 18 January)
• RE: Caution about Style Sheets (Wednesday, 17 January)
• RE: Caution about Style Sheets (Wednesday, 17 January)
• Caution about Style Sheets (Wednesday, 17 January)
• RE: testing to ensure 508 compliance (Monday, 15 January)
• RE: Fw: Disturbing trend in tables (Friday, 12 January)
• Re: Fw: Disturbing trend in tables (Wednesday, 10 January)
• RE: QUESTION: use of JavaScript to comply with Sect 508 (Sunday, 7 January)
• RE: QUESTION: use of JavaScript to comply with Sect 508 (Sunday, 7 January)
• RE: QUESTION: use of JavaScript to comply with Sect 508 (Saturday, 6 January)
• RE: Methodology (Wednesday, 3 January)

Jim Tobias

• RE: Adobe Announces Acrobat 5.0 -- Support for Accessibility (Tuesday, 13 March)

Jo Donkin

• Screen Readers (Friday, 16 February)

Joe Clark

• Web AccessiBlog posted (Friday, 12 January)

joeclark@contenu.nu

• Tidbits accessibility article (Tuesday, 13 March)
• New book coming out (Tuesday, 13 March)

joeclark@qube.seeto.com

• Re: ALT - TITLE - LONGDESC? (Friday, 23 February)

joeclark@reddevil.seeto.com

• Tidbits tetralogy draws to a close (Wednesday, 21 March)

Joel Sanda

• RE: Accessible _By_ (Friday, 19 January)

Jon Hanna

• RE: Text unavailable to sighted users but available to screen reader users (Friday, 9 March)
• RE: <HR> (Thursday, 8 March)
• RE: <HR> (was Re: Fleet Boston's...) (Wednesday, 7 March)
• Amusing (but very annoying) accessibility error (Friday, 2 March)
• RE: [w3c-wai-ig] side menu and screen readers (Friday, 2 March)
• RE: Plain Language Resources (Tuesday, 27 February)
• RE: ALT - TITLE - LONGDESC? (Friday, 23 February)
• RE: ALT - TITLE - LONGDESC? (Friday, 23 February)
• RE: Any examples of <NOSCRIPT>? (Wednesday, 21 February)
• RE: Screen Readers (Monday, 19 February)
• RE: Screen Readers (Monday, 19 February)
• RE: "Text-Only" Versions Considered Harmful (Friday, 16 February)
• RE: "Text-Only" Versions Considered Harmful (Friday, 16 February)
• RE: I Want to Learn about ECMAScript (Friday, 16 February)
• RE: onmouseover, onfocus, onclick (Friday, 16 February)
• RE: Screen readers and Lists (Thursday, 15 February)
• RE: Section 508 Question on Javascript - Section 1194.22, Paragraph (l) (Wednesday, 14 February)
• onmouseover, onfocus, onclick (Wednesday, 14 February)
• "Text-Only" Versions Considered Harmful (Wednesday, 14 February)
• Am I off-topic? ( was Section 508 Question on Javascript...) (Wednesday, 14 February)
• RE: [media] Making Sites Accessible Makes Sense For All Customers (Wednesday, 14 February)
• A few questions (Friday, 9 February)
• RE: Client Side vs. Server Side Image Maps (Friday, 9 February)
• RE: Client Side vs. Server Side Image Maps (Thursday, 8 February)
• RE: Consumers combat pop-ups with software, Tricks (Thursday, 8 February)
• RE: Consumers combat pop-ups with software, Tricks (Thursday, 8 February)
• RE: Consumers combat pop-ups with software, Tricks (Thursday, 8 February)
• RE: Consumers combat pop-ups with software, Tricks (Thursday, 8 February)

Jonathan Chetwynd

• isketch.net (Tuesday, 27 March)
• Re: Literacy in the UK (Thursday, 22 February)
• Literacy in the UK (Thursday, 22 February)
• Re: Printing shockwave? (Wednesday, 7 February)
• Re: Printing shockwave? (Tuesday, 6 February)
• Printing shockwave? (Tuesday, 6 February)
• playing sounds in netscape or ie, using javascript: onmouseover (Tuesday, 16 January)
• playing sounds in netscape, using javascript (Monday, 15 January)
• sound problems (Wednesday, 3 January)

Judy Brewer

• CREN Webcast on Web accessibility, Thursday March 8 4pm US EST (Thursday, 8 March)
• Review reminder: Web Content Accessibility Guidelines 2.0 Working Draft (Thursday, 15 February)
• Tone of messages (Wednesday, 14 February)
• WAI Interest Group meeting, Saturday, March 24, 2001, following CSUN 2001 (Tuesday, 13 February)
• RE: President's New Freedom Initiative on disability - Clarification Sought (Friday, 2 February)
• RE: President's New Freedom Initiative on disability (Friday, 2 February)
• Please review: Web Content Accessibility Guidelines 2.0 Working Draft (Thursday, 25 January)

Judy Schnitzer

• Lynx user (Tuesday, 30 January)

K Roberts

• Plural acronyms (Monday, 19 February)

Karl Dubost

• Parody of commercial websites (Thursday, 29 March)

karl.hebenstreit@gsa.gov

• Re: Lotus Domino and Accessible Tables (Thursday, 1 March)
• RE: Plain Language Resources (Tuesday, 27 February)

Kathleen Anderson

• [media] Breaking the Access Barrier (Wednesday, 14 February)
• [media] Making Sites Accessible Makes Sense For All Customers (Monday, 12 February)
• [media] Web Accessibility Ripples Through IT (Monday, 12 February)
• [media] What Should Sites Do for People with Disabilities? (Friday, 9 February)
• Re: Simplicity of Authoring and Accessibility Tools (Friday, 19 January)
• Re: Disturbing trend in tables (Thursday, 18 January)
• Re: Fw: Disturbing trend in tables (Tuesday, 16 January)
• Re: Fw: Disturbing trend in tables (Saturday, 13 January)
• Re: Fw: Disturbing trend in tables (Friday, 12 January)

Katie Haritos-Shea

• RE: Section 508 Question on Javascript - Section 1194.22, Paragraph (l) (Wednesday, 14 February)
• FW: Languages and 508 for the Web (Wednesday, 14 February)
• Languages and 508 for the Web (Wednesday, 14 February)
• RE: Section 508 Question on Javascript - Section 1194.22, Paragraph (l) (Tuesday, 13 February)

Kelly Ford

• Re: Skipping navigation tactics (Tuesday, 20 March)
• Re: Other browsers, etc... (Thursday, 8 March)
• RE: Skipping Links (Friday, 16 February)
• Re: Design Question (Thursday, 25 January)
• Design Question (Wednesday, 24 January)
• Re: How closely does Windows narrator simulate JAWS (Friday, 5 January)
• Re: Screen reader question: data table documentation (Thursday, 4 January)

kelly@ripco.com

• Fleet Boston's Web Access Standards (Tuesday, 6 March)

Kristi R Schueler/NONFS/USDAFS

• Standard Keyboard Controls? (Monday, 22 January)
• New Web Technology Released - How does this meet with Section 508? (Wednesday, 3 January)

Kristina Seyer Smith

• MouseOver in Netscape (Tuesday, 16 January)
• Re: playing sounds in netscape, using javascript (Tuesday, 16 January)

Kynn Bartlett

• Re: Kynn's Soapbox: Accessibility and Usability (was: accessibility makeovers) (Friday, 30 March)
• Kynn's Soapbox: Accessibility and Usability (was: accessibility makeovers) (Thursday, 29 March)
• April is Accessibility Month at HTML Writers Guild (Monday, 26 March)
• FWD: "Traffic: Hit Box Reporter" (Monday, 26 March)
• Press Release: Reef Debuts EveryWare [nee Edapta] (Wednesday, 14 March)
• "Guest Lecturers" (volunteers) Sought for Online Course (Wednesday, 14 March)
• Resource site I never knew about... (Friday, 9 March)
• Re: Most Web Books Ignore Accessibility and Usability (Friday, 9 March)
• RE: Process/Procedure for Accessibility Testing of Software (Wednesday, 7 March)
• Process/Procedure for Accessibility Testing of Software (Wednesday, 7 March)
• Fwd: Plain Language Resources (Tuesday, 27 February)
• RE: Any examples of <NOSCRIPT>? (Wednesday, 21 February)
• RE: Any examples of <NOSCRIPT>? (Wednesday, 21 February)
• RE: Any examples of <NOSCRIPT>? (Wednesday, 21 February)
• RE: Any examples of <NOSCRIPT>? (Wednesday, 21 February)
• Re: Any examples of <NOSCRIPT>? (Tuesday, 20 February)
• Re: ALT - TITLE - LONGDESC? (Tuesday, 20 February)
• Re: Skipping Links (Friday, 16 February)
• Re: Skipping Links (Friday, 16 February)
• Re: Going The Whole Hog (Friday, 16 February)
• RE: "Text-Only" Versions Considered Harmful (Friday, 16 February)
• Re: "Text-Only" Versions Considered Harmful (Friday, 16 February)
• Re: Animated GIFs and accessibility guidelines (Friday, 16 February)
• Re: Screen Readers (Friday, 16 February)
• Skipping Links (Friday, 16 February)
• Re: Animated GIFs and accessibility guidelines (Thursday, 15 February)
• Re: 508 Accessibility Deadline (Thursday, 15 February)
• Re: [media] Making Sites Accessible Makes Sense For All Customers (Wednesday, 14 February)
• RE: Section 508 Question on Javascript - Section 1194.22, Paragraph (l) (Wednesday, 14 February)
• RE: Section 508 Question on Javascript - Section 1194.22, Parag raph (l) (Monday, 12 February)
• RE: Section 508 Question on Javascript - Section 1194.22, Paragraph (l) (Monday, 12 February)
• Re: Section 508 Question on Javascript - Section 1194.22, Paragraph (l) (Monday, 12 February)
• RE: ABBR vs ACRONYM, round 57894174803 [a tirade] (Tuesday, 6 February)
• RE: ABBR vs ACRONYM, round 57894174803 [a tirade] (Tuesday, 6 February)
• RE: ABBR vs ACRONYM, round 57894174803 (Monday, 5 February)
• FAQ for Accessible Web Design Online Course (Monday, 5 February)
• Re: ABBR vs ACRONYM, round 57894174803 (Monday, 5 February)
• RE: use of alt attributes in decorative images (Monday, 5 February)
• RE: ABBR vs ACRONYM, round 57894174803 (Monday, 5 February)
• Use of Color -- WCAG1 checkpoint 2.1 (Monday, 5 February)
• RE: bobby compliant (Monday, 5 February)
• RE: bobby compliant (Monday, 5 February)
• ABBR vs ACRONYM, round 57894174803 (Monday, 5 February)
• Re: bobby compliant (Monday, 5 February)
• Re: Bobby rating over rated (Monday, 5 February)
• Re: Accessible chat software (Sunday, 4 February)
• Re: HTML validator (Sunday, 4 February)
• Re: bobby compliant (Sunday, 4 February)
• Re: Accessible chat software (Sunday, 4 February)
• Re: A question of titles (Saturday, 3 February)
• Re: use of alt attributes in decorative images (Saturday, 3 February)
• Re: Accessibility - A perfect solution? (Saturday, 3 February)
• Online Course: Revised HWG D201, Accessible Web Design (Friday, 2 February)
• Re: Acronyms... With Indistinct Spellings (Wednesday, 31 January)
• Re: Betsie and other text only conversion applications (Thursday, 25 January)
• Re: use of alt attributes in decorative images (Thursday, 25 January)
• Re: use of alt attributes in decorative images (Thursday, 25 January)
• RE: Accessibility - A perfect solution? (Wednesday, 24 January)
• Re: Accessibility - A perfect solution? (Tuesday, 23 January)
• New White House site (Monday, 22 January)
• What HTML Means (Saturday, 20 January)
• XHTML vs. WYSIWYG vs. Whatever? (Saturday, 20 January)
• Re: Simplicity of Authoring and Accessibility Tools (Saturday, 20 January)
• Re: Disturbing trend in tables (Saturday, 20 January)
• Re: Fw: Disturbing trend in tables (Saturday, 20 January)
• RE: Fw: Disturbing trend in tables (Friday, 19 January)
• RE: Simplicity of Authoring and Accessibility Tools (Friday, 19 January)
• RE: Simplicity of Authoring and Accessibility Tools (Friday, 19 January)
• RE: Simplicity of Authoring and Accessibility Tools (Friday, 19 January)
• RE: Accessible _By_ (Friday, 19 January)
• Re: Simplicity of Authoring and Accessibility Tools (Friday, 19 January)
• RE: Simplicity of Authoring and Accessibility Tools (Friday, 19 January)
• RE: Accessible _By_ (Friday, 19 January)
• RE: B vs Strong (Friday, 19 January)
• Re: B vs Strong (Friday, 19 January)
• Re: B vs Strong (Friday, 19 January)
• RE: Simplicity of Authoring and Accessibility Tools (Friday, 19 January)
• RE: Simplicity of Authoring and Accessibility Tools (Friday, 19 January)
• RE: Simplicity of Authoring and Accessibility Tools (Friday, 19 January)
• RE: Accessible _By_ (Friday, 19 January)
• RE: B vs Strong (Friday, 19 January)
• RE: Fw: Disturbing trend in tables (Friday, 19 January)
• Re: Disturbing trend in tables (Friday, 19 January)
• B vs Strong (Friday, 19 January)
• FrontPage Wants to be FREEEEEEEE (Thursday, 18 January)
• Accessible _By_ (Thursday, 18 January)
• Re: server side images for geographic mapping data (Thursday, 18 January)
• Simplicity of Authoring and Accessibility Tools (Thursday, 18 January)
• RE: Fw: Disturbing trend in tables (Thursday, 18 January)
• Re: media: aaa from a f b? (Thursday, 18 January)
• Re: Caution about Style Sheets (Wednesday, 17 January)
• Re: Somehwhat OT - Size of Accessibility Market (Friday, 12 January)
• RE: Politics: Strict Guidelines Considered Harmful (Thursday, 4 January)
• Macromedia article on my CNet Accessibility Session (Thursday, 4 January)

Lakespur Roca

• Re: Simplicity of Authoring and Accessibility Tools (Friday, 19 January)
• Re: Simplicity of Authoring and Accessibility Tools (Friday, 19 January)

laura.dangelo@hrdc-drhc.gc.ca

• Consumers combat pop-ups with software, Tricks (Wednesday, 7 February)

Laurie Davis-Covin

• CSS - font-size (Monday, 26 March)

Laurie Harrison

• Frame Title and Screenreader Access (Saturday, 17 February)

Leonard R. Kasday

• Testing Cold Fusion Code [was Aaargh] (Tuesday, 13 February)
• Table Rendering Bug [was RE: Aaargh .. Whatever happened to Bobby (Tuesday, 13 February)
• Re: Examples of screen reader processing (Friday, 9 February)
• Re: Caution about Style Sheets (Tuesday, 23 January)
• Re: Caution about Style Sheets (Tuesday, 23 January)
• RE: Caution about Style Sheets (Monday, 22 January)

Lloyd G. Rasmussen

• Re: Screen Readers (Wednesday, 21 February)
• Public Comment Period for Digital Talking Book standard (Friday, 16 February)
• CSUN 2001 Presentations (Friday, 26 January)
• Re: Tables and Screen reader question (Friday, 5 January)

Loretta Guarino Reid

• Re: Adobe Announces Acrobat 5.0 -- Support for Accessibility (Tuesday, 13 March)
• Re: Guideline 11 Interpretation (Monday, 8 January)

Lori.Petrucci@cui.unige.ch

• announcing WebSound 1.0 (Wednesday, 24 January)

Lubow Scott

• Re: 508 Accessibility Deadline (Thursday, 15 February)
• Associate Data and Header cells (Monday, 12 February)
• Client Side vs. Server Side Image Maps (Thursday, 8 February)
• Re: sites with bobby rating (Monday, 5 February)
• Re: QUESTION: use of javascript to comply with Sect 508 (Thursday, 4 January)
• Re: screen readers (Wednesday, 3 January)

Mark Dale

• Re: [w3c-wai-ig] side menu and screen readers (Friday, 2 March)

Marti

• Re: Animated GIFs and accessibility guidelines (Sunday, 4 March)
• Re: [w3c-wai-ig] side menu and screen readers (Friday, 2 March)
• Re: 508 wording/intent (Tuesday, 20 February)
• 508 wording/intent (Sunday, 18 February)
• Re: Skipping Links (Friday, 16 February)
• Re: bobby compliant (Monday, 5 February)
• Re: sites with bobby rating (Monday, 5 February)
• Re: bobby compliant (Sunday, 4 February)
• Re: Accessible chat software (Sunday, 4 February)
• Re: Simplicity of Authoring and Accessibility Tools (Sunday, 21 January)
• Re: Guideline 11 Interpretation (Monday, 8 January)
• Re: New Web Technology Released - How does this meet with Section 508? (Wednesday, 3 January)

Martin McCormick

• Re: Screen Readers (Monday, 19 February)
• I Want to Learn about ECMAScript (Friday, 16 February)
• Re: [media] Making Sites Accessible Makes Sense For All Customers (Wednesday, 14 February)
• Re: [media] Making Sites Accessible Makes Sense For All Customers (Monday, 12 February)

Masayasu Ishikawa

• Re: Longdesc (Tuesday, 20 February)
• Re: Longdesc (Tuesday, 20 February)
• Re: character codes and repeated link phrase questions (Tuesday, 23 January)
• Re: ISO-HTML and headers / form elements (Saturday, 13 January)

MDeFeoJr@aol.com

• Re: Skipping navigation tactics (Tuesday, 20 March)

Melanie BEECH

• RE: ezine:Fw: The Webwriters' Tipsheet Ezine (Wednesday, 14 March)
• RE: Consumers combat pop-ups with software, Tricks (Thursday, 8 February)

Michael Burks

• an interesting question (Friday, 5 January)

Michael Cooper

• RE: bobby compliant (Monday, 5 February)
• RE: Methodology (Friday, 5 January)

Mike Baker

• Methodology (Wednesday, 3 January)

Mike Paciello

• RE: Adobe Announces Acrobat 5.0 -- Support for Accessibility (Tuesday, 13 March)
• Adobe Announces Acrobat 5.0 -- Support for Accessibility (Tuesday, 13 March)
• RE: Process/Procedure for Accessibility Testing of Software (Wednesday, 7 March)
• RE: Process/Procedure for Accessibility Testing of Software (Wednesday, 7 March)
• RE: Process/Procedure for Accessibility Testing of Software (Wednesday, 7 March)
• FW: Speaker for grad class at KSU? (Request for Speaker in Kansas) (Sunday, 18 February)

Mike Scott

• RE: accessibility makeovers (Wednesday, 28 March)
• RE: Controlling headers w/ CSS (Thursday, 22 February)
• RE: ALT - TITLE - LONGDESC? (Tuesday, 20 February)
• RE: Skipping Links (Friday, 16 February)
• RE: Screen Readers (Friday, 16 February)
• RE: Screen readers and images (Tuesday, 13 February)
• RE: Screen readers and images (Friday, 9 February)
• RE: use of alt attributes in decorative images (Monday, 5 February)
• RE: Table columns and screen readers (Thursday, 1 February)

mmclachlan@enmax.com

• Re: Please review: Web Content Accessibility Guidelines 2.0 Wor king Draft (Wednesday, 21 March)

Nick Kew

• Re: Aaargh .. Whatever happened to Bobby? (Wednesday, 14 February)
• Aaargh .. Whatever happened to Bobby? (Monday, 12 February)
• Commercial toolkit looking for review/guineapigs (Wednesday, 7 February)
• RE: HTML validator (Sunday, 4 February)
• Re: Can the W3C HML validaor send email when the page becomes invalid (was Re: WWW: Interoperability Crisis?) (Wednesday, 24 January)
• Re: Fw: Disturbing trend in tables (fwd) (Monday, 22 January)

Nicolae Herrera

• Re: buying power (Friday, 2 February)

Nicolas Lesbats

• ISO-HTML and headers / form elements (Friday, 12 January)

Nouiouat, Athmane

• FW: Web Page Disability Access Design (Tuesday, 13 March)

Oliver@iic-ltd.com

• Re: sample CSS for screen readers (Monday, 8 January)

Patrick Burke

• Re: Animated GIFs and accessibility guidelines (Thursday, 15 February)
• Re: Animated GIFs and accessibility guidelines (Thursday, 15 February)
• Re: Consumers combat pop-ups with software, Tricks (Wednesday, 7 February)
• RE: wtop Let Us Hear From You (Saturday, 3 February)
• RE: server side images for geographic mapping data (Thursday, 18 January)
• Re: disturbing trend... oops, should have read (Wednesday, 10 January)
• Re: Fw: Disturbing trend in tables (Wednesday, 10 January)
• Re: Screen reader question: data table documentation (Thursday, 4 January)

Paul Bohman

• Re: Kynn's Soapbox: Accessibility and Usability (was: accessibility makeovers) (Thursday, 29 March)
• Re: RE: accessibility makeovers (Wednesday, 28 March)
• Re: accessibility makeovers (Wednesday, 28 March)
• accessibility makeovers (Tuesday, 27 March)
• Re: Section 508 Question on Javascript - Section 1194.22, Paragraph (l) (Wednesday, 14 February)

Paul Davis

• sites with bobby rating (Tuesday, 6 February)
• sites with bobby rating (Monday, 5 February)
• Bobby rating over rated (Monday, 5 February)
• Potential Market Places was Off Topic Question on Size of Market for 'Accessible Web Services' (Tuesday, 30 January)
• Off Topic Question on Size of Market for 'Accessible Web Services' (Monday, 29 January)
• Re: Off Topic Question on Size of Market for 'Accessible Web Services' (Monday, 29 January)
• [w3c-wai-ig] <none> (Friday, 19 January)
• screen readers (Wednesday, 3 January)
• Graphic Designers are Allies, not Egotistical Enemies (Monday, 1 January)

Pedlow, Robert

• seeking information on W3C compliance for dynamically generated w eb pages (Friday, 19 January)

Phill Jenkins

• Re: Other browsers, etc... (Thursday, 8 March)
• Re: [media] Making Sites Accessible Makes Sense For All Customers (Wednesday, 14 February)
• Re: [media] Making Sites Accessible Makes Sense For All Customers (Wednesday, 14 February)
• Re: [media] Making Sites Accessible Makes Sense For All Customers (Wednesday, 14 February)
• Re: cio discusses accessibility (Friday, 2 February)
• Re: A question of titles (Thursday, 1 February)
• RE: Fw: Disturbing trend in tables (Wednesday, 10 January)
• Re: QUESTION: use of javascript to comply with Sect 508 (Saturday, 6 January)
• Re: QUESTION: use of javascript to comply with Sect 508 (Friday, 5 January)

Rapidfind

• Do it yourself (Friday, 26 January)

Rebecca Cox

• Table columns and screen readers (Wednesday, 31 January)

Reidy Brown

• RE: Section 508 Question on Javascript - Section 1194.22, Parag raph (l) (Monday, 12 February)
• Screen reader question: data table documentation (Thursday, 4 January)
• RE: QUESTION: use of javascript to comply with Sect 508 (Thursday, 4 January)
• QUESTION: use of javascript to comply with Sect 508 (Thursday, 4 January)
• RE: FYI (Tuesday, 2 January)

Ricardo Sánchez

• Longdesc (Monday, 19 February)
• google and pdf (Saturday, 10 February)

rkthunga@humanmarkup.org

• Human Markup Language -- Initiative (Monday, 19 February)

Robert Neff

• Re: Animated GIFs and accessibility guidelines (Sunday, 4 March)
• device independence (Sunday, 4 March)
• RE: Printing shockwave? (Monday, 12 February)
• RE: Printing shockwave? (Wednesday, 7 February)
• RE: bobby compliant (Monday, 5 February)
• RE: Swedish Handicap Institute adopts WCAG 1.0 (Monday, 5 February)
• RE: Bobby rating over rated (Monday, 5 February)
• RE: Accessible chat software (Monday, 5 February)
• RE: HTML validator (Sunday, 4 February)
• RE: HTML validator (Sunday, 4 February)
• RE: HTML validator (Sunday, 4 February)
• HTML validator (Sunday, 4 February)
• bobby compliant (Sunday, 4 February)
• RE: wtop Let Us Hear From You (Friday, 2 February)
• RE: buying power (Friday, 2 February)
• RE: cio discusses accessibility (Friday, 2 February)
• buying power (Friday, 2 February)
• cio discusses accessibility (Friday, 2 February)
• RE: President's New Freedom Initiative on disability (Friday, 2 February)
• RE: President's New Freedom Initiative on disability (Thursday, 1 February)
• President's New Freedom Initiative on disability (Thursday, 1 February)
• RE: Simplicity of Authoring and Accessibility Tools (Friday, 19 January)
• RE: Fw: Disturbing trend in tables (Friday, 19 January)
• RE: Fw: Disturbing trend in tables (Friday, 19 January)
• RE: Simplicity of Authoring and Accessibility Tools (Thursday, 18 January)
• RE: Fw: Disturbing trend in tables (Thursday, 18 January)
• RE: server side images for geographic mapping data (Thursday, 18 January)
• RE: server side images for geographic mapping data (Thursday, 18 January)
• RE: Caution about Style Sheets (Thursday, 18 January)
• RE: Caution about Style Sheets (Wednesday, 17 January)
• RE: Caution about Style Sheets (Wednesday, 17 January)
• RE: Caution about Style Sheets (Wednesday, 17 January)
• RE: Fw: Disturbing trend in tables (Wednesday, 17 January)
• RE: testing to ensure 508 compliance (Tuesday, 16 January)
• RE: Fw: Disturbing trend in tables (Wednesday, 10 January)
• RE: Disturbing trend in tables (Wednesday, 10 January)
• RE: Disturbing trend in tables (Wednesday, 10 January)
• RE: Guideline 11 Interpretation (Monday, 8 January)

Ryan Eby

• Re: FrontPage Wants to be FREEEEEEEE (Friday, 19 January)

Sam Cancilla

• Re: New White House site (Wednesday, 24 January)

sarah@thedesigngirl.com

• listservs (Wednesday, 14 March)

Schmetzke, Axel

• Call for Articles (Friday, 9 February)

Schuur, Shawn M

• RE: server side images for geographic mapping data (Thursday, 18 January)
• server side images for geographic mapping data (Thursday, 18 January)
• screen readers (Wednesday, 3 January)
• RE: Methodology (Wednesday, 3 January)

Scott Luebking

• BayCHI meeting on future Oracle interfaces and GNOME (Monday, 8 January)

Sean B. Palmer

• Re: <HR> (Thursday, 8 March)
• Re: Going The Whole Hog (Friday, 16 February)
• Going The Whole Hog (Friday, 16 February)
• Re: Animated GIFs and accessibility guidelines (Thursday, 15 February)
• Re: ABBR vs ACRONYM, round 57894174803 [a tirade] (Tuesday, 6 February)
• Re: ABBR vs ACRONYM, round 57894174803 (Monday, 5 February)
• Acronyms... With Indistinct Spellings (Wednesday, 31 January)

Selway, James K

• ARPCT (Monday, 29 January)
• RE: WAI Website design (Tuesday, 2 January)
• WAI Website design (Tuesday, 2 January)

Simon Harper

• Re: Skipping navigation tactics (Tuesday, 20 March)

sinarmaya@retemail.es

• RE: ABBR vs ACRONYM, round 57894174803 (Thursday, 8 February)

Steven McCaffrey

• Re: Kynn's Soapbox: Accessibility and Usability (was: accessibility makeovers) (Thursday, 29 March)
• Re: Process/Procedure for Accessibility Testing of Software (Wednesday, 7 March)
• RE: Any examples of <NOSCRIPT>? (Wednesday, 21 February)
• Re: President's New Freedom Initiative on disability (Thursday, 1 February)
• Re: New White House site (Tuesday, 23 January)
• Accessibility of federal statistical tables (Tuesday, 23 January)
• Re: MouseOver in Netscape (Tuesday, 16 January)
• disturbing trend... oops, should have read (Wednesday, 10 January)
• RE: Fw: Disturbing trend in tables (Wednesday, 10 January)
• Re: Tables and Screen reader question (Friday, 5 January)

Sue Hill

• Re: Printing shockwave? (Tuesday, 6 February)

Suzanne Nikolaisen

• WML question (Friday, 16 March)
• Other browsers, etc... (Thursday, 8 March)

T. V. Raman

• Importance of interchangeable electronic information (Sunday, 28 January)
• Alert to guide-dog users travelling to Europe-- (Friday, 26 January)

Taylor-Made

• [w3c-wai-ig] <none> (Saturday, 20 January)
• [w3c-wai-ig] <none> (Saturday, 20 January)

Terje Bless

• RE: HTML validator (Sunday, 4 February)
• Re: Can the W3C HML validaor send email when the page becomes invalid (was Re: WWW: Interoperability Crisis?) (Wednesday, 24 January)

Terrie King

• Re: media: aaa from a f b? (Thursday, 18 January)

Terry Crowley

• RE: Simplicity of Authoring and Accessibility Tools (Friday, 19 January)
• RE: Disturbing trend in tables (Wednesday, 10 January)

Terry Hammon

• Keyboard Alternatives and Vision Solutions (Thursday, 18 January)

Thomas, Cassandra

• Examples of checkpoint 6.4? (Friday, 12 January)
• Somehwhat OT - Size of Accessibility Market (Friday, 12 January)

Timothy Stephen Springer

• RE: Skipping navigation tactics (Tuesday, 20 March)
• RE: Section 508 Question on Javascript - Section 1194.22, Parag raph (l) (Monday, 12 February)
• RE: Section 508 Question on Javascript - Section 1194.22, Paragraph (l) (Monday, 12 February)

Tina Marie Holmboe

• Re: Any examples of <NOSCRIPT>? (Wednesday, 21 February)
• Re: Can the W3C HML validaor send email when the page becomes invalid (was Re: WWW: Interoperability Crisis?) (Wednesday, 24 January)
• Re: Fw: Disturbing trend in tables (Wednesday, 17 January)
• Re: Fw: Disturbing trend in tables (Tuesday, 16 January)
• Re: Fw: Disturbing trend in tables (Saturday, 13 January)
• Re: Fw: Disturbing trend in tables (Saturday, 13 January)
• Re: Fw: Disturbing trend in tables (Saturday, 13 January)
• Re: Fw: Disturbing trend in tables (Saturday, 13 January)
• Re: Fw: Disturbing trend in tables (Friday, 12 January)
• Re: Fw: Disturbing trend in tables (Wednesday, 10 January)
• Re: Fw: Disturbing trend in tables (Wednesday, 10 January)
• Re: Fw: Disturbing trend in tables (Wednesday, 10 January)

tina@elfi.org

• Re: Methodology (Thursday, 4 January)

tom mcCain

• RE: Accessible _By_ (Friday, 19 January)

Wayne Myers

• RE: "Text-Only" Versions Considered Harmful (Friday, 16 February)
• RE: Betsie and other text only conversion applications (Monday, 29 January)
• RE: Betsie and other text only conversion applications (Monday, 29 January)
• RE: Betsie and other text only conversion applications (Friday, 26 January)

Welna.Sarah

• RE: Am I off-topic? ( was Section 508 Question on Javascript...) (Wednesday, 14 February)

Last message date: Thursday, 29 March 2001 19:41:09 UTC