w3c-wai-ig@w3.org from January to March 2015 by date

Tuesday, 31 March 2015

• Re: Are word forms accessible? accessys@smart.net
• Are word forms accessible? Madhavi Herle

Sunday, 29 March 2015

• Re: 508 Refresh, request to delay until reasonable accommodation is possible for low vision Wayne Dick
• Re: 508 Refresh, request to delay until reasonable accommodation is possible for low vision Olaf Drümmer
• Re: 508 Refresh, request to delay until reasonable accommodation is possible for low vision chaals@yandex-team.ru

Saturday, 28 March 2015

• For educators: How to create a curriculum for teaching ARIA; differentiating between content authors and developers Bryan Garaventa
• 508 Refresh, request to delay until reasonable accommodation is possible for low vision Wayne Dick

Friday, 27 March 2015

• RE: Usage of Articles Léonie Watson
• Re: Usage of Articles Userite
• RE: Usage of Articles David Best
• Re: Usage of Articles Gunderson, Jon R
• RE: Usage of Articles Léonie Watson
• RE: Usage of Articles David Best

Thursday, 26 March 2015

• Re: Usage of Articles chaals@yandex-team.ru

Thursday, 20 November 2014

• Usage of Articles Oscar

Thursday, 26 March 2015

• Professional Certificate in Web Accessibility registrations close 7 April Adrian Redden

Monday, 23 March 2015

• RE: Screen reader support and browsers Bourne, Sarah (ITD)

Sunday, 22 March 2015

• Re: Screen reader support and browsers accessys@smart.net
• Re: Screen reader support and browsers chaals@yandex-team.ru
• Re: Screen reader support and browsers jason@accessibleculture.org
• Re: Screen reader support and browsers Patrick H. Lauke
• Re: Screen reader support and browsers Felix Miata
• Screen reader support and browsers Erin Prichard

Wednesday, 18 March 2015

• RECALL: REQUEST: Indicate your ability to meet on Thursday May 14th at Austin Face-to-Face Sharron Rush
• REQUEST: Indicate your ability to meet on Thursday May 14th at Austin Face-to-Face Sharron Rush

Friday, 13 March 2015

• RE: Accessibility in WordPress John Foliot
• Re: Accessibility in WordPress Graham Armfield
• Re: Accessibility in WordPress Jennifer Sutton
• Re: Accessibility in WordPress chaals@yandex-team.ru
• Re: Accessibility in WordPress Katherine Mancuso
• Accessibility in WordPress Char Easter

Wednesday, 4 March 2015

• SV: SV: HTML Image Description Extension (longdesc) is a W3C Recommendation Lisa Yayla
• SV: SV: HTML Image Description Extension (longdesc) is a W3C Recommendation Lisa Yayla

Tuesday, 3 March 2015

• Re: Data Table Sort Feature Devarshi Pant
• Re: Data Table Sort Feature Sailesh Panchang
• Re: SV: HTML Image Description Extension (longdesc) is a W3C Recommendation Shawn Henry
• WCAG-EM Report Tool: Web Accessibility Evaluation Report Generator Shawn Henry
• Web Accessibility Tutorials on Forms, Images, Tables Shawn Henry
• How to Meet WCAG 2.0 Quick Reference - Redesign In-Progress Shawn Henry
• Re: Data Table Sort Feature Devarshi Pant
• Re: SV: HTML Image Description Extension (longdesc) is a W3C Recommendation Laura Carlson
• SV: HTML Image Description Extension (longdesc) is a W3C Recommendation Lisa Yayla

Monday, 2 March 2015

• Re: Data Table Sort Feature Sailesh Panchang
• Data Table Sort Feature Devarshi Pant
• RE: Your definition of WCAG2.0 conformance Oscar Cao
• RE: Your definition of WCAG2.0 conformance Oscar Cao
• Re: Your definition of WCAG2.0 conformance Patrick H. Lauke
• Re: Your definition of WCAG2.0 conformance Michael A. Peters
• Your definition of WCAG2.0 conformance Oscar Cao

Friday, 27 February 2015

