w3c-wai-ig@w3.org from April to June 2016 by date

Thursday, 30 June 2016

RE: Conforming to WCAG 2.0 SC 2.4.5 (Multiple Ways) for pdf files Sean Murphy (seanmmur)
RE: Conforming to WCAG 2.0 SC 2.4.5 (Multiple Ways) for pdf files Jonathan Avila
Re: Conforming to WCAG 2.0 SC 2.4.5 (Multiple Ways) for pdf files Duff Johnson
Re: Conforming to WCAG 2.0 SC 2.4.5 (Multiple Ways) for pdf files Olaf Drümmer
Conforming to WCAG 2.0 SC 2.4.5 (Multiple Ways) for pdf files Michèlle

Tuesday, 21 June 2016

Monday, 20 June 2016

RE: [CSSWG][css-content] FPWD of CSS Generated Content L3 Phillips, Addison
[CSSWG][css-content] FPWD of CSS Generated Content L3 fantasai
Announcing the Research Questions Task Force Janina Sajka
The Professional Certificate in Web Accessibility is now enrolling Philip Jenkinson

Saturday, 18 June 2016

Re: content in document twice but displayed once Mark Sadecki
content in document twice but displayed once Michael A. Peters

Friday, 17 June 2016

Re: Accessible Documents - PDF vs. HTML Andrew Cunningham
RE: Accessible Documents - PDF vs. HTML George Kerscher
Re: Accessible Documents - PDF vs. HTML Duff Johnson

Thursday, 16 June 2016

RE: Accessible Documents - PDF vs. HTML George Kerscher
Re: Accessible Documents - PDF vs. HTML Thad C
Re: Accessible Documents - PDF vs. HTML deborah.kaplan@suberic.net
Re: Accessible Documents - PDF vs. HTML accessys@smart.net
Re: Accessible Documents - PDF vs. HTML Graham Armfield
Re: Accessible Documents - PDF vs. HTML Andrew Cunningham
Re: Accessible Documents - PDF vs. HTML Duff Johnson
Re: Accessible Documents - PDF vs. HTML Dean Birkett | AssistiveWare
Re: Accessible Documents - PDF vs. HTML Olaf Drümmer
Re: Accessible Documents - PDF vs. HTML Thad C
Re: Accessible Documents - PDF vs. HTML J. Albert Bowden

Wednesday, 15 June 2016

Re: Single Page Architecture General Concepts Adam Zerner
Re: Names for ARIA menu and menubar David MacDonald
Re: Accessible Documents - PDF vs. HTML Olaf Drümmer
Re: Accessible Documents - PDF vs. HTML Olaf Drümmer
Re: Accessible Documents - PDF vs. HTML Ta, Duc
Re: Accessible Documents - PDF vs. HTML Paul J. Adam
RE: Accessible Documents - PDF vs. HTML George Kerscher
Re: Accessible Documents - PDF vs. HTML lists@srinivasu.org
Re: Accessible Documents - PDF vs. HTML deborah.kaplan@suberic.net
Re: Accessible Documents - PDF vs. HTML Karen Lewellen
RE: Accessible Documents - PDF vs. HTML Balusani, Shirisha
Re: Accessible Documents - PDF vs. HTML Duff Johnson
Accessible Documents - PDF vs. HTML Macintosh, Kristy (OMAFRA)
AW: Single Page Architecture General Concepts Batusic, Mario
AW: Names for ARIA menu and menubar Batusic, Mario
RE: Creating personas for WAI site redesign Jonathan Avila

Tuesday, 14 June 2016

