-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New role for audio transcripts #2164
Comments
Discussed briefly during new issue triage: https://www.w3.org/2024/04/25-aria-minutes.html#t01 |
Both
A transcript can live within the same page as the video or elsewhere. For the scope of the web, a transcript has no technical spec behind it (except that of the host language). None of I am covering all this to set the baseline representation in standards today. Which then brings me to some questions to try to understand the request...
|
CONTEXT
CLARIFICATION
Hope it is clearer. |
Description of bug or feature request
For accessible video, we can qualify some tracks as subtitles/captions/descriptions, thanks to the kind attribute.
For accessible audio only (i.e. outside apart from videos), there no such equivalent. So far, audio transcripts are simply associated to their audio though a div element, in order to group both the audio and its transcript. Transcripts can modeled in different manners through HTML elements (a, details, div, p), that can be used for other information than transcripts (ex: download, sourcing, etc.). As a consequence, there is no way to distinguish an audio transcript from another information.
Could it be possible to add on HTML elements a, details, div, p the following:
This would provide the means to qualify as such every HTML content provided by the authors to make audio/video accessible (even in an unsynchronized mode):
Will this require a change to CORE-AAM?
If unknown, leave blank. If relevant, link bug.
Will this require a change to the ARIA authoring guide?
If unknown, leave blank. If relevant, link bug.
The text was updated successfully, but these errors were encountered: