Meeting minutes
Github issues
1.1.1 Non-text Content
<JJ> quintin: consider other dimensions of non-text content such as haptic feedback
quintin: Just trying to help people think that mobile introduces new concepts like haptics
I suppose something like haptics falls under the "multiple means"
Julian: Emojis + Custom emojis: Would we want to offer guidance from a linguistic perspective?
Quintin: Because intention is often the key communication, and I would argue to allow people to provide their own meaning in context
Julian: It's about surrounding context
Julian: Another thing is how to integrate emoji into body content - e.g. using them as bullet points
Detlev: Around context specific: Normally surrounding context is self-providing. I imagine an emoji would be better if there was a prescriptive word
That's what I live about :thumbs-up: for example - it's very well self described and non emotive
like not live
Joe: In terms of providing guidance - it should be separate from the main guidance
Agree
<Aashutosh> great idea Joe_Humbert
We should also be careful about letting "hot topics" take control
1.2.1 Audio-only and Video-only (Prerecorded)
Quintin: Is an external link along with the content sufficient? Can we include definitions of transcripts and captions? Do captions need to identify speakers and significant sounds?
<Joe_Humbert> Would the definitions be good updates for the larger AG in general?
Quintin: We should focus on the goal
Detlev: What are the different options? What is an author issue?
Quintin: We should mention to respect the OS user settings
JJ: Nothing changes, perhaps add some best practices
1.2.2 - Captions (Prerecorded)
JJ: Already partially discussed
JJ: Is there a difference or difference in guidance from the Web 1.2.2?
JJ: Mostly on Web captions are not being picked up
Detlev: Players not picking up captions: Is this an app or browsing context?
<JJ> Quitin: Native players provided out-of-the-box on Android/iOS
<JJ> Detlev: so it's mostly guidance for the videoplayer creators vs developers
Agree
JJ: Perhaps provide guidance to facilitate understanding
1.2.3 - Audio Description or Media Alternative (Prerecorded)
<AlainVagner> you can open agendum <number>
JJ: Any additional understanding on 1.2.4?
Aashutosh: They need to be visible
Quintin: Highlight OS settings should be respected re: size and colours of caption font and background
Quintin: Usually vendors specify the position of captions
JJ: Add this to the application part or recommendations
Alain: EN has extra criteria (7.1.4) and 11.7
Alain: Outside of WCAG to support customization
<AlainVagner> EN 301 549 7.1.4 https://
Detlev: It could be trickier in mobile as there is less space for controls, etc.
JJ: How do we deal with open captions regarding guidance?
Detlev: They are a "get out of jail free" card as you can't change them post processing
JJ: Do open captions comply?
Detlev: It's not ideal, but it's something that could "get past" requirements
Quintin: If someone is using a braille display, open captions won't be helpful
<Audrey> the EN also has a criteria for that : 7.1.5 Spoken subtitles, really interesting for that use case.