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

Adam Cooper

• RE: SC 4.1.1 source fails but DOM passes - must a page fail? (Friday, 11 January)

Alastair Campbell

• Re: accessible autocomplete (Wednesday, 20 March)
• Re: Should we add keyboard focus to headings/text/non-linked images? (Tuesday, 5 March)
• RE: CMS required alt text for images (Saturday, 2 March)
• Re: Reconsidering Pre and Reflow (Thursday, 7 February)
• Hidden text - Clip CSS deprecated (Friday, 11 January)
• RE: SC 2.3.3 Animation from Interactions question - an accordion (Thursday, 10 January)
• Re: SC 2.3.3 Animation from Interactions question - an accordion (Thursday, 10 January)

Andrea Douglas

• CMS required alt text for images (Saturday, 2 March)
• Re: Linking to non HTML Resources (PDF) (Word doc) etc. (Monday, 21 January)
• Linking to non HTML Resources (PDF) (Word doc) etc. (Thursday, 17 January)

Andrew Kirkpatrick

• Re: WCAG 2.1 compliance for brochure pdfs (Friday, 11 January)

Andrews, David B (DEED)

• RE: screen readers and punctuation (Wednesday, 13 February)

ann junker

• Re: Problems changing color (Monday, 21 January)

ashraf aleem

• Re: accessible autocomplete (Wednesday, 20 March)

Bristow, Alan

• SC 4.1.1 source fails but DOM passes - must a page fail? (Thursday, 10 January)
• RE: SC 2.3.3 Animation from Interactions question - an accordion (Thursday, 10 January)
• SC 2.3.3 Animation from Interactions question - an accordion (Wednesday, 9 January)

Bryan Garaventa

• RE: accessible autocomplete (Wednesday, 20 March)
• Future AccName Spec planning, strategy, and functional testing using the AccName Prototype. (Thursday, 7 March)
• RE: How to test the AccName algorithm dynamically using AccName Prototype (Monday, 25 February)
• How to test the AccName algorithm dynamically using AccName Prototype (Saturday, 23 February)

Casey Hickey

• Re: screen readers and punctuation (Wednesday, 13 February)
• Re: SC 4.1.1 source fails but DOM passes - must a page fail? (Thursday, 10 January)

chagnon@pubcom.com

• RE: WCAG 2.1 compliance for brochure pdfs (Friday, 11 January)

Charles 'chaals' (McCathie) Nevile

• Re: CMS required alt text for images (Saturday, 2 March)
• Re: Linking to non HTML Resources (PDF) (Word doc) etc. (Thursday, 17 January)

Christophe Strobbe

• Re: SC 4.1.1 source fails but DOM passes - must a page fail? (Friday, 11 January)

Daniel Burnett

• REQUEST for updated review: Verifiable Credentials Data Model 1.0 (Monday, 18 February)

David Best

• RE: CMS required alt text for images (Saturday, 2 March)

Dirks, Susanne

• Easy Reading Newsletter - First Issue (Friday, 22 March)

Eric Eggert

• Re: Reconsidering Pre and Reflow (Wednesday, 6 February)

Granquist, Christina M

• Why Do Buttons in IOS Apps not show up in the VoiceOver Rotor? (Monday, 25 March)

Gunderson, Jon R

• RE: Buttons: Why Space and Enter? Why different event listeners? (ARIA Authoring Practices) (Monday, 25 February)
• AInspector WCAG Add-on for Firefox now available (Wednesday, 20 February)

isabel brison

• Re: Hidden text - Clip CSS deprecated (Saturday, 12 January)

J. Albert Bowden

• Re: Linking to non HTML Resources (PDF) (Word doc) etc. (Thursday, 17 January)

James A.

• RE: screen readers and punctuation (Thursday, 14 February)

Janina Sajka

• Re: (Re-)introduction (Friday, 8 February)

Jessica Korkue

• Accessible Wordpress plugin for pop up alerts (Tuesday, 8 January)

Jim Allan

• Re: screen readers and punctuation (Thursday, 14 February)

Jonathan Avila

• RE: Accessibility Modes (Monday, 4 March)
• RE: Problems changing color (Monday, 21 January)
• RE: Hidden text - Clip CSS deprecated (Thursday, 17 January)
• RE: Hidden text - Clip CSS deprecated (Monday, 14 January)
• RE: SC 4.1.1 source fails but DOM passes - must a page fail? (Friday, 11 January)

Joseph Yang

• Re: screen readers and punctuation (Wednesday, 13 February)
• Re: screen readers and punctuation (Wednesday, 13 February)

Kalpeshkumar Jain

• Re: screen readers and punctuation (Thursday, 14 February)

Karen Lewellen

• RE: screen readers and punctuation (Thursday, 14 February)
• Re: screen readers and punctuation (Thursday, 14 February)
• RE: screen readers and punctuation (Thursday, 14 February)
• Re: screen readers and punctuation (Thursday, 14 February)
• Re: screen readers and punctuation (Thursday, 14 February)
• Re: screen readers and punctuation (Thursday, 14 February)
• Re: screen readers and punctuation (Thursday, 14 February)

