Meeting minutes
Proposal from editors' for refactoring the principles document of User experience guide for accessibility metadata.
https://
https://
gpellegrino: (sharing the screen), it's a draft of the document. We mentionned we'll focus on section 4 where we have metadatas to be displayed. we have one title per category discussed in the spreadsheet. For each group : definition, rational, exemples, link to implementation. These are only placeholders for now...
… in the implementation section there will be link to how to extract informations. Only one exmple is written to see if it works. It is "enable reading withour sight". The draft will be pushed online after this call...
… we changed the wording "screen reader friendly" as non visual reading may be not only thru a screen reader. Currently we focus on the high level structure of the document. Wording will be adressed in a second time.
GeorgeK: should we put english wordings identified to facilitate localizations? We want to make sure other languages can set up a translation based on definition.
Hadrien: we struggle while implementing the previous version of this document. We quickly realize not everyone knows what a screen reader is. This is accessModesufficient: textual, it adresses also TTS. we had persons in schools that made no difference betwween mediaoverlay and TTS. Telling people what it does is more efficient than trying to define the technology.
wendyreid: the user is not thinking about the source, TTS and media overlays are viewed the same, screen reader users know what they need..
JF: interesting discussion because there are many different end users. I see multiple group with different needs.
<wendyreid> gautier: For me screen reader is not just the reading, but it's also navigation, other features. Screen reader will get different information as well
<wendyreid> ... structure is quite good, the sub-headings with the definitions as a question seems to be important
<wendyreid> ... I wonder if the current definition, as a question, is near to the use case
<wendyreid> ... I wonder if we could add definition and use case
wendyreid: definition of TTS, MO, screenreader maybe usefull. This document will also help publisher's understand what they have to inform.
GeorgeK: interesting point, it will help publisher's. In the beginning, we designed it for distribution systems. The scope of this documents is migrating.
CharlesL: primary focus is ditributors, but it is usefull for publisher's and vendors because it allows them to see what will happens when they add a metadata.
gautier: Agree with Charles, yes the focus is distribution, but clearly the publishers can benefit from how it is displayed.
<Madeleine> +1
<Chris> +1
+1
AvneeshSingh: any objections on following this structure? no, ok, let's resolve it. editor's will go forward and we'll have nice discussions about wording.
<GeorgeK> +1
Next call on May 25.
+1
Chris: briefly, we at editeur are working on the codelist and wording (196 but also other related codelists). not exactly a 1 to 1 mapping with schema but we are looking to a clearer mapping. I will share as soon as I have something sufficient.