– DRAFT –
(MEETING TITLE)

principles document of User experience guide for accessibility metadata is restructured.

AvneeshSingh: first agenda item: the restructuring piece
… we started this work on the document on the "Key information" section
… now that this section is pretty stable, we moved to organize the rest of the document

<AvneeshSingh> https://w3c.github.io/publ-a11y/UX-Guide-Metadata/draft/principles/?updated

AvneeshSingh: in this new version we're removing the prioritization of metadata, since it's up to the retailer to decide what to display first
… the general information and introduction is the old one, the "key information" section was renamed "key accessibility information"
… me moved "Discovering accessible content" after key information

<Bill_Kasdorf> This is looking great!

AvneeshSingh: then we have "Localization" and "Implementations" where we'll list different implementations (VitalSource and Fondazione LIA are ready, maybe also someone from France)

George: what about the importance of different key informations?

AvneeshSingh: I would leave defining the order of key information to implementers

CharlesL: maybe we can use a bullet list, so we don't define an order, but just listing

AvneeshSingh: any feedback?

Bill_Kasdorf: we may explicit that there may be different orders for information based on different use cases
… it's difficult to make comments on order because you highlight something and "hide" something else

AvneeshSingh: if there is no objection, then let's move on!

What to display in case of absence of metadata · Issue #184

AvneeshSingh: new topic: what to display when we don't have metadata from the epub creator

<AvneeshSingh> w3c/publ-a11y#184

CharlesL: when publisher omit something in the metadata, it doesn't mean it doesn't exist
… for example hazards
… or like alt-text may mean that we don't have or these are not provided
… or conformance

<Bill_Kasdorf> I like James

<Bill_Kasdorf> . . . James's suggestion: say "Not reported

AvneeshSingh: during editors call we identified three information that should be displayed even if missing: Supports nonvisual reading, Visual adjustments, Conformance
… we would like to have feedback from the group

Naomi: I think we had discussion on this
… doing a lot of remediation semi-automatically it is difficult to say something that requires human check
… to the absence of metadata should be clarified, because in some cases some feature may be present, but not listed in metadata

CharlesL: I would use Accessibility Summary for telling this

JonasLillqvist: I would ask about Visual Adjustments: what is the metadata behind it?

<gautier> Visual adjustments is display transformability yes.

gpellegrino: displayTransformability, if we have this, this means the content can change to user preferences, ONIX latest there is way to express this with a code in ONIX (I can't recall right now).

JonasLillqvist: displayTransormability can be difficult to understand.

JonasLillqvist: yes, sometimes displaytransformability is used to divide reflowable from fixed layout

<Naomi> This is the a11y-discov-vocab ticket I was referring to: w3c/a11y-discov-vocab#74

Bill: how broadly are you considering displayTransformability?

gpellegrino: There are different levels, we check against WCAG for reflow, enlarging text, we check that. There are some publishers who put this in al reflow EPUBs. 95% reflowable EPUBs can adjust font size etc.

Bill: publishers may just automaticly choose displayTransformability. since the Reading Systems can do this.

gpellegrino: could have a reflowable EPUB but could be still problematic.

CharlesL: we didn't update the techniques document, there will be updated links to tell the metadata behind this key information
… in our program we check that metadata reflects the content
… to be sure that is not used in not correct manner

George: we should make sure that is the textual content that will be transformed

JonasLillqvist: I just looked at the DAISY Knowledge Base, to check what are their requirements for displaytrasformability: not image of text, proportionate units of measures
… I think the "images of text" is too strong as requirement

CharlesL: It's true that infographics or images of tables are difficult to manage in live text, so we require to have an alt-text and an extended description
… I think that with these mitigations you can claim that displaytrasformability is true

mgarrish: I think this is a long discussion, I posted a link to a PR trying to work on this
… not sure if alt-text can be a mitigation
… we need further discussion

AvneeshSingh: If we have an agreement on how to evaluate displaytransformability
… then we may has displaytransformability displayed even if not present?
… ok let's update the guidance

AvneeshSingh: do you want other metadata group to be in the "display even with no metadata" group?

CharlesL: I think navigation may also be important
… expecially for textbooks

gautier: I think it is about the audience, if I'm in a scholar context Navigation is important
… in fiction this is less important
… same in academic: pagelist is important
… but I also know that a lot of books do have TOC
… so maybe we can recomend to display something about navigation even if no metadata is present

Naomi: Same as Gauthier, but with the example about "Math and Charts"

AvneeshSingh: I think "Conformance" is really important, the other information is more contextual

Any other business

AvneeshSingh: so we agree to have three information to display always (telling that are missing, if no metadata is present): "Supports nonvisual reading", "Visual adjustments", "Conformance"

George: the issue about certification, we had feedback about "self-certified"
… so I updated the section according to this, I think this simplify the conformance section
… we leave to the user to "check" the certifier

I would say that at the Frankfurt Book Fair there are two events about metadata and accessibility

Supply Chain Seminar from EditEUR (next Tueasday), and accessibility round table (on wednesday)