– DRAFT –
(MEETING TITLE)

Proposed approval for Publishing the Guide for Audio Playback and Text-To-Speech

<AvneeshSingh> https://w3c.github.io/publ-a11y/drafts/audio-playback/

AvneeshSingh: George and Matt worked a lot on this document, it is now time for review

mgarrish: yes it is an introduction for explaining the difference between text-to-speech, media overlay and audio-books
… it is not super technical, it is more editorial

GeorgeK: It came up in different calls and discussions, this should be a point-of-reference for everyone talking about audio and digital publishing (in accessibility)

ChrisOliverOttawa: I've read the document and it was super useful for me, thanks!

JF: is this document going to be published as a working group note?

AvneeshSingh: very interesting, the major issue is that EPUB 3 WG is really focused on the EPUB format, while these documents are more broad (for the whole digital publishing industry)

JF: I understand, but since in the publishing a11y field the information are divided in different silos (W3C, CG, DAISY, etc.)... I see problems for newbies in the field

zheng_xu_: I think this is non spec document, but only an overview document; our goal as Community Group is to make the output of different task forces to become specs
… maybe we can create an index page with links to all the different specs, I think this may be super useful

CharlesL: do we want to add note about the "read now" functionality of reading apps

mgarrish: Yes, I think that there is an index page in the Publishing @ W3C... we may check

<JF> +1 Matt

AvneeshSingh: the publishing community group is a persistent group where discussions happen, the EPUB 3 WG, the audiobook WG, etc are more focused on specs (with a timeline)

JF: I understand, I still think that having an index page for linking to different specs is important

GeorgeK: to Charles "read now" seems more and action, more then a feature, should we add it?

CharlesL: Yes, I mean the functionality to launch the read-aloud

GeorgeK: ok, please check

AvneeshSingh: are we ready to publish this document or do we need some more time?

mgarrish: maybe we can vote for publishing, pending the Charles review

<mgarrish> Proposal: approve publication of the audio playback guide pending review of the read aloud issue by Charles and George

<GeorgeK> +1

<CharlesL> +1

<JF> +1

<AvneeshSingh> +1

<mgarrish> +1

+1

<ChrisOliverOttawa> +1 not sure I can vote

<AvneeshSingh> resolved

Update from accessibility summary guidance document sub task force

GeorgeK: some items have been added to close some issues

<AvneeshSingh> https://w3c.github.io/publ-a11y/drafts/schema-a11y-summary/

GeorgeK: we have Gregorio here, we have a proposal language

gpellegrino: it is fine for me, do we suggest to have multiple accessibility summary in more languages?

GeorgeK: normally one book is for one target, so I think it is fine to have only one

gpellegrino: ok, I think we should make it more explicit, and adding some info about lang attribute on the <meta> tag

JF: I don't think it is possible to put the lang attribute, I mean in the HTML specs it is not possible
… for different languages we may put links in the accessibility summary

mgarrish: Specify the language in the OPF document it is required from the a11y specs
… for JF: it is possible to define language in the OPF file (and also at metadata level)

Naomi: The problem here I see is that the EPUB doesn't support two languages (toc, ncx, etc.)
… I think it is a different question

JF: I see the editorial considerations, but not the technical considerations
… I don't see technical recomandations about formatting, tags, etc.

GeorgeK: I'll create an issue, and the I'll create a paragraph for this

<JF> +1 to i18n issues and lang markup George

<Zakim> JF, you wanted to note that what Matt was speaking about (tech points) is not documented (or I could not find it)

GeorgeK: the thing of having flat text is common to alt-text and other standards

zheng_xu_: I think that having free text from the publisher in the accessibility summary would be great

mgarrish: I think it is feasible to put markup in the package document
… for this we've created the linked records in EPUB

JF: I fully understand, but I think this should be written explicitly somewhere

mgarrish: EPUBCheck checks for this thing, so an accessibility summary with HTML markup will not pass

JF: I'm looking for edge-cases

mgarrish: the specs doens't allow markup in the package document

AvneeshSingh: we should be independent from the format

GeorgeK: ok, for me it is fine if we add a line telling that there should be only one accessibility summary, then we can merge with the main document

JF: ok, for my points I'll file an issue

GeorgeK: if people can review the section on conformance, it would be great

<Zakim> JF, you wanted to note that if we can't put in markup, then we should say that explicitly

<JF> +1 Charles

CharlesL: I think we should take care of the examples, for inconsistency

GeorgeK: yes, I've an issue for that, we'll work on them after finishing the guide

Update from MARC cross walk sub task force

Chris: Technical vs. editorial matches to library world MARC21 and says nothing about how to record the metadata. This is very familiar to me on the accessibilitySummary discussions :)
… , Thank you Gregoria and Madeleine on accessModeSufficient which was very enlightening. Waiting for June meetings and feedback from MARC21 users/experts. June 6 Marrakesh meeting / june 9 meeting and other meetings later in the month.

Michelle_: we aren't talking about discovery just well formed access. would be nice to see what Librarians are using ie. products.
… , how to grab and surface these access points

Chris: We are looking a granularity within MARC21 so it can be machine actionable. could be a proposal RDA group. Yes this is very interesting and our greatest challenge we can record great metadata if 3rd party systems don't use it that is a challenge.

Michelle_: if we can get datapoints - customers who complain get things changed.
… , if there are specific things in EBSCO / Proquest . if there are things we need to put together a proposal I am happy to help.

AvneeshSingh: great call, great inputs, and looking fwd to continued discussions on the issue tracker.