- From: JaninaSajka <janina@rednote.net>
- Date: Wed, 30 Aug 2017 10:46:49 -0400
- To: w3c/push-api <reply+00a418050db125af174187d171465ae0f2cff37345517bd592cf0000000115bdcb7692a16>
- Cc: w3c/push-api <push-api@noreply.github.com>, Mention <mention@noreply.github.com>, W3C WAI Accessible Platform Architectures <public-apa@w3.org>
Martin: I think we're not communicating. So, in an attempt to clarify ... * We have no intention of submitting this text to Notifications * API. * APA is preparing a filing for the Notifications spec that would add a * normative requirement: http://lists.w3.org/Archives/Public/public-apa/2017Aug/0018.html * If accepted it would clearly obviate the content of our * proposed, and now rejected informative Accessibility * Impact statement for Push API. Are you active in WHAT's Notifications work? Janina Martin Thomson writes: > I don't think that we should add this text. The Notifications API is the right place for this text. The proposed text clearly acknowledges this point. I realize that adding text here might appear to help the case for adding text to the Notifications API, but that's not the right way to approach this issue. > > Please take this issue to the Notifications API. The need for user controls over whether notifications are shown is clearly a good thing. To my knowledge most user agents provide these controls, so I don't anticipate any issues with adding some informative text there about the impact of notifications on accessibility. > > -- > You are receiving this because you were mentioned. > Reply to this email directly or view it on GitHub: > https://github.com/w3c/push-api/issues/259#issuecomment-325844182 -- 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 Wednesday, 30 August 2017 14:47:13 UTC