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

2015-10-28 Thread Cynthia Shelly
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 Glazkov ; Olli Pettay ; Chaals McCath

RE: [editing] Responsive Input Terminology

2014-12-11 Thread Cynthia Shelly
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 11

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

2014-08-08 Thread Cynthia Shelly
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 Sub

RE: Request for Comments on Widgets 1.0 Requirements Last Call WD

2008-08-08 Thread Cynthia Shelly
This looks fine to me too. Thanks for addressing it. -Original Message- From: Marcos Caceres [mailto:[EMAIL PROTECTED] Sent: Monday, August 04, 2008 4:32 AM To: Arthur Barstow Cc: Sally Cain; Steven Faulkner; Cynthia Shelly; [EMAIL PROTECTED]; public-webapps Subject: Re: Request for

RE: Accessibility requirement

2008-08-01 Thread Cynthia Shelly
ginal 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, Cynthi

RE: Accessibility requirement

2008-07-21 Thread Cynthia Shelly
es [mailto:[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

Re: Accessibility requirement

2008-07-14 Thread Cynthia Shelly
Marcos said "the reason we have "should" and "may" is to accommodate HTML, which is not as accessible as it could be. To have "must" would mean that HTML4.01 could not meet the requirement." Interesting... My experience has been that HTML 4.01 can be made accessible if it is carefully coded. WC

Accessibility requirement

2008-07-11 Thread Cynthia Shelly
Hi, I'm a member of wai-pf and wcag, and met some of you at the web apps face to face in redmond recently. I was reading through the widgets 1.0 requirements spec, and came across this accessibility requirement. Wondering why only should and may here, and not must? R37. Language Accessibilit