W3C home > Mailing lists > Public > public-apa@w3.org > May 2017

Decision on CfC: Push API Comments

From: Janina Sajka <janina@rednote.net>
Date: Wed, 31 May 2017 10:24:22 -0400
To: public-apa-admin@w3.org
Cc: W3C WAI Accessible Platform Architectures <public-apa@w3.org>
Message-ID: <20170531142422.GB1975@opera.rednote.net>

Colleagues:

No objections have been recieved in response to this Call For Consensus.
It is, therefore, agreed to as a consensus decision of APA.

The head of thread for this CfC is archived at:

http://lists.w3.org/Archives/Public/public-apa-admin/2017May/0000.html

Janina


Janina Sajka writes:
> Colleagues:
> 
> This is a Call for Consensus (CfC) to the Accessible Platform
> Architectures (APA) Working Group on our review of the draft Push API
> specification as detailed below.
> 
> Our review of this specification was expressly requested by the Web
> Platforms Working Group:
> 
> https://www.w3.org/TR/push-api/
> 
> <Begin Draft Comment>
> 
> The Accessible Platform Architectures (APA) Working Group has reviewed
> the Push API specification at:
> 
> https://www.w3.org/TR/push-api/
> 
> We find no issues with the API as presented, except that we believe
> additional feature support is required by emerging use cases.
> 
> Missing Feature
> 
> We require a mechanism whereby applications may temporarily block any
> push notifications or events. All such notifications or events should be
> queued until the application requesting temporary blocking has cleared
> the blocking request.
> 
> We offer two use cases requiring such a feature.
> 
> Use Case #1
> 
> A user engaged in a financial transaction at the point of making (or
> recieving) payment should not be interrupted by unrelated notifications
> and events. This is especially important for persons with disabilities
> relying on assistive technology, but is also relevant to all users of
> emerging web payments specifications.
> 
> Use Case #2
> 
> Users need the ability to interact with certain web content without
> automated updates that might cause presented content to update in an
> adverse manner.
> 
> This might be satisifed by allowing temporary pauses in push events, or
> by controlling a minimum time interval between push events.
> 
> For more on this use case see the comment at:
> http://lists.w3.org/Archives/Public/public-apa/2017May/0026.html
> 
> <End Draft Comment>
> 
> *       ACTION TO TAKE
> 
> This CfC is now open for objection, comment, as well as statements of
> support via email. Silence will be interpreted as support, though
> messages of support are certainly welcome.
> 
> If you object to this proposed action, or have comments concerning this
> proposal, please respond by replying on list to this message no later
> than 23:59 (Midnight) Boston Time, Tuesday 23 May.
> 
> Janina
>  
> 
> -- 
> 
> 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
> 

-- 

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, 31 May 2017 14:24:52 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:55:26 UTC