Topic ideas for TPAC 2024

[spectranaut]

It looks like TPAC 2025 in Anaheim will be well attended!

Let's use this discussion page to propose discussion topics for the F2F meeting. Add a comment below with any topic you think we should discuss. Additionally, you can add the tag "F2FCandidate" to any existing issue that you want discussed at TPAC.

We will record relevant information for the working group and draft schedules on this wikipage: https://github.com/w3c/aria/wiki/TPAC-2024-ARIA-Meetings

[aleventhal]

1. Prohibited name repair (prototype available in Chromium)
   Subtopic: what to do if tabindex=0. Seems better to have a minimum role for these cases instead of prohibiting name.

2. Status update on new HTML and CSS features that are likely ship soon, with a big a11y impact:
   Web platform feature improvements, e.g.:

• Popover (MDN docs)
• CSS anchor positioning (MDN docs)
• Customizable select (explainer)
• popover=hint (explainer)
• command/commandfor attributes (explainer, spec PR, spec issue)
• interesttarget attribute (explainer)
• details/summary a11y improvement
• The CSS reading-flow property (CSS spec, WHATWG proposal, display:contents issue, position:absolute issue)
• ::scroll-marker, scrolltarget

[aardrian]

I came here to raise CSS reading order because I think we need to spend some time with the CSSWG folks.

[aleventhal]

I have a good handle on that one and have been providing input. We have a prototype in Chrome. Today the WG agreed to handle display:contents cases, but, some of the weirder/harder edge cases don't make a lot of sense to bend over backwards for. It comes down to this: you can have intervening display:contents ancestor between the reading container and reading items, but only DOM siblings can be reordered relative to each other. Anything else causes problems.

[aardrian]

Are you saying we don't need to spend time with the CSSWG folks for CSS reading order?

[aleventhal]

We probably really don't. I don't think there will be anything worth using everyone's time on in a big meeting.

[aleventhal]

Maybe we can try having me a give a summary before TPAC on a call and see if anyone sees a blocker that needs wider discussion. It's a good feature for a11y and the only friction was how to deal with weird cases without breaking browser a11y impls.

[smhigley]

I'd like to propose a session on interactive lists to discuss a more specific proposal that I will write sometime in the next week and then link here :D