Karlen Communications

• RE: screen readers and punctuation (Friday, 15 February)
• RE: screen readers and punctuation (Friday, 15 February)
• RE: screen readers and punctuation (Thursday, 14 February)
• RE: screen readers and punctuation (Thursday, 14 February)
• RE: screen readers and punctuation (Thursday, 14 February)

Katherine Shaw

• Re: Should we add keyboard focus to headings/text/non-linked images? (Tuesday, 5 March)
• Should we add keyboard focus to headings/text/non-linked images? (Monday, 4 March)

Katie Haritos-Shea

• Re: (Re-)introduction (Friday, 8 February)

Léonie Watson

• Re: screen readers and punctuation (Thursday, 14 February)
• Re: screen readers and punctuation (Thursday, 14 February)
• Re: screen readers and punctuation (Thursday, 14 February)
• Re: screen readers and punctuation (Wednesday, 13 February)

Mark Rogers

• Re: screen readers and punctuation (Thursday, 14 February)
• Re: SC 4.1.1 source fails but DOM passes - must a page fail? (Friday, 11 January)
• Re: SC 4.1.1 source fails but DOM passes - must a page fail? (Thursday, 10 January)

Matthew Tylee Atkinson

• Accessibility and proposed Chrome extension API and UI changes (Sunday, 24 February)
• (Re-)introduction (Thursday, 7 February)

Michellanne Li

• Re: accessible autocomplete (Thursday, 21 March)
• Re: accessible autocomplete (Wednesday, 20 March)
• accessible autocomplete (Wednesday, 20 March)
• Re: screen readers and punctuation (Wednesday, 13 February)
• Re: screen readers and punctuation (Wednesday, 13 February)
• screen readers and punctuation (Wednesday, 13 February)

Patrick H. Lauke

• Re: CMS required alt text for images (Saturday, 2 March)
• Re: Buttons: Why Space and Enter? Why different event listeners? (Monday, 25 February)
• Re: SC 4.1.1 source fails but DOM passes - must a page fail? (Thursday, 10 January)

Paul E Matthews

• RE: Linking to non HTML Resources (PDF) (Word doc) etc. [SEC=UNOFFICIAL] (Thursday, 17 January)

Phill Jenkins

• Re: screen readers and punctuation (Thursday, 14 February)
• Re: SC 4.1.1 source fails but DOM passes - must a page fail? (Thursday, 10 January)

Pyatt, Elizabeth J

• Re: CMS required alt text for images (Saturday, 2 March)
• Re: screen readers and punctuation (Thursday, 14 February)
• Re: screen readers and punctuation (Thursday, 14 February)
• Re: screen readers and punctuation (Thursday, 14 February)
• Re: screen readers and punctuation (Thursday, 14 February)
• Re: screen readers and punctuation (Thursday, 14 February)
• Re: screen readers and punctuation (Thursday, 14 February)
• Re: screen readers and punctuation (Thursday, 14 February)
• Re: screen readers and punctuation (Thursday, 14 February)
• Re: screen readers and punctuation (Wednesday, 13 February)

Raquel

• Links: different view and new window (Friday, 11 January)

Ryan McCalla

• Document Accessibility Scanner (Wednesday, 27 March)

Samuel Clough

• Accessibility Modes (Monday, 4 March)

Sean Murphy (seanmmur)

• RE: Should we add keyboard focus to headings/text/non-linked images? (Tuesday, 5 March)
• RE: screen readers and punctuation (Thursday, 14 February)
• RE: screen readers and punctuation (Wednesday, 13 February)
• RE: Linking to non HTML Resources (PDF) (Word doc) etc. (Thursday, 17 January)

Sharron Rush

• Accessibility Internet Rally for college student teams (AIR-U) (Sunday, 27 January)

Srinivasu Chakravarthula

• Re: CMS required alt text for images (Sunday, 3 March)

Steve Green

• RE: accessible autocomplete (Wednesday, 20 March)

Steve Lee

• Re: accessible autocomplete (Tuesday, 26 March)
• Re: accessible autocomplete (Wednesday, 20 March)
• Re: Buttons: Why Space and Enter? Why different event listeners? (Monday, 25 February)
• Re: (Re-)introduction (Monday, 11 February)

Taliesin Smith

• Re: Buttons: Why Space and Enter? Why different event listeners? (Sunday, 3 March)
• Re: Buttons: Why Space and Enter? Why different event listeners? (Thursday, 28 February)
• Buttons: Why Space and Enter? Why different event listeners? (Monday, 25 February)

Taylor Snook

• Re: Document Accessibility Scanner (Thursday, 28 March)

Tobias Bengfort

• Re: accessible autocomplete (Wednesday, 20 March)
• Re: How to test the AccName algorithm dynamically using AccName Prototype (Saturday, 23 February)

Wayne Dick

• Reconsidering Pre and Reflow (Tuesday, 5 February)
• Re: Problems changing color (Monday, 21 January)
• Problems changing color (Saturday, 19 January)

Last message date: Thursday, 28 March 2019 20:47:35 UTC