Requesting accessibility review of Push API

# Léonie Watson (17 days ago)

Hello APA,

The WebPlat WG would welcome an accessibility review of the Push API specification [1]. We'd like to transition to CR in the coming months, and this review will help us assess what remains to be done before then.

If you could file your comments as Github issues [2], before 16th June 2017, that would be appreciated.

Any questions, you know where to find us - please just ask.

Thanks Léonie [1] www.w3.org/TR/push-api [2] w3c/push-api

Contact us to advertise here
# Janina Sajka (17 days ago)

Leonie:

I have been reading and will shortly post draft comments for APA discussion, which will then make their way to Web Platforms.

I don't expect any problems meeting your timeline.

As things stand, the short version of comments relates to a possible need for additional features relating to critical circumstances around web payments use cases, i.e. there are occasions where pushes should queue and not be presented until a particular task has cleared.

I'm working on how to be more clear about this. hth.

Janina

Léonie Watson writes:

# Drake, Ted (16 days ago)

The document states clearly the user must authorize the push:

User agents MUST NOT provide Push API access to webapps without the express permission of the user. User agents MUST acquire consent for permission through a user interface for each call to the subscribe() method, unless a previous permission grant has been persisted, or a prearranged trust relationship applies. Permissions that are preserved beyond the current browsing session MUST be revocable.

There’s also a section for how to deal with expired pushes. There’s also a section for push subscription options.

Does this allow a user to set a period of time between pushes?

For instance, a person may be reading an article’s comments and the comment feed is updated every 30 seconds to add additional comments. That may cause the layout to jump and the user may want to turn off the comment pushes, or slow down the update to once every minute.

Thanks

Ted

On 5/3/17, 7:28 AM, "Léonie Watson" tink@tink.uk wrote:

Hello APA,

The WebPlat WG would welcome an accessibility review of the Push API 
specification [1]. We'd like to transition to CR in the coming months, 
and this review will help us assess what remains to be done before then.

If you could file your comments as Github issues [2], before 16th June 
2017, that would be appreciated.

Any questions, you know where to find us - please just ask.

Thanks
Léonie
[1] [https://www.w3.org/TR/push-api/

](www.w3.org/TR/push-api ) [2] [w3c/push-api ](w3c/push-api

)

@LeonieWatson tink.uk Carpe diem
# Léonie Watson (12 days ago)

On 04/05/2017 16:18, Drake, Ted wrote:

The document states clearly the user must authorize the push:

User agents MUST NOT provide Push API access to webapps without the express permission of the user. User agents MUST acquire consent for permission through a user interface for each call to the subscribe() method, unless a previous permission grant has been persisted, or a prearranged trust relationship applies. Permissions that are preserved beyond the current browsing session MUST be revocable.

There’s also a section for how to deal with expired pushes. There’s also a section for push subscription options.

Does this allow a user to set a period of time between pushes?

If you could file this as a question/issue on the spec repo, that'd be really helpful [2].

Léonie

[2] [https://github.com/w3c/push-api/](https://github.com/w3c/push-api/)
--

Want more features?

Request early access to our private beta of readable email premium.