IRC log of a11yedge on 2024-09-11
Timestamps are in UTC.
- 18:24:29 [RRSAgent]
- RRSAgent has joined #a11yedge
- 18:24:33 [RRSAgent]
- logging to https://www.w3.org/2024/09/11-a11yedge-irc
- 18:24:33 [Zakim]
- RRSAgent, make logs Public
- 18:24:34 [Zakim]
- please title this meeting ("meeting: ..."), janina
- 18:24:48 [janina]
- Meeting: Accessibility at the Edge Community Group Teleconference
- 18:24:55 [janina]
- ate: 11 Sep 2024
- 18:25:00 [janina]
- Chair: Janina
- 18:25:16 [janina]
- agenda+ Welcome & Introductions (As needed)
- 18:25:26 [janina]
- agenda+ Whither Capabilities?
- 18:32:21 [Lionel_Wolberger]
- Lionel_Wolberger has joined #a11yedge
- 18:32:29 [Lionel_Wolberger]
- present+
- 18:32:33 [Lionel_Wolberger]
- agenda?
- 18:32:42 [Lionel_Wolberger]
- scribe+
- 18:33:44 [janina]
- present+
- 18:33:55 [janina]
- scribe+
- 18:34:00 [Lionel_Wolberger]
- present+ Jason
- 18:34:08 [Lionel_Wolberger]
- present+ Shari
- 18:34:15 [Lionel_Wolberger]
- present+ Mike
- 18:34:21 [Lionel_Wolberger]
- zakim, who is here?
- 18:34:21 [Zakim]
- Present: Lionel_Wolberger, janina, Jason, Shari, Mike
- 18:34:23 [Zakim]
- On IRC I see Lionel_Wolberger, RRSAgent, Zakim, janina, Daniel
- 18:36:28 [Lionel_Wolberger]
- janina: Proposing we meet next week 18 Sept, then take off 25 Sept and week following
- 18:36:31 [Lionel_Wolberger]
- ... due to TPAC
- 18:37:22 [Lionel_Wolberger]
- Lionel_Wolberger: 2 Oct is Rosh Hashanna
- 18:37:53 [Lionel_Wolberger]
- Lionel_Wolberger: The group agrees.
- 18:38:03 [Lionel_Wolberger]
- zakim, next item
- 18:38:03 [Zakim]
- agendum 1 -- Welcome & Introductions (As needed) -- taken up [from janina]
- 18:38:07 [Lionel_Wolberger]
- zakim, close this item
- 18:38:07 [Zakim]
- agendum 1 closed
- 18:38:08 [Zakim]
- I see 1 item remaining on the agenda:
- 18:38:08 [Zakim]
- 2. Whither Capabilities? [from janina]
- 18:38:14 [Lionel_Wolberger]
- zakim, next item
- 18:38:14 [Zakim]
- agendum 2 -- Whither Capabilities? -- taken up [from janina]
- 18:39:21 [Lionel_Wolberger]
- janina: Frames the issue of how to get the most value out of this document as it stands now.
- 18:40:14 [Lionel_Wolberger]
- ... propose re-titling the document
- 18:40:23 [Lionel_Wolberger]
- ... Jason has been proposing that for a long time
- 18:40:33 [Lionel_Wolberger]
- ... after re-titling, we re-write the abstract
- 18:40:49 [Lionel_Wolberger]
- ... this document examines the opportunities to refine accessibility after the source is committed
- 18:41:17 [Lionel_Wolberger]
- ... this is the minimum
- 18:43:06 [Lionel_Wolberger]
- Mike: I suggest we put a time limit or deadline as well
- 18:43:08 [Lionel_Wolberger]
- +1
- 18:44:12 [Lionel_Wolberger]
- Lionel: Proposing titles
- 18:44:15 [Lionel_Wolberger]
- ... ... Post-Source Accessibility Capabilities
- 18:45:09 [Lionel_Wolberger]
- Mike: Who is the audience?
- 18:45:45 [Lionel_Wolberger]
- ... let's brainstorm here, as I'd like time to consider
- 18:46:03 [Lionel_Wolberger]
- janina: Let's get a provisional title
- 18:46:17 [Lionel_Wolberger]
- jason: Post-source accesibility techniques and capabilities
- 18:46:44 [Lionel_Wolberger]
- Mike: Post-Source Accessibility
- 18:47:09 [Lionel_Wolberger]
- Mike: What is 'source'?
- 18:47:30 [Lionel_Wolberger]
- Lionel: The group continued to brainstorm. Post Source Code Accessibility
- 18:48:11 [Lionel_Wolberger]
- ... post production accessibility
- 18:49:05 [Lionel_Wolberger]
- janina: 9 am Thursday 26 September we are getting an overview of what is coming in WCAG 3
- 18:49:26 [Lionel_Wolberger]
- Shari: Invite me too
- 18:50:50 [Lionel_Wolberger]
- Lionel_Wolberger: Accessibility capabilities post-source code or content
- 18:52:16 [Lionel_Wolberger]
- Jason: AS long it includes browsers
- 18:52:29 [Lionel_Wolberger]
- ... something is live. How to we further improve something once it is live
- 18:52:40 [Lionel_Wolberger]
- ... could be browser manufacturers, AT, etc
- 18:53:04 [Lionel_Wolberger]
- janina: there could be a sub-title
- 18:53:37 [Lionel_Wolberger]
- Lionel_Wolberger: "Improving" in the subtitle
- 18:54:07 [Lionel_Wolberger]
- Lionel_Wolberger: Accessibility capabilities, post-source code or content
- 18:54:39 [Lionel_Wolberger]
- Mike: +1
- 18:54:42 [janina]
- +1
- 18:54:44 [Lionel_Wolberger]
- Jason: +1
- 18:54:50 [Lionel_Wolberger]
- Shari: +1
- 19:01:48 [Lionel_Wolberger]
- Topic: TPAC
- 19:01:51 [Lionel_Wolberger]
- janina: https://www.w3.org/2024/09/TPAC/registration.html
- 19:01:57 [Lionel_Wolberger]
- rrsagent, make minutes
- 19:01:59 [RRSAgent]
- I have made the request to generate https://www.w3.org/2024/09/11-a11yedge-minutes.html Lionel_Wolberger
- 19:02:55 [Lionel_Wolberger]
- Topic: Next edits
- 19:03:10 [Lionel_Wolberger]
- Jason: We need a new abstract
- 19:08:16 [Lionel_Wolberger]
- Jason: Let's re-examine the recurring subheadings (the current definition list)
- 19:08:35 [Lionel_Wolberger]
- ... Source, Trade-offs, Benefit, Automatability
- 19:08:55 [Lionel_Wolberger]
- Lionel_Wolberger: Perhaps we can combine the first three into one subheading, Considerations
- 19:09:31 [Lionel_Wolberger]
- janina: There are recurring themes
- 19:09:47 [Lionel_Wolberger]
- ... such as a portable configuration that a user takes to every website
- 19:09:54 [Lionel_Wolberger]
- ... this requires being done in post-source
- 19:14:57 [Lionel_Wolberger]
- jason: Most things are likely best, when done at source
- 19:15:11 [Lionel_Wolberger]
- ... but there are often compelling commercial reasons to do it post-source
- 19:15:28 [Lionel_Wolberger]
- ... and often there is minimal to no downside
- 19:16:09 [Lionel_Wolberger]
- ... The document is a guide to how you can do things post-source
- 19:16:23 [Lionel_Wolberger]
- ... and should show the potential pitfalls
- 19:16:55 [Lionel_Wolberger]
- ... as for example, when post-source code hinges on source code (where the source developer does not know there are downstream code )
- 19:17:26 [Lionel_Wolberger]
- ... and if the source developer makes a change, it will essentially turn off the post-source code
- 19:18:06 [Lionel_Wolberger]
- ... so there is a level of collaboration with the people who manage the source code that is required
- 19:18:20 [Lionel_Wolberger]
- ... for much of these post-source fixes to be robust
- 19:27:00 [Lionel_Wolberger]
- janina: Clarifying that the audience is W3C brings new nuances to the fore
- 19:32:43 [Lionel_Wolberger]
- rrsagent, make minutes
- 19:32:45 [RRSAgent]
- I have made the request to generate https://www.w3.org/2024/09/11-a11yedge-minutes.html Lionel_Wolberger
- 19:35:37 [Lionel_Wolberger]
- janina: Can we go with Accessibility capabilities, post-source code and content
- 19:35:50 [Lionel_Wolberger]
- Shari: +1
- 19:35:53 [Lionel_Wolberger]
- Jason: +1
- 19:35:57 [Lionel_Wolberger]
- Lionel_Wolberger: +1
- 19:36:03 [Lionel_Wolberger]
- rrsagent, make minutes
- 19:36:05 [RRSAgent]
- I have made the request to generate https://www.w3.org/2024/09/11-a11yedge-minutes.html Lionel_Wolberger
- 19:36:25 [Lionel_Wolberger]
- zakim, end meeting
- 19:36:25 [Zakim]
- As of this point the attendees have been Lionel_Wolberger, janina, Jason, Shari, Mike
- 19:36:27 [Zakim]
- RRSAgent, please draft minutes
- 19:36:28 [RRSAgent]
- I have made the request to generate https://www.w3.org/2024/09/11-a11yedge-minutes.html Zakim
- 19:36:33 [Zakim]
- I am happy to have been of service, Lionel_Wolberger; please remember to excuse RRSAgent. Goodbye
- 19:36:35 [Zakim]
- Zakim has left #a11yedge