Checkpoint 6.3 : Programmatic access to non-HTML/XML content
For content other than HTML and XML, provide structured programmatic read access to content.
If the user can modify the state or value of a piece of non-HTML/XML content through the user interface (e.g., by checking a box or editing a text area), allow programmatic read access to the current state or value, and allow the same degree of write access programmatically as is available through the user interface.
As part of satisfying provision one of this checkpoint, implement at least one API according to this API cascade:
The API is defined by a W3C Recommendation, or the API is publicly documented and designed to enable interoperability with assistive technologies.
If no such API is available, or if available APIs do not enable the user agent to satisfy the requirements,
implement at least one publicly documented API to satisfy the requirements, and
follow operating environment conventions for the use of input and output APIs.
Normative inclusions and exclusions
"Structured programmatic access" means access through an API to recognized information items of the content (such as the information items of the XML Infoset [INFOSET]). Plain text has little structure, so an API that provides access to it will be correspondingly less complex than an API for XML content. For content more structured than plain text, an API that only provides access to a stream of characters does not satisfy the requirement of providing structured programmatic access. This document does not otherwise define what is sufficiently structured access.
An API is considered "available" if the specification of the API is published (e.g., as a W3C Recommendation) in time for integration into a user agent's development cycle.