3 ms·

That popup menu is not accessible though, no keyboard navigation and if you really wanted follow all accessibility guidelines you still need javascript to toggl

• eldelshell 5y ago
  It also isn't a "pure" HTML solution as all the magic is happening on CSS. So, convoluted CSS or two lines of JS?
  • smichel17 5y ago
    As someone who browses with js off by default (uMatrix rule) and has implemented a fancy drop-down using css rather than js[1], my current opinion is that it's better to display all menus expanded by default and then hide them if/when your js loads. It's less effort to write and, more importantly, browsing with js disabled means I want interactivity off. If I want the "full experience as intended", I'll enable js. I frequently do. But I browse without it by default because frequently that experience is a downgrade from just the raw (well, styled) content. Leaving the fancy stuff to js suits everyone best. [1] please note the content on the page is outdated, this is just a prototype -- the drop-down below "PayPal": https://sdproto.gitlab.io/donate/ https://sdproto.gitlab.io/donate/
• Wowfunhappy 5y ago
  If a native html feature isn't accessible, that sounds like something the browser makers need to correct, no? (Although, you could argue the end-result for users who need accessibility features is the same, regardless of who is at fault.)