diff --git a/index.html b/index.html
index f782408..e1b1a63 100644
--- a/index.html
+++ b/index.html
@@ -1520,6 +1520,44 @@ Same-origin restriction
+
+
+
+ Accessibility considerations
+
+
+ The Compute Pressure API is focused on improving the user experience. There are two ways in which applications that build on the API can positively impact accessibility.
+
+
+ -
+ Considering users' access needs when making decisions based on information gathered using the API.
+
+ -
+ Designing and making user interfaces based on information gained from the API with accessibility in mind.
+
+
+
+ As a consumer of the API, it's important to consider both of these opportunities. Here are some examples:
+
+ -
+ Decision: In a video conferencing scenario, there may be multiple video streams. The system may determines that it needs to drop certain streams in order to conserve resources. If one of the video streams comes from a sign language interpreter, then that stream must be prioritized over others, so that the user can still understand the conversation. In practice, this could be simply implemented by allowing the user to "pin" a certain stream, and ensuring that that pinned stream is never automatically dropped by the system.
+
+ -
+ User Interface:
+
+ -
+ A simple load-level meter, in which the current usage level bucket is indicated on the screen. This information must be conveyed using more than just color, so that people who cannot perceive color can still perceive the information. A symbol could be used in conjunction with color. Text could also be used in conjunction with both shape and color.
+
+ -
+ Some applications may present a notification to the user when some functionality is restricted due to compute pressure. These notifications may take the form of "toast" messages, in which case care must be taken to ensure that people using assistive technologies (including screen readers) can be made aware of the notification, and dismiss it, without unduly interrupting their workflow.
+
+
+
+
+
+
+
+