18:22:45 <RRSAgent> RRSAgent has joined #a11yedge
18:22:50 <RRSAgent> logging to https://www.w3.org/2024/07/10-a11yedge-irc
18:22:50 <Zakim> RRSAgent, make logs Public
18:22:51 <Zakim> please title this meeting ("meeting: ..."), janina
18:23:12 <janina> Meeting: Accessibility at the Edge Community Group Teleconference
18:23:26 <janina> Chair: Janina
18:23:49 <janina> agenda+ Welcome & Introductions (As needed)
18:24:28 <janina> agenda+Further Capabilities Editing--Continuing H2-H3 review
18:24:38 <janina> agenda+Actions & Next Steps
18:24:46 <janina> agenda+ Be done
18:38:34 <Lionel_Wolberger> Lionel_Wolberger has joined #a11yedge
18:38:47 <Lionel_Wolberger> scribe+
18:38:50 <Lionel_Wolberger> present+
18:39:23 <janina> present+
18:39:26 <janina> scirbe+
18:39:34 <Lionel_Wolberger> present+ Chris
18:40:06 <Lionel_Wolberger> zakim, next item
18:40:06 <Zakim> agendum 1 -- Welcome & Introductions (As needed) -- taken up [from janina]
18:40:23 <BC> BC has joined #a11yedge
18:40:31 <BC> Bev C is here
18:40:35 <janina> Lionel_Wolberger: Notes we're in summer when vacations fall
18:40:49 <janina> Lionel_Wolberger: Proposing next telecon is 31 July
18:41:21 <BC> July 31 is good
18:41:35 <BC> Bev C is present+
18:42:12 <janina> present_
18:42:20 <BC> present+ Bev C
18:42:31 <Lionel_Wolberger> zakim, who is here?
18:42:31 <Zakim> Present: Lionel_Wolberger, janina, Chris, Bev
18:42:33 <Zakim> On IRC I see BC, Lionel_Wolberger, RRSAgent, Zakim, janina, dmontalvo
18:42:57 <janina> +1
18:43:40 <janina> RESOLVED: Next telecon will be 31 July
18:44:00 <janina> rrsagent, make minutes
18:44:01 <RRSAgent> I have made the request to generate https://www.w3.org/2024/07/10-a11yedge-minutes.html janina
18:44:46 <Lionel_Wolberger> zakim, next item
18:44:46 <Zakim> agendum 2 -- Further Capabilities Editing--Continuing H2-H3 review -- taken up [from janina]
18:45:17 <janina> regrets: Mike, Jason
18:46:37 <Lionel_Wolberger> https://a11yedge.github.io/capabilities/
18:53:28 <Lionel_Wolberger> janina: Numbers and strings of digits: Phone numbers are the best example, they are read as numbers
18:54:11 <Lionel_Wolberger> ... e.g. 800-5555555 might be read as eight hundred, five million 5 hundred 55 thousand, 5 hundred and 55.
18:55:21 <Lionel_Wolberger> ... edge technology could somehow cause such a number to be more intelligible
18:55:36 <Lionel_Wolberger> janina: There is some support in SSML
18:56:05 <Lionel_Wolberger> Lionel_Wolberger: This is aspirational, as it would be very difficult to implement today
18:56:16 <Lionel_Wolberger> Bev: +1
18:57:28 <Lionel_Wolberger> Topic: Acronym expansion
18:57:44 <Lionel_Wolberger> Lionel_Wolberger: This is very similar to 5.11.1 Dictionary on Demand
18:59:22 <Lionel_Wolberger> janina: It's more than a dictionary lookup, take for example CD
18:59:36 <Lionel_Wolberger> ... compact disk, certifice of deposit? Candela?
19:00:12 <Lionel_Wolberger> ... AI could read the adjacent text and context and provide the fully spelled out name
19:00:45 <Lionel_Wolberger> Lionel_Wolberger: Same problem as the above digits, I do not see how the page would encode this information for the screen reader to pick up
19:03:15 <Lionel_Wolberger> Lionel_Wolberger: This is aspirational
19:04:09 <Lionel_Wolberger> Topic: Post-source as a descriptive term for 'accessibility at the edge'
19:05:08 <Lionel_Wolberger> Lionel_Wolberger: I find the term "post source" does work well, once context is provided.
19:05:30 <Lionel_Wolberger> janina: I propose incorporating it in a descriptive section
19:05:36 <Lionel_Wolberger> ... e.g., the introduction
19:06:45 <BC> +1 Research related features
19:09:54 <Lionel_Wolberger> Topic: Looking at WCAG to find what we may have missed
19:10:00 <Lionel_Wolberger> Link, https://www.w3.org/TR/WCAG22/#text-alternatives
19:12:50 <Lionel_Wolberger> janina:  WCAG 2.2 1.1.1, Non-text content, is an Edge capability thanks to AI
19:13:28 <Lionel_Wolberger> Lionel_Wolberger: We have it in the capabilities doc under 3.1.1 Image Alternative Text Provisioning
19:13:48 <Lionel_Wolberger> janina: The mention in capabilities could cross-link to WCAGhttps://www.w3.org/TR/WCAG22/#text-alternatives
19:14:56 <BC> BC has joined #a11yedge
19:16:10 <BC> WCAG 3
19:16:49 <Lionel_Wolberger> https://www.w3.org/TR/wcag-3.0/
19:17:03 <Lionel_Wolberger> Topic: WCAG 3.0
19:17:20 <Lionel_Wolberger> janina: I propose we link to WCAG 3.0
19:17:37 <Lionel_Wolberger> Lionel_Wolberger: I am concerned it will still change quite a bit and such links will be brittle
19:17:58 <BC> too early to know
19:18:13 <Lionel_Wolberger> janina: It may not change that much, and Edge Capabilities has a big overlap
19:18:29 <Lionel_Wolberger> +1 to 'too early to know'
19:20:20 <Lionel_Wolberger> WCAG 2.2, Guideline 1.2 Time-based Media: Provide alternatives for time-based media.
19:20:42 <BC> screen reader, closed captions
19:22:02 <Lionel_Wolberger> janina: This is now common for the edge to provide close captions
19:22:25 <Lionel_Wolberger> ... it is aspirational that AI could provide some audio description
19:23:51 <Lionel_Wolberger> zakim, end meeting
19:23:51 <Zakim> As of this point the attendees have been Lionel_Wolberger, janina, Chris, Bev
19:23:53 <Zakim> RRSAgent, please draft minutes
19:23:54 <RRSAgent> I have made the request to generate https://www.w3.org/2024/07/10-a11yedge-minutes.html Zakim
19:24:00 <Zakim> I am happy to have been of service, Lionel_Wolberger; please remember to excuse RRSAgent.  Goodbye
19:24:01 <Zakim> Zakim has left #a11yedge
19:24:03 <BC> exit