- From: Matthew Atkinson (W3C Calendar) <noreply+calendar@w3.org>
- Date: Wed, 12 Nov 2025 13:13:14 +0000
- To: Accessible Platform Architectures Working Group <public-apa@w3.org>, Accessible Rich Internet Applications Working Group <public-aria@w3.org>
- Message-ID: <77becce0f85a1aaa64ca4e977d260ced@w3.org>
[View this event in your browser](https://www.w3.org/events/meetings/312f1ce1-505a-4681-9345-14c970c25911/)
Accessible Rich Internet Applications WG, Accessible Platform Architectures WG joint meeting Upcoming Confirmed
================================================================================================================
13 November 2025, 13:45 -15:00 Asia/Tokyo
Floor 4 - 403
[ Accessible Platform Architectures Working Group ](https://www.w3.org/groups/wg/apa/calendar/)[ Accessible Rich Internet Applications Working Group ](https://www.w3.org/groups/wg/aria/calendar/) Agenda
------
- Pronunciation
- Status (reboot with a focus on user needs, and specific issues)
- [Use Cases](https://w3c.github.io/pronunciation/user-scenarios/)
- [Explainer](https://w3c.github.io/pronunciation/explainer/)
- Quick wins: what more can be exposed via the accessibility tree?
- Bringing ARIA expertise into horizontal reviews
- Yes, please!
- A couple of ways we could co-ordinate this, based on how APA works with other groups.
Background on accessibility reviews:
Some members of the group attended the [breakout on accessibility horizontal review for spec authors](https://www.w3.org/events/meetings/af242c02-5463-4aea-9203-7b2616111a6e/). You can check out [the slides](https://raw.githack.com/w3c/apa/main/presentations/2025/TPAC/building-it-in/index.html), but here are key points, in the context of this meeting:
- TAG and APA are working on ways to get a 'heads up' on proposals earlier.
- We find a lot of the input we give is to provide use cases and user needs, based on our experience, and resources such as [the Accessibility User Requirements docs](https://www.w3.org/WAI/research/user-requirements/) and ["Content Usable"](https://www.w3.org/TR/coga-usable/).
- APA has some CSS expertise, and access to expertise in some other areas - would be great to complement this with expertise from ARIA.
- APA does [longitudinal tracking of the accessibility of specs](https://github.com/w3c/a11y-longitudinal-tracking/).
Joining Instructions
--------------------
Instructions are restricted to meeting participants. You need to [ log in](https://auth.w3.org/?url=https%3A%2F%2Fwww.w3.org%2Fevents%2Fmeetings%2F312f1ce1-505a-4681-9345-14c970c25911%2F) to see them.
Participants
------------
### Groups
- [Accessible Platform Architectures Working Group](https://www.w3.org/groups/wg/apa/) ([View Calendar](https://www.w3.org/groups/wg/apa/calendar/))
- [Accessible Rich Internet Applications Working Group](https://www.w3.org/groups/wg/aria/) ([View Calendar](https://www.w3.org/groups/wg/aria/calendar/))
### Invitees
- Chris Pryor
Report feedback and issues on [ GitHub](https://github.com/w3c/calendar "W3C Calendar GitHub repository").
Attachments
- text/calendar attachment: event.ics
Received on Wednesday, 12 November 2025 13:13:19 UTC