Accessibility self-review

[chrisn]

WebCodecs provides access to low level image, video, and audio encoding and decoding, so the API brings no particular accessibility concerns for implementations. The display or rendering of the media is the responsibility of the web application, e.g., using the HTML <canvas> element or Web Audio API, so rendering is less integrated with platform-level accessbility features. Consequently, accessibilty must be considered by the application developer and content author.

Responses to FAST Checklist:

• If technology allows visual rendering of content

  • Not applicable

• If technology provides author control over color

  • Not applicable

• If technology provides features to accept user input

  • Not applicable

• If technology provides user interaction features

  • Not applicable

• If technology defines document semantics

  • Not applicable

• If technology provides time-based visual media

  • See description above. Items in the Media Accessibility Checklist are the responsibility of the web application and/or content author

• If technology provides audio

  • See description above

• If technology allows time limits

  • Not applicable

• If technology allows text content

  • Not applicable

• If technology creates objects that don't have an inherent text representation

  • See description above

• If technology provides content fallback mechanisms, whether text or other formats

  • Not applicable

• If technology provides visual graphics

  • See description above

• If technology provides internationalization support

  • Not applicable

• If technology defines accessible alternative features

  • Not applicable

• If technology provides content directly for end-users

  • See description above

• If technology defines an API

  • See description above

• If technology defines a transmission protocol

  • Not applicable