search

w3c / dapt

Dubbing and Audio description Profiles of TTML2
https://w3c.github.io/dapt/
Other
7 stars 3 forks source link

Consider defining a mapping into an HTML representation for assistive tech #143

Open nigelmegitt opened 1 year ago

nigelmegitt commented 1 year ago

Assistive technology users are likely to have a hard time navigating a DAPT document. Consider defining a mapping (maybe an XSLT?) that allows people to render a DAPT document into an HTML representation that plays nicely with e.g. screen readers.

nigelmegitt commented 1 year ago

Discussed on Editor's call 2023-05-18: this is certainly a nice thing to have, but would not be a normative part of the specification.

brennanyoung commented 1 year ago

See https://github.com/whatwg/html/issues/9829

nigelmegitt commented 1 year ago

Thanks for relating that issue to this one of an HTML representation @brennanyoung - it's a great idea to have a UA-side model for how to express and present a transcript alongside the media that it represents. In a sense, DAPT already has that for audio playback and mixing, but there are no specific provisions for exactly how to present text, for example into an aria live element. That's currently left as an implementation choice (for the page author).

Initially, my intent was only considering the question "if I have a DAPT document, how can I understand what is in it?" given that it is an XML document that has a defined semantic structure. I considered mapping it into static HTML just for seeing it, but I would also want that HTML to work well with assistive technology, ideally. It could be that there are two distinct requirements here.