8 ms·
The core problem with hamburger menus
- stevelini 4y agoI was expecting to read something about McDonald's. Now I feel stupid.
- moritzwarhier 4y agoNice, skipped the headline yesterday. Today this blows up with >200 comments and I thought the article must be about how fast food chains rip people off. Time to go outside. To contribute something: I feel that some more refined approaches of dealing with limited space are emerging. Also I see less and less collapse-hamburger-hell on desktop, where the space is actually available in the plenty. There is one problem that is not solvable by technology: invest a lot of time, energy and expertise into organizing your content to make digestible pieces. Especially regarding how many subpages you have, their name etc. I also feel that multi-level mega menus are on their way out, making room for more thoughtful forms of site organization. There will always be tradeoffs. You cannot show all content at once (or you shouldn't). But indeed, less pages with more content on them, landing pages instead of multi-level navigation, both can help to clean up a sitemap. Then show your most important pages immediately, if you have too many, make each of them a "landing page". For menus in web applications (not just websites) with lots of actions, plenty of alternatives to the hamburger exist. E.g. horizontally scrollable menu bars with "..." instead of the hamburger. Or just lists of links and buttons. Design them in a nice way, then there's no need to hide them.
- wkat4242 4y agoohhh I agree sooo much with this. And also, the very concept of hiding "complex" options under a "more options" option. Windows 11's new right-click menu in the file explorer is one such example. Every time I had to press "refresh" I now have to do two clicks instead of one. Because someone at Microsoft feels like I should be punished for wanting to do something not many people do all the time. Luckily this particular nonsense can be switched off in the registry. But many can't.
- fuzzfactor 4y ago>Microsoft feels like I should be punished for wanting to do something not many people do all the time. Maybe it's more like something they would not like people to miss if the more powerful options go away in the future.
- bbarn 4y agoThis was infuriating until I found the hack work-around. It's not just "complex" things - it's any context menu extension you may have used for a decade hidden behind that wall. In my example, it's "Edit with Notepad++". Is that a "complex" use case for most people? No, it's just Microsoft trying to force you to do things their way with their tools.
- PcChip 4y agoI 100% agree with you, but fyi you can just hit F5
- wkat4242 4y agoI can't believe I never tried that lol. Thanks!
- scrollaway 4y agoI don't think the alternative "just put everything in the footer" is always acceptable. A site with simply "Home", "About us", "Contact" + a wide logo already has too many links for a portrait orientation small-screen device. You can get around it by finding a square version of the logo and shrinking stuff but it's not necessarily pretty.
- onychomys 4y agoThey're lousy in very specific use cases, but there's clearly some reason why every website in the 90s had a footer menu and now they all have hamburgers instead. Is it all just 100% because they're cleaner looking? Or is there some actual usefulness reason for the switch? I don't know enough about the space to have an opinion on it, but there's obviously something at work here.
- prenoob 4y agoMobile changed UIs profoundly, screen real estate is at a premium and that's how we got to hamburger menus
- Andrew_nenakhov 4y agoNo. Use hamburger menus where appropriate if you feel that this is the best way to offer additional options.
- cosmotic 4y agoIt should not be based on what YOU (the developer or designer) feels, it should be based on user research. User research shows hamburger menus are bad.
- Andrew_nenakhov 4y agoOne of the companies I own (rather smallish one) creates commercial websites. Hamburger menus work just fine according to our research and a/b testing, sometimes superior to other navigation methods, sometimes not. YMMV.
- usr1106 4y agoDoes your research and a/b testing cover users that access the site via a screen reader?
- Andrew_nenakhov 4y agoNot really, unfortunately. Very few customers require good UX with a screen reader, and we certainly can't afford the expenses necessary to research it on our own initiative. To be honest, I didn't even think about it until now, but since you mentioned it, I'll ask my design team to do a small-ish research and in the future try to build navigation better accessible for people with impaired vision. I'll hardly be a top-notch experience, but at least we'll try to pick the lowest hanging fruit.
- usr1106 4y agoI was not the first to mention it, the submitted article was.
- 4y ago
- psygn89 4y agoThe only thing I would change is calling it "Menu" instead of "Sitemap" at the top. Saves more space and is understandable by all.
- droptablemain 4y agoI'm not aware of any overwhelming disdain for hamburger menus among users. I'm all for accessibility improvements for sure, but at some point there has to be discussion about the trade-off of making something worse for 98% to accommodate 2%. That doesn't really make sense in general.
- SoftTalker 4y agoWell in the beginning menus were always at the top of the page, or split between the top (horizontal) for main sections, and left margin menus for section-specific menus. Then we got various trees and drop-downs and expandable widgets, as browsers and technology became more capable of supporting them, eventually sort-of-standardizing on hiding it all behind the hamburger icon. Now we want menus in the footer? Maybe I'm too old but the bottom of the page is the last place I look for anything.
- etchalon 4y agoWhile Hamburger menus are terrible, users have come to expect and look for them. Accessibility issues aren't unique to hamburger menus. Bad developers will implement all sorts of design patterns in in-accessible ways. There are ways to implement hamburger menus with good accessibility. We do it a lot.
- kid64 4y agoThe author challenges you to demonstrate this.
- legitster 4y agoEh. I've come around on them. In 2015 I might have agreed. But they clearly caught on. We now have enough data that shows users know how to use them, and in many cases prefer them. There's even one built into the Xbox controller for crying out loud. I won't begrudge the purists out there who find creative ways to avoid assimilating. But, uhhhh, I don't think this confusing footer link trick would actually win out in a UX test in 2023.
- jmartrican 4y agoIts also a key on keyboards. https://en.wikipedia.org/wiki/Menu_key https://en.wikipedia.org/wiki/Menu_key
- panzi 4y agoAlso on the Amazon Fire Stick remote: https://m.media-amazon.com/images/I/51Da2Z+FTFL.jpg https://m.media-amazon.com/images/I/51Da2Z+FTFL.jpg
- codetrotter 4y agoTbh the keyboards at the time when the hamburger menu first showed up had symbols quite different from the symbol of the hamburger menu. And at the moment that symbol still looks different in the same way. Perhaps eventually keyboards will begin to use the hamburger menu symbol on the menu key. Probably a few do already. But I mean most keyboards. And also the hamburger menu symbol is not so much different from all of the other “mystery meatballs” (as Lynda Weinmann called them, many many years ago) that we all know and love. Today I expect that most people will be able to recognise and know how to use the hamburger menu.
- NoZebra120vClip 4y agoMy ThinkPad for Windows has no Menu key at all. Needless to say, my brand new Acer Chromebook definitely has no Menu key, much less a Hamburger key.
- bombela 4y ago
- actuator 4y agoI have less of a problem with web UIs but when this sort of minimalistic design starts invading even washrooms, that's where I draw the line. There are no door handles for cubicle doors, you have to push them inside after seeing the separation lines. The first time I went to such a washroom, I was confused where should I enter from. The paper towels are hidden behind the mirrors, if someone pulls and the next one doesn't flow down, you really will have no way of knowing the paper towels were there. There are many other such things. I get that minimalistic design looks clean, but do you know what's better, accessibility.
- kabdib 4y agoThere's a phrase for this that I've heard used by architecture critics. "That building probably won an award." Who cares if there aren't enough elevators, or if the cooling system can't keep up with insolation, or if windows fall out or plumbing is always breaking down. That pretty glass box with the innovative lobby won an award! (And now we have to work in it...)
- crazygringo 4y agoI agree on them being confusing, but to be clear that's not copying a hamburger menu. That sounds like it's copying what are often called "handles", "grab handles" or "drag handles" in UX -- the close-together lines or dots in UX elements that indicate something can be dragged, a friction surface you can hold on to [1]. They mimic the grooves on a plastic cover for the battery compartment of a remote control, for example. But those are universally understood to indicate sliding, and should never be used for push/pull. That's literally what "door push plates" are for [2]. [1] https://ux.stackexchange.com/a/25696 https://ux.stackexchange.com/a/25696 [2] https://www.google.com/search?q=door+push+plate&tbm=isch https://www.google.com/search?q=door+push+plate&tbm=isch
- methodical 4y agoI don't understand this take at all. Why would you bury your navigation on your (hypothetical) marketing site in the footer on mobile? Most users don't even scroll far enough to make it to the footer and they certainly wouldn't expect the navigation there.
- DaveSchmindel 4y ago> The biggest headache when coming across these menus on the web is the complete disregard for accessibility.
- methodical 4y agoI read that part, but I don't think trading off massive amounts of usability for the majority of people to slightly increase the usability for the minority is the right decision in almost any case.
- twelve40 4y agoplacing the links at the bottom is very bizzare and not a great improvement to accessibility because nobody in the world expects those links there and its hard to even scroll there. If one is worried about accessibility maybe have both, why not, because I found the footer to be less intuitive and convenient.
- usr1106 4y agoIt's easy to scroll there. Just click the link at the top. Did it on my 10 year old mobile phone and it worked. The blog post says users are conditioned. That's exactly the problem. The author hopes that users would be conditioned to find a site map at the bottom. I have the feeling 15-20 years ago in the ages of pure HTML that was more common. Nowadays 99% of the users don't learn that. It wouldn't be hard or impossible to learn. It's just that marketing driven design for fancy UI has ruined accessibility because those user have no voice.
- tsimionescu 4y ago
- mmphosis 4y agoOffer a consistent menu system. Offer a choice of one of: Menu bar, Hamburger menu, ... Right now I have: * a Global panel that looks like a global menu bar but isn't. * Menu bars usually displayed in each window. I had to right click the Hamburger with my one-button mouse and click the check box for Menu bar. * a Hamburger menu displayed off to the right side that I can't hide.
- morkalork 4y agoThe worst is when an app has multiple levels of hamburger menu or "⋮"/"..." buttons. I'm always opening the wrong one! Looking at the git panel in vscode, I see 4 different clickable "..." buttons stacked above the each other, its terrible! It's like a designer decided to make a UI with only "OK" buttons and no other labels.
- laweijfmvo 4y agoThe footer on this simple page is atrocious. Seems like a not-great alternative IMO.
- poniko 4y agoI always say to my peeps, if you have stuff you don't want users to find/use then put them in a hidden menu.
- jahlove 4y ago> Cons: Footer can become large with many links (although I really don't see this as a big deal) Also: you now have to scroll all the way to the bottom of the page to navigate to other parts of the site?
- mrozbarry 4y agoMy only real gripe with hamburgers is inconsistent implementations with various "works on browser X and Y, but not Z." On top of that, not many (or no one?) has take advantage of publishing web components that aren't framework-dependent, so not only are there inconsistent implementations of hamburgers, some implementations require managing multiple js/css frameworks.
- VoodooJuJu 4y agoUnfortunately, not going to happen. Even though they were a bad idea ten years ago, and still a bad idea now, with them being forced down everyone's throats over the course of a decade, they've become a standard that users expect and understand, much to their chagrin. It's a a nice case study, as with ipv6. You can ignore the needs and wants of your users, force-feed them crap, and as long as you standardize that crap, the user will eventually submit, for better or worse.
- amadeuspagel 4y agoThe most basic aspect of the hamburger menu, which the "sitemap footer" lacks, is that it toggles. You click on the hamburger icon to open the menu and then you click the same icon in the same place again to close it.
- pcurve 4y agoYou know what gets me... is, when web sites only show hamburger menu in desktop viewport despite having plenty of space. I would try to enlarge the browser window to see if the full menu shows. Nope.
- mgaunard 4y agoI wished I knew what a hamburger menu was.
- hoppyhoppy2 4y agohttps://en.m.wikipedia.org/wiki/Hamburger_button https://en.m.wikipedia.org/wiki/Hamburger_button
- chiefalchemist 4y agoMaybe. But not on my "Please God Make It Stop" list. - Stop using hovers when there's no indication I need to hover to see what I need. - Stop using hover that requires mousing over a limited sweet spot (else the nav closes) - Stop with your over zealous forms. - Stop with your forms that give ambiguous errors. - Stop with the loading spinners for pages that aren't that content heavy Etc. - Stop having required form inputs and not making that clear.
- spinbutton 4y agoHow is having a button that jumps you to the bottom of the page different than a button that opens an offscreen menu? I'm not sure this argument scales particularly well.
- dinkleberg 4y agoUsing a footer as a replacement for a nav bar is ridiculous. Which requires more interaction? Clicking a button to see available actions or scrolling all the way to the bottom of the page (and making the bold assumption that you happen to know that the menu is at the bottom)? If you’ve got sufficient space at the top of your page to show your nav items, especially for larger window sizes, just show them instead of hiding them away behind a menu. But if you have limited space, like on mobile, a hamburger menu is a fine solution.
- scotty79 4y agoYou could always put a link at the top that will scroll you down to the footer menu. If you do it the simplest way possible the back button will bring you back to where you were if you change your mind.
- tobr 4y agoIt’s not ridiculous. Look at how it’s done on the page itself: a link to the footer in the header. I’d argue that the word “sitemap” isn’t a great choice for the link text, but the interaction itself works ok.
- waboremo 4y agoIf we're using this page as an example, they could have fit the entire navigation menu at the top of the page just fine. If it's pointless even at this small scale, what good is this going to do implementing on larger platforms like Amazon? I agree with the "stop resorting to hamburger menus so fast" take however.
- WWLink 4y agoI agree. Start using Taco Menus!
- Nijikokun 4y agoThis doesn't work for infinity loading. Hamburger menus are often fine in practice and work like every application settings menu anyway.
- noelbautista91 4y agoOne look at a the footer option (not disagreeing with it, btw) and I can already see product and design teams crapping on it. Product usually wants something to look familiar. "Can we make a website like _pulls up phone_, I want ours to look modern".
- kzrdude 4y agoI use linux and hamburger menus in Gnome is one of the greatest tragedies. The global menu bar in macOS is a really nice thing, it's steady. It's a shame several linux DEs now have a top bar but none of them use it in this useful way.
- rickstanley 4y agoKDE has a Global Menu plasmoid. Unfortunately it falls into the plasma's discoverability pit. Even if it did not fall into this, there are non-QT apps that don't export its menu to the DE, for instance: Firefox (https://bugzilla.mozilla.org/show_bug.cgi?id=1419151 https://bugzilla.mozilla.org/show_bug.cgi?id=1419151).
- karaterobot 4y ago> The biggest headache when coming across these menus on the web is the complete disregard for accessibility. It's not clear to me how a hamburger menu is, by itself, an accessibility issue. It can be implemented in a way that makes it inaccessible, sure. But, if properly labeled, etc., what is the intrinsic difference between a hamburger menu and a dropdown menu? > So instead of just whining about hamburger menus, I will actually offer up a solid replacement: sitemap footers. Simply place all your website/application links into the bottom footer and link directly to them from your header. Ha ha, no. Now I understand that the author is approaching this from a narrow perspective: they're thinking about only navigation links, and only on fairly simple websites. A complex website, or a web app that uses hamburger menus to hide less commonly used actions, could not follow this strategy.
- chadlavi 4y agohere's a better idea: stop having unilateral rules about menu layout. Different use cases require different layouts and interactions. You could maybe say "don't just default to hamburger menus."
- tetrisgm 4y agoOh yeah, let's drop Google's design language that they enforce in every app, and instead use a bespoke system. That would be suboptimal in terms of ensuring users feel familiarity, even if this was a good design. The suggested alternative is one that requires scrolling down to the bottom of the page. Good luck scaling this. UX isn't just prettier solutions, sure. It's also not just finding solutions that are more elegant in a vacuum. People have an embedded expectation of the design language of things. You know what a glass of wine looks like, and what a glass of water looks like. If you start making up your own solutions, it needs to acknowledge those expectations. Otherwise it's not UX, but performance art.
- hulitu 4y ago> Oh yeah, let's drop Google's design language that they enforce in every app, and instead use a bespoke system. The problem with "Google's design language" is that only Google speaks that language.
- leepowers 4y ago> "But I Have No Choice!" > I see this argument pop-up frequently when taking to design leaders or developers. I call bullshit on this excuse. You absolutely have the choice to avoid implementing bad designs - that's your job! Either you're not fighting hard enough against those pushing for it, or you're just trying to build a "pretty" portfolio. sigh I'm so tired of this absolutist, ranty way of thinking. Its indicative of Twitter-brain or social media outrage brain. Design is almost always a collaborative process. You literally have no controlling choice on the outcome, because the choice itself is being made by multiple stakeholders, be it your customers, your coworkers, your clients, etc. Also, the author lists himself as the "UX Designer & Front-End Engineer @ Donorbox." Their web site at https://donorbox.org https://donorbox.org appears to be using a hamburger menu on mobile. I hope he isn't beating himself up over it. It's hard to move away from established UI patterns like a hamburger menu because stakeholders expect it, and I suspect users look for that little hamburger icon as well.
- lezojeda 4y agoIt also has the typical annoying dialog open 2 secs after opening the page.
- lostgame 4y agolmao, as if the designer is in charge of what they’d like to do 90% of the time.
- dylan604 4y agoand thank the gawds for that. it's like letting the Jony Ive types rule the world.
- permo-w 4y agoyeah this is an odd article. hamburger menus are not perfect, but they do the job and they’re expected by the user, which is important in UI this article’s main justification for them being poor is that they don’t work well without a mouse and/or when you have javascript turned off. okay there are times and places and people for whom javascript will be off, that’s understandable, but still rare. who is browsing the internet with just a keyboard though? they’re fixing an issue for the vanishingly few by worsening the experience of overwhelming majority, and acting as if this is an obvious solution that developers are too blighted to see
- d--b 4y ago> Best Alternative: Sitemap Footer These authors ought to ask themselves: if all websites using a hamburger menu were to be concerted to sitemap footers, how many people would write blog posts about how shitty this design is?
- marginalia_nu 4y agoI think the main thing is that hamburger menus are stupid on desktop. It's a symptom of attempting to build hybrid interfaces for both mobile/touch and computer screen/mouse+keyboard by basically ignoring the affordances of the latter altogether. When pixels aren't scarce, [𐄒] is a menu but strictly worse. Desktop interfaces don't have a pixel shortage. Like at all. Replacing text+icon buttons with cryptic line icons in general means your users have to learn to decode Linear B to use the interface like it's a Myst puzzle. The design choice is strictly a bad trade-off on desktop. If you're on mobile, where pixels actually are scarce and input precision is low, it makes sense though.
- wolpoli 4y ago"Mobile first design" calls for designing for mobile first, then adopting for desktop second, if there's time anyway. >Desktop interfaces don't have a pixel shortage. Combined with designers adding more and more padding, attempting to fit 2 web sites on desktop on a 1080p monitor ends up triggering mobile design anyway.
- IshKebab 4y agoExactly this. I kind of understand if you want a design that works the same on mobile and desktop. And very occasionally I think it might make sense, e.g. in browsers. The real head scratcher is Gnome. Why are they moving from normal menus which work very well to hamburger menus for apps which have plenty of space and are desktop only? I guess it wouldn't be the first time the Gnome people have made inexplicable UX decisions. Maybe it's just too boring doing the thing that we know works and they want to try new worse things?
- _kst_ 4y ago> When pixels aren't scarce, [𐄒] is a menu but strictly worse. The character in the square brackets is "AEGEAN NUMBER THIRTY", U+010112. It doesn't display in my browser (Chrome on Windows). Oddly, it does display in my xterm, though that's likely to depend on which fonts you're using. (It's three horizontal lines.) I presume most hamburger menus use an image.
- 4y ago
- lwansbrough 4y agoWe've got a pretty large mobile app (hundreds of screens)[0] and we've so far resisted the urge to add a hamburger menu. Hamburger menus are particularly bad with modern screen sizes and force the user to make a physically uncomfortable action by stretching their thumb or adjusting their phone in their hand to reach it. It comes down to understanding what exactly your users are trying to do and developing contextual UI based on the few primary flows. In our case, our main nav at the bottom exposes the most high priority features, and additional pages can be found in the "More" menu. The More menu is functionally similar to the Hamburger menu, but varies in a couple key ways: it sits bottom right of the device, which is much more reachable, and it doesn't include items already shown on the main nav. [0] https://play.google.com/store/apps/details?id=network.tracker.app https://play.google.com/store/apps/details?id=network.tracke...
- codetrotter 4y agoI was gonna criticise OP for how many times I would have to press the tab key to get to his footer navigation menu but then I actually tried to navigate his page with just the keyboard and I have to admit it's pretty good. If you have a lot of links mentioned in the article text then it might become more uncomfortable but OP solved that by having a link in the top of the page that will skip to navigation. Would like to hear from screen reader users how OP's page works for them. I expect that the navigation experience is good for them too. And in general the bottom navigation is a pretty good idea actually. Most websites I land on I land on via links from elsewhere and I am initially not interested in navigating the page. But if I read a good article on some page and I want to explore more then it is convenient that the navigation is at the bottom because I just finished reading the article, and it also avoids the awkwardness of hamburger menus that arises when the hamburger menu content is too big to fit so it either might not scroll at all, or it might scroll in a weird way. In conclusion, OP has a valid point and I will use more footer menus and less hamburgers in the future.
- waboremo 4y ago>OP solved that by having a link in the top of the page that will skip to navigation. Just tested that, and it doesn't skip to navigation. It scrolls down, but the next tab is still the links in the content.
- FinnKuhn 4y agoand it breaks the back button by doing that :D Hamburger menus are fine for mobile devices where space is limited and for desktop devices just use a normal nav bar instead of this mess.
- codetrotter 4y ago> it breaks the back button No it doesn't. One extra step back is not "breaking the back button" when you explicitly have clicked an inline link. That is your browser working as intended.
- codetrotter 4y ago
- ghstcode 4y agoWhy? They work just fine.
- cmdialog 4y ago[dead]
- ghusto 4y agoHonest question: What problem did hamburger menus solve? I remember menus before. They were there, they were obvious, and they didn't need someone to explain them to me. The first time I was on a site with a hamburger menu, I'm not embarrassed to say that it to me _minutes_ to figure out what it was. I see how they're not as obvious, and would make that trade if they solved some serious worthwhile problem, but what was that?
- JohnFen 4y agoIIRC, they came about because of smartphones having limited screen space which made normal menus problematic. In that view, I understand them even though they're terrible. I just wish they'd stay on smartphones and not appear elsewhere.
- Brendinooo 4y agoYou need your menu design to work at every viewport width between 320 and 1900+. So if you want to have your top level items on the screen at all times: 1. You have to decide if your top-level menu will be dictated by the smallest width or not 2. If not 1, then you have to decide what will happen when a lot of menu ends up in a smaller space. Do you wrap it (and risk using up your "above the fold" space on menu items) or do something that requires scrolling/opening submenus? Also, whatever design you come up is almost inevitably messed up after handoff, when the client adds a word to a top-level item or adds five more top-level items. Hamburgers solve this by giving up a bit of usability and gaining a ton of screen real estate to work with as a result. As a designer-turned-developer, I've warmed to them over time, as has the Internet at large. If it helps, maybe consider them as a "the worst solution, except for every other solution" sort of thing. It's a pragmatic choice. And it's not like menus aren't a common paradigm of computing anyways.
- ghusto 4y agoThanks, it makes sense now. Basically needing to play down the the lowest common-denominator :/
- SebastianKra 4y agoIt's ironic that I confusedly searched the header for links to other parts of his blog, before realising that he had actually followed his own advice and put everything in the footer. Man, I hate these broad reductive arguments. They never consider the trade-offs and focus on a single arbitrary principle. Once you actually try to design something, you'll realise just how many conflicting requirements need to be juggled. I don't agree that hamburger menus hurt accessibility. I've never seen a user confused about them. I can navigate them just fine with the keyboard [1]. Further, they match how I interact with most marketing- & news pages. I first scan the landing page for useful details, and then look for specifics in the menu. Having this list at the bottom of the landing page would require scrolling. Having all the links visible at the top would make it harder to get through the landing page. The trade-off presented here forces you to loose your scroll position every time you want to access the menu. [1]: Don't forget that Safari requires holding down option to focus links
- jnwatson 4y agoThe hamburger menu is the junk drawer of UI. It is where you put everything that doesn’t have a place.
- gwern 4y agoWhich is itself OK. It's not always possible to put things in a place. The problem is when people hide away the important things in the hamburger menu, even when they have plenty of unused space. Which begs the question: if it's so useless that it can't even be allowed to be visible lest it take up a bit of screen real estate, why is it useful enough to include in the hamburger - or exist?
- fauntle 4y agoArticles like these are always good for the humor, at the very least. There's a reason hamburger menus are in use everywhere, and it's not because we haven't read your blog post.
- DoneWithAllThat 4y agoIf the “core problem” with something is that they’re mildly inconvenient for a tiny fraction of users that’s not really a compelling argument of there being a problem at all.
- Eliah_Lakhin 4y agoWell, the Footer Sitemap maybe was not that good idea, but why not consider the Header Sitemap instead? HackerNews menu looks good to me. If the Sitemap structure is too large to be in the Header, maybe it's a good marker to think about reducing the amount of information on your website in general. Also, I like to have sidebar menus on the left or right of the page for quick navigation, and when I see the webpage on my home widescreen desktop monitor, or maybe even notebook. But I don't like clicking Hamburger buttons each time to expand them. So, personally, I'm fine to always have such menus stay expanded on Desktops, and to be completely absent on mobiles. If I use the mobile device, I'm acknowledged that it's functions are limited by design.
- throw-4e451c8 4y agoMy 80+ mom still doesn't get hamburger menus in e.g. bank apps even though I've explained them a few times. They are obviously a discoverability fail. Meanwhile she's surprisingly proficent at using Google and the mobile web non-logged in/preview version of Facebook to read gossip from the village she lives in, sometimes in very creative ways due to limitations FB put up for anonymous browsers. (She refuses to get a Facebook account.) No undiscoverable hamburger menus involved in the navigation sequence above. I think Google and FB get it.
- techn00 4y agoWhat do people think about a sticky footer on mobile? Easy to access & familiar
- yuters 4y ago> It seems like most people don't actually like hamburger menus. Is there a source for this? If there was a poll or something I'd be curious to see.
- cmdialog 4y ago[dead]
- JohnFen 4y agoI still don't understand why hamburger menus are a thing. They check just about every box for "bad UI design".
- xkcd1963 4y agoI'm a webdev and put out websites 1:1 to the designers creations, but my private projects have little to nonexistent css, just plain text everywhere, no hidden objects. Sometimes when working on designs I have brainfog events like when you watch a movie and the cutting is well done, you don't notice the cut. I imagine it is similar with designs, a good design hypnotises the user, even though objectively it is unpractical.
- iambateman 4y agoThe core problem is that they demo super well. There are a handful of tricks that help sell a design for a client, and one of them is hamburger menus. Along with background video, scroll jacking, over the top parallax, and (cliche) large logos, they make up a quiet set of ways to get a dev out from under the thumb of an irritating client…at the expense of an actually great website. Ask me how I know.
- INTPenis 4y agoWatching my 80 year old dad use Google Photos web UI on his desktop computer I realize that hamburger menus, or three dot menus, were meant for small screens where realestate is at a premium. On large enough screens they should be words like "Options", or "Menu".
- uzername 4y agoCertainly an interesting take with the footer as the nav. It could work on information centric sites. It might seem strange working in a web app or a hybrid environment, where portions of the site lean towards app while others don't. Looking at the comments here, that's highly skewed towards desktop use, guessing at the HN audience here, skilled with computer usage and decent handlers of visually dense information, I think most common users aren't like that. Many are using smaller screens, many are on mobile the majority of their computing time. When they do have larger screens, their glaze over when there's too much to look at (I think because they're not used to it, and too busy to ever get used to it, but either way). All of that to say, the hamburgers aren't for us, they're for secondary flows for common users.
- Pxtl 4y agoThe fact that this is an article about design-language that contains zero pictures speaks volumes about the author's perspective on the subject.
- Eduard 4y ago> The biggest headache when coming across these menus on the web is the complete disregard for accessibility. Just because most websites / frontend frameworks fail to implement hamburger menus in an accessible way (including Bootstrap 5), does not mean that hamburger menus in general are bad when it comes to accessibility. With that logic, images / img elements are a core problem per se and should be prohibited, because most pages don't use them correctly from an accessibility standpoint (e.g. forgetting to provide an explicit "alt" attribute). WCAG / WAI has pretty good recommendations in how to achieve it. Here is their hamburger menu pattern example: https://www.w3.org/WAI/ARIA/apg/patterns/menu-button/examples/menu-button-links/ https://www.w3.org/WAI/ARIA/apg/patterns/menu-button/example...
- chrismorgan 4y agoMy natural inclination was to say “so hamburger menus can be implemented badly, but they can also be implemented properly so this is no reason to advise against hamburger menus as a whole”. But I think it’s also worth remembering that patterns matter, and if almost everyone gets something wrong, it’s small consolation that it was an unforced error. If a different pattern is similarly acceptable and done badly far less often, pragmatism suggests pushing the alternative, because the average result will be better. When I use hamburger menus on regular web pages, I implement them so that they’re entirely adequately accessible, and work with no JavaScript. (Depending on the situation, I’ll either use <details> or a checkbox hack with reasonable labels and such, and I may enhance things with a small snippet of JavaScript.) But I lack faith in almost anyone else’s implementations. I would note also that the ARIA example you link to fails one of the criteria of this article: JavaScript-free operation. It’s also only suitable for some sorts of hamburger menus; it’s unlikely to be a suitable pattern for website header navigation menus, which are really more a navigation palette than a menu (to use very fuzzy terms!), and which are the main focus of this article.
- joshspankit 4y agoI genuinely hope someone makes an Accessibility AI gets used by companies worldwide to fix their sites and webapps. There are so many great properties waiting to be implemented properly.
- me_bx 4y agoHere's another alternative [0], from a team well versed into usability and accessibility issues: "gov.uk Design System" puts the navigation at the top of the page inside their header component. > Use the header with navigation if you need to include basic navigation, contact or account management links. * A list of links is directly visible in wider screens * These are collapsed into the equivalent of a hamburger menu on smaller screens * The label "Menu" and a downwards-pointing arrow are shown instead of a "hamburger" icon * The possible interactions are highlighted on keyboard navigation (yellow border moves when Tab is pressed) * Degrades gracefully when JavaScript is disabled by leaving the menu expanded. I haven't taken the opportunity to check how this works with a screen reader. [0]: https://design-system.service.gov.uk/components/header/ https://design-system.service.gov.uk/components/header/
- arkaic 4y agoThe hamburger icon is certainly miles better than the harder to see three-dot one Chrome uses. Not sure why they ever decided that this was a better choice.
- bogwog 4y agoHow about a hybrid: Hamburger menu-type icon in the header, but it's just a URI fragment that points to a tag in the footer. Clicking it will just jump the view to the footer, which can be designed to fill the entire viewport on mobile so it looks like what people have come to expect from a hamburger button. An ambiguous up/back arrow will jump the viewport back to the header. CSS can be used to make it look like it's fancier than it actually is, without resorting to javascript. Jumping back won't work great for sticky headers, but that's a feature since it means you'll be less likely to use those awful sticky headers.
- pentagrama 4y agoI think the main issue with hamburger menus is the lack of labeling them, the icon + the label "Menu" improves a lot. Don't see the op solution convincing, but I will suggest always add a sitemap to footers.
- zichy 4y agoAs one user said before, this absolutist way of thinking is tiring. Hamburger menus can absolutely be accessible and I would have liked to read how to do so. Here's my take: * It uses valid HTML and JS. (You could also make it work without JS as a fallback and I love progressive enhancement, but it's not a requirement specifically for accessibility. Actually, JS can contribute a lot towards accessibility. * The toggle button uses either `title`/`aria-label` or visual text in addition to the ≡ icon. * The focus states are clearly visible for keyboard navigation. * The correct ARIA attributes for the interactive elements are used. * Depending on the menu, think about a focus trap/loop. Bonus tip: While I prefer using `<button aria-expanded>` since I believe it is more accessible for screen readers, you can also use `<input type="checkbox">` + `<label>`. If you have to do it this way, please do no use `display: none` on the checkbox input – this will make it unusable by keyboard. It should be only hidden visually.
- isomierism 4y agofor a moment i thought op was talking about hamburger restaurant menus like innout
- bariswheel 4y agoAlso a pain in the ass for left handed folks on mobile. Mobile UI's are atrociously inaccessible for left handed people like myself. Try it and see. Completely unacceptable.
- nonameking2026 4y agoI don’t like it when they have chicken and vegan options on menus either
- bendur_ 4y agoIt's really not that hard to build an accessible hamburger menu if you just test it out and don't make it overly complicated. A lot of design frameworks/templates are completely ridiculous in this regard though.
- paxys 4y agoSo I should have to scroll all the way to the bottom of every page to navigate anywhere? What an idiotic "solution". Hamburger menus are fine. If they aren't accessible, that means they weren't implemented correctly. It is fully possible to use them perfectly with keyboards and screen readers just by adding some extra tags.
- Ylmaz 4y agoThis must be a troll.
- cmdialog 4y ago[dead]
- thecosas 4y agoI fully expected a sharp criticism of fast food menu design rather than UI design. Only one?
- PhasmaFelis 4y agoWhy does practically everyone in this comment thread think the author said "you should have to manually scroll to the bottom of the page to get a menu," when he said very clearly (with working example!) that a menu button at the top of the page should give you the menu (which happens to be at the bottom instead of inside a pop-out)? I mean, I know responding to titles instead of articles is a thing, but here it seems like everyone opened the article and then stopped reading at a very precise point in the middle of the fifth paragraph.
- xp84 4y agoI'm not sure* that the "just put everything the footer and link to the footer" is a solution I'd present seriously to the business stakeholders. The thing I really want to kill with fire is the "junk drawer" method of UI design. This has infested almost all apps, with a three-dot (••• or vertical ⋮ ) scattered literally everywhere in every UI. It says "We couldn't be bothered to build a thoughtful UI, or even to classify the types of actions you might want to perform into a few categories. Even with a full-screen window on a 5K monitor, we'd rather have a sea of whitespace everywhere than to just put the actions where they are visible, discoverable, and can develop muscle memory. I used to think about 15 years ago that a big problem was that developers and designers all used expensive high-res, large monitors and forgot that most users were on 1280x800 or (eek) 1280x720 laptop screens. Today it's the opposite direction with everything being optimized for tiny screens and minimal information visibility. I know "mobile-first" is important but (A) phone users want things to be visible just as much as desktop users do, and (B) the right design for a phone is almost never the right choice on a massive screen. *for an "application" - sure, it works great for a 8-page blog like the article. By all means. I just don't think it'll work for Expedia, Facebook, etc.
- Swalden123 4y agoThere’s a problem with hamburger menus, but this footer link system is a hamburger menu. You click a button to see a menu. Same interaction.
- julieturner99 4y agothis argument is long past its prime. hamburger menus are here. they have been here. and they aren’t going anywhere. could it have been better? probably. could it be still? maybe. will it change today? no.
- Dalewyn 4y agoI hate that those things are called hamburger menus. I thought this was about the menu monitors I see at McDonald's before I delved into the comments.
- mavu 4y ago> It seems like most people don't actually like hamburger menus. So why do we, as developers, keep using them in our products and designs? Oh my. what a great question. Simple answer: Because there are as many incompetent designers as there are incompetent managers, and we usually think "well, i guess he knows what he is doing" (yes. he. almost always) Spoiler: He does not. And modern UIs are full of actively unusable widgets, confusing displays, bad readability and are in a general state of "the emperors new clothes".
- zajio1am 4y agoThis is IMHO one of big fails of web, that navigation is not out-of-band browser feature (like it is for example in PDF browsers), but it is in-band part of a web page.
- dahdum 4y agoOh the irony of reading an article championing accessibility and design written in small pure white text on a near black background.
- luxuryballs 4y agoYou can keep your hamburger menu and still have the screen reader accessible links… they don’t even need to be visible!
- twobitshifter 4y agoResponsive, Pure CSS Off-Canvas Hamburger Menu https://heyoka.medium.com/responsive-pure-css-off-canvas-hamburger-menu-aebc8d11d793 https://heyoka.medium.com/responsive-pure-css-off-canvas-ham... These aren’t problems at all if you follow common practice and have the hamburger be a css styled list. It can be made accessible, usable with a keyboard, and vanish on larger screens.
- kid64 4y ago"built with barf"
- CaesarA 4y agoI was a little bit disappointed when I discovered which type of hamburger menu they were talking about, I initially thought this article was going to address issues with the common types of sandwiches provided by fast food restaurants. But otherwise, I agree with the points stated in this article. Although I would put my links in a <nav> section at the bottom of the page above the footer instead of inside the footer itself. Putting links in the header or the footer always seems to cause accessibility issues. Or better yet, I would put links to the two or three most prevalent pages of the site as well as a link to a separate sitemap page in a navigation section under the header, so it would be something like: "Home - About - Projects - Sitemap".
- berjin 4y agoSitemap footer is not the best idea since I lose my scroll position.