search

w3c / epub-specs

Shared workspace for EPUB 3 specifications.
Other
305 stars 60 forks source link

[FXLA11Y] Media Overlays Section #2605

Closed wareid closed 9 months ago

wareid commented 10 months ago

Adding the text provided by Susan for the Media Overlays section.

sueneu commented 10 months ago

Transposed letters:

  • Ebook creators must ensure auditory playback for epub navigation. This gives reading systems the ability to **sue** auditory labels for links.
  • Ebook creators must ensure auditory playback for epub navigation. This gives reading systems the ability to **use** auditory labels for links.
    • gautierchomel commented 10 months ago

    Preview

    sueneu commented 10 months ago

    Here are the comments from my colleague who specializes in media overlays for children's picture books. He's pretty exasperated with the current state of accessibility in fxl.

    EPUB creators must ensure that all text content is available in audio. Feedback: Better to describe what the EPUB should have in it than to assign a task to a specific role. Not all EPUB creators are the content creators. Propose change to: All text within the EPUB must be available in audio

    Feedback: "All text" available as audio overlays is unrealistic/unreasonable. Asking publishers to create custom audio for things like text in images like a talk bubble, graphical text treatments, and text in logos on the copyright page would be too high a burden. He suggests levels of audio availability. 1 = main text available as audio, 2 = main text + captions, front, and back matter 3 = main text + captions, front matter, back matter + word bubbles and graphical text treatments. TTS is not within an EPUB creator's control. Question for the group: Is a combination of recorded audio/overlays for the main story with TTS for the copyright page and back matter acceptable in this case? Who decides that?

    In order to offer users greater control over content presentation, EPUB creators need to add structure and semantics so that the reading system has the necessary context to enable this type of user experience. With greater context, a reading system can provide the ability to skip past secondary content that interferes with the primary narrative and escape users from deeply nested structures like tables. Feedback: Children's picture books are rarely this complex. Tables are rarely used and semantic markup is never used in them. In picture books, there is little text and children skip by simply turning a page Suggestion: since children's picture books with small amounts of text are only one type of fxl title, let's keep the reference to tables and deeply nested structures. We could continue with EPUB attributes without assigning roles. Propose Change to: An accessible fixed layout EPUB should offer users greater control over presentation. Users should be able to skip past secondary content that interferes with the primary narrative and escape deeply nested structures like tables.

    Ebook creators must ensure auditory playback for epub navigation. This gives reading systems the ability to use auditory labels for links. Feedback: No, reading systems must ensure that they use already-standardized requirements, eg “the tag must contain useful information,” to accomplish this on the e-reader side.</em> <strong>Suggestion:</strong> This is another good place to describe attributes of the EPUB without assigning tasks or responsibilities in this document. <strong>Propose change to:</strong> <code>An accessible EPUB must have auditory navigation</code></p> <p><em><strong>General Feedback:</strong> The encouragement of cells of reflowable content within the fixed-layout structure would solve a lot. It would allow tables to be run as tables, not broken into individual words over a JPEG of the table lines, and also make adding “aside” or “table” or whatever more possible.</em></p> <p><em>Current accessibility in fixed layout picture books is, and there’s no other word, pathetic. Fix the actual issues instead of dreaming up new features, half of which don’t apply to fixed layout EPUBS. The best workaround for the inability of screen readers to handle a big block of words with individual spans without breaking the audio playback is to include aria-hidden=”true” on each word (so the screen reader does NOT read it) and then use role=”image” and aria-label=”text of the paragraph goes here” in a containing div, so the reading system reads that instead. The reading system then says “Image!” and reads the text with much less issue.</em></p> <p><em>Any level of synchronized audio should be considered a level of accessibility feature.</em></p> </div> </div> <div class="page-bar-simple"> </div> <div class="footer"> <ul class="body"> <li>© <script> document.write(new Date().getFullYear()) </script> Githubissues.</li> <li>Githubissues is a development platform for aggregating issues.</li> </ul> </div> <script src="https://cdn.jsdelivr.net/npm/jquery@3.5.1/dist/jquery.min.js"></script> <script src="/githubissues/assets/js.js"></script> <script src="/githubissues/assets/markdown.js"></script> <script src="https://cdn.jsdelivr.net/gh/highlightjs/cdn-release@11.4.0/build/highlight.min.js"></script> <script src="https://cdn.jsdelivr.net/gh/highlightjs/cdn-release@11.4.0/build/languages/go.min.js"></script> <script> hljs.highlightAll(); </script> </body> </html>