Re: Single Page Architecture General Concepts Thad C
Re: Single Page Architecture General Concepts Jennifer Sutton
Re: Creating personas for WAI site redesign deborah.kaplan@suberic.net
Re: Creating personas for WAI site redesign Mike Elledge
RE: Creating personas for WAI site redesign Howard Leicester
Re: Creating personas for WAI site redesign Patrick H. Lauke
Re: Creating personas for WAI site redesign Michiel Bijl
Re: Creating personas for WAI site redesign Denis Boudreau (gmail)
Re: Single Page Architecture General Concepts Mohammad, Ashraf
Re: Creating personas for WAI site redesign Weger, Eli
Re: Creating personas for WAI site redesign Sharron Rush
Re: Creating personas for WAI site redesign Mike Elledge
RE: Single Page Architecture General Concepts Beranek, Nicholas
Single Page Architecture General Concepts Jim Homme
Re: Creating personas for WAI site redesign Sharron Rush
Re: Creating personas for WAI site redesign Sharron Rush
Re: Creating personas for WAI site redesign Ginger Claassen
Re: Creating personas for WAI site redesign Patrick H. Lauke
Re: Creating personas for WAI site redesign Sharron Rush
Re: Names for ARIA menu and menubar David MacDonald
Re: Creating personas for WAI site redesign Sharron Rush
Re: Creating personas for WAI site redesign Gregg Vanderheiden
Mobility Impairment Accessibility Study Dan Berlin
AW: Names for ARIA menu and menubar Batusic, Mario
Re: Names for ARIA menu and menubar David MacDonald
AW: Names for ARIA menu and menubar Batusic, Mario
RE: Names for ARIA menu and menubar ALAN SMITH
Re: Creating personas for WAI site redesign Ginger Claassen
Re: Creating personas for WAI site redesign Kevin White
Re: Creating personas for WAI site redesign Michiel Bijl
Names for ARIA menu and menubar Batusic, Mario
Re: Creating personas for WAI site redesign Michiel Bijl

Monday, 13 June 2016

Knowbility OpenAIR Competition - Mentors Needed - Experienced Accessibility Professionals CB Averitt
Creating personas for WAI site redesign Sharron Rush
FW: PRESS RELEASE: G3ict and World ENABLED Launch Accessible Smart Cities Initiative Katie Haritos-Shea GMAIL

Friday, 10 June 2016

Re: ATAG 2.0 compliant WYSIWYG editors Gunderson, Jon R
ATAG 2.0 compliant WYSIWYG editors Mark Weiler
Re: Reminder -- Call for Review: Web Accessibility Perspectives Shadi Abou-Zahra

Thursday, 9 June 2016

RE: Accessibility of Archieved items Howard Leicester
Re: Accessibility of Archieved items Andrew Cunningham

Wednesday, 8 June 2016

Re: Reminder -- Call for Review: Web Accessibility Perspectives David MacDonald
Reminder -- Call for Review: Web Accessibility Perspectives Katie Haritos-Shea GMAIL
Re: WAI-ARIA design pattern for media players Gunderson, Jon R
Re: WAI-ARIA design pattern for media players rtait14

Tuesday, 7 June 2016

WAI-ARIA design pattern for media players Terrill Thompson
Re: Accessibility of Archieved items Herin Hentry
RE: Accessibility of Archieved items Jonathan Avila
Accessibility of Archieved items Herin Hentry

Saturday, 4 June 2016

Re: accessible drop-down menus Gordon L. Potter
RE: accessible drop-down menus Bryan Garaventa
RE: accessible drop-down menus Bryan Garaventa

Friday, 3 June 2016

RE: New Accessible Playlist Community Group Katie Haritos-Shea GMAIL
Re: accessible drop-down menus Gordon L. Potter
Re: accessible drop-down menus David MacDonald

Thursday, 2 June 2016

Re: accessible drop-down menus Mark Sadecki
Re: accessible drop-down menus Michiel Bijl
New Accessible Playlist Community Group Terrill Thompson
Re: accessible drop-down menus David MacDonald

Tuesday, 31 May 2016

Re: accessible drop-down menus Taliesin Smith

Monday, 30 May 2016

RE: accessible drop-down menus Bryan Garaventa
audio description on demand service seeking testing. Karen Lewellen

Sunday, 29 May 2016

Re: accessible drop-down menus David MacDonald
RE: accessible drop-down menus Bryan Garaventa
RE: accessible drop-down menus Bryan Garaventa
Re: accessible drop-down menus David MacDonald

Saturday, 28 May 2016

RE: accessible drop-down menus Roger Hudson
RE: accessible drop-down menus Bryan Garaventa
accessible drop-down menus Roger Hudson

Friday, 27 May 2016

Minutes of 27 May and updates to work for this week Sharron Rush

Thursday, 26 May 2016

RE: Text entry box with a single underline... Adam Cooper

