- From: Michael Cooper <cooper@w3.org>
- Date: Wed, 23 Aug 2017 12:26:10 -0400
- To: Janina Sajka <janina@rednote.net>, W3C WAI Accessible Platform Architectures <public-apa@w3.org>
Here is a proposed rewording for the accessibility impact section requested of Push API: Accessibility Considerations Push API features introduce a number of needs for a "Do Not Disturb" functionality in various web applications, whether accessed via mobile device or desktop browser. This functionality should be addressed by the Web Notifications specificaton. Web Notifications currently does not provide this feature but an issue has been filed requesting the feature: [URI of issue] Meanwhile, until the use cases described in this issue are appropriately addressed, implementors of this specification should be aware that accessibility problems might be triggered by implementations of this specification and attempt to minimize their impact. On 23/08/2017 11:27 AM, Janina Sajka wrote: > Colleagues: > > Below is a draft Accessibility Impact Section for the Push API against > which APA has provided comments suggesting additional feature support is > needed. > We have been advised our comments would be more > appropriately addressed by the Notifications specification. Meanwhile, > until the missing feature support is provided, problems for > accessibility remain for implementors of Push API. > > The draft section below is intended to advise implementors of the issue > and point to the proposed solution. > > > <Proposed Push API Section> > Accessibility Impact (Informative) > > 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 and we have filed an issue on that specification: > > [URI of issue] > > Meanwhile, until the use cases described in this issue are appropriately > addressed, implementors of this specification should be aware that > accessibility problems might be triggered by implementations of this > specification. >
Received on Wednesday, 23 August 2017 16:26:12 UTC