Add accessibility concerns section

Assembled using the very helpful draft FAST checklist https://w3c.github.io/apa/fast/checklist.html

Resolves #327

Author: inexorabletash

index.bs

@@ -6736,6 +6736,30 @@ approach is to include version identifiers in the serialization
 format, and to reconstruct any internal state from script-visible
 state when older data is encountered.
 
+<!-- ============================================================ -->
+# Accessibility considerations # {#accessibility}
+<!-- ============================================================ -->
+
+*This section is non-normative.*
+
+The API described by this specification has limited accesibility considerations:
+
+* It does not provide for visual rendering of content, or control over color.
+* It does not provide features to accept user input.
+* It does not provide user interaction features.
+* It does not define document semantics.
+* It does not provide time-based visual media.
+* It does not allow time limits.
+* It does not directly provide content for end-users, either in textual, graphical or other or non-textual form.
+* It does not define a transmission protocol.
+
+The API does allow storage of structured content. Textual content can be stored as strings. Support exists in the API for developers to store alternative non-textual content such as images or audio as {{Blob}}, {{File}}, or {{ImageData}} objects. Developers producing dynamic content applications using the API should ensure that the content is accessible to users with a variety of technologies and needs.
+
+While the API itself does not define a specific mechanism for it, storage of structured content also allows developers to store internationalized content, using different records or structure within records to hold language alternatives.
+
+The API does not define or require any a user agent to generate a user interface to enable interaction with the API. User agents may optionally provide user interface elements to support the API. Examples include prompts to users when additional storage quota is required, functionality to observe storage used by particular web sites, or tools specific to the API's storage such as inspecting, modifying, or deleting records. Any such user interface elements must be designed with accessibility tools in mind. For example, a user interface presenting the fraction of storage quota used in graphical form must also provide the same data to tools such as screen readers.
+
+
 <!-- ============================================================ -->
 # Revision history # {#revision-history}
 <!-- ============================================================ -->
@@ -6759,6 +6783,7 @@ For the revision history of the second edition, see [that document's Revision Hi
 * Transactions are now temporarily made inactive during clone operations.
 * Added {{IDBTransactionOptions/durability}} option and {{IDBTransaction/durability}} attribute. ([Issue #50](https://github.com/w3c/IndexedDB/issues/50))
 * Specified [[#transaction-scheduling]] more precisely and disallow starting read/write transactions while read-only transactions with overlapping scope are running. ([Issue #253](https://github.com/w3c/IndexedDB/issues/253))
+* Added <a href="#accessibility">Accessibility considerations</a> section. ([Issue #327](https://github.com/w3c/IndexedDB/issues/327))
 
 <!-- ============================================================ -->
 # Acknowledgements # {#acknowledgements}