– DRAFT –
(MEETING TITLE)

Chris: Editeur ONIX editor.

Jonas: CELA new hire

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

AvneeshSingh: Gregorio added a number of issues

gpellegrino: trying to group a11y metadata into a few categories.

<AvneeshSingh> https://docs.google.com/spreadsheets/d/1rUCXkVE0bFeXf0hJvyPkKkIBeBHIGPYUFWKrQqLJHl8/edit?usp=sharing

gpellegrino: , a11y metadata is a lot more extended outside of a11y itself, so trying to group all the values about 7 categories. some specific values where they should exist. We have github issues for those and naming of these groups. Or combining of groups if agreed.
… , first issue is #145 accessModeSufficent= visual is relevant to EPUBs

w3c/publ-a11y#145
… , number of comments have discussed this in the github issue. accessModeSufficient of visual could not be accessible in other ways. if only visual.

Madeleine: important what books should have vs. what valuable for libraries / bookstores to display.
… , see Charles's last comment in the issue for searching.

<JF> +1 to Gregorio

gpellegrino: blind users will filter out all books of not having "textual"

Naomi: problem saying anything that has a lot of pictures is a picture books. could be old terrible books that had all images of text say in a cookbook that is made up of just images.

gpellegrino: looking for grouping say we use this metadata in reading mode. WIll this mean a readingMode "visual"? current we have readingMode, textual, audio, and visual adjustment. could we add it to visual adjustments?

Charles: I think visual adjustments makes the most sense.

gpellegrino: I agree

<AvneeshSingh> proposed: move accessmodesufficient= visual to readingmode:visual adjustments

<gpellegrino> +1

+1

<wendyreid> +1

<MiiaK> +1

<JF> +1

<AvneeshSingh> resolved

w3c/publ-a11y#146

gpellegrino: madeleine HCD means content meets WCAG 1.4.6
… , contrast minimum and enhanced this is highest level AAA contrast used in special publications made for low vision users.

<Zakim> JF, you wanted to note there are 3 color contrast SC - 2 related to text (AA & AAA) and 1 for non-text element

gpellegrino: , since we have this assumption we move this accessibility feature move to Reading Mode Visual, or in the book features where we collect a lot of a11y features

JF: there are 3 color contrast issues, text contrast the is non-text contrast for visuals.
… , not sure where that fits into this discussion.

<gpellegrino> https://www.w3.org/2021/a11y-discov-vocab/latest/#highContrastDisplay

gpellegrino: this refers to only text contrast and images of text 1.4.6

JF: the WCAG WG they ack a gap. We need to note we have high contrast book without that distinction.

Madeleine: you are right John, but we can't change the definition of the meaning of HighColorContrast metadata

AvneeshSingh: Yes we can add this point for future additions to metadata to handle this new WCAG criteria that John has discussed.

gpellegrino: maybe the name of the category isn't the best, but an end user content is visually adjustable. is a basic feature of reflowable EPUBs. Is info is relevant to most users in reflow-able epubs and not in fixed layout epubs. Could be content itself to the book feature instead.

<Madeleine> +1

Charles: I agree with that. its a book feature not a visual adjustment

<AvneeshSingh> proposed: move high contrast metadata to book feature

<wendyreid> +1

+1

<jamesY_> +1

<MiiaK> +1

<AvneeshSingh> resolved

w3c/publ-a11y#147

gpellegrino: useOfColor thanks to Madeleine two similar metadata which means similar but opposite

From Madeleine's github comment: the ONIX term means "don't worry, there is an alternative to use of color" whereas Schema/W3C has the term "colorDependent" as a part of the accessMode vocabulary with the definition "Indicates that the resource contains information encoded such that color perception is necessary." If images are accompanied by alternative text, that may remove the barrier.
… , where to put this metadata in our groups. currently under visual adjustments, but maybe we should move it to book features.
… , this is a WCAG AA requirement.

<AvneeshSingh> proposed: use of color metadata under book features

+1

<jonas> +1

<MiiaK> +1

