Matt Garrish

We should try to avoid turning this into a discussion of the merits of each syntax. Each has their own strengths and weaknesses and publishers will decide for themselves which...

> But this issue is not formulated as such. It is biased. Even if that were true, no one is going to decide whether to use the xml or html...

> I am not opposed to adding the HTML syntax for those who do not prioritize information assets To answer that seriously, it has always been a knock against epub...

> users tend to ask for an ebook that causes them no headache with the reading system they have at their disposal And this is the problem with trying to...

What I find interesting is that we keep hearing that reading systems aren't actually processing xhtml content documents using an xml parser but (many, most, all?) are already use an...

The onix definition corresponds more broadly to the navigation document as a whole. A reading system can present anything in the nav doc it wants to users, but since the...

schema.org metadata can be used to describe print resources, but even then I don't think it's particularly useful to have a braille value. I'd expect you can determine if it's...

What if the index isn't linked but there's a page nav, is that direct access?

Isn't this supposed to be a direct correlation with [SC 2.2.1 Timing Adjustable](https://www.w3.org/WAI/WCAG21/Understanding/timing-adjustable.html)? Playback speed control for audio and video isn't in WCAG and I don't think we'd want to...

Didn't we have this discussion about annotations already and that on their own they aren't specifically an accessibility feature? I thought we had already deprecated the value, to be honest.