RE: Accessibility requirement

:[EMAIL PROTECTED] Sent: Tuesday, July 15, 2008 3:50 AM To: Cynthia Shelly Cc: public-webapps@w3.org Subject: Re: Accessibility requirement On Tue, Jul 15, 2008 at 12:10 AM, Cynthia Shelly [EMAIL PROTECTED] wrote: Interesting... My experience has been that HTML 4.01 can be made accessible

RE: Accessibility requirement

Message- From: Marcos Caceres [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 30, 2008 10:50 PM To: Arthur Barstow Cc: Cynthia Shelly; public-webapps Subject: Re: Accessibility requirement On Tue, Jul 29, 2008 at 4:15 AM, Arthur Barstow [EMAIL PROTECTED] wrote: Marcos, Cynthia, Perhaps requirement

RE: User Intentions Explainer (was: List of Intentions)

This is a really solid list. Thank you for pulling it together, so we can start towards a harmonized set of user events. From: Ben Peters [mailto:ben.pet...@microsoft.com] Sent: Monday, August 4, 2014 7:28 PM To: public-editing...@w3.org; Julie Parent; public-indie...@w3.org; public-webapps

RE: [editing] Responsive Input Terminology

I like this a lot. In my experience, responsive is a word with positive connotations in web development. I agree that these input events are the corollary to responsive layout. -Original Message- From: Ben Peters [mailto:ben.pet...@microsoft.com] Sent: Thursday, December 11, 2014

RE: [Web Components] proposing a f2f...

I’m not sure I need to be there, but if it’s in Seattle I could attend to discuss javascript accessibility APIs as part of web components. From: Chris Wilson [mailto:cwi...@google.com] Sent: Thursday, October 29, 2015 9:47 AM To: Travis Leithead Cc: Dimitri