16:49:04 RRSAgent has joined #a11yedge 16:49:08 logging to https://www.w3.org/2023/10/23-a11yedge-irc 16:49:08 RRSAgent, make logs Public 16:49:09 please title this meeting ("meeting: ..."), janina 16:50:24 Meeting: A11yEdge Teleconference 16:50:36 Date: 23 Oct 2023 16:50:40 Chair: Janina 16:50:50 agenda+Intros (as needed) 16:51:04 agenda+Capabilities Reorganization Discussion 16:51:14 agenda+Next Steps: Who, what? 17:01:27 stacey has joined #a11yedge 17:01:32 present+ 17:03:40 Lionel_Wolberger_ has joined #a11yedge 17:03:47 present+ 17:04:06 gb, Lionel_Wolberger is lwolberg 17:08:35 topic: Light/Dark Mode Proposal from Daniel 17:09:19 daniel: Sent proposal in email ... 17:09:32 present+ 17:09:44 scribe+ 17:09:55 Lionel_Wolberger_: An email from Daniel is received proposing "proposal for a specification for a dark/bright-mode toggle-switch into websites" 17:10:12 ... github link, https://github.com/WICG/proposals/issues/125 17:10:34 https://lists.w3.org/Archives/Public/public-a11yedge/2023Oct/0006.html 17:10:57 Lionel: notes Daniel is looking for a normative W3C spec that includes locked in location 17:11:36 ... he is asking for consistency regarding the location for such a switch 17:14:03 janina: A set location would likely not be supported, as 'author proposes and user disposes' 17:14:11 stacey: what one person needs is not necessarily the need of the many 17:14:17 ... was he asking for browser usage or native app as well 17:14:25 ... native app is a whole other approach, and screen real estate is harder to get at 17:14:29 ... and the device -- the phone -- handles this mode 17:14:33 janina: worthy, not sure it requires a normative specification 17:14:34 present+ 17:14:36 ... not even sure how we would get two independent implementations 17:14:40 ... browsers (user-agents) are very hard to get on board 17:14:41 scribe+ 17:15:22 Lionel_Wolberger_: It is a fact that edge technologies are doing light/dark mode 17:15:42 janina: certainly a capability or feature that an edge technology can support 17:16:14 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 17:16:31 zakim, next item 17:16:31 agendum 1 -- Intros (as needed) -- taken up [from janina] 17:16:38 zakim, close this item 17:16:38 agendum 1 closed 17:16:39 I see 2 items remaining on the agenda; the next one is 17:16:39 2. Capabilities Reorganization Discussion [from janina] 17:16:39 zakim, next item 17:16:40 agendum 2 -- Capabilities Reorganization Discussion -- taken up [from janina] 17:17:32 Group is looking at sigjam whiteboarding tool for this discussion 17:17:36 stacey: I will share screen and walk you through how this whiteboard collaboration tool 'FigJam' will work 17:18:59 Stacy discusses her proposed approach ... 17:19:09 stacey: Guidelines, Review the capability content. What does the reader absolutely need to know? 17:19:15 ... What type of info isn’t needed? Tone–what is the focus for the capabilities? Example below. 17:19:21 ... let's write one idea per sticky 17:22:38 stacey: is there enough for a conversation? 17:23:32 Lionel_Wolberger_: Notes white space to separate things usually; also colorized 17:24:00 stacyeverything is movable, nestable, etc 17:32:09 Bev has joined #a11yedge 17:32:25 Hi I'm here now this is Bev C 17:33:44 https://a11yedge.github.io/capabilities/#semstruct 17:53:18 The edge can remediate 17:57:30 present+ 17:57:44 present+ 17:58:23 Lionel_Wolberger_: We covered about 9 stickies, and the conversation was really englightening and helpful 17:58:57 ... here are some excerpts, for those who may have trouble logging into the Jam, or using AT on the FigJam 17:59:11 ... "raising awareness to increase access to functionality (need to consider wording as we define what this is)" 17:59:29 ... A principle was proposed, "Design and software development consistently have IMPLIED semantics, by visual layout or page placement, rather than OVERT semantics." 18:00:00 ... we discussed making semantics more overt 18:00:03 Stacey shared FigJam 18:00:19 ... "Expose structural semantics (reword?) content is marked up structurally correct and is available to be use we want content to have structural content... 18:00:51 ... (edge can play a role in this by “exposing” those semantics to users in an understandable way to make edits) 18:01:01 ... -- 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. 18:02:34 janina: We will continue with this agenda item next week 18:02:38 zakim, make minutes 18:02:38 I don't understand 'make minutes', Lionel_Wolberger_ 18:02:43 zakim, end meeting 18:02:43 As of this point the attendees have been stacey, Lionel_Wolberger_, janina, Bev 18:02:45 RRSAgent, please draft minutes 18:02:46 I have made the request to generate https://www.w3.org/2023/10/23-a11yedge-minutes.html Zakim 18:02:53 I am happy to have been of service, Lionel_Wolberger_; please remember to excuse RRSAgent. Goodbye 18:02:53 Zakim has left #a11yedge 18:04:21 Good bye thank you