Meetings/TPAC 2026

We'll do most of our TPAC planning in GitHub, but this page serves as a record of the session proposals that we are making before they make it into the draft schedule.

Officially proposed meetings

1. Accessible Platform Architectures Working Group, Accessible Rich Internet Applications Working Group Joint Meeting (could suggest: Discoverable Destinations; Symbols; ... ?)
2. Accessibility Guidelines Working Group, Accessible Platform Architectures Working Group Joint Meeting (Adapt discoverable destinations; symbols; AG updates/needs - possible RQTF involvement?)
3. Media and Entertainment Interest Group, Timed Text Working Group, Accessible Platform Architectures Working Group Joint Meeting (media taxonomy; MEIG & TTWG updates; MAUR 2 possibilities?)
4. Web and AI Interest Group, Research Questions Task Force (of Accessible Platform Architectures Working Group) Joint Meeting (RQTF's AI doc)
5. WHATWG, Accessible Platform Architectures Working Group Joint Meeting (Symbols PoC; Discoverable Destinations update)
6. Authoring Tool Accessibility Guidelines Working Group, Accessible Platform Architectures Working Group Joint Meeting (assuming it's set up by TPAC).
   We could point them to relevant RQTF work; Adapt's Symbols and Discoverable Destinations work? Also Maturity Model? How does an author shape the aural presentation of content?
7. Authoring Tool Accessibility Guidelines Working Group (assuming it's set up by TPAC).
   We could point them to relevant RQTF work; Adapt's Symbols and Discoverable Destinations work? Also Maturity Model? How does an author shape the aural presentation of content?
8. Cascading Style Sheets Working Group, Accessible Platform Architecture Working Group Joint Meeting to talk about:
   1. Semantic selectors - Note: There was some talk at Web Engines Hackfest about how user style sheets could be really helpful if at least indirectly surfaced in browser UI [e.g. please underline all links] - if we had semantic selectors this would make user stylesheets, or features powered underneath by user stylesheets, much more useful and robust.
   2. how to map roles to new concepts - AAM is good, but how is it overidden/nullified (escape hatch for authors) when we can't modify pseudos?
   3. concerns around ASSIGNING roles via CSS
   4. how to make this stuff (especially anything more semantic) more visible to devs
   5. General text-fit proposals
      1. Any issues
      2. Awareness raising for devs
9. Immersive Web Working Group, Accessible Platform Architectures Working Group Joint Meeting to talk about:
   1. the XAUR, any anticipated updates that we could make;
   2. the developments around interesting proposals such as Spatial CSS; and
   3. what we could do to make Marker Tracking (empty repo for now, but the gist is: QR-like codes being used to trigger or anchor immersive experiences) accessible;
   4. <model> element accessibility (both UI/interaction and content) and future plans there.
   5. Spatial audio / earcons? (esp in relation to above)
10. Publishing Maintenance Working Group, Publishing Maintenance Community Group, Accessible Platform Architectures Working Group Joint Meeting and specifically people focused on accessibility within those, to talk about:
    1. 3.5 plans - especially how fixed layout is being merged in
    2. Updates from APA on Symbols, pronunciation

Agreed on APA call to pursue these as breakouts closer to the time, as required

1. Joint meeting with CSS, ARIA, and WHATWG regarding HTML in Canvas outstanding issues.
2. Joint APA, ARIA, AG meeting to discuss cross-cutting challenges that come up (e.g. Carousels, HTML in Canvas, …) - could do this as a breakout? Does this need to include AG?