Meeting minutes
Further updates to the principles document:
AvneeshSingh: Lot of work with Principle's and techniques documents
<AvneeshSingh> https://
George: We have reordered the main items to be: Visual Adjustments, Support for Non Visual reading followed by the Conformance. those are recommended to always be shown. the rest in the order they are in.
… next up : how to present the Hazard information. since there is an additional "unknown" if the publisher doesn't know if there are any hazards or not vs. the metadata is missing which also implies unknown hazards. Is there a difference? Thoughts welcome.
… also improved the introduction which shows the workflow which Charles helped with the details describing the image.
Bill_Kasdorf: one difficulty lack of understanding of what hazards are.
… by the content creator, it is subjective
George: not well defined in the W3C. no decibel values for sounds etc.
Bill_Kasdorf: which prompts for "unknown."
Charles: is there a real difference with "unknown" or missing?
naomi: you can say you don't know about any hazards. the media content exists, if the book has audio content but doesn't have any visual hazards, but can't say about the audio.
… does not have those media hazards. they can leave the other two blank.
… if any one is missing it is unknown. would behave the same as if its missing from a user perspective.
Madeleine: when we defined the hazards list there were certain sounds but not well defined user subjective. motion hazards if any rapid scene that would be a hazards any rapid motion.
Charles: we don't have specific unknown hazards for sound, visual etc. so unknown and missing are really the same.
AvneeshSingh: if its unknown or no metadata is the same for the displaying it point of view.
Bill_Kasdorf: I appreciate what Naomi and Madeiline has to say. Maybe we should add those 3 unknown hazards would be useful.
George: you can always add the specifics to the accessibilitySummary. If everything is unknown but individually you could state that.
AvneeshSingh: we don't have individual hazards for unknown, but should we do it, but for now focus on the display. We don't have a good way to specifying hazards since it is very subjective.
Madeleine: the goal of this document advise how to display this metadata. do we have a document how to write this metadata.
AvneeshSingh: we will treat unknown and missing as the same for now.
Matt: we already have those 3 metadata for unknown Sound, motionSimulation, and flashing hazards.
Madeleine: we should add an example based on what Naomi has stated about author having only audio but not sure if it has any hazard or not.
Charles: reviewed the 1.1 Publisher metadata ecosystem https://
Review of in-progress techniques documents.
AvneeshSingh: any thoughts? No k.
Madeleine: I did add a new issue for the principles document.
Principles document examples for nonvisual reading w3c/
Madeleine: detailed example had 4 sentences, and compact version had 3, and I think items may be swapped.
charles: https://
Charles: recapped Hazards and Visual Adjustments.
George: we revised the text for Appearance modifiable not known.
AvneeshSingh: we can discuss with the editors about unknown vs. missing hazards.
George: in techniques we always use the compact language should we also use the detailed version? do we need both in the principals? or in the Techniques?
Charles: we should ask Rick who isn't here.
Issue #237: PDF crosswalk and techniques
<AvneeshSingh> w3c/
Charles: reviewed the github issue.
AvneeshSingh: will PDF use the schema.org accessibility metadata. would reduce the need crosswalk, would be simpler.
… I will comment in the github issue.
… ONIX side for PDF as well.
Communication and promotion of the User experience guide.
George: I brought this to the BISG and had DAISY people join their a11y metadata group. to get that in front of them.
… we can talk about how to promote this as we move forward. I think folks need to know about it now even though its not finalized yet.
AvneeshSingh: principles are really good but many would benefit from seeing this even in this editor state.
… next meeting 28'th of March