Minutes of APA call on 2026-04-08

See https://www.w3.org/2026/04/08-apa-minutes.html - text format below my signature.

Best,
Gottfried

[Logo: Kompetenzzentrum Digitale Barrierefreiheit]<https://barrierefreiheit.hdm-stuttgart.de/>
[Logo: Hochschule der Medien]<https://www.hdm-stuttgart.de/>

Onlineangebote des Kompetenzzentrums Digitale Barrierefreiheit:

  *   Abokurse<https://barrierefreiheit.hdm-stuttgart.de/abo-kurse/> zum Selbstlernen, auch als Team
  *   TRAINomat<https://trainomat.bf-lernen.de/>: Meine persönliche Ressourcensammlung
  *   Kursangebote: Grundlagen<https://digitalisierung.hdm-stuttgart.de/barrierefreiheit/einfuehrung-in-web-barrierefreiheit-web-accessibility/> | Web-Barrierefreiheit<https://digitalisierung.hdm-stuttgart.de/barrierefreiheit/einfuehrung-in-web-barrierefreiheit-web-accessibility/> | Workshop-Katalog<https://digitalisierung.hdm-stuttgart.de/barrierefreiheit/workshop-katalog/>
  *   YouTube Playlists: Masterthesen<https://www.youtube.com/watch?v=5mia8RQpUOg&list=PLNVCxdMrGvQl9LnWPU5OcbcbUXCSonADz> | Bachelorthesen<https://www.youtube.com/watch?v=3PWcBHQt45o&list=PLNVCxdMrGvQnsP2_FnG6bdvrs0UB7xk7P> | Usability Projekte<https://www.youtube.com/watch?v=oOS3F29rIm8&list=PLNVCxdMrGvQlaCtmUv7RMJJxt0RLtGlRf> | Smarthome-Projekte<https://www.youtube.com/watch?v=rn_9uWXsB5c&list=PLNVCxdMrGvQm7L8ZzTCffs9jgmbEkIOnr> | Webinare<https://youtube.com/playlist?list=PLNVCxdMrGvQlteN1Qd99X-EjTGlx6If0V> | WCAG 2.1 erklärt<https://www.youtube.com/playlist?list=PLNVCxdMrGvQmJfGplIu4wq6GpQG12Z3MT> | Von Anfang an<https://gpii.eu/vonanfangan/>
  *   Abschlussarbeiten<https://www.zotero.org/groups/5070492/hdm-zimmermann-abschlussarbeiten/library> | Netzwerke<https://cloud.mi.hdm-stuttgart.de/s/4jZdW29icN85trG> | Veranstaltungen<https://cloud.mi.hdm-stuttgart.de/s/mNNrk4x3Ggpo8zK>
  *   Abonnieren Sie unseren Newsletter<https://digitalisierung.hdm-stuttgart.de/barrierefreiheit/newsletter/>, um auf dem Laufenden zu bleiben
  *   Mailingliste für Jobangebote in Barrierefreiheit<https://www.listserv.dfn.de/sympa/admin/hdm-bf-job-market>

[IAAP Certified CPWA]

Prof. Dr. Gottfried Zimmermann
Professor Mobile User Interaction
Hochschule der Medien Stuttgart
Email gzimmermann@acm.org<mailto:gzimmermann@acm.org>
Web www.hdm-stuttgart.de/home/gzimmermann<http://www.hdm-stuttgart.de/home/gzimmermann>
Publications www.zotero.org/gzimmermann<http://www.zotero.org/gzimmermann>
Phone +49 711 8923-2751
Büro: Nobelstr. 5, Stuttgart-Vaihingen<https://goo.gl/maps/pvYsfQML4dZTPc4P7>
Postadresse: Nobelstr. 10, 70569 Stuttgart


   [1]W3C

      [1] https://www.w3.org/

                             - DRAFT -
                       APA Weekly Teleconference

08 Apr 2026

   [2]IRC log.

      [2] https://www.w3.org/2026/04/08-apa-irc

