[Role Parity] What do we do about summary element?

[joanmarie]

No description provided.

[jnurthen]

As detailed at https://github.com/w3c/aria/wiki/Plans-regarding-role-parity#no-consensus-yet-will-do-for-1-3 moving to 1.3

[joanmarie]

Consenus: Button role with aria-expanded.

[scottaohara]

I am very well aware that I was the one banging on about how details/summary can be attributed to button aria-expanded=... ... due to the fact that HTML allows for summary to have heading and link children, but role=button does not (nor likely should), I'm not so sure on this one anymore.

Might we resurrect this issue one more time for discussion? Everyone is invited to throw snarky comments at me for my previous handwavy response to this issue.

[scottaohara]

related to:
#1174

[scottaohara]

linking w3c/html-aam#345

[spectranaut]

Discussed in last weeks meeting: https://www.w3.org/2023/06/08-aria-minutes#t05

[spectranaut]

To schedule for a deep dive after July 4th weekend, potentially July 27th

[jnurthen]

discussed at https://www.w3.org/2023/07/27-aria-dive-minutes

[scottaohara]

thought i posted this in this issue, but I did it in the html AAM thread so cross posting here:

From the ARIA WG deep dive today, there are presently two directions we could take this issue.

1. We create a new role (name pending) to represent a 'disclosure' control. This control would be similar to, for instance, tab and push/expand button roles - in that it's activation would toggle the display of other associated content. However, it would need to be different than those roles to account for the fact it would need to allow its own instances of structural elements (headings) or interactive elements (links / text fields, etc.).

2. We do not create a new role, but instead look to have browsers revise the shadow DOM of the summary element to be exposed to users as a button element with the arbitrary content that can be added to a summary element as a separate element which would provide the accessible name for the persistent button element. I created a codepen to demonstrate how this "could" be structured (again as far as the end user is concerned) - https://codepen.io/scottohara/pen/RwqQgML

3. We could go with another direction that someone could propose.

Thank you everyone for your participation / input in today's meeting.