Wednesday, 25 May 2016

Re: Text entry box with a single underline... Paul Stewart
Re: Text entry box with a single underline... Elizabeth Pyatt
Re: Text entry box with a single underline... Glenda Sims
RE: [WebAIM] Elderly and self identification as having a disability Jonathan Avila
RE: Text entry box with a single underline... Jonathan Avila
Re: Text entry box with a single underline... Andrew Arch
RE: Text entry box with a single underline... John Colby
Re: Text entry box with a single underline... Patrick H. Lauke
Text entry box with a single underline... Alistair Garrison
RE: [WebAIM] Elderly and self identification as having a disability Sean Murphy (seanmmur)
Re: [WebAIM] Elderly and self identification as having a disability Phill Jenkins

Tuesday, 24 May 2016

Re: [WebAIM] Elderly and self identification as having a disability David Sloan
Re: Elderly and self identification as having a disability Rafael Xavier
Re: Elderly and self-identification as having a disability Weger, Eli
RE: Elderly and self-identification as having a disability Cain, Sally
Elderly and self identification as having a disability Jim Allan
Request for feedback: Navigation and image maps Chaals McCathie Nevile

Monday, 23 May 2016

AHG 2016: Call for Proposals ends in 8 days Howard Kramer
RE: Disabled people and copyright infringement Léonie Watson

Friday, 20 May 2016

RE: Disabled people and copyright infringement Jonathan Avila
RE: Disabled people and copyright infringement Gill Whitney
Re: Disabled people and copyright infringement David Woolley
RE: Disabled people and copyright infringement Howard Leicester
Disabled people and copyright infringement Léonie Watson
Re: Screen Reader Survey for User Research Class Taliesin Smith

Wednesday, 18 May 2016

AccessWorks on GAAD Sharron Rush
Inclusive Design 24 Léonie Watson
Resources for GAAD and beyond Shawn Henry
RE: Assistive Technology (AT) survey Léonie Watson
Re: Assistive Technology (AT) survey David MacDonald
Re: Screen Reader Survey for User Research Class Karen Lewellen

Tuesday, 17 May 2016

Re: Screen Reader Survey for User Research Class Anh Hua
Re: Screen Reader Survey for User Research Class Karen Lewellen
Re: Screen Reader Survey for User Research Class Karen Lewellen
Call for Review: Web Accessibility Perspectives Shawn Henry
New Videos: Perspectives on Web Accessibility -- Essential for Some, Useful for All Shawn Henry
Re: Screen Reader Survey for User Research Class Anh Hua
Re: Screen Reader Survey for User Research Class Anh Hua
Re: Screen Reader Survey for User Research Class accessys@smart.net
RE: Screen Reader Survey for User Research Class William
Re: Screen Reader Survey for User Research Class Karen Lewellen
Re: Screen Reader Survey for User Research Class accessys@smart.net
RE: Assistive Technology (AT) survey Howard Leicester
Screen Reader Survey for User Research Class Anh Hua

Monday, 16 May 2016

Assistive Technology (AT) survey Léonie Watson

Monday, 9 May 2016

RE: In WCAG NEXT let's put a date field on failures White, Jason J
Re: In WCAG NEXT let's put a date field on failures Gregg Vanderheiden RTF
Re: In WCAG NEXT let's put a date field on failures Sailesh Panchang
RE: Re: In WCAG NEXT let's put a date field on failures White, Jason J
Re: Re: In WCAG NEXT let's put a date field on failures Sailesh Panchang
RE: paypal. Karen Lewellen
Re: paypal. Karen Lewellen
RE: paypal. accessys@smart.net
RE: paypal. Sean Murphy (seanmmur)
Re: paypal. accessys@smart.net

Sunday, 8 May 2016

RE: paypal. Karen Lewellen
RE: paypal. Sean Murphy (seanmmur)
Re: paypal. Karen Lewellen
Re: paypal. Len Burns
Re: paypal. Karen Lewellen
Re: paypal. accessys@smart.net
Re: paypal. Karen Lewellen
Re: paypal. Karen Lewellen
Re: paypal. accessys@smart.net
Re: paypal. David Edward Best
paypal. Karen Lewellen

Friday, 6 May 2016

