Meeting minutes
Use of the term "landmark"
Daniel: "Landmarks" was confusing. It means different things for different people. Proposal:
… visual aspects included in Module 1: "Visual Design" -> Topic: "Cues" -- No use of "landmark", instead "cues" and "headings" to define page regions
https://
Daniel: It was a bit confusing for some people. Visual aspects are included in Module 1 but are referred as “cues”…
… people agree with the proposal on visual design or is here something missing?
David: Proposal makes sense to distinguish problematic features.
Gerhard: I am ok.
Estella: +1
Daniel: We do plan to have a discussion on this subject on EO this Friday.
… I will present this on Friday together with other issues.
General agreement to avoid landmarks on visual design to avoid confusions.
Scope of media player design.
Daniel: The suggestion was to revise this to make designers aware, look for accessible players and propose their own if not found.
Daniel: The proposal is to first raise awareness, second choose existing media player, third if you are designing your own you have to follow the guidelines
David: Cannot find how this is being implemented in the content. But I agree with the principles being applied.
<dmontalvo> https://
Daniel: And expand topic "Alternatives to Multimedia Content"
Estella: Agree also but how this will be displayed, shown in the curriculum.
Daniel: It will be associated with the learning outcomes and also mention to controls.
“Description" terminology
<dmontalvo> https://
Daniel: Issue related to the resource “How to make audio and video accessible”. Terminology used in the curriculum will be the same...
Daniel: according to EOWG decision, we will have:
… "description of visual information" in first occurrence and intro for Topic "Alternatives to Multimedia Content"
… will have description of visual information instead of audio description…
… the background for that is that for some people audio description could be a confusing term.
… Should we explain a bit more what we mean with “description of visual information”?
Gerhard: For me it’s quite clear.
Estella: For me audio description is the standard term but I will go with consensus.
Daniel: I am aware that in Europe is the standard term but not sure if in other regions is the same situation. Maybe we can include the region aspect in a sentence.
Estella: My question would be if “description of visual information” is a standardised term?
Michele: Audio description is not the only term used for describing the visual information.
… Not necessarily not the only “term”, just not the only “way”
Daniel: Audio description can be provided as audio but also as extended description in written text and others.
… The designers need to be aware that these alternatives exist. In the content authors we can expand…
… ”description of visual information” and point to the services.
David: Will this “description of visual information” include spoken subtitles/audio subtitles.
Estella: Audio subtitles are not audio description. They are complementary.
Daniel: We may consider adding audio subtitles/spoken subtitles as a different service but for content producers. <eoncins> ... content authors. Multimedia aspects will be discussed there.
Coverage of Custom widgets
Daniel: Proposal: no module for custom widgets. Instead, covered in module Interaction Design. Rationale:
… concept of custom widgets is much more related to developers (standard versus non-standard coding practices)
… design is more related to art, everything is meant to be unique
https://
Daniel: My rationale for not having custom widgets is more related to coding practices and it is important for developers…
… custom interactions and gestures might be more relevant for designers.
… will include also standards and complex components.
… Do you agree of having costume widgets in interaction design instead of a separate module?
David: I think I agree with that.
Estella: +1
Daniel: That’s now the idea and needs refinement.
Next Steps
Daniel: Next steps will be discussing the new module on “Forms”
… next meeting might be most probably on the 19th October…
… I will bring some other things to EOWG this Friday, such as discussions on module information design.
… I will provide feedback about the EO meeting.
… Next survey will be probably end of October beginning of November.