Matt Garrish

That's what has me wondering if we really need two properties for this or if that's making a semantic distinction that never makes it to the end user. Is there...

Right now the plan is to not use the `refines` attribute so these would be contact emails for the publication and not tied to other metadata. If the property is...

> These links are not programmatically identifiable as extended descriptions You can use aria-details to point to a link to a description. It's one of the examples they provide in...

> Are we thinking that semantics of a link to an extended description is needed? Are links to descriptions all that ambiguous? The reason we added the semantics we did...

We already have an extensive caution note in the epub:type attribute definition to explain this: https://www.w3.org/TR/epub-34/#caution-7

There's already a scripting accessibility section that refers to WAI-ARIA: https://www.w3.org/TR/epub-34/#sec-scripted-a11y Sorry, I just don't share your enthusiasm for informative sections in standards. The EPUB specification is not where people...

FYI, this isn't the best place to ask for help with validation errors. This is where the epubcheck application is developed so questions like this usually get closed because they...

Note that I reopened https://github.com/w3c/epub-specs/issues/667 and we're going to be adding application/x-font-ttf to the list of core media types for TTF fonts in https://github.com/w3c/epub-specs/pull/2726 It will eventually mean that this...

The relationships section is meant to explain specific implementation details or differences with the underlying technologies used in EPUB. In the case of WCAG, ARIA, etc. those are technologies that...

> OK for adding at least a TOC entry named "_Relationship to ARIA-DPUB_" as you suggest. No, I'm only suggesting that we can mention DPUB-ARIA in the existing accessibility section....