Re: Re: In WCAG NEXT let's put a date field on failures David MacDonald

Thursday, 5 May 2016

Re: warning category for techniques / failures. David MacDonald
Re: warning category for techniques / failures. Gregg Vanderheiden
Re: warning category for techniques / failures. Gregg Vanderheiden
Re: warning category for techniques / failures. Sailesh Panchang
Re: warning category for techniques / failures. Phill Jenkins
Re: warning category for techniques / failures. Alastair Campbell
Re: warning category for techniques / failures. Ta, Duc
Re: warning category for techniques / failures. Gregg Vanderheiden RTF
Re: warning category for techniques / failures. Alastair Campbell

Wednesday, 4 May 2016

Re: Let's add an approved date field to Failures and Techniques Mitchell Evan
Re: Let's add an approved date field to Failures and Techniques Ta, Duc
Re: warning category for techniques / failures. Alastair Campbell
Re: warning category for techniques / failures. josh@interaccess.ie
warning category for techniques / failures. Alastair Campbell
Re: Let's add an approved date field to Failures and Techniques Phill Jenkins
Re: Let's add an approved date field to Failures and Techniques Gregg Vanderheiden
RE: Let's add an approved date field to Failures and Techniques Phill Jenkins

Tuesday, 3 May 2016

RE: Let's add an approved date field to Failures and Techniques Jonathan Avila
RE: Let's add an approved date field to Failures and Techniques Jonathan Avila
Re: Let's add an approved date field to Failures and Techniques Gregg Vanderheiden RTF
RE: Let's add an approved date field to Failures and Techniques White, Jason J
HTML (Accessibility) Bug Triage Meeting - Upcoming: Thursday, 5th May Katie Haritos-Shea GMAIL
Re: Let's add an approved date field to Failures and Techniques Alastair Campbell
Re: Let's add an approved date field to Failures and Techniques Gregg Vanderheiden
Re: Let's add an approved date field to Failures and Techniques Gregg Vanderheiden
Re: Let's add an approved date field to Failures and Techniques Gregg Vanderheiden
Re[2]: Let's add an approved date field to Failures and Techniques josh@interaccess.ie
Re: Let's add an approved date field to Failures and Techniques Alastair Campbell

Monday, 2 May 2016

Re: Let's add an approved date field to Failures and Techniques David MacDonald
Call for review and comment: EPUB Accessibility: Conformance and Discovery George Kerscher
Re: Let's add an approved date field to Failures and Techniques John Foliot
RE: Not hearing grouping labels for checkboxes, radio buttons and link lists. ALAN SMITH
RE: Not hearing grouping labels for checkboxes, radio buttons and link lists. Jonathan Avila
RE: Let's add an approved date field to Failures and Techniques White, Jason J
RE: Let's add an approved date field to Failures and Techniques Emmanuelle Gutiérrez y Restrepo
Re: Let's add an approved date field to Failures and Techniques David MacDonald
RE: Not hearing grouping labels for checkboxes, radio buttons and link lists. Jonathan Avila
Re: Not hearing grouping labels for checkboxes, radio buttons and link lists. Patrick H. Lauke
Not hearing grouping labels for checkboxes, radio buttons and link lists. ALAN SMITH
Re: Let's add an approved date field to Failures and Techniques Gregg Vanderheiden RTF
Re: Let's add an approved date field to Failures and Techniques Gregg Vanderheiden RTF

Sunday, 1 May 2016

RE: Let's add an approved date field to Failures and Techniques White, Jason J
Re: Let's add an approved date field to Failures and Techniques David MacDonald
Re: In WCAG NEXT let's put a date field on failures Gregg Vanderheiden RTF

Saturday, 30 April 2016

