– DRAFT –
(MEETING TITLE)

Progress update on document for guiding, how to write good accessibility summary

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

<Murata_> pres t

George: we have a draft we wish to finish. A small group of people raised hands.

Charles: started as a group at benetech & daisy.

<Michelle_> present

used kind of structure usable for respec

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

charles: lot of publisher copy past info for this summary. Making it of little use. Last interrogation was is it pertinent to keep this summary ?

Makoto want to join the group redacting this summary guideline

Michelle: will make it circulate to librarians so they can give theyre impression.

Charles: some info is present in others metas. This is where publishers can indicat wcag level and shortcomings (exemple : all images described)

charles: to be very informative. Some is potentialy automated (presence of video or alt text, etc.). Any automation could appear in SMART by Daisy.

Georges: the idea is that professor selecting a title could easy determine if it meets needs. the same for any person wishing to read a book.

Georges: it came from publishers willing to be able to describe freely in a human narrated way. (exemple: this book can be read with eyes, fingers and ears)

Georges: some usecases also appeared as content un describle by actual metadats (exemple: there is ruby anotations in this book)

Makoto: we need a way to indicate caracter table used (china, japan don't use unicode)

<Michelle_> 1+

Georges: there is also a pronounciation guideline groupe working. Some question appeared about 500 caraters limit

gpellegrino: yes, it comes from ONIX, not a strong requirement but a suggestion. Some actors of the supplky chain truncket so we need to speak with editeur.

Michelle: there are caracter limits in MARC too but usually so high it doesn't matter. This could make library system timeout. We need a research to make sur what technologies allows.

Michelle: (the problem may come from library system more than metadata limit)

<Bill_Kasdorf> works for me

Georges: idea: a subtaskforce next week same time to investigate this point

Georges: i'll send an invit to everyone, come who wants

Georges: remeber to use the issue tracker wisely : one question by issue.

Update on extending crosswalk of schema.org accessibility metadata and ONIX to MARC

<AvneeshSingh> https://w3c.github.io/publ-a11y/drafts/a11y-crosswalk-MARC/

<ChrisOliverOttawa_> From Hong Cui: The length limit for MARC field is 9999 octets max. https://www.loc.gov/marc/specifications/

Gautier: describe table crosswalk

Charles: one confusing think was to find ...

Chris: not eared back from unimarc comitee

Chris: on marc21 side we had a primary meeting and have a preliminary mapping. But need more discussion to make consensus.

Chris: very practical :i have github edit right, but find it hard to use.

<ccarr> https://www.loc.gov/standards/sourcelist/accessibility.html

Christopher: we also need a controlled vocabulary. This table will make ou work easier.

ccarr: we used the docx document previously circulated. We would llike to share but maybe not publicly yet

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

Michelle: the link that was shared in IRC is this the space for editing / comenting ? I have rights too, i can do this.

https://github.com/w3c/publ-a11y/tree/main/drafts/a11y-crosswalk-MARC

Charles: i'll break that table in multiple tables to make it easier to read

Avneesh: who will lead this subtaskforce?

Avneesh: any volunteer?

<ChrisOliverOttawa_> I can volunteer to help lead

<ccarr> I can co-lead

Madeline: i'll provide schema help

Charles: me too

<Bill_Kasdorf> I think that was Michelle

Georges: Michelle said once this group do the work we have to take it to a wilder audience. Does that mean MARC community ?

ChrisOliverOttawa: yes

Georges: the goal is to have a strong draft for a wilder review.

Georges: we have to keep people informed to invite them join in

ccarr: there are discussions underway at PCC but actually we can't add accessibility notes.

ccar: you can't say file format or drm presence actually.

ChrisOliverOttawa: Marc ddvisor comitee has a full agenda. This would come in the next meeting (june). We may ofeer to add this mapping to this meeting.

Bill_kasdorf: from a publisher point of view. we not use marc commonly. it's coming and may be but book publishers don't use so much marc but they all use ONIX.

Michelle: ONIX will help for transformations

Michelle: automated transformation

Avneesh: who will lead this group? Do you wish to discuss it first?

ChrisOliverOttawa_: maybe make sure we have all email. we need a meeting just focusing on marc.

Any other business

<ChrisOliverOttawa_> good