- From: Alan Stearns (W3C Calendar) <noreply+calendar@w3.org>
- Date: Tue, 17 Sep 2024 20:32:19 +0000
- To: Accessible Platform Architectures Working Group <public-apa@w3.org>, "Cascading Style Sheets (CSS) Working Group" <www-style@w3.org>
- Message-ID: <d402bce378882ab1cf6da45f3f4e3af4@w3.org>
[View this event in your browser](https://www.w3.org/events/meetings/c7fff076-c85e-4a09-a769-e5053df41385/) Cascading Style Sheets WG, Accessible Platform Architectures WG Joint Meeting Upcoming Confirmed ================================================================================================= 23 September 2024, 16:30 -18:00 America/Los\_Angeles 2 Ballroom Level - California B [ Accessible Platform Architectures Working Group ](https://www.w3.org/groups/wg/apa/calendar/)[ Cascading Style Sheets (CSS) Working Group ](https://www.w3.org/groups/wg/css/calendar/) Agenda ------ - Any general issues CSS WG would like to raise (edit from Alan Stearns - possibly these?) - \[css-display-4\] Should the reading-order-items property apply to tables in addition to flex and grid layouts? <https://github.com/w3c/csswg-drafts/issues/9922> - \[css-display-4\] Define how reading-flow interacts with focusable display: contents elements. <https://github.com/w3c/csswg-drafts/issues/9230> - \[css-view-transitions\] Users need to be able to disable view transitions <https://github.com/w3c/csswg-drafts/issues/10267> Thanks, Alan - Query on CSS Speech: blockers to implementation; possibility of implementing a 'core' subset? - Context: relating to Pronunciation TF's work, there are a few things that, if present in CSS, we could build on to more effectively solve the problems identified by this TF. - We have identified different facets of the problem of pronunciation: some we feel are more apt for CSS (largely user-controlled); others relate directly to the content (hence we are proposing markup for them). - Many of our use cases come from education. Background info: [Pronunciation Gap Analysis and Use Cases](https://w3c.github.io/pronunciation/gap-analysis_and_use-case/) 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%2Fc7fff076-c85e-4a09-a769-e5053df41385%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/)) - [Cascading Style Sheets (CSS) Working Group](https://www.w3.org/groups/wg/css/) ([View Calendar](https://www.w3.org/groups/wg/css/calendar/)) ### Invitees - Eric Meyer Report feedback and issues on [ GitHub](https://github.com/w3c/calendar "W3C Calendar GitHub repository").
Attachments
- text/calendar attachment: event.ics
Received on Tuesday, 17 September 2024 20:32:22 UTC