Re: In WCAG NEXT let's put a date field on failures Gregg Vanderheiden
Re: In WCAG NEXT let's put a date field on failures Wayne Dick
Re: Let's add an approved date field to Failures and Techniques Gregg Vanderheiden RTF
Re: Let's add an approved date field to Failures and Techniques Katie Haritos-Shea
Re: Let's add an approved date field to Failures and Techniques Gregg Vanderheiden RTF
RE: Let's add an approved date field to Failures and Techniques White, Jason J
Re: Let's add an approved date field to Failures and Techniques Katie Haritos-Shea
Re: Let's add an approved date field to Failures and Techniques Gregg Vanderheiden RTF
Re: Let's add an approved date field to Failures and Techniques Katie Haritos-Shea
Re: Let's add an approved date field to Failures and Techniques David MacDonald
Re: Let's add an approved date field to Failures and Techniques Gregg Vanderheiden RTF
RE: Re: Let's add an approved date field to Failures and Techniques Joshue O Connor
Re: Let's add an approved date field to Failures and Techniques Gregg Vanderheiden RTF
Re: Let's add an approved date field to Failures and Techniques David MacDonald

Friday, 29 April 2016

RE: Re: Let's add an approved date field to Failures and Techniques White, Jason J
Re: Let's add an approved date field to Failures and Techniques Gregg Vanderheiden RTF
Re: Let's add an approved date field to Failures and Techniques Joshue O Connor
Re: Let's add an approved date field to Failures and Techniques David MacDonald
RE: Let's add an approved date field to Failures and Techniques ALAN SMITH
Re: Let's add an approved date field to Failures and Techniques Gregg Vanderheiden RTF
Re: Let's add an approved date field to Failures and Techniques Joshue O Connor
Re: Let's add an approved date field to Failures and Techniques David MacDonald
RE: Let's add an approved date field to Failures and Techniques Katie Haritos-Shea GMAIL
Re: In WCAG NEXT let's put a date field on failures Alastair Campbell

Thursday, 28 April 2016

Re: Let's add an approved date field to Failures and Techniques Denis Boudreau (gmail)
Re: Let's add an approved date field to Failures and Techniques Kevin White
Re: Let's add an approved date field to Failures and Techniques Laura Carlson
RE: Let's add an approved date field to Failures and Techniques John Foliot
RE: Let's add an approved date field to Failures and Techniques Jonathan Avila

Wednesday, 27 April 2016

RE: Let's add an approved date field to Failures and Techniques Katie Haritos-Shea GMAIL
Re: Let's add an approved date field to Failures and Techniques David MacDonald
RE: In WCAG NEXT let's put a date field on failures White, Jason J
RE: Let's add an approved date field to Failures and Techniques White, Jason J
RE: Let's add an approved date field to Failures and Techniques John Foliot
RE: Let's add an approved date field to Failures and Techniques Katie Haritos-Shea GMAIL
RE: Let's add an approved date field to Failures and Techniques Katie Haritos-Shea GMAIL
RE: Let's add an approved date field to Failures and Techniques John Foliot
Re: In WCAG NEXT let's put a date field on failures Alastair Campbell
Re: Let's add an approved date field to Failures and Techniques Mike Elledge
Re: Let's add an approved date field to Failures and Techniques David MacDonald
Re: In WCAG NEXT let's put a date field on failures Paul J. Adam
Re: Re[4]: Let's add an approved date field to Failures and Techniques Alastair Campbell
Re: In WCAG NEXT let's put a date field on failures David MacDonald
Re: Re[4]: Let's add an approved date field to Failures and Techniques Glenda Sims
RE: Re[4]: Let's add an approved date field to Failures and Techniques ALAN SMITH
Re[4]: Let's add an approved date field to Failures and Techniques josh@interaccess.ie
RE: Re[2]: Let's add an approved date field to Failures and Techniques White, Jason J
Re[4]: Let's add an approved date field to Failures and Techniques josh@interaccess.ie
Re: Let's add an approved date field to Failures and Techniques Gregg Vanderheiden
Re: Re[2]: Let's add an approved date field to Failures and Techniques Andrew Kirkpatrick
Re[2]: Let's add an approved date field to Failures and Techniques josh@interaccess.ie
Re: In WCAG NEXT let's put a date field on failures Alastair Campbell
Re: Let's add an approved date field to Failures and Techniques Mitchell Evan

Tuesday, 26 April 2016

Re: In WCAG NEXT let's put a date field on failures Patrick H. Lauke
RE: In WCAG NEXT let's put a date field on failures John Foliot
RE: Let's add an approved date field to Failures and Techniques Gian Wild
Let's add an approved date field to Failures and Techniques David MacDonald
Re: An accessible interface for data mining Mitchell Evan

