– DRAFT –
(MEETING TITLE)

<GeorgeK> I am on zoom, do I have the wrong one?

Organizing meeting with APA group in TPAC.

AvneeshSingh: APA meeting?

GeorgeK: Pronunciation TF - emotion / poetry cadence etc. would require more work
… , could be done in separate steps.
… , could be a topic for discussion.

<AvneeshSingh> WAI-adapt

<AvneeshSingh> https://www.w3.org/WAI/adapt/

<MURATA> +present

<AvneeshSingh> accessible interlinear e-texts (e.g. Opera parts)

CharlesL: gave an explanation of ADAPT

AvneeshSingh: Interlinear Text

Naomi: having a text academic - presented like a footnote on every line,

George: Like margin annotations.

Naomi: its not secondary, it goes along the main

GeorgeK: when a teacher marks up for grammar notes etc.

MURATA: this is used a lot in Japan. Ruby is a good example of this CJK characters
… , over use of interlinear Text is a debate between the older generation and younger.

AvneeshSingh: APA may want our perspective of this.

GeorgeK: informing the a11y community about the wins in EPUB 3.3 I think WAI is explanation / communication of EAA

MURATA: invite the China publishing working group to this meeting. I have his email address.
… , status of SSML?

AvneeshSingh: we will get an update on this.

gpellegrino: Are DPUB roles under APA or not?

AvneeshSingh: Charles will get in touch with James Craig during TPAC.

gpellegrino: I will be also going to TPAC and will help Charles with that meeting with James

AvneeshSingh: they proposed the 13th but we have our own meetings then. 15th of Sept.

AvneeshSingh: 15th sounds like good and in the morning would be best for me and Gregorio.

Feedback for MARC crosswalk.

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

AvneeshSingh: review of MARC, thanks Gautier for your comments.

Madeleine: I have not read through it. Chris is there parts of it which need feedback on? Or do you have a good handle on it.

Chris: EPUB and schema.org metadata could be converted to ONIX and then into MARC21
… , we would need to add subfields to hold a URL ?

gpellegrino: there is a ReSpec issue in the JSON. to fix this so it can be loaded completely. Is there respec for tables as this is a known problem. I don't have knowledge of MARC. for conformance not change to URL we may change it to a simple string. so new epubs

Charles: I don't see URLs being required.

Michelle_: ONIX to MARC who would do this. Libraries wouldnt do this.

Chris: no that would happen upstream. Proquest could do this for example.

gpellegrino: workflow you are expecting would be important to highlight at the beginning of the file.

Charles: Likes this idea

Chris: the last published crosswalk between ONIX and MARC is over a decade old. last one was the previous ONIX standard. We can check to see if they will be updating the crosswalk to the latest version of ONIX.
… , what one thing would identify "Screen Reader Friendly".

<gpellegrino> https://www.w3.org/publishing/a11y/UX-Guide-metadata/techniques/epub-metadata/index.html#screen-reader-friendly

<gpellegrino> https://www.w3.org/publishing/a11y/UX-Guide-metadata/techniques/onix-metadata/index.html#screen-reader-friendly

Madeleine: if you conform to WCAG-A or AA if accessmodeSufficient of textual alone.

Chris: accessModeSufficient of textual would be enough? - Yes.

Madeleine: "Screen Reader Friendly" is a part of our recommendation to how to present this to users.

GeorgeK: OCLC does a crosswalk, do they also provide a transliteration? - No just the documentation
… , is everyone writing their own software to do this?

Hong Cui: We haven't done any ONIX MARC request to OCLC - news release they accept ONIX data, OCLC members can send ONIX we should content them on how they do that.

Michelle_: any collaborative software conversion. There is not. ONIX is considered proprietary format, in any conversion is handled by the publisher. if there is something can be done open source, but would take a lot of publishers to bring their ONIX but would be great if we can do it.

gpellegrino: I am sure we could do something that is not proprietary.

Guidance document for accessibility summary

<AvneeshSingh> https://github.com/w3c/epub-specs/issues/2116

GeorgeK: the issue got raised to the EPUB WG I have only seen +1 to that proposal.

AvneeshSingh: we have given 2 weeks so we can resolve this and close this so accessibilitySummary will be a SHOULD not a MUST anymore. Matt will update the language in the CR.
… , I will add specific action items.

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

GeorgeK: that will trigger a complete rewrite of this document. accessibilitySummary now is only supplementary vs. inclusive as was done in the 1.0. spec.
… , we could do the 18th at this same time. Charles and Gautier can make it. I can do a first crack at this (framework).

Any other business.

AvneeshSingh: lets meet on Aug 25th.