12:28:13 <RRSAgent> RRSAgent has joined #apa
12:28:17 <RRSAgent> logging to https://www.w3.org/2026/04/08-apa-irc
12:28:17 <Zakim> RRSAgent, make logs Public
12:28:18 <Zakim> please title this meeting ("meeting: ..."), janina
12:28:30 <janina> Meeting: APA Weekly Teleconference
12:28:40 <janina> Chair: Matthew
12:28:48 <janina> Date: 08 Apr 2026
12:28:52 <janina> agenda+ Agenda Review & Announcements
12:28:52 <janina> agenda+ Proposal: Well-Known URI for A11y Issue Reporting -- Paul
12:28:52 <janina> agenda+ New charters review
12:28:52 <janina> agenda+ New on TR
12:28:52 <janina> agenda+ [Spec review requests](https://github.com/w3c/a11y-request/issues)
12:28:54 <janina> agenda+ [Issue tracking](https://github.com/w3c/a11y-tracking/issues)
12:28:57 <janina> agenda+ CSS Update (Paul)
12:28:59 <janina> agenda+ Other business
12:29:02 <janina> agenda+ Be done
12:56:41 <janina>  /join #rqtf
13:51:15 <matatk> matatk has joined #apa
13:51:21 <matatk> agenda?
13:53:06 <Fazio> Fazio has joined #apa
13:54:06 <PaulG> PaulG has joined #apa
13:55:59 <janina> present+
13:56:06 <janina> rrsagent, make minutes
13:56:08 <RRSAgent> I have made the request to generate https://www.w3.org/2026/04/08-apa-minutes.html janina
13:57:15 <janina> s/\/join #rqtf//
14:01:00 <Fredrik> Fredrik has joined #apa
14:01:28 <Fredrik> present*
14:01:39 <Fredrik> present+
14:01:43 <matatk> matatk has joined #apa
14:01:54 <matatk> present+
14:01:57 <matatk> agenda?
14:02:31 <gottfried> gottfried has joined #apa
14:02:51 <Abhinav> Abhinav has joined #apa
14:02:58 <Abhinav> present+
14:03:24 <gottfried> scribe: gottfried
14:03:31 <gottfried> zakim, Agenda?
14:03:31 <Zakim> I see 9 items remaining on the agenda:
14:03:32 <Zakim> 1. Agenda Review & Announcements [from janina]
14:03:32 <Zakim> 2. Proposal: Well-Known URI for A11y Issue Reporting -- Paul [from janina]
14:03:32 <Zakim> 3. New charters review [from janina]
14:03:32 <Zakim> 4. New on TR [from janina]
14:03:33 <Zakim> 5. [Spec review requests](https://github.com/w3c/a11y-request/issues) [from janina]
14:03:33 <Zakim> 6. [Issue tracking](https://github.com/w3c/a11y-tracking/issues) [from janina]
14:03:33 <Zakim> 7. CSS Update (Paul) [from janina]
14:03:33 <Zakim> 8. Other business [from janina]
14:03:33 <Zakim> 9. Be done [from janina]
14:03:41 <gottfried> zakim, open item 1
14:03:41 <Zakim> agendum 1 -- Agenda Review & Announcements -- taken up [from janina]
14:04:59 <Fazio> present+ICCHP Impact of Cognitive Accessibility on Mental Health ICCHP Session https://www.linkedin.com/posts/davidpfazio_the-impact-of-cognitive-accessibility-on-share-7442970597833285633-6VAo?utm_source=share&utm_medium=member_desktop&rcm=ACoAAAnG4zkBQvvaqYwGbagPSF4GxpMmed4DwKg
14:05:11 <marcelo> marcelo has joined #apa
14:06:00 <gottfried> Gottfried: My session on overlay tools was cancelled due to too few submissions.
14:06:09 <marcelo> present+ marcelo
14:06:17 <gottfried> zakim, next item
14:06:17 <Zakim> agendum 2 -- Proposal: Well-Known URI for A11y Issue Reporting -- Paul -- taken up [from janina]
14:06:22 <PaulG> present+
14:06:25 <matatk> https://github.com/w3c/a11y-tracking/issues/312
14:06:38 <matatk> present+
14:06:57 <gottfried> present+
14:07:05 <Fazio> present+
14:08:01 <Jen> Jen has joined #apa
14:08:03 <Jen> present+
14:09:01 <gottfried> PaulG: Reporting about accessibility problems.
14:09:09 <gottfried> … Available for humans and agents.
14:09:29 <gottfried> ... AT can also do this.
14:09:51 <gottfried> ... Reporting channel: URL, e.g. via <link>
14:09:55 <Fazio> Sounds like this spec meets the needs of "Find Help" from the COGA How To Make Content Usable to People with Cognitive and Learning Disabilitires Guide
14:10:09 <gottfried> ... HTML form to fill out.
14:10:12 <kirkwood> kirkwood has joined #APA
14:10:37 <gottfried> ... One person willing to do a prototype for it.
14:11:04 <matatk> q?
14:11:11 <gottfried> ... Internal data (on page, etc.) automatically filled out.
14:11:40 <matatk> q+ to talk about well-known vs discoverable; and Reporting API
14:12:12 <gottfried> ... AI could potentially fix it before a human reads it.
14:12:17 <marcelo> link to Paul's spec: https://autosponge.github.io/well-known-accessibility-report/spec
14:13:17 <chiace> chiace has joined #apa
14:13:19 <stevef> stevef has joined #apa
14:13:30 <stevef> present+
14:13:31 <gottfried> ... Benefits: Faster fixes, less reporting and conversations, status tracking (get request on report)
14:13:38 <chiace> present+
14:13:40 <matatk> q?
14:13:41 <gottfried> ... This is a draft. Please provide feedback
14:13:44 <Fazio> q+
14:14:38 <matatk> ack me
14:14:38 <Zakim> matatk, you wanted to talk about well-known vs discoverable; and Reporting API
14:14:49 <matatk> Well-known vs 'discoverable' - background: https://github.com/w3c/adapt/blob/main/explainers/discoverable-destinations.md
14:15:07 <Neha> Neha has joined #apa
14:15:16 <Neha> present+
14:15:32 <gottfried> matatk: ADAPT is working on well-known URIs. Like landmarks for regions.
14:16:37 <gottfried> ... We were advised against it. Many websites are complex, multi-tenant, multi-target groups, etc.
14:16:44 <janina> q+
14:16:48 <gottfried> ... Need a conversation about the best way to do this
14:17:07 <gottfried> ... I will put a link in to ADAPT
14:17:26 <matatk> Reporting API: https://www.w3.org/TR/reporting-1/
14:17:28 <gottfried> ... Also working on standard for accessibility metadata - relevant here
14:18:10 <gottfried> ... Reporting API must adhere to privacy - important
14:18:43 <gottfried> ... Webpages draw from multiple sources frequently.
14:19:05 <gottfried> ... Webpages often are not static; might be meshups or overlays.
14:19:53 <matatk> q?
14:20:02 <gottfried> ... I cann pass along Information from a previous discussion on discoverable destinations: Links vs. well-known.
14:21:12 <gottfried> PaulG: What mechanism works best for your organization/deployment, do it. There is not necessarily a one-size-fits-all.
14:21:49 <gottfried> ... The idea came from reporting API. It is about browser and machine-to-machine. It is not designed for humans to report.
14:22:02 <matatk> rrsagent, make minutes
14:22:04 <RRSAgent> I have made the request to generate https://www.w3.org/2026/04/08-apa-minutes.html matatk
14:23:09 <gottfried> ... For meshups, etc.: harder to pinpoint to problem. Payload could include screenshots and other information.
14:23:47 <gottfried> ... One issue per request important.
14:24:26 <gottfried> ... This is not an audit tool. This is for untrusted actors to report what they find as a barrier.
14:25:33 <JonCohn> JonCohn has joined #apa
14:25:50 <stevef> q+
14:25:54 <matatk> q?
14:26:14 <matatk> ack Fazio
14:26:14 <gottfried> matatk: Please provide feedback on the tracking issue.
14:26:56 <gottfried> Fazio: Sounds very much like COGA How To Make Content Usable to People with Cognitive and Learning Disabilitires Guide
14:27:14 <JonCohn> present+
14:27:17 <matatk> https://www.w3.org/TR/coga-usable/
14:27:23 <gottfried> ... Was published 6 years ago. Please have a look into it.
14:27:26 <matatk> q?
14:27:31 <matatk> ack janina
14:28:08 <gottfried> janina: I like this - first principles. This becomes more important as we get agents on the web.
14:28:26 <gottfried> ... I have a hard time how to report on barriers, e.g. ZOOM
14:28:55 <gottfried> ... This is predictable for users.
14:29:15 <gottfried> ... ADAPT vs. this one: We can have two specs, but they must not clash.
14:29:39 <gottfried> ... Reliable accessibility statement is relevant too
14:29:51 <gottfried> ... Hope this will make it into WCAG 3
14:30:27 <matatk> q?
14:30:29 <gottfried> matatk: If it is hard to report, bugs will likely not be reported
14:30:30 <matatk> ack stevef
14:31:36 <matatk> q?
14:31:42 <gottfried> stevef: JAWS had something like a reporting system in place - but now it is gone.
14:31:48 <Fredrik> q+
14:31:57 <Fredrik> tjaws accessibility reporting
14:32:02 <matatk> q?
14:32:06 <matatk> ack Fredrik
14:32:22 <Fredrik> q-
14:33:13 <gottfried> Fredrik: There was a sales pitch for the ARC server - looks like now put to sleep
14:33:35 <gottfried> ... It was basically just a web form
14:34:22 <matatk> q?
14:34:28 <gottfried> matatk: Commercial providers could hook into this. Choice of to whom it gets reported.
14:34:58 <Fredrik> rrsagent, make minutes
14:34:59 <RRSAgent> I have made the request to generate https://www.w3.org/2026/04/08-apa-minutes.html Fredrik
14:35:41 <matatk> q+ to ask about venue, harmonisation, how/where to contribute
14:35:54 <gottfried> PaulG: I published this as RFC. The idea is not new. We have many convergent technologies right now.
14:36:33 <janina> q+
14:36:35 <gottfried> ... I don't care how we get there. But the time is ripe.
14:37:12 <matatk> q?
14:37:16 <matatk> ack me
14:37:16 <Zakim> matatk, you wanted to ask about venue, harmonisation, how/where to contribute
14:37:20 <Abhinav> q+
14:37:55 <gottfried> matatk: IETF as venue. We could seek advice on this if you want.
14:38:10 <gottfried> ... W3C spec on well-known URI for changing passwords.
14:38:39 <gottfried> ... Maybe we could harmonise together with well-known URI...
14:38:55 <Fredrik> Fredrik In honour of Red Dwarf, how aout Discoverable Accessibility Missteps Messaging Integration Technology - where does that land in the Backronymicon?
14:39:19 <gottfried> ... Micro-formats wiki, get people to use it, then register as URL type.
14:40:05 <Fredrik> Fredrik: You could change "Discoverable" to "Defined".
14:40:48 <gottfried> ... You don't want to overwhelm people, but also collect as much Information as possible.
14:42:15 <gottfried> ... Same reporting form on every webpage is a good think, but also a UX challenge.
14:42:20 <gottfried> c/think/thing
14:42:38 <gottfried> s/think/thing
14:43:41 <gottfried> PaulG: The discovery doc has an object describing the format of reporting (e.g. EARL, AC rules, ...)
14:43:56 <matatk> s/AC Rules/ACT Rules/
14:44:00 <Abhinav> q?
14:44:13 <gottfried> ... The minimum is a human-written description of the problem
14:45:20 <gottfried> ... Hope that early prototypes will clarify what is needed and implementable
14:45:53 <matatk> ack janina
14:46:26 <gottfried> janina: I don't see a clash between this and ADAPT. But good if Matthew checks with the community.
14:47:00 <gottfried> ... Could this be a template approach for other types of reporting (e.g. security, privacy, etc.)
14:47:00 <matatk> s/checks with the community/checks with the community about the suitability of well-known for this/
14:47:05 <matatk> rrsagent, make minutes
14:47:06 <RRSAgent> I have made the request to generate https://www.w3.org/2026/04/08-apa-minutes.html matatk
14:47:25 <matatk> ack Abhinav
14:48:39 <gottfried> Abhinav: Can you elaborate on discoverable destination?
14:49:12 <gottfried> matatk: Imagine the following workflow: You Experience a problem, press a button, fill in data on a form.
14:49:25 <gottfried> ... But it is dependent on the page you are on.
14:50:00 <gottfried> Abhinav: To my understanding, the form is a well-known page on the Domain.
14:50:54 <chiace> I think a useful next step would be to map the end-to-end reporting journeys across different user scenarios
14:50:55 <gottfried> PaulG: User presses button - an extension may open. Header information may not be available to the extension.
14:51:20 <matatk> q+ to talk about next steps
14:51:55 <gottfried> ... Opportunity for third parties to handle stuff on the server.
14:52:37 <gottfried> ... Let's do all: Well-known AND discoverable
14:53:30 <PaulG> there is a flow diagram (sorry ascii art) here: https://github.com/AutoSponge/well-known-accessibility-report?tab=readme-ov-file#two-step-protocol
14:53:40 <PaulG> but I agree more user journey info would help
14:53:47 <gottfried> matatk: Chiara had a good proposal in the chat.
14:54:01 <marcelo> I can help PaulG
14:54:03 <matatk> q?
14:54:06 <Abhinav> Abhinav: gottfried - You can find details at:
14:54:06 <Abhinav> 1) https://github.com/w3c/adapt/blob/main/explainers/discoverable-destinations.md
14:54:06 <Abhinav> 2)   https://github.com/w3c/adapt/blob/main/explainers/navigation-and-content-tools-for-agents-using-discoverable-destinations.md
14:54:08 <matatk> ack me
14:54:08 <Zakim> matatk, you wanted to talk about next steps
14:54:15 <gottfried> ... We should think about the next steps in terms of registration as RFC, etc.
14:55:13 <chiace> I can help as well for UX/UI
14:55:22 <gottfried> matatk: We are adjourned.
14:55:30 <matatk> zakim, end meeting
14:55:30 <Zakim> As of this point the attendees have been janina, Fredrik, matatk, Abhinav, ICCHP, Impact, of, Cognitive, Accessibility, on, Mental, Health, Session,
14:55:32 <Zakim> ... https://www.linkedin.com/posts/davidpfazio_the-impact-of-cognitive-accessibility-on-share-7442970597833285633-6VAo?utm_source=share&utm_medium=member_desktop&rcm=ACoAAAnG4zkBQv
14:55:32 <Zakim> ... vaqYwGbagPSF4GxpMmed4DwKg, marcelo, PaulG, gottfried, Fazio, Jen, stevef, chiace, Neha, JonCohn
14:55:32 <Zakim> RRSAgent, please draft minutes
14:55:34 <RRSAgent> I have made the request to generate https://www.w3.org/2026/04/08-apa-minutes.html Zakim
14:55:40 <Zakim> I am happy to have been of service, matatk; please remember to excuse RRSAgent.  Goodbye
14:55:40 <Zakim> Zakim has left #apa
14:57:03 <gottfried> zakim, bye
14:57:12 <gottfried> rrsagent, draft minutes
14:57:14 <RRSAgent> I have made the request to generate https://www.w3.org/2026/04/08-apa-minutes.html gottfried
15:00:39 <gottfried> gottfried has joined #apa
15:02:40 <janina> janina has left #apa
15:37:12 <kizu> kizu has joined #apa
16:11:30 <usrjordi> usrjordi has joined #apa