Monday, 25 April 2016

ASSETS 2016 [Deadlines of 24 June]: Posters and Demos, Experience Reports, Doctoral Consortium, and Student Research Competition Kyle Rector
WCAG Next Possible Models Makoto UEKI - Infoaxia, Inc.

Wednesday, 20 April 2016

WCAG Next Possible Models lisa.seeman

Tuesday, 19 April 2016

RE: Accessible eLearning Zhivi Williams
Re: Accessible eLearning Ian Jacobs
RE: Accessible eLearning Zhivi Williams
Re: Accessible eLearning Ian Jacobs
RE: Accessible eLearning Zhivi Williams
Re: Problem: The W3 Wiki enlarges very poorly. Wayne Dick

Monday, 18 April 2016

Re: Problem: The W3 Wiki enlarges very poorly. Kevin White
Re: Problem: The W3 Wiki enlarges very poorly. Wayne Dick
Problem: The W3 Wiki enlarges very poorly. Wayne Dick
The Professional Certificate in Web Accessibility is now enrolling Philip Jenkinson

Sunday, 17 April 2016

WCAG Next Possible Models Gian Wild

Saturday, 16 April 2016

Re: Accessible eLearning Ian Jacobs
An accessible interface for data mining Alan Bridgeman
Re: Accessible eLearning Sarah Horton
WCAG. next (of interesting note) John Foliot

Friday, 15 April 2016

Re: Accessible eLearning Karen Sorensen

Wednesday, 13 April 2016

SV: Seeking example of quality alt text in STEM book Lisa Yayla
Re: Seeking example of quality alt text in STEM book Michiel Bijl
SV: Seeking example of quality alt text in STEM book Lisa Yayla

Tuesday, 12 April 2016

Re: Straw man list for WCAG.NEXT, another proposal... jason@accessibleculture.org
Re: Seeking example of quality alt text in STEM book accessys@smart.net
Seeking example of quality alt text in STEM book Gies, Edward M. (ELS-DAY)
RE: WCAG Next Possible Models Jonathan Avila
RE: WCAG Next Possible Models accessys@smart.net
RE: WCAG Next Possible Models accessys@smart.net
RE: WCAG Next Possible Models Jonathan Avila
RE: WCAG Next Possible Models Sean Murphy (seanmmur)
RE: WCAG Next Possible Models Balusani, Shirisha
Re: WCAG Next Possible Models Frederick Boland

Monday, 11 April 2016

RE: Regulatory / Government requirements for - WCAG Next Possible Models Katie Haritos-Shea GMAIL
Re: Regulatory / Government requirements for - WCAG Next Possible Models Lainey Feingold
RE: Regulatory / Government requirements for - WCAG Next Possible Models Katie Haritos-Shea GMAIL
FW: Regulatory / Government requirements for - WCAG Next Possible Models Katie Haritos-Shea GMAIL
RE: Regulatory / Government requirements for - WCAG Next PossibleModels John Foliot
RE: Regulatory / Government requirements for - WCAG Next Possible Models John Foliot
RE: Regulatory / Government requirements for - WCAG Next PossibleModels Phill Jenkins
RE: Regulatory / Government requirements for - WCAG Next PossibleModels ALAN SMITH
RE: Regulatory / Government requirements for - WCAG Next Possible Models Katie Haritos-Shea GMAIL
RE: Regulatory / Government requirements for - WCAG Next Possible Models Phill Jenkins
RE: Regulatory / Government requirements for - WCAG Next PossibleModels ALAN SMITH
Re: WCAG Next Possible Models accessys@smart.net
RE: Agenda: HTML bug triage Katie Haritos-Shea GMAIL
RE: Regulatory / Government requirements for - WCAG Next Possible Models John Foliot
RE: Regulatory / Government requirements for - WCAG Next Possible Models Katie Haritos-Shea GMAIL
Regulatory / Government requirements for - WCAG Next Possible Models ALAN SMITH
Authroing tools and WAI guidelines (was RE: Straw man list for WCAG.NEXT, another proposal...) White, Jason J
Re: WCAG Next Possible Models David MacDonald
Re: WCAG Next Possible Models Mike Elledge
Re: Straw man list for WCAG.NEXT, another proposal... David MacDonald
Re: WCAG Next Possible Models Paul J. Adam
RE: WCAG Next Possible Models accessys@smart.net
RE: WCAG Next Possible Models John Foliot
RE: WCAG Next Possible Models Katie Haritos-Shea GMAIL
RE: WCAG Next Possible Models accessys@smart.net
RE: WCAG Next Possible Models John Foliot
RE: WCAG Next Possible Models Katie Haritos-Shea GMAIL
Re: WCAG Next Possible Models Andrew Kirkpatrick
RE: WCAG Next Possible Models John Foliot
RE: Straw man list for WCAG.NEXT, another proposal... White, Jason J
Re: WCAG Next Possible Models Andrew Kirkpatrick
RE: Straw man list for WCAG.NEXT, another proposal... Katie Haritos-Shea GMAIL
Re: Straw man list for WCAG.NEXT, another proposal... Andrew Kirkpatrick
RE: WCAG Next Possible Models [OFFICIAL] Kirsty Smith
RE: WCAG Next Possible Models Macintosh, Kristy (OMAFRA)