Attendees

   Present
          Abhinav, Accessibility, chiace, Cognitive, Fazio,
          Fredrik, gottfried, Health,
          https://www.linkedin.com/posts/davidpfazio_the-impact-of
          -cognitive-accessibility-on-share-7442970597833285633-6V
          Ao?utm_source=share&utm_medium=member_desktop&rcm=ACoAAA
          nG4zkBQv, ICCHP, ICCHP Impact of Cognitive Accessibility
          on Mental Health ICCHP Session
          https://www.linkedin.com/posts/davidpfazio_the-impact-of
          -cognitive-accessibility-on-share-7442970597833285633-6V
          Ao?utm_source=share&utm_medium=member_desktop&rcm=ACoAAA
          nG4zkBQvvaqYwGbagPSF4GxpMmed4DwKg, Impact, janina, Jen,
          JonCohn, marcelo, matatk, Mental, Neha, of, on, PaulG,
          Session, stevef, vaqYwGbagPSF4GxpMmed4DwKg

   Regrets
          -

   Chair
          Matthew

   Scribe
          gottfried

Contents

    1. [3]Agenda Review & Announcements
    2. [4]Proposal: Well-Known URI for A11y Issue Reporting --
       Paul

Meeting minutes

   <janina> /join #rqtf

   <janina> s/\/join #rqtf//

   <Fredrik> present*

  Agenda Review & Announcements

   Gottfried: My session on overlay tools was cancelled due to too
   few submissions.

  Proposal: Well-Known URI for A11y Issue Reporting -- Paul

   <matatk> [5]w3c/a11y-tracking#312

      [5] https://github.com/w3c/a11y-tracking/issues/312

   PaulG: Reporting about accessibility problems.
   ... Available for humans and agents.
   ... AT can also do this.
   ... Reporting channel: URL, e.g. via <link>

   <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

   PaulG: HTML form to fill out.
   ... One person willing to do a prototype for it.
   ... Internal data (on page, etc.) automatically filled out.
   ... AI could potentially fix it before a human reads it.

   <marcelo> link to Paul's spec: [6]https://autosponge.github.io/
   well-known-accessibility-report/spec

      [6] https://autosponge.github.io/well-known-accessibility-report/spec

   PaulG: Benefits: Faster fixes, less reporting and
   conversations, status tracking (get request on report)
   ... This is a draft. Please provide feedback

   <Zakim> matatk, you wanted to talk about well-known vs
   discoverable; and Reporting API

   <matatk> Well-known vs 'discoverable' - background: [7]https://
   github.com/w3c/adapt/blob/main/explainers/
   discoverable-destinations.md

      [7] https://github.com/w3c/adapt/blob/main/explainers/discoverable-destinations.md

   matatk: ADAPT is working on well-known URIs. Like landmarks for
   regions.
   ... We were advised against it. Many websites are complex,
   multi-tenant, multi-target groups, etc.
   ... Need a conversation about the best way to do this
   ... I will put a link in to ADAPT

   <matatk> Reporting API: [8]https://www.w3.org/TR/reporting-1/

      [8] https://www.w3.org/TR/reporting-1/

   matatk: Also working on standard for accessibility metadata -
   relevant here
   ... Reporting API must adhere to privacy - important
   ... Webpages draw from multiple sources frequently.
   ... Webpages often are not static; might be meshups or overlays.
   ... I cann pass along Information from a previous discussion on
   discoverable destinations: Links vs. well-known.

   PaulG: What mechanism works best for your
   organization/deployment, do it. There is not necessarily a
   one-size-fits-all.
   ... The idea came from reporting API. It is about browser and
   machine-to-machine. It is not designed for humans to report.
   ... For meshups, etc.: harder to pinpoint to problem. Payload
   could include screenshots and other information.
   ... One issue per request important.
   ... This is not an audit tool. This is for untrusted actors to
   report what they find as a barrier.

   matatk: Please provide feedback on the tracking issue.

   Fazio: Sounds very much like COGA How To Make Content Usable to
   People with Cognitive and Learning Disabilitires Guide

   <matatk> [9]https://www.w3.org/TR/coga-usable/

      [9] https://www.w3.org/TR/coga-usable/

   Fazio: Was published 6 years ago. Please have a look into it.

   janina: I like this - first principles. This becomes more
   important as we get agents on the web.
   ... I have a hard time how to report on barriers, e.g. ZOOM
   ... This is predictable for users.
   ... ADAPT vs. this one: We can have two specs, but they must not
   clash.
   ... Reliable accessibility statement is relevant too
   ... Hope this will make it into WCAG 3

   matatk: If it is hard to report, bugs will likely not be
   reported

   stevef: JAWS had something like a reporting system in place -
   but now it is gone.

   <Fredrik> tjaws accessibility reporting

   Fredrik: There was a sales pitch for the ARC server - looks
   like now put to sleep
   ... It was basically just a web form

   matatk: Commercial providers could hook into this. Choice of to
   whom it gets reported.

   PaulG: I published this as RFC. The idea is not new. We have
   many convergent technologies right now.
   ... I don't care how we get there. But the time is ripe.

   <Zakim> matatk, you wanted to ask about venue, harmonisation,
   how/where to contribute

   matatk: IETF as venue. We could seek advice on this if you
   want.
   ... W3C spec on well-known URI for changing passwords.
   ... Maybe we could harmonise together with well-known URI...

   <Fredrik> Fredrik In honour of Red Dwarf, how aout Discoverable
   Accessibility Missteps Messaging Integration Technology - where
   does that land in the Backronymicon?

   matatk: Micro-formats wiki, get people to use it, then register
   as URL type.

   <Fredrik> Fredrik: You could change "Discoverable" to
   "Defined".

   matatk: You don't want to overwhelm people, but also collect as
   much Information as possible.
   ... Same reporting form on every webpage is a good think, but
   also a UX challenge.

   c/thing/thing

   PaulG: The discovery doc has an object describing the format of
   reporting (e.g. EARL, AC rules, ...)

   <matatk> s/AC Rules/ACT Rules/

   PaulG: The minimum is a human-written description of the
   problem
   ... Hope that early prototypes will clarify what is needed and
   implementable

   janina: I don't see a clash between this and ADAPT. But good if
   Matthew checks with the community about the suitability of
   well-known for this.
   ... Could this be a template approach for other types of
   reporting (e.g. security, privacy, etc.)

   Abhinav: Can you elaborate on discoverable destination?

   matatk: Imagine the following workflow: You Experience a
   problem, press a button, fill in data on a form.
   ... But it is dependent on the page you are on.

   Abhinav: To my understanding, the form is a well-known page on
   the Domain.

   <chiace> I think a useful next step would be to map the
   end-to-end reporting journeys across different user scenarios

   PaulG: User presses button - an extension may open. Header
   information may not be available to the extension.
   ... Opportunity for third parties to handle stuff on the server.
   ... Let's do all: Well-known AND discoverable

   <PaulG> there is a flow diagram (sorry ascii art) here:
   [10]AutoSponge/
   well-known-accessibility-report?tab=readme-ov-file#two-step-pro
   tocol

     [10] https://github.com/AutoSponge/well-known-accessibility-report?tab=readme-ov-file#two-step-protocol

   <PaulG> but I agree more user journey info would help

   matatk: Chiara had a good proposal in the chat.

   <marcelo> I can help PaulG

   <Abhinav> Abhinav: gottfried - You can find details at:

   <Abhinav> 1) [11]https://github.com/w3c/adapt/blob/main/
   explainers/discoverable-destinations.md

     [11] https://github.com/w3c/adapt/blob/main/explainers/discoverable-destinations.md

   <Abhinav> 2) [12]https://github.com/w3c/adapt/blob/main/
   explainers/
   navigation-and-content-tools-for-agents-using-discoverable-dest
   inations.md

     [12] https://github.com/w3c/adapt/blob/main/explainers/navigation-and-content-tools-for-agents-using-discoverable-destinations.md

   <Zakim> matatk, you wanted to talk about next steps

   matatk: We should think about the next steps in terms of
   registration as RFC, etc.

   <chiace> I can help as well for UX/UI

   matatk: We are adjourned.


    Minutes manually created (not a transcript), formatted by
    [13]scribe.perl version 248 (Mon Oct 27 20:04:16 2025 UTC).

     [13] https://w3c.github.io/scribe2/scribedoc.html

Diagnostics

   Warning: 's/\/join #rqtf//' interpreted as replacing '\' by
   'join #rqtf/'

   Failed: s/\/join #rqtf//

   Succeeded: s/think/thing

   Failed: s/AC Rules/ACT Rules/

   Succeeded: s/checks with the community/checks with the
   community about the suitability of well-known for this/

   All speakers: Abhinav, Fazio, Fredrik, Gottfried, janina,
   matatk, PaulG, stevef

   Active on IRC: Abhinav, chiace, Fazio, Fredrik, gottfried,
   janina, Jen, JonCohn, marcelo, matatk, Neha, PaulG, stevef