W3C

– DRAFT –
WAI-Adapt Teleconference

01 Jul 2025

Attendees

Present
Abhinav, janina, Lionel_Wolberger, matatk
Regrets
-
Chair
Lionel_Wolberger
Scribe
janina, Lionel_Wolberger, matatk

Meeting minutes

a

Any need for admin conversation today?

TPAC?

matatk: We have a draft schedule APA Chairs will review and comment/adjust as needed

matatk: Includes quite a bit of Adapt

janina: I will be away on the 29th

Well Known Destinations

matatk: My actions are still outstanding; have been heads down on APA horizontal, Charter ...

matatk: Considering the list of targets from COGA; have tagged; we want to have a record

matatk: Proposes we can close following up from our conversation

matatk: e.g. we know we'll have A11y Statement; we not "End"

janina: Who's percolating on them?

matatk: Propose we, Adapt, add comments or close as we see fit; we can trust each other--and we can certainly reopen

matatk: Once settled in our Explainer we'll get wider feedback

<matatk> Issues tagged WKD but not proposed destinations: https://github.com/w3c/adapt/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22Well-known%20destinations%22%20-label%3Aproposed-destination

janina: We need to prepare for TPAC, as we depend on implementation

matatk: Suggests Breakouts; Should be ready by then

matatk: Also cross-group mtgs;

janina: AGWG?

matatk: Notes we also have APA room and open calendar for working sessions

matatk: Proposing different UI options (via extensions) to the same site and WKD

janina: We want AG WG and others up to speed by the beginning of October. Need the Explainer to be done and us be comfortable with it.

janina: It's Note track, so should we have done FPWD?

matatk: Suggests a second doc--Note track "Best Practices for WKD"

matatk: No point to Notetrack for Explainer; Rather it's our BP

janina: Also distributable extension?

matatk: Can be done; Just needs our new method

Well Known Destinations Issue Review

w3c/adapt#244

<gb> Issue 244 Updates needed to the WAI-Adapt Explainer and WAI-Adapt Requirements pages (by snidersd) [explainer] [editorial] [Symbols] [Well-known destinations]

*Group looking at areas of the requirements for specification document that are listed as WAI-Adapt requirements:* https://w3c.github.io/adapt/requirements/#wai-adapt-features

matatk: The ten items in the requirements are Familiar Terms and Symbols, Symbol Sets, Enable alternatives for numeric concepts, Importance identification, Enable Alternate Language Complexity of Same Content, Enable Alternate for Non-Literal Content, Enable Additional Help Information, Enable Additional Feedback, Step Indicator, Message

Categorization,

janina: We should wait for post-TPAC to revisit this and update it as needed.

Example of a Note: http://www.w3.org/TR/media-accessibility-reqs/

<Abhinav> <a href="#section2">Go to Section 2</a>

<Abhinav> <a href="javascript:alert('Hello World!');">Execute JavaScript</a>

<Abhinav> <a href="mailto:someone@example.com">Send email</a>

Minutes manually created (not a transcript), formatted by scribe.perl version 244 (Thu Feb 27 01:23:09 2025 UTC).

Diagnostics

Succeeded: s/end of October latest/beginning of October/

All speakers: janina, matatk

Active on IRC: Abhinav, janina, Lionel_Wolberger, matatk