Closed 7mary4 closed 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:
Displaying a notification. This is the common case, where the Notifications API is used to display the notification. This often means that display, and options thereof, are delegated to the underlying operating system.
Updating an opened page. Notably, displaying the received message in an already opened chat window, or comment stream. This, as well as the pursuing layout changes, is entirely the developer's doing.
Update the cache. In this case nothing has to be displayed to the user at all.
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.
@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.
The document states clearly the user must authorize the push:
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.