Is there any possibility of aria-query adding an accessible role for the summary element? As the native, accessible, JS-free solution for "Accordion Components", the details and summary elements are incredibly important when it comes to testing web apps (for instance, with the Testing Library tools or with Playwright). As I pointed out in Playwright's Repository, many user agents are already giving the summary element some kind of "button-like" role in the end. So it would be great if aria-query could expose summary elements as buttons too.
Is there any possibility of
aria-queryadding an accessible role for thesummaryelement? As the native, accessible, JS-free solution for "Accordion Components", thedetailsandsummaryelements are incredibly important when it comes to testing web apps (for instance, with the Testing Library tools or with Playwright). As I pointed out in Playwright's Repository, many user agents are already giving thesummaryelement some kind of "button-like" role in the end. So it would be great ifaria-querycould exposesummaryelements asbuttons too.That said, I don't know how
aria-queryfeels about agents driving the role instead of the spec.(Note: I opened this as its own issue since #44 didn't seem conclusive.)