– DRAFT –
(MEETING TITLE)

AS: Introductions of new members

HB: introduces himself (welcome!)

Feedback for Accessibility Summary authoring guidelines.

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

AS: this document has been under review for couple of months, have some feedback

<AvneeshSingh> w3c/publ-a11y#152

GP: reviewed doc, added some comments

Summary name is a bit misleading

perhaps start with an intro of what the purpose is, then "the story" (history) of why this was made optional

idea is this is for other info that cannot be described with existing metadata

GK: should we make that change then?

<AvneeshSingh> w3c/publ-a11y#153

[agreement]

GK: will get to that

GP: suggests that the tables for accessibility summary are good, but --- machine readable data: suggest changing first column with some questions to aid content creator

for example: can you be sure you meet WCAG AA? or "Does the publication include an index?" and then follow on questions

another example: distinction of type of math content (MathML vs LaTeX)

comment: there is some redundancy in current draft

GK: all of these may have machine-readable metadata, but the idea here is if that data needs enhancing

GK: if a book has *1* MathML example, then the metadata would confirm that, but we would then be able to qualify that there is only one (or minimal) MathML

GP: agree, but what is put in the summary is not what is in the metadata, but in the content

for non-expert implementers, they may see a mapping and get confused (?)

CL: this is going to be difficult. In GK's example, if there is only 1 math equation in the book, then fine, but if there are multiple maths as images, then we need to tease that out further

CL: understands GP's direction, but this means there will be a lot of questions. i.e. "Do yo uhave "limited" math equations?

This will be unwieldly for publishers

another example: does not fully pass WCAG AA - one image is not comformant... then what?

JF: if we introduce questions, we need to qualify those questions (eg: "Limited" = how many?)

GP: eg: tables are provided as images,with full text provided in <details> - do we add this type of info

CL: response to JF - don't want to be defining Limited,but rather some use 1 technique, others use another

<Bill_Kasdorf> +1 to Charles--it's not about a number, it's about whether there are inaccessible equations, tables, etc.

GK: approach was to associate the nuance statements with a specific metadata entry

<gpellegrino> +1 for me

GK: brainstorming... what if we scrap associating this with other machine readable MD, and instead provide categories of nuanced explanation

we list those as general areas of book structure

and completely revise the table

+!

<Bill_Kasdorf> +1

Charles: I like the idea of broad topics, we can have sections on Math, Images, Tables, Language etc. then specific questions in there.
… GCA publishers will use this document on how to write a11y summary as soon as its ready.

JF: +1 George's idea a guided tour on how to write this.
… focus on problem areas, "have you declared this as metadata" do you want to add more about it.
… consistency is important as well.
… huge +1 on guided tour on how to write the summary

<AvneeshSingh> proposed: finalize current structure and release Accessibility Summary document, and in parallel start work on restructuring

George: I can get the first part updated quickly the abstract can be updated in the next couple days. then we can look at making changes after that. will take a while and consensus, we could change table head for guided tour approach.

<Zakim> JF, you wanted to ask if we could start with a basic template of those high-level sections

JF: basic template shows those levels and publish that. giving folks a framework early would be helpful
… table with 5 rows topic statement would be useful starting point

<GeorgeK_> +1

AvneeshSingh: vote on the proposal

+1

<Jonas> +1

+1

<jamesY_> +1

<gpellegrino> +1

<Bill_Kasdorf> +1

<gautier> +1

<AvneeshSingh> resolved

<MiiaK> +1

<AvneeshSingh> w3c/publ-a11y#154

gpellegrino: multiple documents… we may want to be part of the techniques or some index.

AvneeshSingh: lets bring this up in the WG maintenance group

Presentation from Hans Beerens from Dedicon for displaying accessibility metadata.

Hans: Demo on metadata
… from Dedicon Netherlands
… Introducing Accessibility Metadata - research user values, introducing and using metadata
… Dutch Royal Library
… Jun 22 - Mar 23
… mock catalogue made, conducted interviews/ discussions, international developments, workflow
… functional catalogue, ebooks audio books, recreational reading EPUB3/2 pdf mp3 daisy wav. displayed all metadata
… schema and ONIX. many a11y search filters
… objective evaluate a11y metadata, 1 blind, 2 low vision, 2 dyslexic, 2 no reading impairments
… given tasks, with participants speaking their though process. at home using their own AT
… Findings: most claimed no value metadata was useful. most irrelevant. Not inclined to use filters to find books.
… most didn't understand most metadata but did acknowledge some would be useful.
… either a book is a11y or not.
… some assumed that books would be 100 accessible. assumed you can change contrast. a11y features are for VI users only, some had inaccessible experiences in past ie. no TOC etc.
… Readability for dyslexic users clarification.
… introducing a11y metadata into the supply chain.
… recommendations: introduce human readable metadata
… machine readable metadata should also have equal focus to introduce this to new users to support the learning curve the adoption and prevent mistakes when adding metadata.
… make a11y metadata accessible
… explanation of concepts and importance. helpdesk / kb or workshops.
… different reading purposes, recreation, school study, etc.
… different levels of complexity simple / mod / complex
… different libraries have different audiences and may required different ways to display UI/UX follow international guidelines on display.
… showcase mockups samples design options. emphasize business case.
… how how to present a11y metadata, and update over-time
… share knowledge and collaborate

AvneeshSingh: There are so many people with disabilities only use specialized libraries, would be great to have these use public libraries

JF: recommendations slide - provide a human readable summary of the features in the book, the summary shouldn't echo the machine readable data. are we heading in the wrong direction.

Hans: no, we should focus on the Machine Readable data, its not about A11y Summary, people should be able to use and understand the useful a11y metadata to discover accessible books.

JF: so the Machine Readable metadata should be presented in a human readable form?

<gpellegrino> this is what we're woking on in the UX guide :)

Hans: people need to understand what this metadata means, and focus on the communication of the metadata and what it implys and allow systems to communicate

<Bill_Kasdorf> So this is where our User Experience Guide comes in, correct?

JF: so you "library tool" it would fall on at to present in a human readable format.

George: accessModeSufficient = textual translated to "Screen Reader Friendly" but will be translated into another visual indicator or other appropriate language which makes sense for that audience.

Hans: end users need to know what to expect

JF: different tools may export it to the users, but translated the Machine Readable metadata into a Human Readable / understandable way

gpellegrino: we need to find a way in the User Experience Guide to make this mapping.

AvneeshSingh: will send Hans the invite for the User Guide work, and Hans will attempt when time permits to attend that group.

Bill_Kasdorf: Do have any insights on Educational Reading?

Hans: Recreational reading was chosen due to funding. Scientific reading could have more a11y challenges. I

Discussion on grouping of the relevant accessibility metadata for user experience guide for accessibility metadata.

<AvneeshSingh> w3c/publ-a11y#148

Daylight saving time adjustment in terms of UTC from next call.

AvneeshSingh: US will be DLS time, and will be 1 hour earlier. Meeting on 23rd, same time in the USA, but time might be different in other parts of the world.

GeorgeK: on 23rd should try to get as much done on the Summary. should I try to do both abstract and work on the table header / associated with metadata.

Hadrien having mic issues, and asks: I don't have an invite for the 23rd

AvneeshSingh: I may not be able to make the 23rd and I will inform the group in advance.
… I will send out the invite due to DLS time