Menu (or not)
This article marks the third time I try …
Details / Summary Are Not [insert control here]
adrianroselli.comOnce major browsers started supporting <details> & <summary> developers immediately started to play with them to see what sorts of patterns they could enhance or replace. This is a good thing. Experimentation pushes boundaries, improves understanding. However, we need to be careful of christening this new-to-us interaction as the solution…
Why <details> is Not an Accordion
I learned something this week and I thought I would share it. Earlier this year I read Adrian Roselli’s post “Details/Summary are not [insert control here]”. In this post Adrian says <details> is not a tab set, it’s not a subnavigation menu, not a dialog, not an accordion, not a … wait, what? Not an accordion‽⁈
A details element as a burger menu is not accessible
Using the native HTML disclosure widget for a burger menu is so enticing. Unfortunately, the details/summary elements come with accessibility issues, so it's not an inclusive solution.
the details element and in-page search - Manuel Matuzovic
A quick note about the details element and in-page search.
Let's build an accessible disclosure (show/hide accordion) - FED Mentor
How to build an accessible disclosure pattern, like those used for mobile menus or accordions.
HTML: The Inaccessible Parts
I’ve always abided in the idea that “HTML is accessible by default and then we come along and mess it up.” In a lot places this is very true and by just using a suitable HTML element instead of a generic div or span we can have a big Accessibility impact.
Liskov's Gun: The parallel evolution of React and Web Components
Writing at the end of the world, from Hveragerði, Iceland