Meeting minutes
<ChrisOttawa> p+
Updated Guidance document for accessibility summary
<AvneeshSingh> https://
George: looking at the preview, we covered most initial items, go down to A11y Features, should we just delete this whole section?
… , change in the WG with Accessibility 1.1 we changed the accessibiltySummary from a MUST to a SHOULD.
… , based on the schema.org guidance supplementary, whatever the regular metadata does not cover now can go into the summary. We don't want to repeat information.
Charles: alternativeText we could include who wrote the accessibility summary.
<Bill_Kasdorf> I can't get on Zoom. I think I have an outdated link. I can't access .ics files; I need the actual link.
<MadeleineRothberg> https://
Avneesh: putting in the list of accessibilityFeatures, unless it requires some additional information.
<Bill_Kasdorf> Thanks, Madeleine!
Naomi: you may want to provide an example for the reader.
Chris: would be useful to have examples of what one might put there. Lets not loose these examples. They are valuable.
Matt: We shouldn't be stating production techniques, if there is a concern, if it is done by AI / crowd soured. I don"t think we don't want to get into the production side. things that we are not 100% sure of.
MadeleineRothberg: in keeping with new ethos with a11y summary. These examples were written when we were repeating information. these are just definitions, the only value would be to point out. like longDescriptions you could say that some have long descriptions but others may not. Not sure if we need feature by feature examples.
Bill_Kasdorf: I think this should be a accessibilityNote not Summary.
Avneesh: that would be a schema.org change much larger issue.
Matt: remember this is tailored for EPUB but is still valid on the web in general.
Bill: we could say in pros that this is meant to be used as an Accessibility Note and not a complete Summary of all the accessibility features within this EPUB.
George: Keep the Table and put in some examples with alternative text "This material was auto generated and may have errors" longDescription "This book contains long descriptions of importance to aid in the understanding of the content.
Naomi: Heading Structure could be affected due to the author's request to match the Print book. If someone went above and beyond. could point this out. "most of the images have well defined alternative text, but the images in some of the Notes may not have descriptions".
George: Hazards, we can just delete the table and include the summary.
<MadeleineRothberg> +1 to charles on detail of where the hazard is
Charles: I think we need to include this to tell the reader of additional detail of where this hazard occurs in the book. Eg: "If there is a motionHazard, and point out where this occurs in the Book"
Naomi: I think we need this to remain a SHOULD. as an EPUB publisher, for back titles we might not know where the hazard is, because that information may not be available and would require research to figure out again.
GeorgeK: I hope to have these two sections by the 22 since we have TPAC next week. Only thing remaining would be examples. If anyone can write up some examples you can do it yourself or send them to me.
Further Feedback for MARC crosswalk.
<AvneeshSingh> https://
GeorgeK: , I will work on getting what we discussed today implement by the 22nd.
AvneeshSingh: Any comments on the Crosswalk?
ChrisOttawa: I have not received any feedback.
… , The Libraries took a break for the Summer but will start meeting again next week.
… , MARC21 is an encoding standard but it alone does not reflect the structure of the data.
… , as a way to make a11y metadata forward look at make that data element more granular. wether there are other librarian colleagues to help with this effort.
Hong: I did contact some national libraries but they have not sent any feedback yet, but would be very supportive to the additional changes to MARC for accessibility.
APA + Publishing community joint meeting organized on Thursday, September 15, at 15 UTC
AvneeshSingh: This sounds good, and are looking forward to any future developments you may have.
<AvneeshSingh> https://
AvneeshSingh: , this is the agenda for the TPAC APA / Publishing WG/CG
GeorgeK: in our discussions over the past few weeks, people have pointed out that this is a really good point that we are removing and should move to the User Experience Guides. I have these as branches where we can go grab those texts and add them to the guide.
AvneeshSingh: We don't need the accessibilitySummary to be complete but we can work on these in parallel.
Naomi: I will create a GitHub Issue, about print page numbering and where those should fall in the text in a nonlinear book. Complex data structure and where the page mark should go. I will write up some examples where there can be a couple pages out of sync potentially.
George: could be a great example for the accessibilitySummary.
Bill_Kasdorf: Naomi, are you to physical page break markers should map to the print page.
Naomi: you may have a side bar and the main document on the print page, but in the digital version we may move that sidebar down the page where it makes more sense for the digital experience.. There may be print constrains and we may move the image to a different page.
… , I need to sit down a write out these examples.
… , what level of accuracy is needed. Which is more important good digital experience or keep the page fidelity of the print edition.
George: citations could get interesting.
gautier: Citation people in academics to paragraphs not to pages but is an experiment, but there is a lot of work happening on page reference. We will have to maintain two different ways to thinking.
… , If we make it in a different way for the digital format. I have seen the MSWord page numbers, but has nothing to do with the printed page reference which is a big problem for scholars and from a RS point of view, in Thorium we have a "WhereAmI" feature and we figured out with a SR we can't determin where the SR is really located at. We get a force page number, you think you are at page 3 but may be at page 4, and where the SR ma
y be at different place.
Bill_Kasdorf: in some sectors of publishing "Reference & Legal" publishing and citations are very granular. However there usually is no print. We do have a locators TF at work so this may eventually get addressed.
AvneeshSingh: Looking forward to see the use cases on the issue tracker.
… , safe travels and see you all on the 22nd.