BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Sabre//Sabre VObject 4.6.1//EN
CALSCALE:GREGORIAN
LAST-MODIFIED:20260629T215918Z
BEGIN:VTIMEZONE
TZID:America/New_York
X-MICROSOFT-CDO-TZID:10
BEGIN:STANDARD
DTSTART:20251102T060000
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
TZNAME:EST
END:STANDARD
BEGIN:STANDARD
DTSTART:20261101T060000
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
TZNAME:EST
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20260308T070000
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:b3d3fb17-9637-4fae-a68a-39f8f9a6719a
DTSTAMP:20260629T215918Z
SUMMARY:APA Weekly Teleconference
DTSTART;TZID=America/New_York:20260701T100000
DTEND;TZID=America/New_York:20260701T105500
DESCRIPTION:https://www.w3.org/events/meetings/b3d3fb17-9637-4fae-a68a-39f8
 f9a6719a/20260701T100000/\n\n\n\nAgenda\n\n1. Agenda Review & Announcement
 s\n2. TPAC 2026\n	- Including funding support to attend: https://www.surve
 ymonkey.com/r/W3C-Apply\n3. New charters\n	- [Authoring Tools Accessibilit
 y Guidelines Group Charter](https://github.com/w3c/strategy/issues/552)\n4
 . New on TR\n	- (none so far this week)\n5. WebMCP - should it be adopted 
 as W3C work?\n	- Please see the email following this for info. Here are th
 e pertinent links...\n	* WebMCP explainer: <https://github.com/webmachinel
 earning/webmcp/blob/main/README.md>\n	* Tracking issue for WebMCP accessib
 ility considerations: <https://github.com/w3c/a11y-tracking/issues/318>\n	
 * Tracking issue for 'Redundancy with accessibility tree' thread: <https:/
 /github.com/w3c/a11y-tracking/issues/317>\n	* Standards positions of the t
 hree main engines:\n	  - Chromium/Chrome: Supportive\n	  - Gecko/Mozilla F
 irefox: No official position yet\; thread: <https://github.com/mozilla/sta
 ndards-positions/issues/1412>\n	  - WebKit/Safari: Opposed\; position thre
 ad: <https://github.com/WebKit/standards-positions/issues/670> and the spe
 cific comment where they state their objections is: <https://github.com/We
 bKit/standards-positions/issues/670#issuecomment-4608432694>\n6. [Spec rev
 iew requests](https://github.com/w3c/a11y-request/issues)\n	- 2026-07-29: 
 [Attribution Level 1](https://github.com/w3c/a11y-request/issues/167)\n7. 
 [Issue tracking](https://github.com/w3c/a11y-tracking/issues)\n	- Open UI 
 - interest invokers - [Should ::interest-button be opt-in\, opt-out\, or e
 nabled via media query?](https://github.com/w3c/a11y-tracking/issues/331)\
 n		- 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>\n		- The source CSS WG issue lin
 ks to ARIA and WHATWG discussions around this topic\, too.\n	- Open UI - c
 ustom select element - [Keyboard behaviour of custom select options](https
 ://github.com/w3c/a11y-tracking/issues/329)\n8. CSS Update (Paul)\n9. Othe
 r business\n10. Be done
STATUS:TENTATIVE
CREATED:20260629T215658Z
LAST-MODIFIED:20260629T215918Z
SEQUENCE:3
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Accessible Platfor
 m Architectures Working Group:mailto:public-apa@w3.org
RECURRENCE-ID;TZID=America/New_York:20260701T100000
END:VEVENT
END:VCALENDAR