Sunday, 10 April 2016

RE: Straw man list for WCAG.NEXT, another proposal... White, Jason J
RE: Straw man list for WCAG.NEXT, another proposal... John Foliot
Re: Straw man list for WCAG.NEXT, another proposal... Phill Jenkins

Saturday, 9 April 2016

Re: Straw man list for WCAG.NEXT, another proposal... Liddy Nevile
Re: Straw man list for WCAG.NEXT, another proposal... David MacDonald
RE: Straw man list for WCAG.NEXT, another proposal... Emmanuelle Gutiérrez y Restrepo
Re: Straw man list for WCAG.NEXT, another proposal... David MacDonald
Re: Straw man list for WCAG.NEXT, another proposal... Chaals McCathie Nevile
RE: Straw man list for WCAG.NEXT, another proposal... White, Jason J
Re: Straw man list for WCAG.NEXT, another proposal... Chaals McCathie Nevile
Re: Straw man list for WCAG.NEXT, another proposal... Jutta Treviranus
Re: Straw man list for WCAG.NEXT, another proposal... John Foliot
Re: Straw man list for WCAG.NEXT, another proposal... Chaals McCathie Nevile

Friday, 8 April 2016

RE: Straw man list for WCAG.NEXT, another proposal... White, Jason J
RE: Straw man list for WCAG.NEXT, another proposal... John Foliot
Re: WCAG Next Possible Models David MacDonald
Re: WCAG Next Possible Models Chaals McCathie Nevile
Call for Proposals: Accessing Higher Ground 2016 Howard Kramer
RE: WCAG Next Possible Models Malamud, Mark (NIH/NHLBI) [E]
RE: WCAG Next Possible Models Jim Tobias
WCAG Next Possible Models Paul J. Adam
RE: WCAG Next Possible Models White, Jason J
WCAG Next Possible Models John Foliot
ASSETS 2016 - Call for Papers - Deadline: May 6th, 2016 Kyle Rector

Thursday, 7 April 2016

Re: Accessibility for trustworthiness indicators Thad C
Re: Accessibility for trustworthiness indicators Thad C
Re: Accessibility for trustworthiness indicators Daisuke MIYAMOTO
Re: Accessibility for trustworthiness indicators Chaals McCathie Nevile
Re: Accessibility for trustworthiness indicators Daisuke MIYAMOTO

Wednesday, 6 April 2016

RE: Accessibility for trustworthiness indicators Andrews, David B (DEED)
Re: Accessibility for trustworthiness indicators Chaals McCathie Nevile
Accessibility for trustworthiness indicators Daisuke MIYAMOTO

Saturday, 2 April 2016

Re: OT: OpenSource.com seeking articles on accessibility and open source tech Graham Armfield

Friday, 1 April 2016

Re: HTML email and Accessibility Chaals McCathie Nevile
OT: OpenSource.com seeking articles on accessibility and open source tech Kevin Cole
RE: HTML email and Accessibility Caid, Lisa M.
HTML email and Accessibility Paul Tykodi

Last message date: Thursday, 30 June 2016 23:44:04 UTC