Meeting minutes
gb, Lionel_Wolberger is lwolberg
Light/Dark Mode Proposal from Daniel
<janina> daniel: Sent proposal in email ...
Lionel_Wolberger_: An email from Daniel is received proposing "proposal for a specification for a dark/bright-mode toggle-switch into websites"
… github link, WICG/
<janina> https://
<janina> Lionel: notes Daniel is looking for a normative W3C spec that includes locked in location
Lionel_Wolberger_: he is asking for consistency regarding the location for such a switch
janina: A set location would likely not be supported, as 'author proposes and user disposes'
stacey: what one person needs is not necessarily the need of the many
… was he asking for browser usage or native app as well
… native app is a whole other approach, and screen real estate is harder to get at
… and the device -- the phone -- handles this mode
janina: worthy, not sure it requires a normative specification
… not even sure how we would get two independent implementations
… browsers (user-agents) are very hard to get on board
Lionel_Wolberger_: It is a fact that edge technologies are doing light/dark mode
janina: certainly a capability or feature that an edge technology can support
Lionel_Wolberger_: We'll invite Daniel to attend to discuss why his move to the 'solution space' (hard coded button in the corner) is likely not the solution
Intros (as needed)
Capabilities Reorganization Discussion
Group is looking at sigjam whiteboarding tool for this discussion
stacey: I will share screen and walk you through how this whiteboard collaboration tool 'FigJam' will work
Stacy discusses her proposed approach ...
stacey: Guidelines, Review the capability content. What does the reader absolutely need to know?
… What type of info isn’t needed? Tone–what is the focus for the capabilities? Example below.
… let's write one idea per sticky
stacey: is there enough for a conversation?
Lionel_Wolberger_: Notes white space to separate things usually; also colorized
stacyeverything is movable, nestable, etc
<Bev> Hi I'm here now this is Bev C
https://
<Bev> The edge can remediate
Lionel_Wolberger_: We covered about 9 stickies, and the conversation was really englightening and helpful
… here are some excerpts, for those who may have trouble logging into the Jam, or using AT on the FigJam
… "raising awareness to increase access to functionality (need to consider wording as we define what this is)"
… A principle was proposed, "Design and software development consistently have IMPLIED semantics, by visual layout or page placement, rather than OVERT semantics."
… we discussed making semantics more overt
<Bev> Stacey shared FigJam
Lionel_Wolberger_: "Expose structural semantics (reword?) content is marked up structurally correct and is available to be use we want content to have structural content...
… (edge can play a role in this by “exposing” those semantics to users in an understandable way to make edits)
… -- make it easier and clearer for people to understand and use (bridge the gap between people that code and understand vs. those that want a header, as an example, to look how they want it to look in the structure.
janina: We will continue with this agenda item next week