Skip to content
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

3.4.2.3.1 Completeness in EPUB A11Y 1.1 #2221

Closed
t-kudou opened this issue Apr 5, 2022 · 8 comments · Fixed by #2237
Closed

3.4.2.3.1 Completeness in EPUB A11Y 1.1 #2221

t-kudou opened this issue Apr 5, 2022 · 8 comments · Fixed by #2237
Labels
Accessibility11 Issues addressed in the Accessibility 1.1 revision Cat-Accessibility Grouping label for all accessibility related issues Spec-Accessibility The issue affects the EPUB Accessibility 1.1 Recommendation

Comments

@t-kudou
Copy link

t-kudou commented Apr 5, 2022

https://www.w3.org/TR/epub-a11y-11/#sec-mo-complete

Meeting this Objective
EPUB Creators MUST provide synchronized audio playback via Media Overlays for all textual content.

This statement could be interpreted as saying to provide synchronized audio using the Media Overlays mechanism, and not to use another mechanism.
Since the main purpose of this clause is to say that the complete audio narration should also be provided along with the full text, we believe that "for all textual content" is a weak explanation and should be "for complete textual content".

@murata2makoto
Copy link
Contributor

Kudou-san is a member of the JDC technical committee.

Does the sentence quote by Kudou-san mandate the use of MO? I guess not but it can be interpreted so.

Here is my interpretation of "via Media Overlays all textual content"

If an element within the XHTML body element has child text content, this element MUST be referenced by some PAR element or MUST be a descendant of an element referenced by some PAR element.

@mattgarrish mattgarrish added Cat-Accessibility Grouping label for all accessibility related issues Spec-Accessibility The issue affects the EPUB Accessibility 1.1 Recommendation labels Apr 5, 2022
@mattgarrish
Copy link
Member

Does the sentence quote by Kudou-san mandate the use of MO?

No, there is no requirement to use media overlays to meet the specification. And even if you use media overlays, you are not required to meet the objectives yet. We've kept that optional, as it says in the application section:

To maximize the effectiveness of Media Overlays for people with different reading needs, however, EPUB Creators are strongly encouraged to meet the OPTIONAL objectives defined in the next section.

@mattgarrish
Copy link
Member

Here is my interpretation of "via Media Overlays all textual content"

It would have to account for SVG, too.

@murata2makoto
Copy link
Contributor

It would have to account for SVG, too.

Any text element within an SVG content document MUST be referenced by some PAR element or MUST be a descendant of an element referenced by some PAR element.

@iherman
Copy link
Member

iherman commented Apr 6, 2022

It becomes a big more convoluted than that, @murata2makoto. It is not a par element that refers to a text element, it is a text SMIL element within a par that does that (via a src attribute).

Maybe it is enough to replace the reference to par to a text, and not refer to par; the structure of a valid SMIL document would require that text to be part of a par anyway.

@murata2makoto
Copy link
Contributor

It becomes a big more convoluted than that, @murata2makoto. It is not a par element that refers to a text element, it is a text SMIL element within a par that does that (via a src attribute).

Stand corrected. My bad.

But how can we make sure that all text element within an SVG content document is covered by SMIL?

@mattgarrish
Copy link
Member

There's probably a larger question here about why we're referencing media overlays directly if we want this to be technology agnostic. If media overlays are replaced in a future epub, we have to rewrite all the objectives to account for the new technology.

The section should probably be "Synchronized Text-Audio Playback" and we should write out the specific references to media overlay documents and par/seq elements. That explanation belongs in the techniques.

@mattgarrish
Copy link
Member

Assuming we move in this direction, the one good thing is that the techniques don't go to CR so we don't have to have any new additions in place before we transition. We'd just need to clean up the specification.

mattgarrish added a commit that referenced this issue Apr 14, 2022
Add change log entry to core spec for #2221
@mattgarrish mattgarrish added the Accessibility11 Issues addressed in the Accessibility 1.1 revision label May 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Accessibility11 Issues addressed in the Accessibility 1.1 revision Cat-Accessibility Grouping label for all accessibility related issues Spec-Accessibility The issue affects the EPUB Accessibility 1.1 Recommendation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants