w3c / push-api

Push API
https://w3c.github.io/push-api/
Other
145 stars 40 forks source link

User preference for timing #257

Closed 7mary4 closed 7 years ago

7mary4 commented 7 years 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 and a section for push subscription options.

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

For instance, a person may take longer to read/complete a sequence due to a disability. If the screen changes too quicklly, due to a push, they could lose track of what they are doing. For these users, they may prefer to change their settings.

beverloo commented 7 years ago

Hi Ted, thank you for your report! The Push API is a communication protocol and defines means through which a message could reach the user. The developer then has to use other features to display the content to the user, if at all necessary. To give some example options:

Specifically to your question, I feel that it's a shared responsibility between the user agent (who choses a notification center) and the operating system (who usually provides one) to ensure displayed notifications are sufficiently accessible. However, since the act of displaying content is out of scope of this specification, I'm not sure whether adding a note would be sufficiently beneficial.

martinthomson commented 7 years ago

@7mary4, please see the discussion on #259, where the same issue was raised. There, the suggestion was to take this up as an accessibility note on the Notifications API.