• FCC Extends Deadline for Chairman’s AAA and Invites Submission of Supplementary Materials Jamal Mazrui
• Re: best way to make content visible only to screen readers ?? Michael A. Peters
• RE: best way to make content visible only to screen readers ?? Jonathan Avila
• Re: best way to make content visible only to screen readers ?? Adam Powell
• Re: What's everyone's view on backwards-support, etc for ARIA Gijs Veyfeyken
• Re: What's everyone's view on backwards-support, etc for ARIA Patrick H. Lauke
• Re: What's everyone's view on backwards-support, etc for ARIA Steve Faulkner
• Re: What's everyone's view on backwards-support, etc for ARIA Mitchell Evan
• Re: best way to make content visible only to screen readers ?? Mitchell Evan
• RE: What's everyone's view on backwards-support, etc for ARIA Oscar Cao
• best way to make content visible only to screen readers ?? Michael A. Peters

Thursday, 26 February 2015

• Call for Review: SVG Accessibility API Mappings Working Draft Shawn Henry
• Understanding WCAG & WCAG Techniques Updated February 2015 Shawn Henry
• Call for Review: Mobile Accessibility - How WCAG 2.0 and Other W3C/WAI Guidelines Apply Shawn Henry
• HTML Image Description Extension (longdesc) is a W3C Recommendation Shawn Henry
• Re: mobile accessibility search? Karen Lewellen
• RE: What's everyone's view on backwards-support, etc for ARIA Jonathan Avila
• Re: mobile accessibility search? Jon Gibbins
• Re: What's everyone's view on backwards-support, etc for ARIA Steve Faulkner
• What's everyone's view on backwards-support, etc for ARIA Oscar Cao

Wednesday, 25 February 2015

• RE: mobile accessibility search? Karen Lewellen
• Re: mobile accessibility search? Karen Lewellen
• RE: mobile accessibility search? Kriss Fearon
• Re: mobile accessibility search? Patrick H. Lauke
• Re: mobile accessibility search? Patrick H. Lauke
• mobile accessibility search? Karen Lewellen

Tuesday, 24 February 2015

• RE: About WCAG 2.0 David Best
• Re: About WCAG 2.0 chaals@yandex-team.ru
• Re: About WCAG 2.0 Lars Ballieu Christensen
• About WCAG 2.0 Daeho Kang
• W3C WAI Report... Colin German

Sunday, 22 February 2015

• Re: 508 Refresh and Reasonable Accommodation for Low Vision Jim Tobias

Friday, 20 February 2015

• Re: Using the HTML header element safely Steve Faulkner
• Using the HTML header element safely Mitchell Evan
• RE: Example of an accessible autocomplete field Bryan Garaventa
• Re: Understanding the main element Michael A. Peters
• Re: Understanding the main element Michael A. Peters
• Understanding the main element Michael A. Peters
• Example of an accessible autocomplete field Erin Prichard

Thursday, 19 February 2015

• Re: 508 Refresh and Reasonable Accommodation for Low Vision Jim Allan
• Re: 508 Refresh and Reasonable Accommodation for Low Vision info@denisboudreau.org
• Meanwhile in Europe (was: 508 Refresh to be published) Christophe Strobbe
• Re: 508 Refresh and Reasonable Accommodation for Low Vision Mike Elledge
• More on 508 Refresh Wayne Dick

Wednesday, 18 February 2015

• Re: 508 Refresh and Reasonable Accommodation for Low Vision Phill Jenkins
• Re: 508 Refresh and Reasonable Accommodation for Low Vision Mike Elledge
• Re: 508 Refresh and Reasonable Accommodation for Low Vision Olaf Drümmer
• 508 Refresh and Reasonable Accommodation for Low Vision Wayne Dick

Tuesday, 17 February 2015

• Re: Accessibility of Google's new reCAPTCHA accessys@smart.net
• RE: Accessibility of Google's new reCAPTCHA Haileselassie, Antonio O. (HQ-LM020)[DIGITAL MANAGEMENT INC.]
• Accessibility of Google's new reCAPTCHA Williams, William R -FS

