13:45:04 <RRSAgent> RRSAgent has joined #pcg-a11y
13:45:04 <RRSAgent> logging to https://www.w3.org/2022/05/26-pcg-a11y-irc
13:45:14 <AvneeshSingh> zakim, this will be pcg-a11y
13:45:14 <Zakim> ok, AvneeshSingh
13:45:28 <AvneeshSingh> present+
13:45:45 <AvneeshSingh> chair: AvneeshSingh
13:47:01 <AvneeshSingh> agenda+ Proposed approval for Publishing the Guide for Audio Playback and Text-To-Speech
13:47:20 <AvneeshSingh> agenda+ Update from accessibility summary guidance document sub task force
13:47:39 <AvneeshSingh> agenda+ Update from MARC cross walk sub task force
13:47:54 <AvneeshSingh> agenda+ Any other business.
13:47:55 <ChrisOliverOttawa> ChrisOliverOttawa has joined #pcg-a11y
13:53:20 <GeorgeK> GeorgeK has joined #pcg-a11y
13:53:42 <GeorgeK> present+
13:54:48 <mgarrish> mgarrish has joined #pcg-a11y
14:00:13 <gpellegrino> gpellegrino has joined #pcg-a11y
14:00:35 <gpellegrino> present+
14:01:18 <JF> JF has joined #pcg-a11y
14:01:24 <CharlesL> CharlesL has joined #pcg-a11y
14:01:25 <JF> Present+
14:01:26 <ChrisOliverOttawa> present+
14:01:29 <CharlesL> present+
14:01:40 <JF> agenda?
14:01:43 <mgarrish> present+
14:02:02 <gpellegrino> scribe+
14:02:20 <AvneeshSingh> zakim, next agendum
14:02:20 <Zakim> agendum 1 -- Proposed approval for Publishing the Guide for Audio Playback and Text-To-Speech -- taken up [from AvneeshSingh]
14:02:52 <AvneeshSingh> https://w3c.github.io/publ-a11y/drafts/audio-playback/
14:03:10 <zheng_xu_> zheng_xu_ has joined #pcg-a11y
14:03:11 <gpellegrino> AvneeshSingh: George and Matt worked a lot on this document, it is now time for review
14:03:39 <zheng_xu_> present+
14:04:11 <Naomi> Naomi has joined #pcg-a11y
14:04:18 <gpellegrino> mgarrish: yes it is an introduction for explaining the difference between text-to-speech, media overlay and audio-books
14:04:25 <Naomi> present+
14:04:31 <gpellegrino> ... it is not super technical, it is more editorial
14:05:03 <AvneeshSingh> q?
14:05:22 <gpellegrino> 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)
14:05:22 <ChrisOliverOttawa> q+
14:05:31 <JF> Q+
14:05:38 <AvneeshSingh> ack next
14:05:55 <gpellegrino> ChrisOliverOttawa: I've read the document and it was super useful for me, thanks!
14:06:02 <AvneeshSingh> ack next
14:06:11 <chiaradm95_> chiaradm95_ has joined #pcg-a11y
14:06:26 <Michelle_> Michelle_ has joined #pcg-a11y
14:06:35 <Michelle_> present+
14:06:38 <gpellegrino> JF: is this document going to be published as a working group note?
14:06:49 <chiaradm95_> present+
14:06:53 <zheng_xu_> q+
14:06:58 <CharlesL> q+
14:07:43 <AvneeshSingh> q?
14:07:46 <gpellegrino> 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)
14:09:14 <mgarrish> q+
14:09:20 <AvneeshSingh> ack next
14:09:21 <gpellegrino> 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
14:11:05 <gpellegrino> 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
14:11:24 <JF> Q+
14:12:33 <AvneeshSingh> ack charl
14:12:34 <gpellegrino> ... maybe we can create an index page with links to all the different specs, I think this may be super useful
14:13:36 <gpellegrino> CharlesL: do we want to add note about the "read now" functionality of reading apps
14:13:39 <AvneeshSingh> ack next
14:14:15 <gpellegrino> mgarrish: Yes, I think that there is an index page in the Publishing @ W3C... we may check
14:14:18 <JF> +1 Matt
14:14:37 <GeorgeK> q+
14:15:30 <gpellegrino> 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)
14:15:54 <AvneeshSingh> ack next
14:17:39 <gpellegrino> JF: I understand, I still think that having an index page for linking to different specs is important
14:17:45 <AvneeshSingh> q?
14:17:51 <AvneeshSingh> ack george
14:18:51 <gpellegrino> GeorgeK: to Charles "read now" seems more and action, more then a feature, should we add it?
14:19:12 <AvneeshSingh> q?
14:19:13 <gpellegrino> CharlesL: Yes, I mean the functionality to launch the read-aloud
14:19:20 <gpellegrino> GeorgeK: ok, please check
14:19:42 <gpellegrino> AvneeshSingh: are we ready to publish this document or do we need some more time?
14:20:00 <gpellegrino> mgarrish: maybe we can vote for publishing, pending the Charles review
14:20:54 <mgarrish> Proposal: approve publication of the audio playback guide pending review of the read aloud issue by Charles and George
14:21:01 <GeorgeK> +1
14:21:04 <CharlesL> +1
14:21:05 <JF> +1
14:21:05 <AvneeshSingh> +1
14:21:08 <mgarrish> +1
14:21:11 <gpellegrino> +1
14:21:21 <ChrisOliverOttawa> +1 not sure I can vote
14:21:22 <AvneeshSingh> resolved
14:21:48 <Murata_> Murata_ has joined #pcg-a11y
14:21:52 <AvneeshSingh> zakim, next agendum
14:21:52 <Zakim> agendum 2 -- Update from accessibility summary guidance document sub task force -- taken up [from AvneeshSingh]
14:21:59 <Murata_> present+
14:22:14 <gpellegrino> GeorgeK: some items have been added to close some issues
14:22:14 <AvneeshSingh> https://w3c.github.io/publ-a11y/drafts/schema-a11y-summary/
14:22:38 <JF> Q+
14:23:00 <AlexGrover> AlexGrover has joined #pcg-a11y
14:23:04 <AlexGrover> present+
14:23:15 <gpellegrino> ... we have Gregorio here, we have a proposal language
14:24:26 <Naomi> q+
14:25:18 <gpellegrino> gpellegrino: it is fine for me, do we suggest to have multiple accessibility summary in more languages?
14:27:29 <gpellegrino> GeorgeK: normally one book is for one target, so I think it is fine to have only one
14:27:31 <mgarrish> q+
14:28:04 <gpellegrino> gpellegrino: ok, I think we should make it more explicit, and adding some info about lang attribute on the <meta> tag
14:29:17 <gpellegrino> JF: I don't think it is possible to put the lang attribute, I mean in the HTML specs it is not possible
14:30:02 <gpellegrino> ... for different languages we may put links in the accessibility summary
14:30:10 <CharlesL> ack JF
14:30:13 <CharlesL> ack Naomi
14:31:35 <gpellegrino> mgarrish: Specify the language in the OPF document it is required from the a11y specs
14:31:39 <gpellegrino> q+
14:31:54 <JF> Q+ to note that what Matt was speaking about (tech points) is not documented (or I could not find it)
14:32:27 <Naomi> q+
14:32:44 <JF> ack mg
14:33:01 <gpellegrino> ... for JF: it is possible to define language in the OPF file (and also at metadata level)
14:33:06 <CharlesL> ack Naomi
14:34:24 <gpellegrino> Naomi: The problem here I see is that the EPUB doesn't support two languages (toc, ncx, etc.)
14:34:32 <gpellegrino> ... I think it is a different question
14:34:52 <zheng_xu_> q+
14:34:56 <gpellegrino> q-
14:36:20 <gpellegrino> JF: I see the editorial considerations, but not the technical considerations
14:37:05 <mgarrish> q+
14:37:19 <gpellegrino> ... I don't see technical recomandations about formatting, tags, etc.
14:38:04 <gpellegrino> GeorgeK: I'll create an issue, and the I'll create a paragraph for this
14:38:54 <JF> +1 to i18n issues and lang markup George
14:39:08 <CharlesL> ack J
14:39:08 <Zakim> JF, you wanted to note that what Matt was speaking about (tech points) is not documented (or I could not find it)
14:39:12 <CharlesL> ack z
14:39:14 <gpellegrino> ... the thing of having flat text is common to alt-text and other standards
14:41:17 <gpellegrino> zheng_xu_: I think that having free text from the publisher in the accessibility summary would be great
14:42:11 <gpellegrino> mgarrish: I think it is feasible to put markup in the package document
14:42:24 <gpellegrino> ... for this we've created the linked records in EPUB
14:42:32 <JF> Q+ to note that if we can't put in markup, then we should say that explicitly
14:42:58 <JF> ack mg
14:43:57 <gpellegrino> JF: I fully understand, but I think this should be written explicitly somewhere
14:45:37 <gpellegrino> mgarrish: EPUBCheck checks for this thing, so an accessibility summary with HTML markup will not pass
14:46:31 <gpellegrino> JF: I'm looking for edge-cases
14:47:01 <gpellegrino> mgarrish: the specs doens't allow markup in the package document
14:47:27 <gpellegrino> AvneeshSingh: we should be independent from the format
14:49:15 <gpellegrino> 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
14:49:36 <gpellegrino> JF: ok, for my points I'll file an issue
14:50:11 <CharlesL> q+
14:50:12 <gpellegrino> GeorgeK: if people can review the section on conformance, it would be great
14:50:48 <JF> ack me
14:50:48 <Zakim> JF, you wanted to note that if we can't put in markup, then we should say that explicitly
14:50:56 <CharlesL> ack me
14:51:37 <JF> +1 Charles
14:51:52 <gpellegrino> CharlesL: I think we should take care of the examples, for inconsistency
14:52:16 <gpellegrino> GeorgeK: yes, I've an issue for that, we'll work on them after finishing the guide
14:52:44 <CharlesL> zakim, next item
14:52:44 <Zakim> agendum 3 -- Update from MARC cross walk sub task force -- taken up [from AvneeshSingh]
14:52:58 <CharlesL> scribe+
14:53:45 <CharlesL> 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 :)
14:54:55 <CharlesL> …, 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.
14:55:03 <Michelle_> q+
14:55:11 <CharlesL> ack Michelle_
14:55:50 <CharlesL> Michelle_:  we aren't talking about discovery just well formed access.  would be nice to see what Librarians are using ie. products.
14:56:02 <CharlesL> …, how to grab and surface these access points
14:57:10 <CharlesL> 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.
14:57:37 <CharlesL> Michelle_:  if we can get datapoints - customers who complain get things changed.
14:58:23 <CharlesL> …, if there are specific things in EBSCO / Proquest .  if there are things we need to put together a proposal I am happy to help.
14:59:34 <CharlesL> AvneeshSingh: great call, great inputs, and looking fwd to continued discussions on the issue tracker.
15:05:19 <CharlesL> rrsagent, make logs public
15:05:26 <CharlesL> rrsagent, draft minutes
15:05:26 <RRSAgent> I have made the request to generate https://www.w3.org/2022/05/26-pcg-a11y-minutes.html CharlesL
15:07:32 <CharlesL> CharlesL has left #pcg-a11y
15:09:19 <Avneesh> Avneesh has joined #pcg-a11y
15:09:43 <Avneesh> rrsagent, make logs public
15:09:59 <Avneesh> rrsagent, make logs public
15:10:16 <Avneesh> rrsagent, make minutes
15:10:16 <RRSAgent> I have made the request to generate https://www.w3.org/2022/05/26-pcg-a11y-minutes.html Avneesh
15:11:19 <Avneesh> zakim, leave
15:11:19 <Zakim> leaving.  As of this point the attendees have been AvneeshSingh, GeorgeK, gpellegrino, JF, ChrisOliverOttawa, CharlesL, mgarrish, zheng_xu_, Naomi, Michelle_, chiaradm95_, Murata_,
15:11:19 <Zakim> Zakim has left #pcg-a11y
15:11:22 <Zakim> ... AlexGrover
16:12:54 <mgarrish> mgarrish has joined #pcg-a11y