W3C

– DRAFT –
(MEETING TITLE)

30 November 2021

Attendees

Present
Alex_, avneeshsingh, CharlesL, George, gpellegrino, JF, Madeleine, mgarrish, rickj
Regrets
-
Chair
avneeshsingh
Scribe
avneeshsingh, gpellegrino

Meeting minutes

Guidance for writing accessibility summary (Raw document for starting point is at:https://github.com/benetech/AccessibilitySummaryEPUBMetadata/blob/master/AccessibilitySummaryAuthoringGuidelines.md)

avneeshsingh: welcome to Publishing CG a11y TF
… the idea is to define an agenda for the next months
… let's start from today's agenda

https://github.com/benetech/AccessibilitySummaryEPUBMetadata/blob/master/AccessibilitySummaryAuthoringGuidelines.md

avneeshsingh: Guidence document for Accessibility Summary
… it's a metadata for humans (non-machine-readable)
… publishers are asking for guidance on how to create che accessibility summary

George: we started with this guide at the same time of the UX guidelines for displaying metadata
… the UX guide was more urgent, so we focused on it

gpellegrino: what's the status of the document?

avneeshsingh: it is an early draft

JF: will it be published as a W3C note?

avneeshsingh: it should be published as a Community Group note

JF: I suggest to investigate in publishing as a W3C note

avneeshsingh: can you move the document in ReSpec?
… CharlesL

CharlesL: yes, if mgarrish can help with the first transformation

Madeleine: does this will enable issue tracking for this doc?

avneeshsingh: yes

rickj: ??? (sorry)

CharlesL: accessibilitySummary is only text, we cannot have formatting there

rickj: I think this could be useful also for other formats (like PDFs)

https://www.w3.org/publishing/a11y/UX-Guide-metadata/principles/

avneeshsingh: next big item is maintenance of the UX guide for metadata
… there are some changes in the new specs, so we have to modify them
… to align
… me and Gregorio had a call with EDRLab on their work in France

<Madeleine> https://github.com/w3c/publ-a11y/issues

gpellegrino: they're setting up a working group for displaying accessibility metadata of ebooks, really similar to out work
… this work was requested by the French Ministry for Culture
… they've set up a working group with publishers, librarians, ecommerce and end-users

<Zakim> rickj, you wanted to mention https://github.com/w3c/publ-a11y/issues/77

gpellegrino: they've translated the UX guide in French
… and they've developed a mockup for displaying metadata
… they'll test it with end users and give us feedback

rickj: I think it may be important to find a solution for accessibility metadata reconciliation (from different sources)
… the problem is if they're conflicting

gpellegrino: I think we can work on it in this TF, producing best practices

<mgarrish> https://www.w3.org/community/a11y-discov-vocab/

avneeshsingh: for maintaining the Schema.org values we've created a specific community group lead by Charles and Madeleine

https://www.w3.org/community/a11y-discov-vocab/

CharlesL: we have a wiki page with the different values for EPUB accessibility
… we have to clean them; some examples are outdated

Madeleine: for now the group will work more on issues and posting rather than with meetings

Further plans for User experience guide for displaying accessibility metadata.

https://github.com/w3c/publ-a11y/blob/main/editorial-drafts/audio-playback/index.html

Document for explaining difference between audio books, audio sync with text and read aloud

avneeshsingh: people were confused on the difference between audiobooks, TTS, MO, etc.
… The document is nearly finished, I think in the next meeting we can vote for publish it

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

avneeshsingh: as a CG report

Should we move ARIA roles and bpub:type guide from IDPF to W3C?

https://idpf.github.io/epub-guides/epub-aria-authoring/

mgarrish: we have some IDPF documents that weren't re-published as W3C
… the only document that is related to accessibility is the mapping between epub:type and DPUB Aria roles
… it needs some updates
… the question is: should we republish it?

gpellegrino: I think it is important to update and re-publish it

George: I'm a little bit concerned of too many documents... maybe we can add it to the DPUB Aria specs

mgarrish: this is very much related to EPUB

avneeshsingh: is a Community Report the right type of document?

mgarrish: yes, maybe it is something that may be transfered to the EPUB WG

CharlesL: I don't even know if it is an "accessibility" document

mgarrish: I'll open an issue in the EPUB WG for moving this document

CharlesL: with the CG we have a broaden audience, but the document is done, so we only have to update and publish it

mgarrish: yes, when published everyone can give feedback, it is open

avneeshsingh: we have even speak about it in this group

<JF> +1 to Rick

rickj: I think all the work of the IDPF should be moved to the EPUB WG

Further discussion

<JF> which is why I asked about making the accessibility statement document an actual w3c Note

avneeshsingh: are other tasks on which members want to work on?

George: what about MARC technique for UX guide?

pascal: we have a metadata group in he library focused in accessibility
… we have some contacts in IFLA

avneeshsingh: great!

George: maybe we can open an issue on that

CharlesL: there is a grant for libraries for developing accessibility metadata, training, etc.

<JF> https://epub.tools

avneeshsingh: I hope there will be more calls for this TF
… thank you all for this co-planning of the next 7-8 months!

Minutes manually created (not a transcript), formatted by scribe.perl version 159 (Fri Nov 5 17:37:14 2021 UTC).

Diagnostics

Succeeded: s/update/updates/

Succeeded: s/epub.tools/https://epub.tools

No scribenick or scribe found. Guessed: avneeshsingh

Maybe present: pascal