Monday, 16 February 2015

• Re: the official definition [of web accessibility] from the W3C is wrong Gregg Vanderheiden
• RE: the official definition [of web accessibility] from the W3C is wrong Jonathan Avila
• Re: the official definition [of web accessibility] from the W3C is wrong Michael Gower
• Re: the official definition [of web accessibility] from the W3C is wrong Gregg Vanderheiden
• Re: the official definition [of web accessibility] from the W3C is wrong Michael Gower

Saturday, 14 February 2015

• Re: 508 Refresh to be published Mike Elledge
• RE: the official definition [of web accessibility] from the W3C is wrong Jan Eric Hellbusch

Friday, 13 February 2015

• 508 Refresh to be published Phill Jenkins
• Re: the official definition [of web accessibility] from the W3C is wrong Kate Perkins
• Re: the official definition [of web accessibility] from the W3C is wrong Phill Jenkins
• RE: the official definition [of web accessibility] from the W3C is wrong Roger Hudson

Thursday, 12 February 2015

• RE: the official definition [of web accessibility] from the W3C is wrong John Foliot
• Re: the official definition [of web accessibility] from the W3C is wrong Gregg Vanderheiden
• RE: the official definition [of web accessibility] from the W3C is wrong Howard Leicester
• Re: the official definition [of web accessibility] from the W3C is wrong Kate Perkins
• Re: the official definition [of web accessibility] from the W3C is wrong Sailesh Panchang

Wednesday, 11 February 2015

• Re: the official definition [of web accessibility] from the W3C is wrong Wayne Dick

Monday, 9 February 2015

• RE: the official definition [of web accessibility] from the W3C is wrong Jan Eric Hellbusch

Sunday, 8 February 2015

• Re: the official definition [of web accessibility] from the W3C is wrong Jens Oliver Meiert
• Re: the official definition [of web accessibility] from the W3C is wrong accessys@smart.net

Saturday, 7 February 2015

• Re: the official definition [of web accessibility] from the W3C is wrong Rakesh

Friday, 6 February 2015

• Re: the official definition [of web accessibility] from the W3C is wrong deborah.kaplan@suberic.net
• Re: the official definition [of web accessibility] from the W3C is wrong Christophe Strobbe
• Re: the official definition [of web accessibility] from the W3C is wrong Erich Manser
• Re: the official definition [of web accessibility] from the W3C is wrong Phill Jenkins
• Re: the official definition [of web accessibility] from the W3C is wrong Devarshi Pant
• Re: the official definition [of web accessibility] from the W3C is wrong Steve Faulkner
• Re: the official definition [of web accessibility] from the W3C is wrong chaals@yandex-team.ru
• Re: the official definition [of web accessibility] from the W3C is wrong Brian Cragun
• Re: the official definition [of web accessibility] from the W3C is wrong Bjoern Hoehrmann
• RE: the official definition [of web accessibility] from the W3C is wrong Jan Eric Hellbusch
• Call for papers: Accessibility track at the International Conference of Web Engineering, ICWE 2015 Markel Vigo
• the official definition [of web accessibility] from the W3C is wrong Steve Faulkner
• Re: Accessible Testing Protocol for Mobile Website Gijs Veyfeyken

Thursday, 5 February 2015

• RE: Accessible Testing Protocol for Mobile Website Phill Jenkins
• RE: Accessible Testing Protocol for Mobile Website Jonathan Avila
• Re: Accessible Testing Protocol for Mobile Website Userite
• RE: Accessible Testing Protocol for Mobile Website Howard Leicester
• Re: Accessible Testing Protocol for Mobile Website Mike Elledge
• RE: Accessible Testing Protocol for Mobile Website Phill Jenkins
• Re: Accessible Testing Protocol for Mobile Website Rafael Xavier
• RE: Accessible Testing Protocol for Mobile Website Alastair Campbell
• RE: Accessible Testing Protocol for Mobile Website Andy Keyworth
• RE: Accessible Testing Protocol for Mobile Website Jamal Mazrui
• RE: Accessible Testing Protocol for Mobile Website SALES, TERRY LYNN
• Accessible Testing Protocol for Mobile Website Mike Elledge

