Scott digs into the historical past of the <menu> component. He traced it way back to HTML 2 (!) in a 1994 changelog. The vibe then, it appears, was to mark up an inventory. I’d suspect the intention is very similar to <nav> is as we speak, however I actually don’t know.
Brief story: HTML 4 deprecated it, HTML 5 revived it—this time as a “group of instructions”—after which HTML 5.2 deprecated it once more. Sort of a bummer because it has some clear use instances.
So, it’s been fairly the curler coaster for ol’ <menu>! There by no means appears to be any simple wins for HTML evolution. As of now, it’s in “don’t hassle” territory:
I actually wrote this submit as a kind of counter level to the usually uttered phrase “use semantic HTML and also you get accessibility totally free!” That assertion, on its floor, is essentially true. And also you ought to use semantic HTML wherever its use is acceptable. <menu>, sadly, doesn’t actually give us all that a lot, though it has clearly outlined semantics. Its meant semantics and what we really want in actuality are higher served by both simply utilizing the extra strong <ul> component, or creating your individual position=toolbar, menubar, and so forth.. Utilizing this semantic component, for semantics sake, is simply that.