Details do not benefit from aria-pressed

Reran tests and they failed still.

Looking at some recent examples, including Scott's above, I'm not sure that we need any aria for the detail/summary. There was an outstanding bug for NVDA, but I think that's been resolved now.

Some follow-up links:

• https://blog.learningtoo.eu/expanding-summary-details-accessibly
• https://dequeuniversity.com/library/aria/expand-collapse-summary
• https://www.hassellinclusion.com/blog/accessible-accordions-part-2-using...
• https://developer.mozilla.org/en-US/docs/Web/HTML/Element/summary

Wouldn't it be nice if we could just get it down to very basic HTML - <summary class="claro-details__summary">

Dropped testing for the attribute that got removed.

Taking #5 as accessibility sign off then :)

Oh splendid. I have an open ticket to remove this attribute from our themes, as it confuses VoiceOver into announcing the summary/details as if it is a form element rather than a fieldset.

This will do nicely.

I'm triaging RTBC issues → . I read the IS, the comments and the MR. I didn't find any unanswered questions or other work to do.

There is support for this change from an Accessibility topic maintainer, #5.

Leaving at RTBC.

Agree that from reading the docs aria-pressed indicates the pressed state of a toggle button, and while <details> could be considered a toggle button, the value of aria-expanded would seem to have more relevance. As these are always the same value then removing aria-pressed makes sense.

Backporting to 10.2.x as an accessibility fix.

Committed and pushed 91a743c141 to 11.x and 5d5a43b86f to 10.2.x. Thanks!

longwave → closed merge request !5497

Automatically closed - issue fixed for 2 weeks with no activity.