APA Weekly Teleconference
- Past
- Tentative
- Past
- Tentative
Meeting
Please check the "Agenda" section (after following the "APA Weekly Teleconference" link to get to this call's event details page) for links to read the specs, comment threads, and actions we'll be reviewing in the next meeting.
Resources and Minutes
- APA WG: https://www.w3.org/WAI/APA/minutes
- Adapt TF: https://www.w3.org/WAI/APA/task-forces/adapt/minutes
- COGA TF: https://www.w3.org/WAI/GL/task-forces/coga/minutes
- Pronunciation TF: https://www.w3.org/WAI/APA/task-forces/pronunciation/minutes
- Maturity Model TF: https://www.w3.org/WAI/APA/task-forces/maturity-model/minutes
- Research Questions TF: https://www.w3.org/WAI/APA/task-forces/research-questions/minutes
Additional resources for APA at: https://www.w3.org/WAI/APA/wiki/Key_Resources_and_Links
Agenda
- Agenda Review & Announcements
- TPAC 2026
- Including funding support to attend: https://www.surveymonkey.com/r/W3C-Apply
- New charters
- New on TR
- (none so far this week)
- WebMCP - should it be adopted as W3C work?
- Please see the email following this for info. Here are the pertinent links...
- WebMCP explainer: https://github.com/webmachinelearning/webmcp/blob/main/README.md
- Tracking issue for WebMCP accessibility considerations: https://github.com/w3c/a11y-tracking/issues/318
- Tracking issue for 'Redundancy with accessibility tree' thread: https://github.com/w3c/a11y-tracking/issues/317
- Standards positions of the three main engines:
- Chromium/Chrome: Supportive
- Gecko/Mozilla Firefox: No official position yet; thread: https://github.com/mozilla/standards-positions/issues/1412
- WebKit/Safari: Opposed; position thread: https://github.com/WebKit/standards-positions/issues/670 and the specific comment where they state their objections is: https://github.com/WebKit/standards-positions/issues/670#issuecomment-4608432694
- Spec review requests
- 2026-07-29: Attribution Level 1
- Issue tracking
- Open UI - interest invokers - Should ::interest-button be opt-in, opt-out, or enabled via media query?
- For reference, the relevant part of the Interest Invokers explainer: https://open-ui.org/components/interest-invokers.explainer/#option-35---add-an-opt-in-info-button-pseudo-element
- The source CSS WG issue links to ARIA and WHATWG discussions around this topic, too.
- Open UI - custom select element - Keyboard behaviour of custom select options
- Open UI - interest invokers - Should ::interest-button be opt-in, opt-out, or enabled via media query?
- CSS Update (Paul)
- Other business
- Be done
Minutes
Read minutesExport options
Personal links
Please log in to export this event with all the information you have access to.
Public links
The following links do not contain any sensitive information and can be shared publicly.