Meeting minutes
Further editorial changes done in the principles document of User experience guide for accessibility metadata. (For information purpose) AvneeshSingh]
<AvneeshSingh> https://
AvneeshSingh: Editorial changes to principles Doc. Charles added some editorial improvements in a PR.
… any other issues please open an issue.
Chris: there is a closed group, ask permission to post a draft.
Approach for techniques documents and localization.
AvneeshSingh: Comments are welcome.
<AvneeshSingh> w3c/
AvneeshSingh: Next Localization
<AvneeshSingh> w3c/
AvneeshSingh: , for techniques pseudo code vs. descriptive plain english on decision tree.
… , Gregorio has put in a pull request.
… , we could also do XSLT
AvneeshSingh: , this could help technical people potentially.
… , Localization piece. workflow is English Text in descriptive text. so when retailers can use these descriptive sentences. the localization should use these descriptive text. We don't want other languages to use a language translation as the base, it should always use English first. ie. English - French, English - Italian. NOT French - Italian.
… , we want to be able to also who did the localization, so end users can decide to "trust" that translation.
… , v1 well defined english terms and the localization of these terms. But in this version we are providing descriptive text.
… , coming up with a huge list with all permutations is not feasible.
… , using a non-exhaustive text as examples.
… , this also means a high dependence on the techniques.
… , this is the overall plan.
George: we want to identify in this repo template who has submitted the work, description of how it was developed, governmental group, or whatever process, the language that is used and expect each entry would get an ID to be referenced. so when they produce their Italian version and LIA worked say with 10 people, and it is in Italian, and the ID of that Entry in English Version produced.
… , always has an ID that can be referenced.
… , any thumbs up?
Charles +1
<JonasLillqvist> +1
<Miiak> +1
We are converging on the approach for Search and filtering.
<AvneeshSingh> w3c/
AvneeshSingh: filtering and discovery
… , from Rick Johnson.
… , Recommending two sets min. metadata req. and extended metadata. min metadata for all users / distributors. the extended for other groups.
… , supports visual adjustments, non visual reading. the extended set support for mathml, extended descriptions etc.
… , the minimum and extended set of metadata please vote
<JonasLillqvist> +1
<Miiak> +1
<AvneeshSingh> Good approved.
AvneeshSingh: , the extended metadata for filtering / searching that a distributor would be able to filter on and present metadata they want for their specific user base.
RESOLUTION: Using the Minimum / Extended Metadata for Filtering
gautierchomel: Minimum set - 3 metadata (discovery of any accessibility metadata provided. one search option any title with accessibility metadata. main information ways to read: search titles non-visual reading, and visual adjustment. Any title with a11y metadata, nonvisual and visual adjustments are the 3 main metadata set.
AvneeshSingh: What about Conformance be added?
gautierchomel: this is currently in the extended set. this can become manditory depending on the regional requirements.
George: is conformance going to be required for EAA?
gautierchomel: from French authorities, currently just require the accessibility metadata
George: any implementer can always display / filter on any of the metadata.
gautierchomel: there can be 50/60 items to search by, but if we just elements about minimizing other facets. we want to have a min set that should be implemented everywhere.
Charles: wasn't there a requirement for 3rd party certification for conformance?
gautierchomel: not to my knowledge, the legalization can always change so its not up to us.
AvneeshSingh: there is CMARK for the products, and EPUBs are in the services.
… , maybe Gregorio can send out an email to us if this is not the case.
JonasLillqvist: discovery of all titles with accessibility metadata, what about accessibilityFeature "unknown" or "none"
AvneeshSingh: We can add a note to this.
Hadrien: for this filtering capability if we push for more a11y metadata there is a lot of volume with TOC, pageNavigation. There may be 1/2 of this in a very large number of books, does this defeat the goal of this? is it useful if we know if a publication has a TOC and that is all?
AvneeshSingh: Good question, any thoughts?
George: I know Internet Archive only has 1 entry with a TOC
Hadrien: OVER 90% have a TOC.
… , TOC 92% actual numbers, Print Pagination 15%
… , lot of books with just those two and nothing else.
George: when a11y metadata is unknown that there is only TOC for accessibility that a11y metadata is absent?
gautierchomel: not a lot of folks will document unknown or none. but through inferences we could get minimum set, but should that be displayed? We don't have the ability to say documented vs. inferred. could get it from ONIX few publishers are not capable, could extract the metadata from the OPF or inferred by looking inside the book.
AvneeshSingh: Inferred is out of scope.
gautierchomel: we must address this in the future. this document is not only for Europe.
… , EAA this will increase these facets as accessibility metadata will be required in 1-3 years this will grow due to the new legislation. It will be great when we need to revisit this since all the books in Europe have this metadata.
Hadrien: aside from what the filter returns what is missing is expression of the need.
… , ex. I need publication which supports non-visual reading or enlarge the font size.
… , the need for any accessibility at all -expression of need, maybe smaller subset.
JonasLillqvist: I think Hadrien has a point. but only the min set of 3 that are displayed I am not sure it will be useful to find / filter on the first facet.
Charles: used in conjunction with other filters to reduce the list size.
gautierchomel: I understand this better now.
<AvneeshSingh> proposed: minimum set of accessibility metadata should include Titles that support non visual reading and Titles that support visual adjustments.
gautierchomel: , stick with 2 minium facets and add a note about accessibility metadata include it with which context may be intersting.
<JonasLillqvist> +1
AvneeshSingh: please vote on this proposal
<Hadrien> +1
+1
<Miiak> +1
<AvneeshSingh> resolved
+1 George
gautierchomel: Discovery of a title where very view titles have any accessibility metadata to find them. we hope that vast majority with accessibility metadata it won't be very useful.
… , could result in a false positive.
… , complex to achieve you can't say any ONIX 196 code is present then we assume we have accessibility metadata. I am pretty sure achieve a facet to view 40 + metadata properties.
AvneeshSingh: we will bring this to the editors call.
Hadrien: In our case, accessmode Sufficient for auditory the entire text is pre-recorded audio. this is interesting there is a very large group of users where this would be very useful.
… , having entire publication as audio.
AvneeshSingh: the decision here is not carved in stone, we can revisit any of this in the future. I like your point it is very important.
… , prerecorded is a very strong use-case is this for all parts of the world or not is the question. we can revisit.
Extended set of metadata. main 4-5 examples for different kinds of user segments.
… , we can do this in an incremental way.
… , a continuous process.
AvneeshSingh: Any objections?
RESOLVED
AvneeshSingh: Any other business?
Any other business.
George: Acknowledgments are incomplete. I suggest, multiple people,
<AvneeshSingh> kerscher@montana.com
Folks can send your names for Acknowledgments.
… to George
AvneeshSingh: Thanks everyone and Happy Holidays.