Meeting minutes
Review of editorial refactoring of EPUB Accessibility 1.2 and techniques document.
Avneesh Singh: We collect comments and have some specific questions.
<Avneesh Singh> https://
Matt Garrish: where should we keep the references to Optimized publications?
George Kerscher: I would be in favor of an Appendix.
George Kerscher: there's confusion about audiobook, we want accessibility metadata about audiobooks in the trade. It is good to make sure there is no confusion with optimized daisy formats.
Gregorio Pellegrino: The title of the document is EPUB accessibility, this section is about other formats. We should not change the document name and push them (and the audiobook references) to an annex.
Charles LaPierre: I would expect Optimized to be an EPUB Optimized, with Braille ready inside.
Avneesh Singh: Braille rendition of EPUB is an important subject we are discussing at DAISY.
George Kerscher: A media overlay is an EPUB that can easily become an audiobook.
Avneesh Singh: This section is for education purpose. EPUB accessibility and WCAG 2.x is great but cannot fit all needs. Could we keep a section to inform this concept.
<Charles LaPierre> +1 to a dual approach
Matt Garrish: I understand, then maybe not as a big section.
Gautier Chomel: maybe then we want to inform about limitations of EPUB for accessibility.
Matt Garrish: yes, accessible universal does not fits every needs.
Matt Garrish: Second question is about the Guide to Optimized Publication Standards for a non-normative list of standards.
https://
Matt Garrish: do we want to have this guidance here or at daisy?
Matt Garrish: it's legacy from the IDPF.
Avneesh Singh: It probably makes more sense to have this list on daisy side
Avneesh Singh: Most of optimized accessibility specifications compatible with EPUB are created by DAISY community.
George Kerscher: we have the legacy specifications at daisy and the ebraille incoming. All of those are Daisy Standards.
George Kerscher: NIMAS will be revisited also, it's derived from Daisy. It is good to have a register of all optimized formats.
Matt Garrish: Next question, in dc conform to you could use the value none. Shall we example that and be clear it is usable?
Charles LaPierre: unknown and none are useful, but then you must say who evaluated.
Matt Garrish: probably the accessibility summary is more important when the publication is not accessible, to explain why.
Avneesh Singh: conformsTo is a string you can put what ever you want.
Charles LaPierre: the guidance already mention xyz conformance. We only miss information about what to do if we use none or unknown.
Avneesh Singh: That's an interesting discussion for the community group, I'll put it on next week agenda to have feedback.
Charles LaPierre: I have seen conformsTo with "ACE version xx"
Gregorio Pellegrino: the important information is in metadata. Conformance is black or white, it helps secure production.
Matt Garrish: we cannot really just display what is in ConformsTo, we use a control vocabulary to trigger displays. So the question is what should we do with none and unknown.
George Kerscher: conformance require human intelligence, no magic bullet exist.