- From: Janina Sajka <janina@rednote.net>
- Date: Wed, 23 Aug 2017 11:30:10 -0400
- To: W3C WAI Accessible Platform Architectures <public-apa@w3.org>
Colleagues: We are advised our comments on the Push API specification would more properly be addressed by the Notifications specification. Below is a draft filing for your review and improvement. Since the W3C Notification specification is not currently in active development: http://www.w3.org/TR/notifications/ We are advised by our colleagues in the Web Platforms WG to work with the WHAT-WG successor specification: https://notifications.spec.whatwg.org/ Please provide any comments, and particularly sample API code for the below. <begin message> The Accessible Platform Architectures (APA) Working Group at the W3C believes there are significant use cases requiring API support for "Do Not Disturb" functionality in various web applications, whether accessed via mobile device or desktop browser. We are advised by W3C colleagues that the appropriate locus for our feature request is the Notification specification. One such use case is the conclusion of a financial transaction where it is critical that the key terms of the transaction can be completed without distracting interruptions--which could also trigger timeouts that would exaserbate the user's ability to complete the transaction. The key juncture of a financial transaction might include the screen where payment is finally authorized, a digital signature is applied, and an accessible receipt is recieved. Another use case is to prevent a list of items from scrolling while a screen reader user is iterating through the list. Push actions which result in scrolling exaserbate the user's ability to function smoothly by causing the focus to shift outside the user's control. We note this kind of functionality is available heuristically on mobile platforms. An example Android application providing similar functionality is: https://play.google.com/store/apps/details?id=com.tryagent However, what is needed is the ability to temporarily suspend push notifications via an API call, so that an application can invoke a "Do not disturb" feature based on context, and so that users may gain easier access to turning notifications on and off directly, whatever the platform, without navigating multiple menus. We propose the addition of a section in support of this feature requirement as follows: Section 2.12 Defer and Queue When this flag is set no notifications are delivered to the user interface. Rather they are queued for display once the flag is cleared. [example code needed] -- 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, 23 August 2017 15:30:34 UTC