<gpellegrino> +1

<Madeleine> +1

<jamesY_> +1

<AvneeshSingh> resolved

w3c/publ-a11y#148

gpellegrino: "Reading Mode: Audio" and "Reading Mode: Non visual" should we merge them.

AvneeshSingh: Syntetic speech vs. human narrated audio

JF: I would argue against merging them, what about Braille Output.
… , tactile reading mode.

gpellegrino: non-visual reading mode jumping from 1 heading to another, the audio is more beginning to end,

AvneeshSingh: maybe its the name that is a problem.

Madeleine: Non-Visual seems like not a lot of users would understand. Audio everyone would understand. we need to make book providers are already making those types of books easier to find.

<JF> +1 to Gregorio

gpellegrino: audio may also means media overlays in EPUB,

JF: could we call it "Reading mode - Pre Recorded"?
… , non-tech people know what we are talking about.

AvneeshSingh: Media Overlays?

JF: well those overlays would be pre-recorded right?

gpellegrino: Yes, but could be done with deep learning voices apple / google is pre-recorded is right word. what about a different word for non-visual.

wendyreid: challenges here straying into reading systems. non visual reading via reading system with TTS.
… , if a RS has these features could have a audio based reading modality when a reading system offers this even if the EPUB itself didn't provide this.
… , auto-generated from AI audio books.

AvneeshSingh: non-visual needs to be replaced then we can decide what fits.
… , lets discuss this online in github / a future call.

w3c/publ-a11y#149

accessibilityFeature = bookmarks
… , Madeleine identified - This feature was included in Schema.org for describing reading systems, not books.
… , different interpretations of this metadata
… , bookmarks to key points as was defined in PDFs
… , do we leave it in book features or navigation section, since its in the navigation for PDFs, but since its deprecated in W3C defitions

gpellegrino: if its used in interactiv TOC in PDF then this is critical as TOC in EPUBs so important. Since PDF's don't include a11y metadata then I suggest keeping it out of the grouping, we didn't mention this since its depricated.

<Madeleine> +1

<AvneeshSingh> proposed: keep bookmarks metadata out of the guide, while providing explanation.

+1

<jamesY_> +1

<wendyreid> +1

<jonas> +1

<MiiaK> +1

<gpellegrino> +1

<AvneeshSingh> resolved

w3c/publ-a11y#150

accessibilityFeature = none

gpellegrino: does this makes sense to include? do we group it in conformance section. From Madeleine - This term was added to support the ability to make accessibiltyFeature mandatory. If a book is not accessible, we might still have hazard or accessMode info available. accessibilityFeature needed to be able to have a value for those cases.
… , does it makes sense to have in conformance section even though there wouldn't be any conformance statement

AvneeshSingh: Yes we should keep it.

gpellegrino: do we group it in conformance or some other place.

Madeleine: I think conformance is a good spot. people looking a features wouldn't be looking there for none

MiiaK: I was going to say what Madeleine.

gpellegrino: maybe when there is no conformance and a11y feature of none then we can say that it does not conform, not that we don't know if conformance is missing.

Madeleine: I am comfortable leaving this under Conformance. we could recommend where there a conflicts based on the metadata present if we get to that.

wendyreid: looking at case : person who did the metadata that accessibility features are "unknown" odd book with 0 features could even exist.

Charles: there is a11y feature of "unknown"

gpellegrino: we should mention how to handle conflicting metadata. what happens if we have differences in schema / ONIX section on conflicts.

MiiaK: from EU Act smaller countries will be publishers who don't have to follow these regulations they won't know if they conform or not.

AvneeshSingh: Wendy would it harm keeping this "none" under conformance.

wendyreid: could be confusing "Features = none"

AvneeshSingh: ONIX has a code for inaccessible

Charles: isn't inaccessible for onix same as "none" and no conformance statement

wendyreid: I wonder if on schema side there won't be a case with "none" or there is some bigger issue here.
… , if anything is missing it become inaccessible.

AvneeshSingh: take this issue to github.