3 ms·
FWIW This article is almost 4 years old. When it was written 3 years hadn’t passed since Firefox had full support in Firefox 48. Meaning that more time has pass
by runarberg 4y ago
FWIW This article is almost 4 years old. When it was written 3 years hadn’t passed since Firefox had full support in Firefox 48. Meaning that more time has passed since this article was published then the time between Firefox support and the publication.
- myfonj 4y agoYes, yet last update was last year and coincidentally mentions article "A details element as a burger menu is not accessible" Published on September 20th, 2022: https://cloudfour.com/thinks/a-details-element-as-a-burger-menu-is-not-accessible/ https://cloudfour.com/thinks/a-details-element-as-a-burger-m...
- runarberg 4y agoI don’t think we should take this article at face value. Putting a heading <h2> inside the <summary> is weird and the aforementioned article recommends against it (most experienced web devs know not to put headings inside interactive elements other then <a>). On top of that we have people in this threat that use screen readers and claim that they have no problems with <details>/<summary> which aren’t present in other elements[1]. 1: https://news.ycombinator.com/item?id=34547915 https://news.ycombinator.com/item?id=34547915