Meeting minutes
W3C Communications Survey Posted
English Members: https://
English External: https://
Welcome, Announcements, & Introductions (As needed)
see above for the W3C survey!
Capabilities Nesting (Continued Review):
Video Description
How does edge do that
Lionel_Wolberger: With the great leaps in computer vision, describing scenes is now very possible
janina: The challenge of interleaving added video description with dialog and sounds remains
… not only does it need to generate a good textual description, it needs to interleave it well
… though the MAUR supports pausing a video, to give time for extended descriptions
Lionel_Wolberger: That's why automatability is 'in some cases'
Lionel_Wolberger: ACTION move 4.3.1 "Optimize Color Contrast" to be under the heading 2, Color
… Add a new heading 3, "Color Personalization".
… See for example 1.4.6
… “Some of the combinations that could be chosen may have contrast levels that will be lower than those specified here. This is not a violation of this Success Criterion, provided there is a mechanism that will return to the required values set out here.” (1.4.6)
Lionel_Wolberger: .... Automatability? No meaningful way. If a person could have a privacy preserving portable profile, that could be carried and applied to many sites
janina: Next heading 1
Lionel_Wolberger: 5.1.1 Expose Structural Semantics, add Automatability: In Most Cases
… 5.1.2 "Normalize Control & Content Layout" -- move to Aspirational
… 5.3.2 and 5.3.3 are very similar; Form Labels and Form Validation
… Move "Managing Time Outs" to Forms
… 5.6.2 handle dynamic pages -- move up to Semantic Structures
janina: OK to enhance readability, interchange Forms and Structural Semantics
janina: ... move 5.7.1 correct semantic behavior to the Semantic Heading 2
Lionel_Wolberger: Change "native HTML elements cannot fully describe the widget???s function"
… to read, "native HTML elements cannot fully describe their own function without the extra markup."
… Change the heading from "5.7.2 apply or adjust ARIA elements" to "apply or adjust ARIA" and move to the Semantic heading 2
janina: Move "5.7.3 replace component when needed with an accessible version" also under semantic. Pending approval by others.
Lionel_Wolberger: All of 5.8 "Textual Affectations" describe CSS adjustments. Move them all to 4.2 text styling
… or perhaps a new H2 called Page Styling
… Keep your eye out for bugs on the H3s, as they are rendering as H4s on my screen
janina: And I will move "5.8.2 Interactive Text Elements" into "Navigation"
… rename 5.10 Authentication to 5.10 User Authentication
Lionel_Wolberger: Change "way&mdasy;" to "way—"
janina: Rename Video Alternatives to be Rich Media
… Move 5.12 Rich Media to the new Rich Media section 3.2. Change its name to, "Other Rich Media Enhancements"
… Move 5.13 Voice Command to Navigation
Chris: Speaking of drop caps, Deckled edges come to mind
… Also speaking of color contrast, there are still many sites with poor color contrast
… customized color would enable an end user to solve this themselves