1. Introduction
For now, see the explainer.
See https://garykac.github.io/procspec/, https://dlaliberte.github.io/bikeshed-intro/index.html, and https://speced.github.io/bikeshed/ to get started on your specification.
Copyright © 2024 the Contributors to the Auto-Generate Captions for <video> Specification, published by the Web Platform Incubator Community Group under the W3C Community Contributor License Agreement (CLA). A human-readable summary is available.
Proposal to enhance the <video>
element with an auto-generate-caption
attribute to improve accessibility by natively generating captions for video content.
This specification was published by the Web Platform Incubator Community Group. It is not a W3C Standard nor is it on the W3C Standards Track. Please note that under the W3C Community Contributor License Agreement (CLA) there is a limited opt-out and other conditions apply. Learn more about W3C Community and Business Groups.
For now, see the explainer.
See https://garykac.github.io/procspec/, https://dlaliberte.github.io/bikeshed-intro/index.html, and https://speced.github.io/bikeshed/ to get started on your specification.
Conformance requirements are expressed with a combination of descriptive assertions and RFC 2119 terminology. The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in the normative parts of this document are to be interpreted as described in RFC 2119. However, for readability, these words do not appear in all uppercase letters in this specification.
All of the text of this specification is normative except sections explicitly marked as non-normative, examples, and notes. [RFC2119]
Examples in this specification are introduced with the words “for example”
or are set apart from the normative text
with class="example"
,
like this:
Informative notes begin with the word “Note”
and are set apart from the normative text
with class="note"
,
like this:
Note, this is an informative note.
Tests relating to the content of this specification may be documented in “Tests” blocks like this one. Any such block is non-normative.