-
Notifications
You must be signed in to change notification settings - Fork 63
Move details of media overlays to techniques #2237
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
Conversation
…to identify all the skippable/escapable structures. The intention is that you don't have to identify other kinds beyond the recommendations, but may.
Co-authored-by: Ivan Herman <ivan@w3.org>
…nto a11y/issue-2221 # Conflicts: # epub33/a11y-tech/index.html
|
It seems that escaping from the table entirelly is appropriate. Creating a complex user interface and placing authoring requirements is too much. |
…lls and add note about process not being well defined
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wondering if this example should be coded with role="doc-example"?
<aside class="example" title="Identifying a skippable footnote">
If you're asking about examples in general, that's problematic as the superclass is changing to figure in DPUB 1.1. I don't know yet how that impacts its use on asides. I don't want to muck around with the respec template until I'm sure. |
|
Sorry Matt, the code snippit was stripped out it was an example we were providing I believe. See above now. |
remove table cell and row semantics and list item from escapable structure lists; add note about unreliability of support for nested escapable structures to core spec; add note to the accessibility techniques about the same issue that references across to the core spec for more details; link semantics to the ssv in the core spec;
Yes, this is what I was referring to. The use of |
…nto a11y/issue-2221
This is my best attempt to make the accessibility objectives less tied to media overlays.
In place of "Media Overlays", I've used "Synchronized Text-Audio Playback" for the main specification.
I've also added a technique to match each objective. These should work as starters, but they need thorough review.
The examples I added for skippability and escapability were largely copied from the ones already in the media overlays section of the core spec. I just tweaked them to exemplify different semantics. I didn't try to make examples for the reading order and complete text techniques, as these would be complex and time-consuming to build. I don't think they're critical to have.
Let me know if you think I have anything wrong, or have thoughts on how to improve what's there.
Fixes #2221
Preview | Diff