Meeting minutes
Review of editorial refactoring of EPUB Accessibility 1.2 and techniques document.
AvneeshSingh: We collect comments and have some specific questions.
<AvneeshSingh> https://
mgarrish: where should we keep the references to Optimized publications?
George: I would be in favor of an Appendix.
George: 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.
gpellegrino: 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.
CharlesL: I would expect Optimized to be an EPUB Optimized, with Braille ready inside.
AvneeshSingh: Braille rendition of EPUB is an important subject we are discussing at DAISY.
George: A media overlay is an EPUB that can easily become an audiobook.
AvneeshSingh: 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.
<CharlesL> +1 to a dual approach
mgarrish: I understand, then maybe not as a big section.
gautierchomel: maybe then we want to inform about limitations of EPUB for accessibility.
mgarrish: yes, accessible universal does not fits every needs.
mgarrish: Second question is about the Guide to Optimized Publication Standards for a non-normative list of standards.
https://
mgarrish: do we want to have this guidance here or at daisy?
mgarrish: it's legacy from the IDPF.
AvneeshSingh: It probably makes more sense to have this list on daisy side
AvneeshSingh: Most of optimized accessibility specifications compatible with EPUB are created by DAISY community.
George: we have the legacy specifications at daisy and the ebraille incoming. All of those are Daisy Standards.
George: NIMAS will be revisited also, it's derived from Daisy. It is good to have a register of all optimized formats.
mgarrish: Next question, in dc conform to you could use the value none. Shall we example that and be clear it is usable?
CharlesL: unknown and none are useful, but then you must say who evaluated.
mgarrish: probably the accessibility summary is more important when the publication is not accessible, to explain why.
AvneeshSingh: conformsTo is a string you can put what ever you want.
CharlesL: the guidance already mention xyz conformance. We only miss information about what to do if we use none or unknown.
AvneeshSingh: That's an interesting discussion for the community group, I'll put it on next week agenda to have feedback.
CharlesL: I have seen conformsTo with "ACE version xx"
gpellegrino: the important information is in metadata. Conformance is black or white, it helps secure production.
mgarrish: 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: conformance require human intelligence, no magic bullet exist.