Add accessibility section (#342)

* Add accessibility section * fixup * Update index.html Co-authored-by: Martin Thomson <[email protected]> * Additional text from mt Co-authored-by: Martin Thomson <[email protected]>
w3c · Oct 25, 2021 · 63abbbd · 63abbbd
1 parent 95c742d
commit 63abbbd
Showing 1 changed file with 18 additions and 0 deletions.
diff --git a/index.html b/index.html
@@ -1265,6 +1265,24 @@ <h2>
         </tr>
       </table>
     </section>
+    <section>
+      <h2>
+        Accessibility
+      </h2>
+      <p>
+        The <cite>Push API</cite> does not provide any means itself to present data it receives
+        from a [=push service=]. Instead, the <cite>Push API</cite> relies on other APIs –
+        primarily the [[[NOTIFICATIONS]]] – to present received information to an end user. As
+        such, there are no accessibility requirements for the <cite>Push API</cite> itself.
+        However, specifications such as [[NOTIFICATIONS]] provide guidance how to present
+        notifications in an accessible manner.
+      </p>
+      <p>
+        Further, presenting an accessible interface might depend on transferring more information
+        than a push message can convey. Push messages are best suited to carrying small amounts of
+        content or identifiers. Any larger resources need to be fetched from servers.
+      </p>
+    </section>
     <section id="conformance">
       <p>
         This specification defines conformance criteria that apply to a single product: the