Wednesday, 28 January 2015

• RE: Ubuntu on a dial up modem with Lynx (RE: PDF accessibility guidelines. WAS: Re: PDF's and Signatures) John Foliot

Tuesday, 27 January 2015

• RE: Ubuntu on a dial up modem with Lynx (RE: PDF accessibility guidelines. WAS: Re: PDF's and Signatures) accessys@smart.net
• RE: Ubuntu on a dial up modem with Lynx (RE: PDF accessibility guidelines. WAS: Re: PDF's and Signatures) John Foliot
• Re: Ubuntu on a dial up modem with Lynx (RE: PDF accessibility guidelines. WAS: Re: PDF's and Signatures) Olaf Drümmer
• Re: Ubuntu on a dial up modem with Lynx (RE: PDF accessibility guidelines. WAS: Re: PDF's and Signatures) accessys@smart.net
• Ubuntu on a dial up modem with Lynx (RE: PDF accessibility guidelines. WAS: Re: PDF's and Signatures) John Foliot
• Re: PDF accessibility guidelines. WAS: Re: PDF's and Signatures Olaf Drümmer
• RE: PDF accessibility guidelines. WAS: Re: PDF's and Signatures accessys@smart.net
• RE: PDF accessibility guidelines. WAS: Re: PDF's and Signatures Howard Leicester
• Re: PDF accessibility guidelines. WAS: Re: PDF's and Signatures Duff Johnson
• [list parameters & thread closed] Re: PDF accessibility guidelines. WAS: Re: PDF's and Signatures Shawn Henry
• RE: PDF accessibility guidelines. WAS: Re: PDF's and Signatures Adam Cooper
• I am always amazed at the inaccessibility of classroom materials Chris Leighton

Monday, 26 January 2015

• RE: PDF accessibility guidelines. WAS: Re: PDF's and Signatures accessys@smart.net
• Re: PDF accessibility guidelines accessys@smart.net
• Re: PDF accessibility guidelines. WAS: Re: PDF's and Signatures David Woolley
• RE: PDF accessibility guidelines. WAS: Re: PDF's and Signatures SALES, TERRY LYNN
• RE: PDF accessibility guidelines. WAS: Re: PDF's and Signatures John Foliot
• Re: PDF accessibility guidelines Felix Miata
• Re: PDF accessibility guidelines. WAS: Re: PDF's and Signatures accessys@smart.net
• Re: PDF accessibility guidelines. WAS: Re: PDF's and Signatures accessys@smart.net
• Re: PDF accessibility guidelines accessys@smart.net
• Re: PDF accessibility guidelines. WAS: Re: PDF's and Signatures David Woolley
• Re: PDF accessibility guidelines. WAS: Re: PDF's and Signatures Duff Johnson
• Re: PDF accessibility guidelines. WAS: Re: PDF's and Signatures David Woolley
• Re: PDF accessibility guidelines. WAS: Re: PDF's and Signatures accessys@smart.net
• Re: PDF accessibility guidelines. WAS: Re: PDF's and Signatures Thompson, Rachel
• Re: PDF accessibility guidelines. WAS: Re: PDF's and Signatures Duff Johnson
• RE: PDF accessibility guidelines. WAS: Re: PDF's and Signatures Adam Cooper
• Re: PDF accessibility guidelines Felix Miata
• Re: PDF accessibility guidelines. WAS: Re: PDF's and Signatures Duff Johnson
• Re: PDF accessibility guidelines. WAS: Re: PDF's and Signatures Duff Johnson
• RE: PDF accessibility guidelines. WAS: Re: PDF's and Signatures Adam Cooper
• RE: PDF accessibility guidelines. WAS: Re: PDF's and Signatures Jonathan Avila

Sunday, 25 January 2015

• RE: PDF accessibility guidelines. WAS: Re: PDF's and Signatures Howard Leicester
• Re: PDF accessibility guidelines. WAS: Re: PDF's and Signatures Elizabeth J. Pyatt

Saturday, 24 January 2015

• Re: PDF accessibility guidelines. WAS: Re: PDF's and Signatures Olaf Drümmer
• Re: PDF accessibility guidelines. WAS: Re: PDF's and Signatures Wayne Dick
• RE: PDF accessibility guidelines. WAS: Re: PDF's and Signatures accessys@smart.net
• RE: PDF accessibility guidelines. WAS: Re: PDF's and Signatures John Foliot
• RE: PDF accessibility guidelines. WAS: Re: PDF's and Signatures John Foliot
• Re: PDF accessibility guidelines. WAS: Re: PDF's and Signatures Wayne Dick

Friday, 23 January 2015

• Re: PDF accessibility guidelines accessys@smart.net
• Re: PDF accessibility guidelines. WAS: Re: PDF's and Signatures Duff Johnson
• Re: PDF accessibility guidelines Phill Jenkins
• Re: PDF accessibility guidelines Olaf Drümmer
• Re: PDF accessibility guidelines Felix Miata
• RE: PDF accessibility guidelines. WAS: Re: PDF's and Signatures accessys@smart.net
• RE: PDF accessibility guidelines. WAS: Re: PDF's and Signatures Jonathan Avila
• RE: PDF accessibility guidelines. WAS: Re: PDF's and Signatures John Foliot
• Re: PDF accessibility guidelines. WAS: Re: PDF's and Signatures Duff Johnson
• RE: PDF accessibility guidelines. WAS: Re: PDF's and Signatures John Foliot
• Re: PDF accessibility guidelines. WAS: Re: PDF's and Signatures Duff Johnson
• Re: PDF accessibility guidelines. WAS: Re: PDF's and Signatures Wayne Dick
• Re: PDF accessibility guidelines. WAS: Re: PDF's and Signatures accessys@smart.net

Thursday, 22 January 2015

• Re: PDF accessibility guidelines. WAS: Re: PDF's and Signatures Elizabeth J. Pyatt
• RE: PDF accessibility guidelines. WAS: Re: PDF's and Signatures Jonathan Avila
• Re: WCAG Techniques - errors? (was RE: PDF's and Signatures) Duff Johnson
• WCAG Techniques - errors? (was RE: PDF's and Signatures) John Foliot
• PDF accessibility guidelines. WAS: Re: PDF's and Signatures Thompson, Rachel
• Re: PDF's and Signatures Duff Johnson
• RE: PDF's and Signatures Foliot, John

Wednesday, 21 January 2015

• RE: PDF's and Signatures Andy Keyworth
• PDF's and Signatures Kane, Sarah

Tuesday, 20 January 2015

• RE: Announcement nosetothepage.org site and first article. Howard Leicester
• Top strategies to build your digital accessibility career (webinar) Dr Jonathan Hassell
• Re: Announcement nosetothepage.org site and first article. Felix Miata
• Announcement nosetothepage.org site and first article. Wayne Dick

Saturday, 17 January 2015

• RE: Access to security indicators Léonie Watson

Thursday, 15 January 2015

• Call for Review: Cognitive Accessibility User Research Shawn Henry
• Updated Working Draft: IndieUI Events - for Mobile and More Shawn Henry

Tuesday, 13 January 2015

• RE: Which SC Should Apply When Content Can Only Be Seen By Screen Reader Madhavi Herle
• Re: Which SC Should Apply When Content Can Only Be Seen By Screen Reader Mike Elledge
• Re: Which SC Should Apply When Content Can Only Be Seen By Screen Reader Mitchell Evan
• Which SC Should Apply When Content Can Only Be Seen By Screen Reader Jim

Friday, 9 January 2015

• Help test ATAG 2.0 Shawn Henry

Thursday, 8 January 2015

• Call for Review: WCAG 2.0 Techniques Draft Updates Shawn Henry
• Re: Access to security indicators chaals@yandex-team.ru
• RE: Access to security indicators Léonie Watson
• Access to security indicators chaals@yandex-team.ru

Last message date: Tuesday, 31 March 2015 23:55:00 UTC