- From: Janina Sajka <janina@rednote.net>
- Date: Tue, 26 Apr 2016 11:23:28 -0400
- To: Léonie Watson <tink@tink.uk>
- Cc: "'Rich Schwerdtfeger'" <richschwer@gmail.com>, "'White, Jason J'" <jjwhite@ets.org>, "'John Foliot'" <john.foliot@deque.com>, "'Birkir Gunnarsson'" <birkir.gunnarsson@deque.com>, public-aria@w3.org
Léonie Watson writes: > From: Rich Schwerdtfeger [mailto:richschwer@gmail.com] > Sent: 26 April 2016 15:36 > “That is correct. ARIA is about interoperability at the API/browser level. It is not about mandating user agent visible user experience. It is not about mandating AT behavior. We have stated that from the very beginning.” > > > > Then we cannot include a role that, when implemented incorrectly by ATs, creates a security vulnerability or which puts users in a position of uncertainty as to their personal data security. > I don't follow this exit criterion. It seems to me with this kind of requirement one might never cross a street. Again, this strikes me as a new kind of exit criterion that no other ARIA feature has previously had to meet. We do our best to specify what correct implementation is, then we show correct implementations and the W3C requirements are met. I'm simply unaware that we've ever been required to show that any kind of "incorrect" implementation does no harm. Janina > > > > > Léonie. > > > > -- > > @LeonieWatson tink.uk Carpe diem > > > > > -- Janina Sajka, Phone: +1.443.300.2200 sip:janina@asterisk.rednote.net Email: janina@rednote.net Linux Foundation Fellow Executive Chair, Accessibility Workgroup: http://a11y.org The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI) Chair, Accessible Platform Architectures http://www.w3.org/wai/apa
Received on Tuesday, 26 April 2016 17:03:26 UTC