Meeting minutes
/join #rqtf
Agenda Review & Announcements
WAI Coordination
matatk: Notes restart of WAI Coordination calls
<matatk> https://
matatk: Addressing issues that cut across WAI groups and common interests
matatk: Above link shows WAI activities
matatk: Notes a reprise of Authoring Tools Working Group is pending; proposed charter coming soon
matatk: Desire is to update with something normative, i.e. ATAG++
matatk: Will look at incorporating AI
matatk: Please inform APA Chairs if something that should be a topic for WAI coordination
matatk: Notes WHAT-WG has regular meetings. Should some of us attend?
janina: I'll be attending IETF late July
janina: More to follow on that
TPAC 2026
matatk: Deadline looming to name who we want cross-group mtg with at TPAC
matatk: Due 17 June
matatk: Working on enhancing my scheduling tool from last year to be even more functional for us
matatk: Suggest reminding TF of the requested 17 June deadline
matatk: We should discuss next week here
New charters review
Browser Tools and Testing
Roy_Ruoxi: They are planning to drop AT-Driver
Roy_Ruoxi: Have let ARIA know
Roy_Ruoxi: Notes effort (or accidental?) drop of A11y Driver
matatk: Definitely a concern; project seemed to be going well
Roy's comment: w3c/
matatk: Notes David Burns pointed to another approach option; so discussion progressing over this
matatk: Don't think it's dropped officially yet or because it's flawed. Rather the usual time/resources
Spec review requests
Digital Credentials
due 2026-07-14
matatk: Is an API to facilitate presentation and verification of credentials
matatk: Could be wide ranging application
matatk: A concert ticket ...
matatk: A governmentally issued ID
matatk: Would integrate and store in a digital wallet
matatk: So api provides for some mediation and interaction
matatk: May replace holding a passport up to the camera
matatk: Could be age verification
matatk: This not the selective disclosure of of verifiable credentials approach
matatk: Zero knowledge proof on the horizon -- would support selective
matatk: There are other systems
matatk: It's a complex area over all; this API is request and presentation of credentials
matatk: Work has been controversial; laws very; misuse a concern; but lots of legitimate use that could be empowering
matatk: W3C has chosen to be involved rather than not while work continued elsewhere
matatk: We need to focus on a11y; other groups will address other concerns
matatk: Some of what we might ask would be out of scope for our comment
matatk: We can still encourage use of more supportive approaches
matatk: the Accessibility Considerations section does include some normative provisions
matatk: We need to look for what might be missing
matatk: Status is beyond FPWD; is wanting CR
matatk: It's a formal review request
PaulG: Is the credential or the mechanism for accessing/mediating?
matatk: The latter -- the API
matatk: Certain ISO formats have been chosen by gov entities; so choices already made
paul: Is it challenge and wallet?
matatk: yes, both sides of the communication
matatk: My guess that this relies on browser UI; so browser for wallet management
PaulG: concerned how we manage for users who may have multiple wallets on multiple devices; how do you know what's what?
PaulG: potential for frustration is high
PaulG: You need confidence request is from a trusted source
PaulG: may have passwords in multiple managers; this can get complicated
PaulG: User needs to know who's asking; and we need confidence our end to end concerns are covered somewhere
janina: We need to know who's supporting what.
janina: It's often not clear who's asking for a password, when you have n windwos open.
janina: Password managers not always reliable; old credentials don't die easily
janina: who's asking is important; if there's any challenge-response going on it's vital we can trust it
PaulG: agrees; who's asking and do we trust their request? How to get more detail because we're concerned over spoofing
janina: Also user initiated expire and delete
matatk: boundaries are unclear and important they be clarified
matatk: I'll distill into our tracking thread from these notes as we figure out next steps
matatk: Would be good for us to file issues and do so early
janina: similar to the notification with just an OK option; but no good access to content or Esc to dismiss
PaulG: What about COGA docs?
matatk: yes
matatk: This will come back for us to continue
matatk: Thanks for a good conversation