[ { "doc_id": "doc-a8ba804db23fd7184b39bb1519118384", "title": "Offer Relevant Autocomplete Suggestions for Closely Misspelled Search Terms and Queries", "g_id": "1001", "url": "https://baymard.com/premium/guideline-collections/tz7qt0/1001", "source_type": "guideline", "importance": 100, "summarized_info": { "description": "Some users presented with no or inadequate autocomplete suggestions when they’ve misspelled a query abandon search, while others waste time trying to correct their misspelling in the search field.", "issue": "Users rely on autocomplete suggestions when typing queries, but suggestions often fail with even slight spelling errors Poor autocomplete suggestions can lead users to spend time correcting their misspelled queries, impacting their search experience If errors aren't noticed, the lack of helpful suggestions could lead users to believe that suitable products aren't available If their alternate product-finding strategy doesn’t quickly lead to relevant results this can cause users to abandon the site altogether", "advice": "Provide relevant autocomplete suggestions when closely misspelled terms and queries are entered in the search field Carefully monitor autocomplete query logs or search logs to identify misspelled queries and prioritize improvement effort", "summary": "Some users presented with no or inadequate autocomplete suggestions when they’ve misspelled a query abandon search, while others waste time trying to correct their misspelling in the search field.", "purpose": "" } }, { "doc_id": "doc-122b93886c40a40e774538a04a184b26", "title": "Have a “View All” Option in the Main Navigation at Each Level of the Mobile Product Catalog", "g_id": "1006", "url": "https://baymard.com/premium/guideline-collections/wqrbe4/1006", "source_type": "guideline", "importance": 100, "summarized_info": { "description": "Users often need to see a broad list of products at many different levels of the category hierarchy, but if they can’t easily navigate to such a list it’s harder to assess and compare items", "issue": "Users often need to see a broad list of products at many different levels of the category hierarchy, but if they can't easily navigate to such a list it's harder to assess and compare items", "advice": "In the mobile main navigation menu, have a “View All…” menu option (that includes the name of the category or subcategory) at each level of the category hierarchy and place it first in the list Avoid using only a tappable category name as a substitute for “View All” Avoid relying on multiple hit areas as a substitute for “View All”", "summary": "Users often need to see a broad list of products at many different levels of the category hierarchy, but if they can’t easily navigate to such a list it’s harder to assess and compare items", "purpose": "" } }, { "doc_id": "doc-cf6b523fdb3d1630bcab9b80ff95d4ff", "title": "Consider Having a “Sales” or “Deals” Filter-Based Category", "g_id": "1008", "url": "https://baymard.com/premium/guideline-collections/mwlwjp/1008", "source_type": "guideline", "importance": 100, "summarized_info": { "description": "Many users want easy and direct access to items that are on sale, but lists of on sale items can be difficult to find.", "issue": "Many users want easy and direct access to items that are on sale, but lists of on sale items can be difficult to find If attributes such as “On Sale” is implemented as a separate category users will be “siloed” and will have difficulty seeing the full product selection", "advice": "Consider having a “Sales” or “Deals” filter-based category — but ensure that it’s always implemented as a preapplied filter and not as a separate category or subcategory (though it can be presented to users as such) Decide whether to implement the 'On Sale' filter-based category at the top level or within relevant subcategories, considering the size of the product list and exposure Ensure comprehensive filtering tools when implementing the 'On Sale' filter at the top level to manage a potentially overwhelming product list Consistently provide the 'On Sale' filter-based category for all relevant product types if implemented within subcategories", "summary": "Many users want easy and direct access to items that are on sale, but lists of on sale items can be difficult to find.", "purpose": "" } }, { "doc_id": "doc-fcf2da512f11240d6ad60808651ed115", "title": "Return Users to the Same Place in Product Lists and Search Results when Returning from the Product Page", "g_id": "1024", "url": "https://baymard.com/premium/guideline-collections/buivs9/1024", "source_type": "guideline", "importance": 100, "summarized_info": { "description": "If users have to refind where they were in product lists or search results after returning from product pages, they may not find products of interest again and will become annoyed at having to redo previous work, and could abandon.", "issue": "When navigating back to product lists or search results from product pages, users expect to return to their previous position in the list — yet some sites take them to the top of the list This disorients users, and it can be tedious and time-consuming for them to refind their original position On mobile devices the problem is particularly severe due to cumbersome tab usage, smaller viewports, and slower pages", "advice": "Always return users to the same place in product lists or search results after they return from product pages Summary Summary Research Findingschevron-down Video & Quiz Review Tool Audit Performances Implementation Examples Benchmark Performances Changelog", "summary": "If users have to refind where they were in product lists or search results after returning from product pages, they may not find products of interest again and will become annoyed at having to redo previous work, and could abandon.", "purpose": "" } }, { "doc_id": "doc-fee4421d262830c2d91c834b91a3dc69", "title": "Consider Implementing “Quick Views” on Mobile", "g_id": "1032", "url": "https://baymard.com/premium/guideline-collections/vnxizq/1032", "source_type": "guideline", "importance": 75, "summarized_info": { "description": "When it is troublesome to move back-and-forth between product lists or search results and product pages, the resulting frustration may cause users to miss out on suitable products.", "issue": "When it is troublesome to move back-and-forth between product lists or search results and product pages, the resulting frustration may cause users to miss out on suitable products Mobile screens limit the amount of detail shown in list items", "advice": "Consider implementing ‘Quick Views’ on mobile sites If implementing a ‘Quick View’, ensure that the ‘Quick View’ can’t be easily mistaken for the product page by keeping the product list or search results visible behind it and providing a prominent link to the product page Ensure that the ‘Back’ button returns users to where they were in the list", "summary": "When it is troublesome to move back-and-forth between product lists or search results and product pages, the resulting frustration may cause users to miss out on suitable products.", "purpose": "" } }, { "doc_id": "doc-cafb3d382a370e81e94438c48245bf63", "title": "Include “Add to Cart” Buttons in Mobile Product Lists and Search Results for Low-Cost and Repeatedly Purchased Items", "g_id": "1039", "url": "https://baymard.com/premium/guideline-collections/vnxizq/1039", "source_type": "guideline", "importance": 75, "summarized_info": { "description": "Users who often repeat-buy items waste time having to go to the product page just to add such items to the cart.", "issue": "Users who often repeat-buy items waste time having to go to the product page just to add such items to the cart", "advice": "For low-cost, repeat-buy list items include “Add to Cart” buttons in list items and search results Ensure the “Add to Cart” buttons don’t interfere with users’ ability to effectively browse and get an overview of product lists and search results Don’t require users to confirm their additions (e.g., via a separate “Added to Cart” overlay)", "summary": "Users who often repeat-buy items waste time having to go to the product page just to add such items to the cart.", "purpose": "" } }, { "doc_id": "doc-251a6fbd82afdbc053d030e3febeb899", "title": "Support Users’ “Back” Button Expectations During Product Finding", "g_id": "1057", "url": "https://baymard.com/premium/guideline-collections/58zheo/1057", "source_type": "guideline", "importance": 0, "summarized_info": { "description": "The “Back” button is a crucial and heavily used browser feature during product finding, but when it doesn’t match users’ expectations of where they are “taken back to” it can take longer for users to find relevant products, or lead to disorientation or abandonments.", "issue": "“Aw man! I have to go all the way back, dang it! Okay, so what I did, I just swiped back with my finger assuming that it would just take me back to that jewelry page and it did not.” A participant at Ted Baker on a product page for earrings (first image) who swiped to return to the product listing from where she came was annoyed at being returned to the homepage instead (second image). She then had to navigate again from scratch to the jewelry subcategory (third image). “For some reason, it’s not letting me go back. Yeah, I don’t know. I keep getting refreshed. So I would just basically close that window and go there again, even though I’d have to provide the search criteria again.” When this test participant tried to “Favorite” a list item (first image), he was taken to a login page (second image). When he tried to back out of this page he was unable to, so had to start again with a new search. When “Back” buttons don’t function as expected, users sometimes come to a full stop. “How do I get back? Just press ‘Back’. Navigation, this isn’t great to be honest. And now it’s brought me back to the women’s. OK. Don’t like this.” In testing, what tapping or clicking “Back” buttons didn’t take participants where they expected to be taken caused a variety of issues, of wide-ranging severity — from a minor interruption and momentary sense of disorientation all the way to being a direct cause of a participant abandoning a product under consideration or a purchase during checkout. Arriving on what is perceived as an unexpected page can be a disruptive experience for users. For example, if a user exits an overlay on the product details page by tapping on the “Back” button, but is taken to the product list instead of the page they were on, they are forced to stop whatever they were doing to work out what has happened. Some users will recover quickly by simply navigating back to where they were. Others, however, may not realize what has happened and, in the worst case scenario, give up on what they were doing. Users expect the “Back” button to take them back to what they perceive to be their previous page. However, there can be a difference between what is technically a new page and what users perceive to be a new page — which can create discrepancies between where users expect the “Back” button to take them and where it actually takes them. Generally we’ve observed that if a new view is sufficiently different visually, or if a new view “feels like” a new page, it will be perceived as one — regardless of whether it technically is a new page or not. For example, if users click a link and 70% of the view changes to something new, most will perceive this to be a new page, even if it’s technically still the same page, just with a new view loaded in. During testing, issues with “Back” buttons were frequently observed when participants were interacting with 2 specific site features: Overlays Filtering and Sorting “Clicking on it takes me to another page with more pictures. Yeah so, oops, okay I thought it would take me to its [product page].” When this participant on AllSaints tapped the “Back” button to exit the image gallery overlay (first image), she expected to be returned to the product page. Being taken instead to the product list (second image) was a jarring experience and delayed the process of finding suitable products. This participant on Daniel Wellington used the “Back” button to close the expanded view image gallery, expecting to return to the main product page (first image). Instead, she was brought back to the previous product list (second image). 2 additional examples During an earlier round of testing, a participant at Gilt was presented with an overlay (first image). Clicking the “Back” button sent him back to the previous page, rather than exiting him from the overlay as he expected (second image). “What just happened?” Another participant in a previous round of testing arrived directly on a product list on Herschel and began to explore it. She was scrolling rapidly back up the product list when she inadvertently opened sorting. She tapped the “Back” button to close sorting, but this took her to the previous site she was on. Overlays are a way to create a new view that’s laid on top of the current page. It follows therefore that some users perceive overlays as separate pages and expect the browser “Back” button to bring them back to the page they were on. However, during testing, the many overlays did not close as the participants clicked the browser “Back” button but instead sent them back beyond the original overlaid page — for example, from an image gallery overlaid on a product details page to the product list. This expectation of “click ‘Back’, exit overlay” was observed during testing on both desktop and mobile sites, for all types of overlays. For example, site-initiated newsletter–sign up requests (see #284), image gallery overlays (see #2940), and prompts for live chat sessions (see #940). Thus, clicking “Back” should close the overlay and return users to the page the overlay was on top of and not the previous page. It’s worth noting that users’ likely use of the “Back” button to exit an overlay varies in proportion to how prominent the site-provided “Close” element is (e.g., an “X” to exit the overlay). Very prominent “Close” elements are likely to be used more frequently by users compared to inconspicuous “Close” elements, and thus the strain on the “Back” button is reduced when overlays have highly prominent “Close” elements. Of course, users should still be exited from the overlay when clicking “Back”, even if provided with a prominent “Close” element. “I don’t know how to get out of this…’Back’ button? So that took me all the way back to the hoodie-finding section [the product list].” A participant tried to exit an image gallery overlay by tapping the “Back” button (first image), but she was taken back to the product list instead (second image). (The site-provided “Back” link was actually hidden by the “Install App” ad; see #930.) During testing, we observed that mobile participants had more difficulty closing overlays using site-provided “Close” elements than those on desktop, often due to hit area issues (see #1083 and #1094), with the “X” often being placed close to the edge of the screen, or even an “Install App” ad covering a “Close” element (see #930). Thus, mobile users are more likely to use the “Back” button to close overlays compared to desktop users, and it’s even more important that their expectation of exiting the overlay is supported when tapping “Back”. “I’d just click ‘Back’…Oh, and that sends me all the way back.” While trying to undo the last sorting change on Greats by tapping the “Back” button, this test participant was taken back to the homepage and was therefore disrupted in the process of assessing products. A participant on Amazon tapped “Back” after applying 3 filters (first image) which removed the last-applied filter (second image). Most users expect that tapping “Back” after applying filters removes the last one they chose. 4 additional examples A participant in an earlier round of testing at Target opened filters to narrow down search results. Not seeing any he wanted to apply, he tapped the “Back” button to exit the filter interface. However, rather than bringing him back to the search results he was sent to the product page he was on before submitting his search. He then had to resubmit his search to get back on-track with looking for a men’s hoodie. When users tap “Back” from filtering or sorting interfaces that take the entire viewport, but don’t see their previous view, they become disoriented. “So I’m going to go back and — oh, it took me back to ‘Day Tours’. So I’m going to have to type that in again. There we go.” During large-scale Travel Tours & Experiences testing this participant at Gray Line Iceland searched for “whale watching”, and after briefly viewing a “Tour Details” page, she clicked the browser “Back” button to return to the search results. However, the search query was cleared, so she had to re-submit it. “I’m going to go back to look at the other whale watching tour, and — oh! It lost all of my settings, which isn’t the best.” This participant at Arctic Adventures applied multiple filters to the tour listings (first image). After he viewed a “Tour Details” page (second image), he decided to return to the listings to view another. However, when he returned to the tour listings, all the filters he’d applied were cleared (third image). He had to re-apply the filters multiple times while browsing the site, resulting in a tedious and frustrating shopping experience. This participant at Gray Line Iceland applied multiple filters and sorted the “Day Tours” listings (first image). He viewed a “Tour Details” page (second image), then decided to return to the listings to view another. However, when he returned to the tour listings, all the applied sort and filter options were cleared (third image). Applying filters or changing sort preferences generally yield an entirely new product list or set of search results and users are therefore likely to perceive each of these actions as a distinct “view”. Even when the filters or new sort orders don’t invoke a page reload as they are applied (see #486), we still observed that test participants generally perceive each discrete iteration of their filtering as a new view. This underscores how users don’t make technical distinctions between what is and isn’t a new page, but rather rely on what they perceive to be a new page. Filtering and sorting, of both category product lists and search results, should therefore support that users go back through each list state when using the browser “Back” button: applied filters should be removed as users click “Back”, and the sorting directions should also be changed to the previously set sorting direction (see #492). “I guess I’ll go back…” A participant in an earlier round of testing at JBL sorted a product list of headphones by price from low to high (first image). After exploring a product on a product page, she decided she wanted to keep browsing, and tapped to go back to the product list (second image). However, she tapped twice: this led her to be taken back to the product list and also changed the sorting direction — but the sorting direction was only changed on the back end, as the sorting direction still read “Price: (Low To High)” (third image). As she said, “The filter [sorting direction] took away even though it says it is still working…They are not in filter [sort] order…The ones I was looking at, I can’t find them.” Such technical bugs were quite common during testing, and caused uncertainty for participants with regards to product list sorting. However, it’s important to note that during testing there were many instances of participants tapping “Back” and a filter being removed or a sorting direction being changed — but this wasn’t communicated to participants on the front end. In other words, while tapping the “Back” button technically did remove a filter or change a sorting direction, it appeared to participants that nothing had changed, as the (now removed) filters were still shown as applied or the sorting direction shown didn’t match the actual sort order of the product list. This obviously will lead to confusion for users, who will wonder whether their “Back” button click or tap has been successful when there’s a mismatch between their actions and what they see displayed in the interface. If filtering or sorting is in an entirely separate interface as on many mobile sites — it’s critical that tapping “Back” while in the interface acts as an “Exit” link would — similar to exiting an overlay. That is, users should be returned to the view they had been looking at just prior to opening the filtering or sorting interface, after tapping the “Back” button from within the interface. While the expectations for “Back” button behavior are quite consistent when it comes to overlays, filtering, or sorting, there are other views users encounter during product finding and exploration where the results of clicking or tapping the “Back” button aren’t so obvious. These are: Multistep processes within a page Anchor links Expanding content Product variations on product details pages A participant during a previous round of testing was interacting with a multistep shipping estimator on a Sears product page (the “Delivery Options” box). He went through several steps, before clicking the browser “Back” button. However he was only scrolled up to the top of the page, rather than being taken to the previous step in the shipping estimator, as he had expected. He then clicked the site-provided “back” link in the shipping estimator and was able to step backwards through the process. 1 additional example “Go back to — I don’t know if it’s just me — it’s just taking me back to this page the whole time. Yeah, I can’t navigate all the way back there.” During large-scale Travel Tours & Experiences testing this participant at Wendella entered her guest count in the embedded “Booking” module to learn the departure time for the cruise. She subsequently dropped the tour from consideration and attempted to return to the tour listings via the browser “Back” button. However, instead of returning to the tour listings, the site reset the selections in the embedded “Booking” module, which was unexpected. She resorted to opening the navigation menu to return to the tour listings. It’s often difficult to determine what to show users after they click the “Back” button when they’re interacting with a multistep process embedded within a page — for example, shipping estimators, product-finding wizards, questionnaires, etc. While some users may assume they’ll be taken to the previous page, others will assume they’ll be taken to the previous step in the process. The design of the embedded process itself likely highly influences user expectations. For example, when a process takes up more than 50% of an interface — which will very often be the case on mobile — many users are likely to expect that after clicking “Back” they’ll see the previous step in the process, not the previous page. However, the length of the process is also a factor here. It’s not difficult for users to click back through, for example, a 3-step process, even if they had expected the “Back” button to take them to the previous page. Hence the consequence of forcing all users to do this isn’t so grave. If, on the other hand, the process is lengthy — for example, a 7-step process — then the act of clicking back becomes much more tedious if, for example, users have to click back through 6 separate views to finally get back to the previous page they were on. Lastly, if the embedded wizard will lose any significant amount of data the user has typed when the back button is used, then the consequences of not taking users to the prior step also increase greatly. Thus, the size and prominence of the embedded process, the length of the process, and any potential data loss of large amounts of user provided data should be considered when deciding whether each step in the process should have its own separate URL (requiring users to click back through each step in the process) or not (where clicking “Back”, even if a user is several steps into a process, returns the user to the previous page, or alternatively exits them from the process). (See also #901.) A participant in an earlier round of testing on a Target product page tapped the review star average at the top of the page (first image), and was jumped down to the reviews section (second image). Being satisfied with the reviews, the participant tapped “Back” but wound up in the product list, rather than back at the top of the product page as she intended (third image). When users click or tap anchor links, their expectations can depend on whether they are immediately jumped down the page or if they are smoothly scrolled to the new position. During testing, it was observed that if participants were jumped down the page, then tapping “Back” was expected to return them to the previous position on the page. For example, if a user is jumped down to the reviews section after tapping a reviews star average at the top of the product page, then they should be returned to the top of the product page when “Back” is tapped. This is because when users are jumped down a page, they tend to lose overview of where they are, and they can think they are indeed on an entirely new page (especially on mobile sites). Returning them to where they originally were when they tap “Back” ensures that they don’t become too disoriented. However, it’s less clear-cut if a user is smoothly scrolled down the page. When users are scrolled to a new position on the page they retain an overview of where they came from. Therefore they’re much less likely to completely lose an overview compared to users who are jumped down the page. Thus, some users may feel like a site isn’t meeting their expectations if after they tap or click “Back” they aren’t brought back to another page, but rather returned to their previous location on the page. As they’ve been smoothly scrolled, they know where they are — they could easily scroll up if they want to, but by tapping “Back” they’re likely signaling their intention to go back a page instead. (Note that it’s recommended that users always are smoothly scrolled, rather than jumped, when tapping an anchor link — see #784.) Note also that, even if the “Back” button doesn’t perform as an individual user expects, the disruption to the user experience by having “too many” “Back” button clicks is much smaller than having too few; for example, if a user tries to exit an overlay by tapping “Back” and winds up on a completely different page because there are too few clicks. If a user isn’t taken back to, for example, the product list, but is rather returned to the top of the product page, it’s at worst a minor interruption to their product-browsing and -exploration experience. Thus, the particular context in which the “Back” button is tapped should be taken into account. If a user is on a mobile site, and it’s a very long product page, then it likely makes sense to take users to the anchor link that was tapped, rather than back a page, when they tap the “Back” button. Alternatively, if there are many anchor links on a page (meaning a user could potentially bounce around the page for awhile when tapping “Back”, if many of the anchor links have been tapped), or if the page isn’t very tall, then taking users back to the anchor links could be disruptive, and it may simply be better to return them to the previous page instead. A test participant at Overstock (Android) was exploring a product page, and in the process she tapped to expand truncated content (first image). Ready to go back to the product list, she scrolled to the top of the page and tapped “Back” (second image). However this brought her back to the content she had just been viewing in the middle of the page (third image). She tapped “Back” again and this time was returned to the product list. Taking users back to a link they tapped to expose truncated content can result in a jarring user experience. Care must also be taken when dealing with content that’s expanded when users tap or click a link or a button. For example, it’s quite common on mobile product pages to display a couple of lines of text of the product description, and then hide the rest behind a “More” link. In this case, most users won’t expect the “Back” button to close the expanded content but to take them back to the previous page. Expanding truncated content simply isn’t enough of a “view change” for users to expect to be taken back to that area of the page. Consider also giving users more of an overview of where they are when they tap to expand the content by smoothly expanding the new content (e.g., by gracefully expanding the content, rather than abruptly jumping to the new content). In an earlier round of testing, a participant was exploring image thumbnails in IKEA’s “Seating Solutions”. Each thumbnail expanded to fill the entire page width when clicked. Having expanded the first thumbnail (first image), the participant expanded another thumbnail, but then wanted to go back to the first image, and clicked the browser “Back” button (second image). The “Back” button however took him all the way back to the main category page, rather than back to the first image he expanded (third image), as the expanded options weren’t part of the browser history. Other expanding content — such as thumbnails expanding to larger images — could be viewed either way, as users could reasonably interpret the expanded content as either a new view or simply the same view, with some content that’s been changed. Not expanding content in this way, but instead switching to an overlay, where it’s clear what to take users to when they click the “Back” button (i.e., exit them from the overlay and return them to the page they were on), may be the easiest solution. Otherwise, similar to multistep processes embedded in pages, much depends on how prominent the expanding content is. If it takes up a large part of the interface then many users will interpret it as a separate page, and thus each piece of content should have its own separate URL. “OK that’s annoying…Just trying to get back to the lipstick page where we were [the product list]. Am I just not holding it [the browser “Back” button] down right?” A participant at Sephora tapped the “Back” button multiple times but nothing seemed to happen, beyond the page moving up slightly (first image). She then opened her browsing history by holding the “Back” button, and was able to return to the product list this way (second image). Prior to tapping the “Back” button the participant had been exploring the color swatches, and from the browser history it appears Sephora had implemented each color variation as a separate URL. Yet the product image never changed for the participant when she tapped “Back” (but it had when she was initially exploring the swatches). Product variations — like items in different colors — should be combined into one product list item (#421). Users can then explore the variations on the product page. Whether or not those product page variations should have separate URLs, however — and thus users would step back through each previous variation they had already explored when tapping “Back” — again depends on the context. When there are generally few product variations for users to consider, then having them as separate URLs may be the best choice, as most users wouldn’t have to tap “Back” more than a few times to get to the actual previous page (often the product list or search results page). While some users will be slightly annoyed at having to tap back 2 or 3 times to get back to the previous page, others will likely be more severely annoyed if they tap “Back” to go to a previously viewed variation and are instead kicked off the product page entirely. This could become a much more disruptive experience if, for example, they’re not returned to where they had previously been in the product list — forcing them to refind the product they had just been viewing (see #1024). If each variation has its own separate URL, however, it’s critical that the product image changes after each tap of the “Back” button. Otherwise, users will be tapping “Back” with no indication that anything is happening in the interface (even if they are technically seeing different URLs). This is a recipe for disaster, as most users will assume the site is “stuck” or will simply be unclear why it appears that their actions are having no effect. If, however, there are dozens of variations — for example, lipstick shades — then it can become a more tedious exercise to step back through potentially dozens of “pages” to finally get back to the previous page the user was on. If it’s decided that tapping “Back” skips previously viewed variations and instead sends users back to the previous page they were on, then it’s critical that users are returned to where they were in the product list (if that was the previous page) so that refinding the product is easy (see #1024). A list of “Recently Viewed” items could be helpful as well (see #827).", "advice": "At Nike, users can view high-quality images of products in an image gallery overlay. However, clicking “Back” doesn’t bring users back to the product page, but instead sends them to the previous page (in this case, the product list). This fails to match users’ expectations of how the “Back” button should work. To reduce the confusion and disorientation caused by users being brought to an unexpected destination, ensure that the “Back” button behaves in accordance with their expectations. When it’s deemed that a “Back” button click should yield what is technically not a separate page — as in the case of overlays, filtering and sorting changes, and some other relevant views — then this “Back” button support should be achieved via history.pushState. The HTML5 History API allows sites to honor users’ expectations by invoking a URL change without a page reload, meaning the site can align the browser “Back” button behavior to match user expectations. The URL needs to be altered on each relevant click (e.g., a filter is applied, or content is expanded) so the correct view can be loaded when a user moves backwards. Finally, it’s worth reiterating that users show little appreciation for the often arbitrary and minute distinctions of when a new view is technically a new page or just an expanded element on the existing page. Users therefore often rely on an element’s visuals, its context, and prior site experience when shaping their expectation of when something is a new page vs. is an altered element on the same page. It’s the outcome of this subconscious snap judgement that determines where the user expects the browser “Back” button to take them. In the case of overlays and filtering and sorting changes, users expect to be taken back to the page they are currently on, or to remove filters or change the sorting direction, respectively. In other cases — for example, product variations on the product page — it’s instead a decision that must be made depending on each individual site or page context.", "summary": "The “Back” button is a crucial and heavily used browser feature during product finding, but when it doesn’t match users’ expectations of where they are “taken back to” it can take longer for users to find relevant products, or lead to disorientation or abandonments.", "purpose": "" } }, { "doc_id": "doc-226fd7dd0b8467eb8f367298ad009857", "title": "Ensure Text in Mobile List Items and Search Results is Unselectable", "g_id": "1070", "url": "https://baymard.com/premium/guideline-collections/lbxiks/1070", "source_type": "guideline", "importance": 33, "summarized_info": { "description": "Making list item text selectable can cause users to detour to product pages and slows the process of scanning the product list.", "issue": "Making list item text selectable can cause users to detour to product pages and slows the process of scanning the product list", "advice": "Disable text selection in list items and search results", "summary": "Making list item text selectable can cause users to detour to product pages and slows the process of scanning the product list.", "purpose": "" } }, { "doc_id": "doc-fbfe115c4011c6307001c3b0920c1b53", "title": "Avoid Overly Prominent “Featured Products” or Sitewide Promos in Mobile Product Lists", "g_id": "1071", "url": "https://baymard.com/premium/guideline-collections/buivs9/1071", "source_type": "guideline", "importance": 33, "summarized_info": { "description": "Users can get diverted from product finding and get disoriented by overly distracting “Featured Products” or sitewide promos.", "issue": "Users can get diverted from product finding and get disoriented by overly distracting “Featured Products” or sitewide promos Promos that push list items out of the viewport can make it difficult for users to see the products and understand the context of the list Out-of-place promos from other categories can distract users and lead to detours, wasting their time and effort Accidental taps on dominating or poorly placed promos can lead users to unrelated product pages and disrupt their product-finding process", "advice": "If placing “Featured Products” or sitewide promos in product lists or search results, ensure they are not overly visually distracting Make sure the addition of “Featured Products” or sitewide promos at the top of the list doesn’t help to push list items out of the viewport Only display “Featured Products” or promos that are relevant to the current list Minimize the likelihood of inadvertent mistaps leading to detours Avoid including ads for external sites in product lists and search results", "summary": "Users can get diverted from product finding and get disoriented by overly distracting “Featured Products” or sitewide promos.", "purpose": "" } }, { "doc_id": "doc-bbd99cb9994388391768fb42442b7d6b", "title": "Ensure Hit Areas on Mobile Are at Least 7mm x 7mm", "g_id": "1083", "url": "https://baymard.com/premium/guideline-collections/xn1mtn/1083", "source_type": "guideline", "importance": 0, "summarized_info": { "description": "Users on mobile are disrupted by erroneous taps caused by hit areas that are too small.", "issue": "This test participant was one of a few who found it impossible to open the tooltip to the right of the “+4 MyPoints” text on Lowe’s (Android) because the hit area was too small. When sizing issues prevent users from accessing information, they can seriously impact purchasing decisions. On H&M (iOS), the cart icon, the “Favorite” heart icon, and the “Back” button are all too small. As a result, users may very well struggle with these commonly used features. During an earlier round of testing, this participant on Adidas (iOS) had to tap 3 times to close the filter interface due to the fact that the “X” was too small. When taps aren’t registered, users can get frustrated and impatient — especially if such issues happen repeatedly. 1 additional example “Also these buttons, the ‘Remove’ and ‘Edit’ buttons are super tiny on mobile, so I have to be very careful not to click too high above because then I’ll hit ‘Remove’. I mean, I get frustrated with technology easily sometimes, so it’s like, ‘I have all my whole order ready’. And then I remove a complicated pizza and I’m like, ‘Oh my gosh’. And I’m like, I’m ordering for a family member or something, and I’m like, ‘Okay, tell it to me again’.” Undersized links like these on Domino’s Pizza (Android) can cause users to lose progress when building orders, and if starting again is too much bother they may well abandon the purchase.", "advice": "The sizing of hit areas such as the search box and icon, the cart icon, the “Heart” icon for saving items to wishlists (first image, iOS), and main navigation items (second image) on Home24 ensures that users are very unlikely to encounter errors when tapping. Filter options on John Lewis (iOS) measure more than 7mm in each direction, making them easy to tap. Color filter options on Amazon (iOS) are also adequately sized making it very easy for users to quickly select all that are relevant to their needs. Swatches and the video “Play” button (among other elements) on Target (iOS) are generously sized, making it very unlikely that users assessing products will have tap issues. Therefore, ensure that the hit areas of all tappable elements are at least 7mm x 7mm (dimensions that are in line with both our test results and the advice of mobile OS providers). With hit areas properly sized (and elements spaced properly — see #1094), users are less likely to be interrupted and slowed by avoidable sizing-related design issues. Instead, with well-sized hit areas, moving through the product finding and checkout flows will be smoother and users will be able to focus on assessing products and completing purchases. The 7mm x 7mm measure is deliberately not stated in pixel size as the pixel density of mobile devices differs, and what matters is the actual “physical” size of the hit area. Therefore, to determine whether hit areas are adequately sized, it’s necessary to calculate the number of device pixels that equate to 7mm. To measure hit areas in millimeters: Find out the the PPI density of the device you want to support Divide the PPI by 25.4 to get the number of pixels per mm for that device Multiplying that number by 7 gives the size of tappable elements for devices with that PPI density Remember to only measure on native full-resolution screenshots when measuring hit areas For example, a phone with 460 pixels per inch translates to (460/25.4) ~18 pixels/mm, so elements should be at least 126 (7x18) pixels in both height and width. On older devices with lower PPI densities, 126 pixels would result in even larger tappable elements — for example an iPhone SE 2nd gen has 326 pixels per inch which translates to (326/25.4) ~12.84 pixels/mm. Therefore a size of 126 pixels in each direction would lead to a physical size of nearly 10mm x 10mm on this device. Size testing of tappable elements should be done on the currently most popular devices to accommodate different screen resolutions with regular retesting as display technologies evolve.", "summary": "Users on mobile are disrupted by erroneous taps caused by hit areas that are too small.", "purpose": "" } }, { "doc_id": "doc-1f37fa526197a4ac45be220d12d12311", "title": "Ensure Tappable Elements on Mobile Are at Least 2mm Apart", "g_id": "1094", "url": "https://baymard.com/premium/guideline-collections/xn1mtn/1094", "source_type": "guideline", "importance": 0, "summarized_info": { "description": "Users can become severely disoriented and completely lose overview if they tap an element they hadn’t intended to.", "issue": "“So… ‘Shop All Face’. I’m going to do ‘Shop All Face’, [and] because I clicked ‘Foundation’, I’m going to go back.” The fact that the links on Bobbi Brown were only 1.3mm apart were a factor in this test participant tapping the wrong one (first image, iOS) and ending up on the “My Review” page (second image) instead of a list of all reviews (the links were also not tall enough, see #1083). While in this case the error was quickly resolved, unintended detours can sometimes be very disruptive. “Let’s see what the reviews are. [I] don’t want to write a review, I want to see reviews.” Because the spacing between the review summary link and the ‘Write a review’ link was too small, this test participant found themselves on the wrong page. Though some mistaps result in minimal disruption, not all users will recover so quickly. A participant during an earlier round of testing at Target unintentionally tapped a free shipping offer, which was placed immediately adjacent to the element he was trying to tap (the profile icon, first image), and was then shown the free shipping overlay (second image). Unintentional taps can range from causing mild annoyance and slight detours (as in this case) to abandonments if users become completely disoriented. 2 additional examples “The fattest finger”. A participant at Target inadvertently selected two filter options in the filter interface. While users may blame themselves for mistaps such as this, the lack of space between the elements is the real issue. Note in these images the size of the participant’s (normal sized) index finger relative to the spacing between the filtering values. The spacing between the filters is just under 2mm. “I did not click on you…”. A participant at Newegg inadvertently tapped a product list item when he was trying to open the sorting tool (first image), and wound up on the product page (second image). The spacing between the sorting tool and the product list item is ~1.1mm. A different participant had a similar issue on Newegg, but was trying to open filtering instead. The link for filtering is slightly better spaced than the sorting widget, though it’s still too close to the product list items, with a spacing of just under 2mm.", "advice": "Links on the CB2 homepage (iOS) are well spaced, making it very unlikely that users will mistap and end up in the wrong category. Footer links on Dollar Shave Club have plenty of space between them making mistaps unlikely. Filter options on John Lewis (iOS) are spaced more than 2mm apart and so are easy to select. Issues caused by mistaps are completely preventable and the solutions are easy to implement. Thus, ensuring adequate spacing between tappable should be a key priority. While it’s good practice to always have adequate spacing between all adjacent elements, it’s especially important to be rigorous when it comes to specific areas that are crucial to users’ smooth progress. A mistap in the checkout process could cause severe disruption and might lead to the purchase being abandoned. Or, unintentionally going from the product list to the product page, then going back, can often result in significant frustration — see #1057 and #1024. Some device manufacturer’s design guidelines stipulate a minimum spacing of 2mm and the results of our testing concur with this recommendation. Therefore, there should be 2mm of space between elements such as links, navigation menu items, filter types, filter options, swatches, and buttons — basically anything that can be tapped. Furthermore, tappable elements should never be placed at the very edge of the screen, as that area is typically unresponsive and users are likely to find it hard to activate those elements. To determine whether spacing is adequate, it’s necessary to calculate the number of device pixels that equate to a spacing of 2mm. To measure spacing between elements in millimeters: Find out the the PPI density of the device you want to support Divide the PPI by 25.4 to get the number of pixels per mm for that device Doubling that number (giving 2mm) gives the number of pixels that should separate tappable elements for devices with that PPI density Remember to only measure on native full-resolution screenshots when measuring the spacing between elements For example, a phone with 460 pixels per inch translates to (460/25.4) ~18 pixels/mm, so elements should be at least 36 pixels apart when viewed on that device to conform with the recommended separation of 2mm. On older devices with lower PPI densities, 36 pixels would result in even more separation — for example an iPhone SE 2nd gen has 326 pixels per inch which translates to (326/25.4) ~12.84 pixels/mm. Therefore a separation of 36 pixels would lead to a physical distance of nearer to 3mm on this device. Testing for adequate spacing between tappable elements should be done on the currently most popular devices to accommodate different screen resolutions with regular updates as display technologies evolve.", "summary": "Users can become severely disoriented and completely lose overview if they tap an element they hadn’t intended to.", "purpose": "" } }, { "doc_id": "doc-ac88fc565566d6821a800b609ca1cbc3", "title": "Ensure That All Pages and Content on Mobile Are Optimized for Mobile", "g_id": "1095", "url": "https://baymard.com/premium/guideline-collections/xn1mtn/1095", "source_type": "guideline", "importance": 0, "summarized_info": { "description": "Pages that are not optimized for mobile can be hard to read and disrupt users.", "issue": "Because the size chart was presented as a graphic on Gerry Weber (iOS, first image), this test participant had to pinch to zoom to be able to read it (second image), and then had to scroll sideways to see the relevant part. Putting users to this much trouble can be very disruptive. Forcing users to scroll sideways (as this test participant was on RiteAid (iOS)) makes it harder for them to read the content in full, thereby slowing down the process of assessing information. “Okay [pinches screen]. Jeez…I was trying to scroll down, but it won’t let me scroll.” When nonoptimized pages are provided on mobile, it can be hard for users such as this test participant on Stylevana (iOS) to navigate around them. This raises the risk that users will overlook or misunderstand content. When tables aren’t optimized for mobile, such as in the Bang & Olufsen app (first image, iOS) the Best Buy app (second image, iOS), and on the Argos site (third image, iOS), the content can be hard to read and assess without a lot of scrolling and zooming. As a result, important information that could be key to a purchasing decision could be missed. “I’m curious. Oh, sorry!” Presenting important information in PDF files such as this one on American Eagle (iOS) can surprise users and makes it very hard for them to actually read and understand the content. This size chart encountered by a test participant on Uniqlo (iOS) had to be zoomed to view on mobile and even then the text was hard to read. Plus, they had to scroll horizontally to see all columns. 4 additional examples Tapping a “Terms of Purchase” link at Buy.com led this participant during a previous round of testing to a page that was clearly not optimized for mobile. The participant abandoned as a result. This participant at Toys’R’Us had tapped on an “FAQ” link during a previous round of testing, and had to scroll horizontally to read the text. A participant at costal.com tapped on a tooltip during a previous round of testing, and wound up at a page with very small text. “It’s free shipping, I wonder if it’s free returns.” A participant at Walmart went looking for returns information and after spending over 3 minutes looking for it she finally arrived at a help page where the content wasn’t optimized for mobile. So she zoomed the page, only to inadvertently tap on “Start a Return”, adding more frustration to the session. Failing to have mobile-optimized pages for all site areas makes a site seem “sloppy”. At Cabela’s during an early round of testing, text for a buying guide was in a very small font, making it difficult for participants to read on mobile. A participant at Walgreens (Android) tapped a “Show more” link on the product page to see more of a product description (first image). However the resulting content was too wide to view without scrolling horizontally (second image), making it unnecessarily difficult for the participant to learn more about the product of interest.", "advice": "Users on JYSK that are interested in topics like Terms & Conditions and Privacy Policies will have no trouble reading them as they are contained in optimized mobile pages rather than PDFs. Help pages on Foot Locker are optimized for mobile with adequate font sizes and spacing and therefore easy to read This size guide on H&M will be easily accessed and understood by users. Only the most important information is displayed, and the table is designed without clutter and with optimal use of space. Displaying a tooltip in a table (as seen here on L.L.Bean (iOS)) could have posed problems for users but it’s careful design — reducing the content to the essentials and using optimal font sizes and spacing — means that users will have no trouble finding the information they need. To avoid these issues, ensure all pages are optimized for mobile. Doing so will prevent avoidable disruption that would damage users’ perceptions of the site. While it’s of course important to check high-traffic areas for issues, it’s also important to check less-visited content and pages, such as help sections and tooltips as these can often contain content that is crucial to making informed decisions about purchasing. All text should be large enough for users to read without having to zoom, and the necessity to scroll horizontally should be minimized. Any graphics containing text (see #752) should be designed to adapt to smaller screen sizes and any text in these graphics should be sized to be readable on mobile devices and shouldn’t be placed on cluttered backgrounds. The Everlane size guide contained in a table enables users to easily find and understand what they need. This readability is enhanced by the fact that only the necessary information is displayed and that font sizes and cell spacing are carefully chosen. The first step to making tables less troublesome on mobile is to make them adaptive to different screen sizes. Consider also removing content that is nonessential to reduce clutter and the need for users to scroll. In addition, the size of text should strike a balance between being readable on mobile and not being so big that fewer columns are visible by default. Lastly, even though horizontal scrolling can be tricky for some users, it should be possible to view all columns by doing so. Finally, PDF files can cause problems for mobile viewers and should be avoided if possible. However, there are a few steps that can be taken to make it more likely that information in PDFs can be easily accessed by users. One is to use a single-column layout so that users are less likely to have to scroll sideways to view the content. Also, choose a font size that is small enough to allow enough room for sufficient content to be shown but is nevertheless easy for users to read. Finally, keeping file sizes as small as possible will help reduce load times.", "summary": "Pages that are not optimized for mobile can be hard to read and disrupt users.", "purpose": "" } }, { "doc_id": "doc-002f3087e121b9fc22b7a2c0a22dc33a", "title": "Avoid Excessively Tall Horizontal Scroll Areas on Mobile for Most Content", "g_id": "1096", "url": "https://baymard.com/premium/guideline-collections/xn1mtn/1096", "source_type": "guideline", "importance": 0, "summarized_info": { "description": "When users are scrolling vertically, touching horizontally scrollable areas can “hijack” the scroll and disorientate them.", "issue": "The tall horizontal scroll areas in prominent positions on Apple (iOS, first image), Nordstrom (iOS, second image), and ASOS (iOS, third image) make it more likely that users will inadvertently scroll sideways when trying to scroll down these pages. A participant at Adidas (Android) in a previous round of testing accidentally scrolled the “Product Snapshot” section while scrolling down the page. Note the height of the horizontal scroll area, which took up nearly the entire viewport. A different participant at Macy’s (Android) in an earlier round of testing accidentally scrolled the homepage carousel (see also #957), which took up nearly the entire viewport. During testing, minor scroll hijacking interruptions were observed where participants inadvertently scrolled horizontal content while intending to scroll vertically. In all instances these were minor interruptions, and participants quickly recovered. However, even minor interruptions can detract from the overall user experience if they’re frequent occurrences, or if they occur in combination with other, more serious issues. The excessive height of horizontal scroll areas were the main factor in these interruptions. One area in which horizontally scrolling areas are commonly found are cross-sells sections on product details pages. While it’s understandable that larger images are presented here to showcase products, a balance must be struck between the risk of users being interrupted by scrolling horizontally and presenting products in their best light. Likewise, carousels (most commonly seen on home pages and intermediary category pages) that take up practically the entire viewport will be touched by almost all users who want to scroll down the page, and at least some of these users will unintentionally scroll horizontally instead.", "advice": "Horizontal scroll areas are reasonably sized on the homepage of the Amazon app (first image, iOS), and in cross-sell areas on the product details pages of the GAP app (iOS, second image) and Home24 (third image, iOS). Users that are interested in featured products can easily scroll sideways, while others are very unlikely to have their vertical scrolling hijacked. A participant in an earlier round of testing at Sephora (iOS) used horizontally scrollable color swatches to view different shades of lipstick. Note the relatively small vertical height of the section, and that the additional swatches are hidden unless users tap on the “View all colors” link. Thus, it’s highly unlikely that users will accidentally scroll horizontally. To minimize accidental horizontal scroll hijacking, limit the height of horizontal scroll areas to a maximum of 50% of the viewport height. This will give users that choose not to scroll horizontally plenty of space below to scroll vertically. In particular, content that isn’t crucial to most users — such as ads, extended product descriptions, cross-sells, and other secondary content — shouldn’t take up more than half the height of the viewport when implemented as horizontally scrollable content. Alternatively, consider avoiding horizontal scroll areas entirely by showing all of the content by default, or showing some of the content and hiding the rest behind a “View More Products” or similar link. Many sites such as Everlane (iOS, first image), American Eagle (iOS, second image), and Nike (iOS, third image) use horizontally scrolling galleries to showcase items on product details pages. This is a common implementation and users are unlikely to overlook the fact that they can scroll both horizontally and vertically in this area of the page. A participant at JBL (Android) in an earlier round of testing explored product images, which were horizontally scrollable, for earphones on the product page. Tall horizontally scrollable areas are acceptable for critical, visually rich content, such as product page images. However, there can be situations where it makes sense for horizontally scrollable content to take up as much of the viewport as possible when large imagery is critical to users’ purchasing decisions. In this situation, the likelihood of scroll-hijacking issues can potentially be outweighed by the importance of the content. As such, product images on product details pages are a prime example of content for which it can be justifiable to provide taller horizontally scrolling galleries.", "summary": "When users are scrolling vertically, touching horizontally scrollable areas can “hijack” the scroll and disorientate them.", "purpose": "" } }, { "doc_id": "doc-f3345937fd51a4d483fb67fa548bbc97", "title": "Always Show Appropriate Keyboard Layouts on Mobile", "g_id": "1100", "url": "https://baymard.com/premium/guideline-collections/zy6bb4/1100", "source_type": "guideline", "importance": 100, "summarized_info": { "description": "Inappropriate keyboard layouts slow users who are filling form fields and can lead to typos and validation errors.", "issue": "Inappropriate keyboard layouts slow users who are filling form fields and can lead to typos and validation errors", "advice": "Consistently show the appropriate keyboard layout for all form fields including numeric, phone, and email form fields", "summary": "Inappropriate keyboard layouts slow users who are filling form fields and can lead to typos and validation errors.", "purpose": "" } }, { "doc_id": "doc-99dfa267a6580e958bcfed006b0ef67a", "title": "Always Disable Autocapitalization for the “Email” Field", "g_id": "1103", "url": "https://baymard.com/premium/guideline-collections/zy6bb4/1103", "source_type": "guideline", "importance": 33, "summarized_info": { "description": "Many users assume their email address has to be entered all in lowercase, so autocapitalization of this input adds needless friction to the typing process.", "issue": "Many users assume their email address has to be entered all in lowercase, so autocapitalization of this input adds needless friction to the typing process In testing, some participants deleted the autocapitalized input to retype it in lowercase, slowing their progress", "advice": "Disable autocapitalization for email fields", "summary": "Many users assume their email address has to be entered all in lowercase, so autocapitalization of this input adds needless friction to the typing process.", "purpose": "" } }, { "doc_id": "doc-9af96bff146c46967ac62cb5489df57e", "title": "Dynamically Change Form Labels on Mobile from Above Fields to Left Aligned in Landscape Mode", "g_id": "1108", "url": "https://baymard.com/premium/guideline-collections/1pjsex/1108", "source_type": "guideline", "importance": 33, "summarized_info": { "description": "In landscape mode, the keyboard takes up so much space that vital context, sometimes even the field label and description, are out of view.", "issue": "In landscape mode, the keyboard takes up so much space that vital context — sometimes even the field label and description — are out of view As a result, users might close the keyboard to find their place, forget the context of the field they are filling, or misinterpret field purposes, leading to mistakes or incorrect data", "advice": "Dynamically change the preferred label position from above the field (in portrait mode) to the left of the field when the user views the form in landscape mode Additionally, make sure all field descriptions align properly in landscape mode Summary Summary Research Findingschevron-down Video & Quiz Review Tool Audit Performances Implementation Examples Benchmark Performances Changelog", "summary": "In landscape mode, the keyboard takes up so much space that vital context, sometimes even the field label and description, are out of view.", "purpose": "" } }, { "doc_id": "doc-cdab375229ae681a143daaef61e354a1", "title": "Always Provide Sticky “Apply” Buttons in the Mobile Filtering Interface", "g_id": "1125", "url": "https://baymard.com/premium/guideline-collections/p8s4px/1125", "source_type": "guideline", "importance": 100, "summarized_info": { "description": "Autosubmitted filters can slow users down when they want to choose multiple filter options, and product finding is hampered by filter choices unexpectedly remaining unapplied.", "issue": "Autosubmitted filters can slow users down when they want to choose multiple filter options Product finding is hampered by filter choices unexpectedly remaining unapplied Participants expressed surprise and annoyance when their filter choices were autosubmitted", "advice": "In separate filter interfaces, provide a prominent, sticky ‘Apply’ button, as well as a ‘Clear’ button and a way to exit the interface without making any changes Avoid autosubmitting filter options as they’re selected", "summary": "Autosubmitted filters can slow users down when they want to choose multiple filter options, and product finding is hampered by filter choices unexpectedly remaining unapplied.", "purpose": "" } }, { "doc_id": "doc-f9be778aad6017868c8a39143ab0824f", "title": "Enable Mobile Users to Search Long Lists of Filter Options", "g_id": "1126", "url": "https://baymard.com/premium/guideline-collections/p8s4px/1126", "source_type": "guideline", "importance": 100, "summarized_info": { "description": "Users can get disoriented and overwhelmed in long lists of filter options and could overlook options of interest.", "issue": "Users can get disoriented and overwhelmed in long lists of filter options and could overlook options of interest Inline scrolling within filter options can cause confusion and frustration for users", "advice": "Allow users to search long lists of more than 15–20 filter options For shorter lists of filter options, a search feature is not necessary, and options can be ordered by popularity or alphabetically", "summary": "Users can get disoriented and overwhelmed in long lists of filter options and could overlook options of interest.", "purpose": "" } }, { "doc_id": "doc-2f7e99cd7d6847913558997c86ff475b", "title": "Make the Reviews Sort Tool Prominent and Easily Findable", "g_id": "1127", "url": "https://baymard.com/premium/guideline-collections/hwvgrc/1127", "source_type": "guideline", "importance": 75, "summarized_info": { "description": "Users may overlook the means for sorting reviews, rendering them less able to zero in on the reviews that are most relevant to their needs.", "issue": "Users often overlook the means for sorting reviews, making it difficult for them to find the most relevant reviews The design of the sort tool, whether a drop-down menu or on-page links, is less important than its visual prominence and labeling", "advice": "Use a sort tool interface (either a drop-down menu or links) that is large relative to other nearby page elements and contrasts with the surrounding page background Provide a separate “Sort By” label (for drop-down implementations) or header (for links) On desktop in particular, place the sort tool proximate to the start of the reviews list, and include the sort tool and the reviews together in the same section", "summary": "Users may overlook the means for sorting reviews, rendering them less able to zero in on the reviews that are most relevant to their needs.", "purpose": "" } }, { "doc_id": "doc-93e5c07298eb590fedc2190baa26223f", "title": "Consider Using “Vertically Collapsed Sections” for Mobile Product Page Layouts", "g_id": "1129", "url": "https://baymard.com/premium/guideline-collections/vz73pj/1129", "source_type": "guideline", "importance": 100, "summarized_info": { "description": "The limited viewport of mobile product pages makes accessing and getting an overview of product page content difficult, leading to users misunderstanding product information or not being able to find it at all.", "issue": "The limited viewport of mobile product pages makes accessing and understanding product information difficult for users A 'Horizontal Tabs' layout performs better on mobile compared to desktop, but some participants still experience issues with content visibility Users also experience issues navigating mobile product pages that use a 'One Long Page' layout for information-dense products", "advice": "A 'Vertically Collapsed Sections' layout is recommended for mobile product pages Consistently implement 'Vertically Collapsed Sections' for all major product page sections Additionally, use informative section titles and provide clear trigger indicators for hidden content For products that have limited product page content and that are mainly visual in nature, a “One Long Page” mobile product page layout is also suitable", "summary": "The limited viewport of mobile product pages makes accessing and getting an overview of product page content difficult, leading to users misunderstanding product information or not being able to find it at all.", "purpose": "" } }, { "doc_id": "doc-2b8d3dcd3663b99bb1d1695397da3640", "title": "How to Implement the Clickable Ratings Average at the Top of the Product Page", "g_id": "1134", "url": "https://baymard.com/premium/guideline-collections/hwvgrc/1134", "source_type": "guideline", "importance": 75, "summarized_info": { "description": "It’s more difficult for users to interpret and use the clickable ratings average when it lacks information scent and fails to meet user interaction expectations.", "issue": "It’s more difficult for users to interpret and use the clickable ratings average when it lacks information scent and fails to meet user interaction expectations The overall rendering of the star ratings average affects users’ ability to leverage this information effectively For a product with no reviews, displaying 5 “empty” stars can confuse users Most users assume that the browser “Back” button will take them back to the ratings average if they're 'jumped' down the page after clicking the ratings average", "advice": "Always include the number of reviews alongside the ratings average to provide context and trust Ensure the star ratings average is prominent and clearly noticeable to help users distinguish partial or fractional stars and read the accompanying number of reviews Clearly indicate when a product has zero reviews Ensure the browser “Back” button works as expected, taking users back to the ratings average if they're 'jumped' down the page after clicking the ratings average Clicking or tapping on the star ratings average should always bring users to the full reviews section on the product page and avoid opening a “Ratings Distribution Snapshot”", "summary": "It’s more difficult for users to interpret and use the clickable ratings average when it lacks information scent and fails to meet user interaction expectations.", "purpose": "" } }, { "doc_id": "doc-ed5649c06d912eb028fc47bba4baa674", "title": "Avoid Using Subpages within the Mobile Product Details Page", "g_id": "1141", "url": "https://baymard.com/premium/guideline-collections/vz73pj/1141", "source_type": "guideline", "importance": 33, "summarized_info": { "description": "It’s often very difficult for users to maintain an overview and know where one is on complex mobile product pages that feature subpages.", "issue": "In an effort to save space and avoid mobile users becoming intimidated and overwhelmed, some sites put product page content on subpages However, some users fail to find information on subpages altogether This leaves these users with a very subpar content experience and leads to an increased risk of product abandonment For users who do find product page subpages, many have trouble retaining a sense of orientation or navigating back to the product page 'main page'", "advice": "Avoid using subpages on mobile product pages If there's a strong desire to use a subpage for a section of the product page, at the very least, clearly indicate additional content Moreover, ensure the 'Back' button works as users expect by taking them back to the product page and not sending them back to the product list", "summary": "It’s often very difficult for users to maintain an overview and know where one is on complex mobile product pages that feature subpages.", "purpose": "" } }, { "doc_id": "doc-91cac5bb6c53f4d6f47850d1d08191e4", "title": "Always Support Pinch-to-Zoom on Mobile", "g_id": "1142", "url": "https://baymard.com/premium/guideline-collections/xn1mtn/1142", "source_type": "guideline", "importance": 0, "summarized_info": { "description": "It becomes much more difficult for mobile users to visually assess products if they can’t zoom in for a closer view.", "issue": "On B&N, this participant noticed a detail in the image cover that piqued her interest: “I’m trying to [zoom in] on the image of the front of the book cover, just so I can read what’s in that little kind of Ferris wheel looking portion of it.” However, her initial attempts to do so were unsuccessful: “It’s not letting me zoom in.” After a few more attempts, she gave up, denying her access to potentially compelling detail about the content of the book. “I don’t like that I can’t zoom in on the shirt! I’m trying to pinch and zoom and it’s not letting me, which would be nice to be able to see the texture of the fabric…No, I don’t know if I love that shirt.” The lack of support for pinch-to-zoom was the direct cause of this participant on Levi’s (iOS) dismissing the product. In fact, she left the site shortly after. “I tried zooming on the picture…” Pinch-to-zoom is often attempted when users such as this participant on Costco try to get a close-up view of text on a product label (see also #2872: Tailor Desktop Zoom to Support Reading “Label Text” Images). If it doesn’t work, as it didn’t in this case, users may dismiss the item if the text (for example describing nutrition details or ingredients) is critical to their purchasing decision. 1 additional example “Now I’m going, ‘Is that as good as it gets?’”. A participant at Walgreens (Android) in an earlier round of testing was unable to zoom in on this lipstick. During testing, it was observed that participants wanted to be able to get as much visual detail as possible when evaluating products on mobile sites — even when the visual detail provided (here, for lipstick) may have appeared to be sufficient in the unzoomed state. This participant from an earlier round of testing (quoted at the start of this guideline) couldn’t zoom to get a better view of a hoodie at Under Armour (Android). He expressed frustration with the site and was unable to visually evaluate the product to the extent he wished. Over multiple rounds of testing, participants have commonly been observed pinching-to-zoom while viewing product images. Mobile users expect this gesture to work, and failing to support it can frustrate them. In fact, one participant in a previous round of testing attempted the pinch-to-zoom gesture 12 times over the course of 15 seconds — but ended up being unable to complete a thorough visual evaluation of a product. In this situation, some users will simply discard what could be a suitable product just because they can’t get the visual detail they require to make a decision. For some product types, being able to zoom in to examine items more closely is critically important. For example, many test participants zoomed in on the material of apparel or furniture products to get a better “feel” for them. Others were observed to zoom in on laptops to more closely examine what ports were available. In the vast majority of cases, mobile users pinched the screen to perform this zoom action, demonstrating that this is the expected method of magnifying screen content on these devices. “It feels clunky when I’m trying to [zoom in].” This participant on Kroger reacted negatively when he had difficulty using pinch-to-zoom to magnify a “Label Text” image. He then noticed the overlaid instruction (first image): “Let’s see, “Long-Touch to Zoom”. Oh, here we go.” However, he quickly found this approach limited his ability to gather the information he needed from the text (second image): “I’ll be honest, my thumb’s kind of in the way when I’m trying to read some of this…I still don’t see…Oh, there’s active ingredients and uses, stuff like that. So my thumb is kind of in the way when I’m trying to long press to zoom and move stuff around.” “I’m trying to figure out what this boucle is…”Tap to zoom”.” Unable to see vital product information at the default scale, this participant on CB2 noticed the overlaid zoom instruction (first image) and tapped the image to zoom in. However, the level of zoom was insufficient (second image) and he was not able to use pinch-to-zoom to increase the level of magnification: “I’m trying to pinch, but it’s not zooming in. I can’t go any closer than this. I personally like to go as close as possible…This is kind of frustrating to do the pinch, and it [doesn’t zoom].” “Not a fan of this website. I don’t like that you can’t enlarge [the image].” A participant in a previous round of testing at Newegg was frustrated when pinch-to-zoom didn’t work while trying to evaluate the main product image on the product page. The participant eventually tapped the image, which did zoom the product. Some mobile sites during testing supported other ways to zoom in on images — for example, tap-to-zoom, double-tap-to-zoom or long-touch-to-zoom. Over multiple rounds of testing, we have observed participants still attempt to use pinch-to-zoom when these gestures were enabled, even when instructions such as “Tap to Zoom” were clearly overlaid on the product image. These alternative zoom methods became problematic for test participants when they replaced or restricted the expected pinch-to-zoom functionality. Not only did this frustrate and delay participants, approaches such as long-touch-to-zoom introduced new (literal) barriers as participants struggled to view image detail past the finger they were being forced to hold on the screen to maintain the zoomed view. Ultimately, failing to meet users’ expectations of how to perform a simple and valuable action such as magnifying an image will add substantial cumulative friction, increasing the likelihood of product, or even site, abandonment. “I’m trying to pinch-zoom on this and it’s not making it bigger.” Further down the product page in the Amazon App (iOS), this participant from an earlier round of testing was interested in some of the visual examples of how a monitor could be used. Unable to see the detail clearly, he attempted to pinch-to-zoom without success: “And I can’t really see some of the things in there. So yeah, I wish I could zoom in or somehow make this picture a little bit bigger. I cannot, so I’m gonna keep scrolling.” When users can’t zoom in on other product page content, they may dismiss the item because of a lack of key visual information. A participant in an earlier round of testing at Newegg (Android) tried to pinch-to-zoom price-discount information on an intermediary category page but wasn’t able to (first image). The same participant later tried to zoom a product list item, but again wasn’t able to use pinch-to-zoom (second image). Note how the participant didn’t “learn” that pinch-to-zoom wasn’t supported — he intuitively tried to use the gesture when he wanted to see page details. Almost all test participants observed trying to use the pinch-to-zoom gesture did so in the product page image gallery. However, in previous rounds of testing, a few mobile test participants have also been observed trying to use the gesture elsewhere on the product page and in other areas of the site such as intermediary category pages, product lists (see also #456), and help sections (see also #1095). It is, therefore, a sitewide issue if mobile users can’t employ this basic gesture to access close-up views of any site content.", "advice": "“Oh, they’ve got a little [split detail], see, I like that you can zoom in on these. That’s nice.” This participant valued the ability to pinch-to-zoom to view a detail of this item on Gerry Weber (iOS). Note that her instinct was to pinch-to-zoom rather than tap the magnifying glass icon at the top left (which opened a new image). On Serena & Lily, this participant was able to use pinch-to-zoom to quickly magnify an important product detail: “And I like this too. They show how to move it around. So this photo’s good because, you know, is it easy to break something like that, that you’re moving around a lot?” A participant in a previous round of testing at Walmart (iOS) was forced to zoom a nonoptimized help page on which the text was very difficult to read (see #1095). Pinch-to-zoom worked in this instance and, despite having to scroll horizontally, the participant was able to read the relevant text. Therefore, always support pinch-to-zoom gestures in all parts of the site. Being able to zoom into images and pages in this way is an established convention on mobile. It is supported on the majority of websites, and users will be better able to assess products when this gesture is available to them. Note that, as well as the ability to pinch to zoom, users also expect images to be of sufficient quality to show adequate detail when zoomed (see #779). “Now I’m trying to get rid of this…go away…there is no X…there it is”. In a previous round of testing, a participant at Adidas successfully used pinch-to-zoom to get a larger view of a shoe (first image). But then she had brief difficulty getting back to the product page, until she eventually zoomed out and found the “X” to close the overlay (second image). Also consider dynamically including any controls for special views (e.g., image gallery or product video overlays) as users zoom. Including the controls in the zoomed-in state, such as the “X” to close an overlay, allows the minority of users who get stuck in the zoomed-in state to easily get back to the default view. This participant using the Walmart app (iOS) was able to use pinch-to-zoom to enlarge the picture of a nightstand despite the “Double tap to zoom” indication. Fully supporting pinch-to-zoom alongside alternative activation methods makes it likely that the majority of users will be able to zoom successfully. “I like the fact that they give you a close-up”, this participant at Bob’s Discount Furniture explained as he tapped to expand the overlay (first image). It wasn’t detailed enough for his liking (second image), so he pinched to zoom in further (third image), which he was pleased to be able to do: “I like the fact that you can do this pinch thing that’s really nice so I can get a super close-up as opposed to a predetermined close-up. I like that I can control that. So you can get a really good sense of what this tabletop is like.” A participant at Target during an earlier round of testing used pinch-to-zoom (using his thumbs) to get a larger view of the product page main image — despite a prominent “tap to zoom” indication on the product image. Finally, as mentioned above, even when other zoom activation methods are provided, many mobile users will still employ pinch-to-zoom as their primary means of magnifying content. This is especially the case if the availability of “Tap to Zoom” or similar is not indicated. Users may also expect pinch-to-zoom to supplement other zoom methods; for example, when the level of magnification accessible via tap-to-zoom is insufficient. While it is fine to support other gestures to zoom, it is therefore vital to ensure that the ability to pinch-to-zoom is not restricted in any way by the presence of an alternative zoom activation method.", "summary": "It becomes much more difficult for mobile users to visually assess products if they can’t zoom in for a closer view.", "purpose": "" } }, { "doc_id": "doc-483755f476902022c06888fae2cdbd52", "title": "Consider Allowing Users to Filter Reviews by Purchase Status, Product Variation, and Image Availability", "g_id": "1160", "url": "https://baymard.com/premium/guideline-collections/hwvgrc/1160", "source_type": "guideline", "importance": 33, "summarized_info": { "description": "Users with specific preferences may have to manually cull through hundreds or thousands of reviews in search of ones that fit their needs.", "issue": "Users with specific preferences may have to manually cull through hundreds or thousands of reviews in search of ones that fit their needs Users value the ability to filter reviews by different criteria, such as verified purchase status, product variation, and the availability of reviewer-uploaded images and videos Without filters, users may give up on finding relevant reviews, potentially missing out on a product they would have otherwise purchased Offering key attributes as sort types rather than filter options does not meet users' expectations", "advice": "If available and relevant, consider allowing users to filter reviews by purchase status, product variation, and inclusion of images or videos Design considerations for a well-performing filtering interface include showing a higher number of reviews when a filter is applied, allowing users to apply more than one filter at a time, displaying the number of reviews associated with each filter, live updating the list without a full page reload, and only displaying filters when a minimum threshold of reviews is reached", "summary": "Users with specific preferences may have to manually cull through hundreds or thousands of reviews in search of ones that fit their needs.", "purpose": "" } }, { "doc_id": "doc-7f17c46e3e08ed11972a9b9894130e0c", "title": "Provide Key Review Attributes", "g_id": "1161", "url": "https://baymard.com/premium/guideline-collections/hwvgrc/1161", "source_type": "guideline", "importance": 75, "summarized_info": { "description": "Users require key pieces of information about individual reviews in order to evaluate them and put them in context.", "issue": "Users require key information about individual reviews to evaluate them and put them in context For products with different variations or formats, it’s crucial for users to know which version of the product is being discussed in each review The date or age of each review is vital; more recent reviews are seen as more reliable and trustworthy The quality of individual reviews significantly impacts their usefulness to users", "advice": "Provide essential review attributes, including the authenticity of reviews, details on benefits provided to the reviewer, the product variation purchased, the review date, and the 'helpfulness' of the review Label reviews from verified purchasers and reviews that were received in exchange for incentives to enhance review authenticity and the site's transparency and trustworthiness Avoid including less helpful attributes, such as reviews originally posted on other sites and the date of purchase", "summary": "Users require key pieces of information about individual reviews in order to evaluate them and put them in context.", "purpose": "" } }, { "doc_id": "doc-8da8ea547564be730fddb651d13b768a", "title": "Always Allow Filtering By Price, User Ratings, Color, Size, and Brand", "g_id": "1167", "url": "https://baymard.com/premium/guideline-collections/jdzgoz/1167", "source_type": "guideline", "importance": 100, "summarized_info": { "description": "Users need to be able to quickly tailor product lists and search results to include only the most suitable items.", "issue": "Users need to be able to quickly tailor product lists and search results to include only the most suitable items Without key filter types, users' ability to tailor selections is restricted", "advice": "Always provide filters for price, user ratings average, color, size, and brand (except on single-brand sites) Providing these essential filters improves users' ability to find relevant products and reduces the likelihood of turning to other sites", "summary": "Users need to be able to quickly tailor product lists and search results to include only the most suitable items.", "purpose": "" } }, { "doc_id": "doc-34d3f57d62cef39db1c5462d540e7fa2", "title": "Have a “Sales” or “Deals” Filter Type", "g_id": "1191", "url": "https://baymard.com/premium/guideline-collections/jdzgoz/1191", "source_type": "guideline", "importance": 75, "summarized_info": { "description": "Users often want to find products on sale, but nonsale items shown in the product list or search results can slow product finding.", "issue": "Users often want to find products on sale, but nonsale items shown in the product list or search results can slow product finding Absence of 'On Sale' filters may lead users to assume there are no discounted items available", "advice": "Provide a “Sale” or “Deal” filter type, and ensure that it is always visible in the filter interface (e.g., don’t hide it in a “Price” filter type) Use familiar terms like 'On Sale', 'Deals', or 'Clearance' for naming filter options", "summary": "Users often want to find products on sale, but nonsale items shown in the product list or search results can slow product finding.", "purpose": "" } }, { "doc_id": "doc-02fa3a64128c705aae0876ca85ad0041", "title": "Always Show Apparel and Accessories Products on a “Human Model”", "g_id": "1193", "url": "https://baymard.com/premium/guideline-collections/6whqq3/1193", "source_type": "guideline", "importance": 0, "summarized_info": { "description": "Users struggle to assess size, fit, and personal style suitability for apparel and accessories products when product images don’t show how the item looks when worn.", "issue": "“Would it have a model wearing it?…I’d like to see because sometimes in some jewelries they do have…a model wearing it. So ideally I would’ve loved to see that.” A participant at All Saints (iOS) was disappointed that there weren’t any product images showing a “Human Model” wearing the earrings that had caught her eye. She returned to the product list to find something else: “So I’m going to find an alternative.” Without the ability to see how jewelry such as earrings look when worn by a person, many users will pass on further exploring suitable items. “These are cute, these are hip!…Their photos are good, but I think I would prefer to see them on a leg.” While browsing cowboy boots at DSW, a participant was disappointed by the absence of images showing them worn by a “Human Model”. With other key product details also missing (see #841: Ensure a Consistently High Level of Detail in the Product Descriptions), she didn’t add the boots to her cart, despite her initial excitement: “So I think these ones I would not purchase.” “I kind of like the color of these a lot. I want to see if there’s a picture of a model with these,” commented a participant as she browsed jeans at Madewell and came across a pair she liked (first image). However, because the product image also didn’t include a “Human Model” (second image), she was uncertain where the jeans would fall at the ankle: “I have short legs.” She turned instead to the “Size Chart” for more guidance and found her size (see #2608: Always Include a Comprehensive “Size Chart” for All Apparel Products), but had to spend additional time and effort due to the lack of informative imagery. Note that apparel products should always include at least 3–5 images to help users thoroughly assess the item (see #2608: Always Include a Comprehensive “Size Chart” for All Apparel Products). “They don’t show them on a model. I would like to see that on a model!” complained a participant as she tapped through 2 color variations of a shirt at Madewell, disappointed by the absence of any “Human Model” images (Android, first and second images). However, she did end up adding the blue plaid shirt to her cart, as it coordinated with the jeans she had already selected. When shopping online for apparel, accessories, or other body-worn products (i.e., headphones), users often struggle when they can’t easily visualize how the item looks on a person — a process that is typically much easier when shopping in-store. Indeed, participants in testing often turned to images showing products worn by a “Human Model” to better evaluate key attributes such as size, proportion, and fit. However, in several cases, participants hesitated about products they had been excited about when “Human Model” images were missing. In particular, some participants had difficulty judging an item’s scale or fit — for example, how big earrings would look when worn or where pants fell on the leg. While some participants in apparel testing were able to use sizing tools like a “Size Chart” to help with fit (see #2608: Always Include a Comprehensive “Size Chart” for All Apparel Products), not all participants turned to them when “Human Model” images were lacking. Many preferred the visual reassurance of judging fit by seeing how clothing fit on a model, especially when aided by easy-to-use sizing tools like the model’s size and “fit summaries” (see #2551: Always Provide the Model’s Size and Height for “Human Model” Images and #2727: Provide a “Fit Summary” near Size Selectors on the Product Page). And while some participants went ahead with purchasing despite feeling uncertain, nearly half abandoned items that lacked any “Human Model” images. Without being able to visualize how the item looked when worn, they didn’t feel confident enough to go ahead with purchasing — even for items that had really caught their eye.", "advice": "“The pictures are really helpful! It’s on a model, you can see every angle! And yeah, they fit well at the ankle,” enthused a participant while assessing a pair of jeans at Levi’s. Seeing the jeans from multiple angles on a “Human Model” gave her a clear sense of their fit and appearance (see #755: Consider Providing 3 or More Images of Products from Multiple Angles). “I love where it ends on the ankle…So baggy, but still kind of tapered. That’s pretty cool! I would totally rock those!” This participant appreciated how seeing the joggers on a “Human Model” made it easy to gauge the ankle fit, which was an important detail in his purchase decision. “I can also see the model so I can see that it’s quite large.” Seeing the handbag worn by a “Human Model” helps answer common questions users may have about its size, as demonstrated here at Next (UK) during our large-scale European testing. “I like these Knotted Heart studs!…I like how it includes a picture on the ear too! Just because it’s good to see the size comparison.” Seeing how earrings she liked were worn by a “Human Model” helped this participant quickly understand their size. “I like how they have a model who’s modelling it so I kind of get an idea of how it looks on somebody’s hand or a wrist,” said a different participant at Pandora as she tapped through images of a bracelet she wanted (Android, first image) and reached the images showing it modeled by a “Human Model” (second and third images). “Human Model” images are also useful to help users understand how jewelry might coordinate with clothing. “Price points are the same, so then it just comes down to, okay, what design would she like?” After confirming that 2 necklaces were similar in both price and product details, a participant shopping for a gift at Pandora based his decision on how each necklace looked on the “Human Model”: “This actually seems larger than I’d anticipated…This one almost seems larger based on this model’s neck (first image). I’d almost go with this one just cause I like the size of it, at least the perceived size of it on the model (second image).” “It’s actually super helpful when they show — especially with jewelry — an image of what it looks like on. So, you can kind of see how big it is and just kind of sizing overall,” explained a participant who clicked to an image of an earring worn by a “Human Model” at Pandora (first image). The “Human Model” photo also helped her decide whether the earrings would suit her mom: “So something like this, I do feel like would be my mom’s style.” “Similarly, at MVMT, another participant appreciated seeing the watch worn by a “Human Model” as part of a complete outfit: ”I really like this picture of it on a hand. I can sort of gauge its size in real life and see how it pairs with an outfit. “I like this, ‘cause you can see the actual size. Like it could be tiny. It could be huge. So it is helpful for jewelry to see it on someone for like to know the size to get a sense of scale.” This “In Scale” image from a previous round of testing, on the Banana Republic app, is ideal for items such as earrings where size is critical for judging suitability. Therefore, to support users in evaluating apparel and accessories items, sites should always provide “Human Model” images that show how products look when worn or carried. In testing, participants consistently used these images to quickly judge sizing details — such as where jeans or joggers fall at the ankle, how large earrings or bracelets appear when worn, or how bulky a backsack looks when carried. These images helped participants understand the product more easily than standalone product shots, product details, or reviews could. Moreover, beyond sizing, testing showed that “Human Model” images also helped participants assess whether a product suited their style. Seeing the item as part of an outfit or “look” helped users make a quick gut check on whether it matched their own style or the style of someone they were shopping for — like their mom or best friend. In many cases, model imagery was a prerequisite for deciding whether to continue evaluating the product or not. Providing this visual reference reassures users that the item will be suitable and gives them the confidence to move forward with purchasing. Combined with the best practices of providing images from multiple angles (see #755: Consider Providing 3 or More Images of Products from Multiple Angles), “Feature Callout” images (see #747), “In Scale” images (see #741: Always Provide ‘In Scale’ Product Images, and “Lifestyle” images #744: Provide 'Lifestyle' Images for Relevant Products), “Human Model” images offer a more comprehensive view of an apparel or accessories product and help users assess its visual qualities to determine whether it is suitable for them.", "summary": "Users struggle to assess size, fit, and personal style suitability for apparel and accessories products when product images don’t show how the item looks when worn.", "purpose": "" } }, { "doc_id": "doc-9299fa66a5d6f300e6b97bab2077d2f2", "title": "Ensure the Paths to Filtering and Sorting on Mobile Are Prominent and Unambiguous", "g_id": "1198", "url": "https://baymard.com/premium/guideline-collections/p8s4px/1198", "source_type": "guideline", "importance": 100, "summarized_info": { "description": "Being able to filter and sort product lists and search results is critical to users’ ability to find suitable items, and when filtering and sorting are difficult to find it can prevent users from finding a suitable product.", "issue": "Being able to filter and sort product lists and search results is critical to users’ ability to find suitable items When filtering and sorting are difficult to find it can prevent users from finding a suitable product 3 specific implementations were observed that made finding filtering and sorting difficult: using only icons to represent the path to filtering or sorting, having overly cluttered interfaces near the paths, and having overly subtle paths", "advice": "Ensure paths to filtering and sorting are easy to recognize by using unambiguous text links or button labels Avoid icon-only paths and overly cluttered interfaces near the paths to filtering and sorting Also, make the paths to filtering and sorting prominent by using size, color, and surrounding whitespace to draw users’ attention Avoid sticky widgets containing paths to filtering and sorting at the side of product lists and search results", "summary": "Being able to filter and sort product lists and search results is critical to users’ ability to find suitable items, and when filtering and sorting are difficult to find it can prevent users from finding a suitable product.", "purpose": "" } }, { "doc_id": "doc-eae2aed403da236b55c544bcf198c7ad", "title": "How to Implement “Hierarchy” Breadcrumbs for Product Pages on Mobile Sites", "g_id": "1213", "url": "https://baymard.com/premium/guideline-collections/m79rxd/1213", "source_type": "guideline", "importance": 100, "summarized_info": { "description": "Many users struggle to identify and use breadcrumbs on mobile sites, resulting in disorientation and slower, more tap-intensive navigation.", "issue": "Many mobile site users find it difficult to identify and use breadcrumbs, leading to slower navigation and disorientation Displaying only the parent category or subcategory or omitting key hierarchy layers from the breadcrumbs can limit users' understanding of the product categorization and navigation options", "advice": "Provide the full category hierarchy for breadcrumbs on mobile website product pages, potentially omitting the homepage and product page layers Breadcrumbs should be styled to be easily distinguishable from other page elements, surrounded by white space, and underlined or include visual separators Avoid overcategorization and long category names to accommodate breadcrumbs in the mobile viewport Consider making breadcrumbs swipeable to save space while still allowing users access to the complete hierarchy In testing, we found no evidence that breadcrumbs were necessary in apps", "summary": "Many users struggle to identify and use breadcrumbs on mobile sites, resulting in disorientation and slower, more tap-intensive navigation.", "purpose": "" } }, { "doc_id": "doc-7ae3c639fb534b9e75d935432746fdb5", "title": "Ensure the Main Product Image and Swatches Are Visible in the Same Mobile Viewport", "g_id": "1217", "url": "https://baymard.com/premium/guideline-collections/7a4utb/1217", "source_type": "guideline", "importance": 0, "summarized_info": { "description": "Users often rapidly cycle through different color variations, which becomes a tedious task when they’re forced to repeatedly scroll vertically to see the new variant selected.", "issue": "“I’m very much interested in all the colors. So I would probably look through those first.” As soon as she arrived on a product page on Nespresso, this participant started experimenting with the available color variations. After tapping on a swatch (first image), she saw no change initially, so had to scroll back to the top of the page: “Um…I expected that it would kind of change up here.” Once she had done so, she was then able to view the updated color variation in the main image gallery (second image): “And it did.” This additional navigational effort is likely to discourage experimentation with product variants, increasing the risk that users will not discover a variant they like. “I don’t like that I have to go all the way back up…just to see it.” A participant at Pottery Barn voiced her displeasure at the amount of vertical scrolling required to get back to the main image gallery (first image) after she had selected a color and fabric option (second image). “The color should be at the top.” Her entirely understandable expectation was that the variation swatches should be closer to the image gallery, minimizing the effort required to view the impact of her most recent variant selection. 2 additional examples In a previous round of testing, this test participant viewing multiple variations of lipstick on Macy’s had to repeatedly scroll down to the swatches, select a new color, and scroll back up again to study the resulting image. When color swatches and the main image are not visible within the same viewport, users are forced to engage in this excessive scrolling behavior. In a previous round of testing, this participant on JBL could not see the gallery indicators or color swatches within the same viewport as the main image gallery without scrolling. When screen real estate isn’t carefully considered, users must work harder to explore visual variations. Over multiple rounds of mobile testing, we have observed that participants often struggled to view images of different product variations when the color selector or swatches (see #849) were not close enough to the main gallery image. This is a particular issue on mobile, where the size and proportions of the viewport mean that page elements are generally stacked vertically as there is insufficient horizontal space to place them side by side. When these elements are visually separated, users must repeatedly scroll down to tap on the appropriate color swatch, then back up again to see the change in the main image, then back down to select a different color, etc. The physical and mental effort required by users to explore product variations is therefore increased, and users who have a difficult time understanding and comparing variations are more likely to abandon a product, even when the desired type and quality of product image is available (Product Images). While we’ve repeatedly observed users are comfortable scrolling, and will generally scroll down on product pages to find product information, being required to scroll repeatedly up and down in order to obtain basic visual information makes the process of exploring product options significantly more burdensome and time-consuming. On EE, this participant was keen to investigate phone color options. However, she had to scroll down from the main product image (first image) past the headline, short description, and promotional message (second image) to reach the swatch variation selectors (third image). Then back to the top of the page to see the new color variant she had just selected. This prompted a negative reaction: “I don’t really like that you can’t see the image when you’re clicking [the swatch]. You have to click that, scroll up to look at it, scroll down, scroll up…” After going through this process a few more times, she summarized her misgivings: “I think if you want to make this process as smooth and easy as possible…you’ve got to make it really simple for the person, so that they can literally just be like: ‘I like that color’.” Note also the sticky “Buy” overlay that restricts the amount of vertical space available in the viewport to view the page content. We observed several layout issues that commonly led to increased distance between the image gallery and swatches (and thumbnails, where they are provided; see #2884). Most commonly, product details such as the product name, star rating average, free shipping information, and price are located between the image gallery and swatches, separating the two elements and increasing the length of this part of the product page. Product pages can also have excessive padding between elements, leading to unusually large white spaces that unnecessarily lengthen the page and increase the visual separation between the gallery and swatches. Finally, sticky elements such as banner ads, navigation, and buy sections that reduce the viewport limit the amount of content that can be displayed without scrolling. Indeed, one participant during a previous round of mobile testing noted the site’s sticky navigation bar and prevalent ad, saying, “This tab here…won’t go away, so I have to keep scrolling back and forth between the colors and her face. It’s annoying me.”", "advice": "“Again, I’ll check the colors.” At Columbia, a participant had no trouble viewing the 3 different colors for a pullover when he selected their color swatches (first through third images) — and quickly settled on the black variation: “So yeah I’m gonna go with this one.” “I’m considering this for my living room.” On Houzz, this participant used the swatches below the main image gallery to color match a rug with one of the rooms in her house. She was able to cycle through multiple options quickly as both the swatch controls and the image gallery appeared within the same viewport on her mobile device. “Okay, I like when they do this, when you can click the color and it comes up.” This participant at Joybird on iOS spent 2 minutes happily browsing through the different color options, using the horizontal bubble filters and swatches to navigate. On Polaroid, this participant was able to evaluate color variations easily: “The colors…seem to indicate that [it’s a professional product] because they’re not ‘fun’ colors…like pink, purple, green…This one’s just like white, black, and I guess they threw in a red.” No vertical scrolling was required, and he was able to move on quickly to learn more about the product. Therefore, to make it as easy as possible for users to visually inspect product variations, ensure the full product image and color swatches are visible within a single viewport. Simple adjustments to the product page layout, such as relocating the product name and price to above the image gallery or below the color swatches, or minimizing the use of sticky page elements, allow the image gallery and color swatches to be more closely aligned. Extraneous information or options — such as promotions, shipping information, item numbers, etc. — should likewise be moved. Essentially, testing revealed that it’s important to think of the main product image and swatches as one “block” of information, as that’s how users will attempt to interact with these elements. When users can see these elements together without the need to scroll, the process of selecting and visually comparing variations becomes easier and less interaction-intensive, saving users time and effort. On this Away product page, users can see the main image, thumbnails, and color swatches within a single viewport. The information scent benefits afforded by thumbnails (as opposed to indicators) make them worthwhile despite the amount of space they require (see #2884). These large visual elements can appear alongside each other easily due to minimal text, with details such as the product title and price appearing above, rather than beneath, the image gallery. Thumbnails are less commonly used within mobile image galleries than other means of indicating additional gallery images such as dots. In fact, thumbnails were used for this purpose in only 25% of the mobile sites in our most recent round of testing (see #2884). When thumbnails are used in this way, however, they should also be considered as part of the information “block” described above. As well as viewing the effect of each visual variation on the default product image, users will benefit from understanding that additional product images are available in the main gallery to help them more fully assess the visual impact of the currently selected variant. As mobile devices and display technologies continue to evolve, we recommend that testing for spacing and layout occur on the most popular — as opposed to the latest — devices to accommodate different screen resolutions relative to the display size. Having an adequate number of breakpoints to account for mobile devices of different resolutions allows the site to respond flexibly and appropriately, scaling images and other page elements to fit within even the smallest of mobile viewports (see also #1095: Ensure That All Pages and Content on Mobile Are Optimized for Mobile). The viewport constraints forced by mobile devices make it difficult — but by no means impossible — to include the image gallery and color selector swatches in close proximity. With careful consideration of layout, sites can accommodate users’ natural behavior by locating color swatches (and thumbnails, if present) within the same viewport as the image gallery, providing all of the elements users need to visually explore and evaluate product variations. Finally, while we observed this issue most commonly for color variation selectors, whether presented as swatches (which is recommended, see #849) or otherwise, the observations and solutions discussed apply to any visual variation selection that results in unique gallery images, such as style, pattern, etc.", "summary": "Users often rapidly cycle through different color variations, which becomes a tedious task when they’re forced to repeatedly scroll vertically to see the new variant selected.", "purpose": "" } }, { "doc_id": "doc-33d1351d322abad0b32b2df3fb513131", "title": "Place the Product Description within 1–2 Viewports of the End of the “Buy” Section on Mobile", "g_id": "1226", "url": "https://baymard.com/premium/guideline-collections/yrj1sh/1226", "source_type": "guideline", "importance": 100, "summarized_info": { "description": "Mobile page designs can make product descriptions — crucial to users’ ability to make a purchase decision — hard to find, especially if “One Long Page” is used.", "issue": "Mobile page designs can make product descriptions — crucial to users’ ability to make a purchase decision — hard to find, especially if “One Long Page” is used Users often struggle to locate the product description if it's found more than 1 or 2 viewports down the page from the 'Add to Cart' button Difficulty in finding the product description can lead to user frustration and product abandonment Some users may not assume a product description exists if it's not easily accessible Users find secondary content like shipping/pickup info, 'Add to List' buttons, sitewide promotions, and cross-sells, relevant only after deciding on the product's suitability based on the product description", "advice": "Place the product description within 1 or 2 viewports of the end of the “Buy” section, and consider partially expanding the description The 'Buy' section should ideally include the product headline, images, variations, price, and the 'Add to Cart' button Secondary content and features should be provided to users only after they’ve had a chance to thoroughly investigate the product by reading the product description", "summary": "Mobile page designs can make product descriptions — crucial to users’ ability to make a purchase decision — hard to find, especially if “One Long Page” is used.", "purpose": "" } }, { "doc_id": "doc-cb06188ca449dac760d6954cded4e7d2", "title": "Avoid Excessive Use of “Marketing Copy” in the Product Description", "g_id": "1238", "url": "https://baymard.com/premium/guideline-collections/yrj1sh/1238", "source_type": "guideline", "importance": 33, "summarized_info": { "description": "Users feel “oversold” by excessive marketing copy, which can in turn damage the credibility of claims made about products, and distract users from learning about a product’s key features.", "issue": "Users feel “oversold” by excessive marketing copy, which can in turn damage the credibility of claims made about products, and distract users from learning about a product’s key features Users often struggle to discern actual product information from the embellished language of marketing copy Users encountering excessive marketing copy often become more skeptical of future marketing copy and product claims", "advice": "Limit marketing copy, or overwrought or flowery language, in the product description Instead, consider separating out marketing copy from the product description (e.g., by placing it within its own section within the product description) Users are less likely to fault a site for excessive marketing copy if it's clear the content was written by other users, such as in social media content or user reviews", "summary": "Users feel “oversold” by excessive marketing copy, which can in turn damage the credibility of claims made about products, and distract users from learning about a product’s key features.", "purpose": "" } }, { "doc_id": "doc-472f923768f03c9e61bb87d7b560bab5", "title": "Consider Scaling Gallery Images Proportionally When Switching to Landscape Mode on Mobile", "g_id": "1488", "url": "https://baymard.com/premium/guideline-collections/7a4utb/1488", "source_type": "guideline", "importance": 0, "summarized_info": { "description": "Users may turn their mobile device to landscape mode in order to see larger, more detailed images and will be disappointed if the image isn’t as large as they expected.", "issue": "", "advice": "", "summary": "Users may turn their mobile device to landscape mode in order to see larger, more detailed images and will be disappointed if the image isn’t as large as they expected.", "purpose": "" } }, { "doc_id": "doc-5fe90ff18bd3995b90bbbd2fbdc52437", "title": "Always Feature Essential Product Details and the Product Thumbnail In the “Added to Cart” Overlay", "g_id": "1490", "url": "https://baymard.com/premium/guideline-collections/40rcjv/1490", "source_type": "guideline", "importance": 100, "summarized_info": { "description": "Users rely on “Added to Cart” overlays to verify the accuracy of just-added items and cannot do so when they lack critical product and order information.", "issue": "Users rely on “Added to Cart” overlays to verify the accuracy of just-added items and cannot do so when they lack critical product and order information Observed issues with overlays include the absence of confirmation messaging, no product information, missing or too small product thumbnails, and lack of critical product details Users often hesitate or backtrack when product information is unavailable in the “Added to Cart” overlay, disrupting their shopping experience", "advice": "“Added to Cart” overlays should prominently confirm that the item was successfully added to the cart Furthermore, it should include a large product thumbnail and the product name, price, quantity, variation selected, discounts or savings, core product specs, free shipping tier indications, and special offer qualifications", "summary": "Users rely on “Added to Cart” overlays to verify the accuracy of just-added items and cannot do so when they lack critical product and order information.", "purpose": "" } }, { "doc_id": "doc-4d1c51d148967c5047fe3a3ca1d76f59", "title": "Test Routinely for UI Bugs and Quirks and Use “Progressive Enhancement”", "g_id": "1498", "url": "https://baymard.com/premium/guideline-collections/58zheo/1498", "source_type": "guideline", "importance": 0, "summarized_info": { "description": "UI bugs and layout glitches erode users’ confidence in a site and degrade their ability to search for, explore, and purchase products.", "issue": "UI bugs and quirks have for years been observed during our testing to be pervasive, persistent, and sometimes a direct cause of abandonment, especially if these errors are experienced in combination with other issues. Tech quirks are, unfortunately, simply a fact of life of the e-commerce user experience. While it’s impossible to ensure that these issues never happen, it is possible to implement practices and strategies that reduce their occurrence and severity. “All right, let’s view our bag…Where did my stuff go? ‘Add to bag.’ ‘Added to bag.’ Where is my stuff?…Yeah, I wouldn’t say that this website is very effective.” A test participant at Nike who had added a sweatshirt (first image) and the matching joggers (second image) to her bag was dumbfounded when she later discovered that her cart was empty (third image). She repeatedly re-added the items to her cart, to no avail. A participant at Nicce encountered difficulty navigating the main menu because some categories were cut off at the bottom of the screen (first image). He finally resized his own screen to accommodate the menu’s full size: “Now I’m able to see it. I just had to get my screen to the right size to fully see that menu. So just a little bit of an issue there.” “No, come on. I dunno if that’s a glitch or what, but if it shows that there’s a thousand products and I can’t sort it by price, which is one of my big demands…” This participant at The Company Store tried to use the “Sort By” feature, but when he clicked on the arrow indicator, nothing happened. He was so frustrated by the inability to sort by price that he almost abandoned the site. “So if I try to add this to the cart it says you can’t add to the cart as well. Even though there’s one in stock. I mean, it seems like if there’s one in stock here that I should be able to put it in the cart. If I want to schedule delivery, I can do that and everything, but I’m unable to do [add the item to the cart], which is annoying.” Some tech issues can have very severe consequences. Many test participants during encountered an issue with adding items to the cart in the Lowe’s app. This issue persisted for a number of days and could have resulted in many lost sales. Throughout large-scale European testing, bugs and quirks caused issues for test participants in the UK, Germany, and Nordic countries. Issues ranged from a search function being unavailable (first image), to a participant getting stuck in an address validator and being unable to proceed (second image), to a page without content appearing when a participant clicked on a tooltip (third image). While some issues can cause mild annoyance, others can lead to users coming to a full stop and leaving the site. “We have a ‘Size Guide’ that says…‘Cannot Be Displayed’. That’s helpful guys [laughs]” This error in the Banana Republic app made a bad impression on this test participant. After tapping on the “Size Guide” (first image), she was redirected to the mobile site (second image) where the requested page was unavailable. When this credit card number was partially obscured by logos, it was very difficult to verify the typed input. 27 additional examples This participant encountered an unexpected error when tapping on an item in the product list in the Walmart app that interrupted the product finding progress. If issues like this persisted, users could easily decide to go elsewhere. “Okay, and now it’s added to cart and let’s see, if we go to my cart, actually I had stuff in my cart already but let’s see, for some reason it didn’t add. Wonder why. Add to cart. Oh, I’m sorry. That’s why — it’s not in stock. That’s why it didn’t add to the cart.” When this participant during app testing found that an item wasn’t added to the cart (third image, only 2 items that had previously been added were in there), he assumed that it was because it was not back in stock for over 3 weeks (as stated in the first image). However it was also stated that it could be backordered (“Order it now.”). Such confusion caused by a tech issue could easily result in a lost sale. A participant (a co-founder and CEO of a real estate company) in our digital subscription services study opened the “Why Slack?” menu in the main navigation and clicked the “Features” link (first image). However, the only response from the site was the display of a dotted line around the “Why Slack?” menu item (second image). Clicking the “Features” link a second time elicited the expected response from the site. This unexpected behavior with Slack’s main navigation occurred multiple times for some participants. “‘Email large files’…It looks like the homepage again. But it has a different name. It looks like they have a bit of a problem with their site [laughing].” A participant (a president of a web consulting firm) in the digital subscription services study clicked what he thought was a promising link in Sync’s footer, “Email large files” (first image). However, it took him to the homepage instead (second image). Links that do not lead to the expected destination waste users’ time and damage their overall perception of the site. “Here’s another price, which is changing…It said something else when I scrolled down here.” A participant (a customer success manager for a computer software / SaaS company) researching team messaging tools noted that the savings calculator on Chanty’s plan matrix page adjusted the number of team members — and thus the annual savings amount — without any input from her. This unexpected behavior caused her to doubt the credibility of the tool. “I don’t know if the scroll is broken or not, is this supposed to happen here?…It takes me down a six watches and it kind of sticks…That would be something that would throw me off at this website pretty quickly, because it looks like the web page isn’t working properly…If I were at this website and this happened, I would leave. I’d be thinking, if this website’s broken, it’s probably not somewhere I want to spend my money.” The large dropdown navigation menu on Farer did not work for this participant, leaving him only able to view part of the scrollable menu. “Hmm. That was weird.” Many participants in grocery testing of Walmart’s mobile site experienced a glitch where the main navigation menu failed to load, opening to a blank layer. Explaining how he would deal with such an issue, one participant shared, “I usually just try and refresh. I’ll just click in and out of something multiple times, and then I’ll usually refresh the page or ‘X’ out and then jump back in. But if it happens more than four or five times, I kind of get frustrated. Unless I really need to use the website, I kind of just give up and move on.” “Oh, ‘It’s not you, it’s me’. What’s up? Do you see that? Well, I’m not calling an 800 number, trust me”, complained a participant shopping for hotels during large-scale Travel Accommodations testing when she encountered an error page at Hilton. “Oh, that’s screwy. I’d be kind of pissed. I would click off the site”, she explained, abandoning the site in frustration after multiple unsuccessful page loads. “I want to get the map out of the way. I’m having trouble with the map.” During testing, multiple participants shopping for whole property rentals at Vrbo experienced display issues with the map. Consequently, they were unable to identify suitable properties for their budget because property prices were obstructed. “It doesn’t look like it completely scrolls down to see everything. Yeah, it seems to be stuck here”, explained a participant shopping for a hotel room at a boutique hotel, The Artezen. She was unable to confirm if the room she was interested in had a mini-fridge, so she abandoned the process of selecting a room. “This image is not loading. I don’t know if that’s a me problem or a website problem. But it does make me frustrated and I don’t like the site already.” A participant shopping for a hotel room at a boutique hotel, The Sohotel, quickly lost patience and abandoned the site when the property image in the hotel details overlay failed to load properly. “I’m gonna click on the Yankee Stadium because I want to know what game days are — and it takes me nowhere — or it seems to scroll me to the bottom of the page. Is that what it is? Oh, no, it did nothing. But it looks like it should have done something.” A participant shopping for helicopter tours at HeliNY during large-scale Travel Tours & Experiences testing clicked on a sight in the route map key, expecting it to display specific details about that particular location. Instead, the page refocused to an area below the map. Frustrated, he abandoned the map. “I kind of like the idea that you can select the — oh, maybe not. I find it a little frustrating — I would’ve thought that if you click on one of these, it would’ve navigated automatically to the key on the left. But, it doesn’t seem to do that.” Another participant at HeliNY was disappointed when he discovered the interactive map of the “City Lights Experience” tour didn’t behave as he expected. “I’m getting an error to look through the calendar. So for me, booking something — getting an error on the website — I’m out. I’m going to a different side at that point. If I can’t get to the calendar, I definitely can’t book it”, complained a participant attempting to check the availability of the “North Shore Shark Adventure” tour at Blue Hawaiian Activities during large-scale Travel Tours & Experiences testing. “The lava tour is $50, but when I tell it ‘sort by price’, all of a sudden those really cheap tours disappear — like this ‘Skylar and Geothermal Spa’ is $76 and then it’s gone”, complained a participant at Gray Line Iceland, unable to sort the tour listings by price. “It’s frustrating that when I start sorting it by different options, certain tours are disappearing”, he remarked as he abandoned the task. “‘Important Information’ Oh, where did it go?” A participant at Roberts Hawaii was briefly disoriented when she clicked to expand vertically collapsed content on a “Tour Details” page and was repositioned to the bottom of the page. “There it is”, she remarked after she scrolled back up and refound her place on the page. “Oh, ‘Material Declaration’, that’s usually where they put RoHS information if they have it. Oh, okay. That’s not helpful”, complained a participant (an electronics engineer) when he encountered an error page while trying to access a document on a product details page at STMicroelectronics during our large-scale B2B electronic components and machinery testing. However an error page was displayed. “They have a section for a ‘Lightning Surge Noise Filter’, but then you go there and there are no results! I feel like if you have something categorized on your site, you should maybe have products for it”, laughed a participant (a design engineer) shopping at CoreStaff during our large-scale B2B electronic components and machinery testing. After clicking a subcategory link (first image), he was redirected to a “No Results” page (second image). “Okay, that’s not very good. That’s a red flag. Yeah, any non-working links obviously that’s just poor maintenance.” A participant (a system design engineer) tried to view the datasheet for a part at TE Connectivity during our large-scale B2B electronic components and machinery testing (first image). However, an error was displayed (second image). Errors damage users’ overall perception of the site and increase the risk of abandonment. “It’s just being very slow in loading. [The supplement page] doesn’t want to open. Yeah, I feel like it’s not loading.” At Swanson Vitamins, a participant became frustrated when they tried to click into a supplement detail page and the site appeared to freeze. As the page took too long to load, the participant abandoned the site. “It looks like the software expired, so I don’t think they should have it on their homepage. Yeah, it looks like they just forgot to take it off. That’s kind of annoying because, you know, I took my time to like read all of this and then they have at the bottom that it’s not even valid anymore. So that’s a little irritating and it makes me think that maybe whoever is in charge of this site is not really paying attention to it, maybe.” At Sea to Table, an expired promotion on the live site caused the participant to view the site especially poorly, as they had already spent time evaluating the promotion before discovering the deadline had already passed. “Oh, it’s on the very bottom. Okay. I thought it was weird that ‘California’ was all the way on the bottom since it’s normally like by alphabetical order.” At Oceanbox, participants had to search the entire “State” drop-down list — which was otherwise in alphabetical order — for “California”. In addition to slowing down users going through the checkout flow, site or database errors such as this can cause users to view the brand unfavorably. “I’m clicking on the ‘info’ [tooltip] and the ‘info’ isn’t working. So I would say one of my biggest critiques with this website is that some of their links don’t actually work or redirect you to the wrong place. And that’s a little less than helpful.” At HelloFresh, participants occasionally encountered issues with the site that resulted in page elements not working as intended. Almost all participants who encountered these issues made negative comments about the site or brand. Even minor site issues can quickly damage users’ brand impression — leading some to abandon out of frustration due to the site “not working”. “After clicking, it’s not really working at all. Yeah, nothing’s happening at all. I double clicked it. Nothing.” After signing up for a promotion at Gobble, the participant tried to use the primary button one the overlay but the button was inactive. After trying to click the button again several times, the user was stopped in their tracks and had to find another method of closing the overlay. At the Microsoft Store, a test participant’s browser autofill clashed with the non-native placeholder text, making the autofilled zip code unreadable. It’s advisable to use native UI components where available, and crucial that any custom UI implementations are tested for compatibility in all common browsers and in combination with common browser features such as autofill. A test participant in an earlier round of testing at Sephora was swiping through the product page image gallery and the second image in the carousel simply read “Invalid SKU selected”. She continued on swiping images. Multiple test participants in one round of testing at Staples experienced a strange error message, “Expectation Failed”, when scrolling product lists. At JBL, after a participant tapped into the search field, the cursor indicator appeared well below the field (note the blue cursor indicator placed just above the “Headphones” heading, left-aligned with the search field). It took the participant repeated, multiple attempts before she was able to get the cursor indicator in the search field and submit the search. Layout bugs such as this one on J.Crew can cause users to feel as if the site is ‘broken’, reducing trust and giving a poor impression.", "advice": "To minimize the number of UI bugs and quirks encountered by users, first develop a list of user and content contexts and use that to develop a “context matrix”, which can be tested at regular intervals and upon each feature launch. (Parsing web analytics logs can help determine the most common user conditions.) The number of combinations may run into three-digit territory for complex or important pages such as the checkout flow. These contexts often include the following: Screen sizes. Make sure to test page designs across a wide array of screen sizes — phone, tablet, laptop, and desktop at a minimum — and preferably some states in-between if the site is responsive and scales fluidly. Input methods. Make sure the site doesn’t restrict users to a single input method, as it can render a site useless if the user’s input method isn’t supported. Pay special attention to input fields (e.g., see #658: Use Localized Input Masks for Restricted Inputs and #669: Be Very Cautious When Using Custom Designed Selection UIs), touch keyboards, and hover states. History and states. A page may exist in different variations depending on the state and history of the user. For instance, a user may have submitted invalid data and see another variation of the page. Another user might have form fields autofilled by their browser or a plugin. Make sure to test all common user and page states, from a completely “pristine” environment to users with plenty of browser features enabled. Multipage content. Some content may appear on multiple pages. Make sure to preview the content in all the contexts in which it appears to avoid presenting conflicting messages to users. Ideally the content management system should be designed to clearly communicate or preview all use contexts. It’s particularly important to test key pages that are part of every user’s path. For example, the checkout process should always be tested since this is required of every user making a purchase. Also, the most commonly used product page templates should be tested. Finally, test your website’s application logic and styling in a range of mobile browsers and operating systems. In addition to routine testing, instead of assuming everything is fine and will tend to stay that way, consider designing for exceptions. It flips the typical mindset on its head by assuming that UI bugs will occur, putting the emphasis on resilience over building a perfect, 100% flawless website. The aim is to minimize UI bugs that creep in over time. In practical terms, a resilient web design requires adopting best practice web development principles such as progressive enhancement, where a pared-down but highly robust baseline experience is developed and then served to everyone regardless of their physical and device capabilities. This baseline experience is then upgraded for those users with extra capabilities and more powerful devices, and increasingly complex site features are added in based on that user’s context, taking the “pared-down baseline experience” and turning it into an increasingly “feature-rich experience” — but only up to the point the user and their device is capable of handling it. A progressively enhanced site never subjects the user to an experience their device isn’t capable of handling, which is a very common cause of layout bugs and flaws in interactive features. Instead, advanced features are only ever served to devices that natively support them. Furthermore, because the user is served the baseline experience first, which is then progressively built upon, if at any point one of the feature enhancements should invoke an error the improvement simply fails and doesn’t get applied, leaving the user with the perfectly usable baseline experience — just without a few of the fancy upgrades. In other words, even when UI bugs do occur, they will often be isolated to a particular feature rather than break the entire experience. The baseline experience would typically be put through a more exhaustive context matrix since this is served to everyone and is thus the foundation on which everything else is built upon, and must therefore be rock-solid. However, where organizational testing procedures can’t (or simply aren’t) automated, it may be possible to save on expensive testing of some site enhancements because they can rely on native modern browser and device features and simply be skipped where unsupported. A good example of progressive enhancement is using “the shell approach” for custom-designed form field UIs, instead of going for truly bespoke custom-developed form inputs — as described in #669: Be Very Cautious When Using Custom Designed Selection UIs. These four ways to support “Progressive enhancement” of site content and features should be considered: Set good CSS defaults for embedded content (images, videos, iframes, etc.). This will minimize the risk of stray layout bugs and ensure content always fits the user’s viewport. When you intentionally want to scale something differently, the cascade-part of CSS allows the generic rule to be easily overwritten to enforce the intended layout. In other words, the default should be to embed the content to fit to the screen, and then to explicitly define other behavior when something else is desired. Utilize native technologies whenever they are available. These technologies are more reliable, and do not depend on JavaScript implementations or CSS rules, which suffer from various UI bugs across browsers. They also have the added benefit of recognizability. The user has seen the element on other pages and in other apps on the device and therefore knows how to interact with it immediately. Only when the native implementation is unsupported by the device should custom styles and behavior be applied as fallback solutions. Avoid or limit the reliance on third-party tools and vendors (and ads). The problem with having these external plugins at the center of a design is that their unavailability can bring down key processes of the site regardless of how bug free your own code is. Again, implementing these third-party resources following the principles of progressive enhancement ensures this won’t happen — by only using external tools to improve the user experience if or once they load, users will be able to use your site perfectly fine even when they don’t (e.g., their servers are down, code is buggy, etc.). Make recovery easy. Making recovery easy is a matter of making sure the user can seamlessly resume where they came from once an error has been fixed. A key aspect of this is preventing data loss. This can obviously be challenging in the case of server errors because the error can blast the usual data-persistence mechanisms, causing the user’s input to be lost. However, there are ways to prevent this by temporarily storing the user’s input in a client-side database (e.g., localStorage) until the server responds with a success message. (Just make sure to implement this using progressive enhancement so it doesn’t break older browsers.) See Validation Errors & Data Persistence. Meanwhile, UI bugs and quirks tend to be hard to identify because they don’t invoke a server alert and therefore aren’t brought to anyone’s attention — and can linger for months before they’re discovered and fixed. This is largely a visibility issue — if people in the organization knew about these UI bugs, they would get fixed. Unfortunately, just because layout and other UI bugs aren’t as “visible” as a server outage doesn’t mean their impact can’t be just as harmful. By testing regularly, and adopting best practice web development principles such as visual regression testing, resilient web pages can be built that don’t break apart due to a single error.", "summary": "UI bugs and layout glitches erode users’ confidence in a site and degrade their ability to search for, explore, and purchase products.", "purpose": "" } }, { "doc_id": "doc-2582ea1c98a1f1cb1ec8bdec5e4f795f", "title": "Make Return Policies Easy to Read and Understand", "g_id": "1501", "url": "https://baymard.com/premium/guideline-collections/lvnybn/1501", "source_type": "guideline", "importance": 0, "summarized_info": { "description": "Users will be less confident about purchasing products if they don’t understand the policies for returning them.", "issue": "", "advice": "", "summary": "Users will be less confident about purchasing products if they don’t understand the policies for returning them.", "purpose": "" } }, { "doc_id": "doc-5d260b0ed4fe45954bdbbab81a6a6379", "title": "Improve the Actual and Perceived Performance of Pages", "g_id": "1509", "url": "https://baymard.com/premium/guideline-collections/58zheo/1509", "source_type": "guideline", "importance": 0, "summarized_info": { "description": "Laggy UIs impede product finding and are a direct cause of abandonments.", "issue": "“Oh, okay. I’m trying to click on other ones but it’s not working, there it goes…I’m clicking at the different colors, but it’s not… It’s taking like three or four taps to change it, which is kind of annoying. It shouldn’t take that long.” This test participant in the Sephora app was frustrated by the delay in registering her taps on color swatches. If users encounter repeated delays during product finding, there is a strong risk that they’ll abandon the process. “It’s loading really slowly. This is going to take forever just to look. But the crazy part is I like the way some of their sofas are, so I want to see what they have…no, I wouldn’t feel comfortable buying from them.” This iOS participant at Joybird liked her initial impression of the site’s products, but when she arrived at the product list, the thumbnails took so long to load that she wasn’t able to shop effectively, leading her to lose trust and abandon the site. “Oh God…the two seconds it takes for that to load, it adds up. It’s enough to make me not want to use it at all. So I’m only going to use that for things that are real deal breakers at this point that don’t involve a lot of clicking.” This iOS participant at Ashley Furniture preferred to shop using plentiful filters, but the lag time after each filter selection was so frustrating to him that he stopped using most of them, making it harder for him to find a product that fit his criteria. “Just scrollin’ on the homepage, seeing what they got here. ‘Shop By Category’, I don’t see anything. Nothing’s showing up here. It’d be nice if they had the pictures, I could get a quick idea of what they carry.” This iOS participant at Parachute was unfamiliar with the brand, so he scrolled the homepage to get a quick impression of what they offer, but was blocked by the slow-loading pictures. “I don’t like how the pictures disappear honestly, based on that I might be like, “Okay, I’m done here.”” Delays in loading crucial content, such as thumbnails here on Joybird, could cause users to shop elsewhere. “So ‘Pants.’ I dunno why it’s taking a little bit to load…It’s the site ‘cause Google loaded quickly. Um, try to do it again. It’s loading. Oh, there it goes. Huh. It’s taking quite a bit…I’m not sure what’s going on.” A participant at Express tried to navigate to the “Pants” category but it wouldn’t load (first image). She successfully opened Google in a new browser tab to ascertain that the problem lay with the site (second image). She waited and reloaded the site for over 2 minutes until the product list appeared — though many users will not be as patient. “Keeps going all crazy on me… it was just like it just was taking a minute to load and I was just being impatient. I was trying to scroll while it was still loading.” A laggy page slowed this test participant on Home Depot, making it unnecessarily hard for her to double check the dimensions of an item she had added to the cart. “It’s slow. We have quite fast internet here. I’m not into slow pages. Nope. Not good at all.” During European testing, it took twelve seconds for this Nordic site to load the search results page after the test participant selected an autocomplete suggestion. Such issues delay product finding, and if they persist, could easily cause users to look elsewhere.", "advice": "“This is a very fast site. I really like it. And it’s very smooth, as well, to scroll through. So, I’m a fan of this one already. Straightaway, I’m scrolling and it’s picking up my sensitivity in my fingers. I quite like that. Just makes it a bit easier to use.” When a site or app was generally experienced by test participants as fast and responsive, finding and purchasing products was a smoother process. Indeed, during testing, participants actively preferred sites that didn’t unnecessarily delay them during product finding and checkout. As one said: “Their website seems to scroll nicely. It’s loading great. I go on some websites sometimes they take forever for the pictures to load. This one is loading really great. It’s got a good speed to it”. However, sites can never completely control how fast they are for all users all of the time — they are, after all, at the mercy of users’ Internet connections, the age and condition of their devices, and so on. That said, there are some general principles that can be explored to attempt to mitigate the frequency and severity of site issues that slow users; in particular, by focusing on improving both actual load times (how long it takes before the entire page has finished loading) and perceived load times (how long users have to wait before being able to interact with the page). A good starting point for understanding and improving your site’s load performance is to run a Google Lighthouse page speed test, which also provides specific recommendations. Beyond that, consider some of the general web performance “basics”, such as the following: Load as little content as possible and serve content from nearby locations (e.g., using a Content Delivery Network) Minify assets: While the most significant savings can be had by reducing and optimizing image sizes, file size reductions for both JavaScript and CSS will also reduce lag. Load Javascript without blocking: JavaScript blocks page rendering by default, which means the page will only show once the entire script has been downloaded and parsed. This often results in users being left to stare at blank screens for long amounts of time. Therefore, JavaScript should instead be loaded in a nonblocking manner so that the page can render without waiting for the JavaScript to be downloaded and parsed. Enable gzip compression: Make sure your webserver is configured to serve your assets gzipped to browsers that support it — which most browsers do. This can shave a significant chunk of bytes off each request. It is not uncommon to see a 50% reduction in file size. Cache indefinitely: “The fastest HTTP request is the one not made” is a classic quote in the web-performance community. The best caching strategy is to cache your assets indefinitely and then use asset timestamps or MD5 fingerprints to expire them. Define the width and height of all images: This prevents elements from shifting around the page as images are loaded, and thus prevents the browser from recalculating the layout multiple times. Equally important, because elements don’t shift around, the user can start scrolling the page without elements suddenly being pushed out of their viewport because an image higher up on the page finished loading. The key to lowering perceived load times is understanding that the impact on users is mainly determined by two factors: How high on the page the content is — everything above the fold is high priority and What the core content of the page is (e.g., the first 8-10 items in product lists or search results). All other features and content have lower priority and can load more slowly without having a significantly detrimental affect on users’ experiences. Main navigation links and text and graphic elements above the fold are high-priority content since these are the bare minimum a user needs in order to interact with the page. Therefore, to improve perceived load times, consider the following: In product lists and search results, prefetch 5–10 products ahead and then present these immediately on the next page if the user requests more items (a technique that applies both to “Load More” (#501) and “Pagination” (#504)). This way new products can be displayed instantly and the user has something to look at while the remainder of the list loads. Provide load indicators — see #928. Without load indicators, users are left without a crucial indication that their touch gesture or action has been registered and that new content is currently in the process of being loaded. As a result, a lack of load indicators has been observed to often cause users to end up tapping multiple times, which can lead to a cascade of issues — for example, unintentionally going back to an area of the site they had been on previously, leading to a sense of disorientation; or firing the request once more, leading to an even longer wait. Limit ads and other content extraneous to the product-finding and purchase process. Ads are perceived as disruptive, and can contribute to a site feeling generally laggy; for example, during mobile testing one participant had to repeatedly dismiss overlays that popped up while she was browsing products, which made the product-browsing process slower and feel more “chunked”. (See #284 and #788.) Ensure the “Back” button functions as users expect — see #1057. When users perceive that they’re stuck due to a slow-loading page or feature, the first action many take is to tap the “Back” button, hoping to reorient themselves and “reset” the site. If the “Back” button takes them to an unexpected location, however, many wind up feeling even more frustrated and disoriented — compounding the already poor experience they’re having.", "summary": "Laggy UIs impede product finding and are a direct cause of abandonments.", "purpose": "" } }, { "doc_id": "doc-88c40f1192f39258a3f64c53ccb65b44", "title": "Adapting Images for Users with Visual Impairments", "g_id": "1543", "url": "https://baymard.com/premium/guideline-collections/cb3zzh/1543", "source_type": "guideline", "importance": 75, "summarized_info": { "description": "Non Decorative Images which lack proper markup can be difficult or impossible for users with visual impairments to understand and use.", "issue": "Non Decorative Images which lack proper markup can be difficult or impossible for users with visual impairments to understand and use Images with embedded text can be problematic as they are inaccessible to assistive technologies such as screen readers and other tools that provide adaptive text sizing", "advice": "Consistently use descriptive 'alt' tags — which don’t rely on the surrounding context — for all non Decorative Images Avoid embedding text in images Present complex images — such as a size chart — as a table, which can be navigated by a screen reader Summary Decorative Informational Functional Buttons (e.g., add to cart, form submission) Icons (e.g., save, search, print, email) Image Links (e.g., product subcategory image links on category pages) “Image, Shop Ann Taylor” “Link, Shop Now” “Link, Shop Petites” “Link, Details” Summary Research Findingschevron-down Video & Quiz Review Tool Audit Performances Implementation Examples Benchmark Performances Changelog", "summary": "Non Decorative Images which lack proper markup can be difficult or impossible for users with visual impairments to understand and use.", "purpose": "" } }, { "doc_id": "doc-4cc4031c9633c0e2b2b1b48cfc58647d", "title": "Creating Accessible Form Fields and Inputs", "g_id": "1544", "url": "https://baymard.com/premium/guideline-collections/cb3zzh/1544", "source_type": "guideline", "importance": 100, "summarized_info": { "description": "Poorly implemented form fields and user inputs can make inputting user information difficult as users can be unsure what information is being asked for and in what format the information is accepted, especially for users aided by assistive technologies.", "issue": "Poorly implemented form fields and user inputs can make inputting user information difficult as users can be unsure what information is being asked for and in what format the information is accepted, especially for users aided by assistive technologies Placeholder text can cause accessibility issues as it is not always supported by assistive technologies and often fails to have the sufficient 4.5:1 contrast ratio with the background", "advice": "Form field labels should be visible to sighted users near their associated form fields and programmatically discernable by assistive technology Grouped fields, similarly, should be associated programmatically with any relevant instructions provided for the form as a whole Inline form field labels and placeholder text should be avoided except for nonessential information (such as input examples) Summary Summary Research Findingschevron-down Video & Quiz Review Tool Audit Performances Implementation Examples Benchmark Performances Changelog", "summary": "Poorly implemented form fields and user inputs can make inputting user information difficult as users can be unsure what information is being asked for and in what format the information is accepted, especially for users aided by assistive technologies.", "purpose": "" } }, { "doc_id": "doc-6a53f717984197a04f078b2598303d1a", "title": "Page Design and Visibility Considerations for Accessibility", "g_id": "1545", "url": "https://baymard.com/premium/guideline-collections/cb3zzh/1545", "source_type": "guideline", "importance": 75, "summarized_info": { "description": "Poor visual design and styling can make it difficult for users with visual impairments to access and understand information on a site.", "issue": "Poor visual design and styling can make it difficult for users with visual impairments to access and understand information on a site Information and site elements exclusively communicated through visual means can be inaccessible to users who rely on assistive technologies like screen readers Insufficient color contrast can make reading text-based content or locating page elements difficult for users with low vision", "advice": "Page design — including text and page elements — should be scalable through the browser’s built-in zoom feature, with no loss of usability Further, the text should be styled using relative units (e.g., em) rather than fixed units (e.g., px) Text-level styling — such as a price strikethrough — should include either an alt label or invisible text Page content should exceed minimum levels of color contrast — 3:1 for large text and page elements, and 4.5:1 for normal-sized text Further, information should not be exclusively communicated through visual means (e.g., color swatches, icons, link styling, etc.) and should be designed to incorporate screen readers Summary Line height (i.e., the spacing between lines of text): 1.5em (i.e., 1.5 times the font size) Paragraph spacing: 2em Word spacing: 0.16em Letter spacing (i.e., tracking): 0.12em Summary Research Findingschevron-down Video & Quiz Review Tool Audit Performances Implementation Examples Benchmark Performances Changelog", "summary": "Poor visual design and styling can make it difficult for users with visual impairments to access and understand information on a site.", "purpose": "" } }, { "doc_id": "doc-0cfc3039e3d3aeed51d6c9534239d910", "title": "Ensure Overlays Are Accessible to Assistive Technologies", "g_id": "1546", "url": "https://baymard.com/premium/guideline-collections/cb3zzh/1546", "source_type": "guideline", "importance": 75, "summarized_info": { "description": "Overlays which don’t incorporate WCAG accessible principles within the HTML markup can leave users aided by screen readers unable to use a keyboard to interact with the overlay’s elements, unsure of the overlay’s purpose, or unaware of the overlay’s existence altogether.", "issue": "Overlays which don’t incorporate WCAG accessible principles within the HTML markup can leave users aided by screen readers unable to use a keyboard to interact with the overlay’s elements, unsure of the overlay’s purpose, or unaware of the overlay’s existence altogether", "advice": "Accessible overlays should identify themselves to assistive technologies as a 'dialog', including a name that describes the overlay's purpose (and possibly a description of content for complex overlays) Furthermore, keyboard focus should be assigned to either the overlay itself or the first interactive element (given that contextual information about the overlay is included) While open, users should only be able to interact with the overlay's elements (which can be done by tagging 'background' elements with an aria-hidden attribute), although standard assistive controls (e.g, up and down arrow, tab, etc.) and universal controls (e.g., escape key and F6 for desktop, “Back” button for mobile, etc.) should still work Summary Ensure the overlay identifies itself as a dialogue Give overlays accessible names Consider giving complex overlays a description using the aria-describedby attribute Assign keyboard focus location on newly opened overlays Isolate keyboard focus to the overlay’s elements Provide a standard method for closing and navigating overlays Summary Research Findingschevron-down Video & Quiz Review Tool Audit Performances Implementation Examples Benchmark Performances Changelog", "summary": "Overlays which don’t incorporate WCAG accessible principles within the HTML markup can leave users aided by screen readers unable to use a keyboard to interact with the overlay’s elements, unsure of the overlay’s purpose, or unaware of the overlay’s existence altogether.", "purpose": "" } }, { "doc_id": "doc-fcd5c1da3493ea95fe402e0f3630bfad", "title": "Fundamentals of Accessible Markup for Custom Page Components", "g_id": "1590", "url": "https://baymard.com/premium/guideline-collections/cb3zzh/1590", "source_type": "guideline", "importance": 75, "summarized_info": { "description": "Nonstandard implementations of common UI elements can fail to be recognized by assistive technologies, such as screen readers, leaving users confused by or unaware of their existence — and unable to properly interact with them.", "issue": "Nonstandard implementations of common UI elements can fail to be recognized by assistive technologies, such as screen readers, leaving users confused by or unaware of their existence — and unable to properly interact with them Mismatches between an element’s visual label and programmatically defined name can lead to problems for users who rely on assistive technologies", "advice": "Custom page elements and UI components must have programmatically discernable names to be read by screen readers; include ARIA roles, and have properly implemented states and properties (with corresponding values) Summary Names, which identify page elements to assistive technology Roles, which mark the purpose of a page element (and how to interact with it) States and Properties, which store the current and potential qualities of a page element using Values Summary Research Findingschevron-down Video & Quiz Review Tool Audit Performances Implementation Examples Benchmark Performances Changelog", "summary": "Nonstandard implementations of common UI elements can fail to be recognized by assistive technologies, such as screen readers, leaving users confused by or unaware of their existence — and unable to properly interact with them.", "purpose": "" } }, { "doc_id": "doc-83f2f90b95c4d02705c252209a86d974", "title": "Ensure Dynamic Content Updates Are Accessible", "g_id": "1591", "url": "https://baymard.com/premium/guideline-collections/cb3zzh/1591", "source_type": "guideline", "importance": 100, "summarized_info": { "description": "Users aided by screen readers may be completely unaware if or when dynamic content is updated on a page. Further, unexpectedly moving keyboard focus to new content can disorient users aided by screen readers.", "issue": "Users aided by screen readers may be completely unaware if or when dynamic content is updated on a page Further, unexpectedly moving keyboard focus to new content can disorient users aided by screen readers", "advice": "When new content loads as a result of a user action, an announcement must be made using either the aria-live or ARIA role='alert' method Whenever a loading indicator (e.g., an animation or icon) is visually present, alt text must be added to the element containing the image Lastly, keyboard focus should only be moved to new content if it is the logical result of user action (e.g., opening up a modal overlay) or requires user action as a response (e.g., a timeout warning) Summary Summary Research Findingschevron-down Video & Quiz Review Tool Audit Performances Implementation Examples Benchmark Performances Changelog", "summary": "Users aided by screen readers may be completely unaware if or when dynamic content is updated on a page. Further, unexpectedly moving keyboard focus to new content can disorient users aided by screen readers.", "purpose": "" } }, { "doc_id": "doc-b7519c261bd1168580c36d9fa5f8f025", "title": "How to Programmatically Update Users on Dynamic Content Changes", "g_id": "1594", "url": "https://baymard.com/premium/guideline-collections/cb3zzh/1594", "source_type": "guideline", "importance": 100, "summarized_info": { "description": "Page elements which lack accessible markup, or have incorrectly implemented markup, can cause users aided by screen readers to miss dynamic content updates, including error messages.", "issue": "Page elements which lack accessible markup, or have incorrectly implemented markup, can cause users aided by screen readers to miss dynamic content updates, including error messages", "advice": "Ensure users aided by screen readers are aware of new content through the use of the ARIA role='alert' and aria-live='assertive' for high-priority content (e.g., error messages, etc.), using aria-live='polite' for medium-priority content (e.g., revolving banner text, etc.), and aria-live='off' for low-priority content (e.g., social media feeds, etc.) Additional contextual information can be included by adding the aria-atomic attribute (e.g., “Minimum price: [X]”) Summary A change has been made to the page’s elements or content What that change is If any user action is required before moving on to other content Summary Research Findingschevron-down Video & Quiz Review Tool Audit Performances Implementation Examples Benchmark Performances Changelog", "summary": "Page elements which lack accessible markup, or have incorrectly implemented markup, can cause users aided by screen readers to miss dynamic content updates, including error messages.", "purpose": "" } }, { "doc_id": "doc-ed12b590219eb978072fc37995391754", "title": "Ensuring Form Field Validation Errors Are Accessible", "g_id": "1661", "url": "https://baymard.com/premium/guideline-collections/cb3zzh/1661", "source_type": "guideline", "importance": 100, "summarized_info": { "description": "Users aided by screen readers may have difficulty recovering from, or even being aware of, form field errors.", "issue": "Users aided by screen readers may have difficulty recovering from, or even being aware of, form field errors Screen reader users may not benefit from the visual indicators and persistent visual presence in proximity to the related field Validation error messages that are overly vague (e.g., “Input error”) are not accessibility compliant", "advice": "Error messages must be programmatically identified (using aria-invalid='true') and associated with their relevant form field or input (using aria-describedby) Furthermore, these messages must be both visible and meaningful (i.e., helpful in understanding and solving the error) Additionally, form fields must adhere to at least 1 of the following methods of error resilience: value-checking entries for validity, including a 'Review' step where users can edit erroneous entries, or making orders cancellable after submission Summary A validation error occurred Specifically which form field or input provoked the error How users can correct the error Field Labels & Microcopy Field Design & Features Credit Card Form Default Values & Autocompletion Programmatically associated with an input field Programmatically discernable as an error message Visible Meaningful form fields must be checked for errors by the site, or form fields must be reviewable by the user, or form fields must be reversible after submission. Summary Research Findingschevron-down Video & Quiz Review Tool Audit Performances Implementation Examples Benchmark Performances Changelog", "summary": "Users aided by screen readers may have difficulty recovering from, or even being aware of, form field errors.", "purpose": "" } }, { "doc_id": "doc-eb572ad0599fac2c3ff9ce37bb52940e", "title": "Allow For a Diverse Range of User Interaction Methods Sitewide", "g_id": "1662", "url": "https://baymard.com/premium/guideline-collections/cb3zzh/1662", "source_type": "guideline", "importance": 75, "summarized_info": { "description": "Users with disabilities who rely on assistive technologies may have difficulty interacting with sites using nonstandard methods (e.g., screen readers, voice control).", "issue": "Users with disabilities who rely on assistive technologies may have difficulty interacting with sites using nonstandard methods (e.g., screen readers, voice control) Indeed, some websites are not optimized for alternative input methods like keyboard navigation and assistive technologies, making it difficult for users with disabilities to engage with the content Complex page elements, like category or homepage image galleries, or product customization overlays, can be difficult for users who rely on assistive technologies to interact with On mobile devices, gestures are often the only method for operating elements, which can be problematic for users who rely on screen readers Keyboard focus can become 'trapped' on certain elements, forcing users to reload the page", "advice": "Users should be able to operate page elements using multiple input methods — including keyboard navigation As such, keyboard focus should be visible with a 3:1 contrast ratio and proceed logically through page elements without becoming “trapped” on any element or reset to the top of the page Complex page elements, such as rotating image galleries, should have keyboard-operable controls Furthermore, requiring gestures to operate elements on mobile should be avoided Finally, user input actions should either 1) occur on the “up” event, or 2) be cancelable, with “drag-and-drop” operations including a review step Summary UI components don’t trigger on the “down” event — that is, when users first click the mouse or make contact with the touch screen but have not yet disengaged the selection. Instead, selections should be finalized on the “up” event, when users release their selection. One exception to the rule of submitting user actions on a “down” event is for UI components such as on-screen keyboards, where users’ inputs on one element are being used on another and are thus not finalized. Users can abort or undo selections through a separate page element or by holding the “down” event and dragging the mouse off the interactive element, such as a button or link. Summary Research Findingschevron-down Video & Quiz Review Tool Audit Performances Implementation Examples Benchmark Performances Changelog", "summary": "Users with disabilities who rely on assistive technologies may have difficulty interacting with sites using nonstandard methods (e.g., screen readers, voice control).", "purpose": "" } }, { "doc_id": "doc-984538977f3abf4baaabe1d7055915fe", "title": "Consider Having a “Best Sellers” Category on DTC sites", "g_id": "1666", "url": "https://baymard.com/premium/guideline-collections/mwlwjp/1666", "source_type": "guideline", "importance": 75, "summarized_info": { "description": "Users who are new to the site or brand often seek the most popular offerings as a place to begin browsing, without which it can be difficult to decide where to start.", "issue": "Users who are new to the site or brand often seek the most popular offerings as a place to begin browsing, without which it can be difficult to decide where to start", "advice": "Consider having a “Best Sellers” category Visually distinguish the 'Best Sellers' category link or featured products on the homepage to facilitate navigation to this popular resource Promoting a 'Best Sellers' category provides an essential entry point for users to explore and find relevant products In fact, 23% of participants on small catalog sites used the 'Best Sellers' category when available, often as their first choice from the homepage 'Best Sellers' carry extra weight on DTC, small catalog sites, as users trust popular products rather than relying heavily on ratings and reviews Note that implementing 'Best Sellers' as a true category, not just a filter, doesn't significantly impact user navigation on small catalog sites", "summary": "Users who are new to the site or brand often seek the most popular offerings as a place to begin browsing, without which it can be difficult to decide where to start.", "purpose": "" } }, { "doc_id": "doc-fb13fed9db5166f184ee60ce0181ec5a", "title": "Be Cautious if Implementing Novel Navigation Menus", "g_id": "1667", "url": "https://baymard.com/premium/guideline-collections/wqrbe4/1667", "source_type": "guideline", "importance": 75, "summarized_info": { "description": "Unique or “creative” navigation menus introduce unnecessary opportunity for confusion and errors.", "issue": "Unique or 'creative' navigation menus can cause confusion and errors Full-viewport navigation overlays can be mistaken for new pages, leading to user frustration and premature site abandonment Dynamic menus that change as the page scrolls distract users and slow down their navigation experience These unconventional menus require users to expend additional mental effort and hinder efficient browsing", "advice": "Implement novel navigation menus with caution In particular, avoid drop-down designs that take up the entire viewport or may otherwise be mistaken for a new page, or menus that change shape as users scroll Deviating from established web conventions should be a careful consideration, weighing the value of novelty against the efficiency of intuitive navigation", "summary": "Unique or “creative” navigation menus introduce unnecessary opportunity for confusion and errors.", "purpose": "" } }, { "doc_id": "doc-081c7fb359bd6c5e45b357ad9aa2b82d", "title": "Avoid Intermediary Category Pages for Small Product Catalogs", "g_id": "1668", "url": "https://baymard.com/premium/guideline-collections/y6hoo8/1668", "source_type": "guideline", "importance": 75, "summarized_info": { "description": "Lacking a deep product catalog, small and direct-to-consumer sites typically don’t require the addition of intermediary category pages, which add unnecessary complexity and increase the amount of interaction required to reach product lists.", "issue": "Lacking a deep product catalog, small and direct-to-consumer sites typically don’t require the addition of intermediary category pages, which add unnecessary complexity and increase the amount of interaction required to reach product lists Intermediary category pages on small catalog sites frustrate users and increase fatigue before product selection 31% of participants in testing struggled to reach the product list on sites with intermediary category pages", "advice": "On sites with a small catalog (e.g., fewer than 25 products), avoid using intermediary category pages Instead, focus on providing details about individual products and the brand Small catalog sites can effectively leverage and highlight auxiliary content through alternative means such as on the homepage and product details pages Summary Summary Research Findingschevron-down Video & Quiz Review Tool Audit Performances Implementation Examples Benchmark Performances Changelog", "summary": "Lacking a deep product catalog, small and direct-to-consumer sites typically don’t require the addition of intermediary category pages, which add unnecessary complexity and increase the amount of interaction required to reach product lists.", "purpose": "" } }, { "doc_id": "doc-153bcce78c14f552d2a30c9570daed7b", "title": "Ensure Multimedia Content Is Accessible through Both Audio and Visual Methods", "g_id": "1698", "url": "https://baymard.com/premium/guideline-collections/cb3zzh/1698", "source_type": "guideline", "importance": 33, "summarized_info": { "description": "Videos and other multimedia without text alternatives can be inaccessible to users with hearing or cognitive impairments.", "issue": "Videos and other multimedia without text alternatives can be inaccessible to users with hearing or cognitive impairments Likewise, information conveyed strictly through visual means in videos can be inaccessible to users with visual impairments Automatically moving or updating visual content (e.g., videos, animations, image carousels) can cause issues for users with cognitive or visual impairments and may be a source of distraction for users with attention deficit disorders Content or page elements that move or flash faster than 3 hertz can trigger seizures in photosensitive users", "advice": "Closed captions must be included for all video content Audio descriptions should also be provided for any video content, particularly any information that is communicated strictly through visual means and cannot be found elsewhere on the page Moreover, consider providing full transcripts for any video or audio-only content Additionally, users must be provided with controls for video (and other moving content) and audio content which allows them to pause, stop, or hide (and control the volume, or mute) said content Avoid flashing content above 3Hz Summary information about the video’s setting, any text or graphics that are shown in the video, and any body language (e.g., facial expressions, physical actions) of individuals depicted in the video. any spoken dialog and narration, identities of any speakers, and any important nonspeech sounds (e.g., sound effects, soundtrack titles). The content moves, blinks, or scrolls The content starts or plays automatically The content lasts more than five seconds The content is presented in parallel with other content Summary Research Findingschevron-down Video & Quiz Review Tool Audit Performances Implementation Examples Benchmark Performances Changelog", "summary": "Videos and other multimedia without text alternatives can be inaccessible to users with hearing or cognitive impairments.", "purpose": "" } }, { "doc_id": "doc-fefb5e62ee3b28973a78b21b3121c7e9", "title": "How to Implement Accessible Search and Search Autocomplete Functionality", "g_id": "1699", "url": "https://baymard.com/premium/guideline-collections/cb3zzh/1699", "source_type": "guideline", "importance": 75, "summarized_info": { "description": "Users aided by screen readers often have difficulty utilizing a site’s search functionality — including the autocomplete feature.", "issue": "Users aided by screen readers often have difficulty utilizing a site's search functionality — including the autocomplete feature", "advice": "Use ARIA role='combobox' to identify the search field and role='listbox' to identify the autocomplete suggestions element in the markup, with individual autocomplete results marked with role='option' Use aria-autocomplete to identify the autocomplete assistance type — with most sites offering 'both' inline- and list-type assistance Use aria-activedescendent to enable a keyboard subfocus selector and announce the current subfocus selection — using each autocomplete option's unique ID Search autocomplete suggestions need to be keyboard navigable, with sufficiently visible primary and secondary keyboard focuses (4.5:1 contrast) Users need to be notified whenever updates are made to search autocomplete suggestions Finally, search scope selection should be implemented as a drop-down list Summary “inline”, “list”, or “both” Summary Research Findingschevron-down Video & Quiz Review Tool Audit Performances Implementation Examples Benchmark Performances Changelog", "summary": "Users aided by screen readers often have difficulty utilizing a site’s search functionality — including the autocomplete feature.", "purpose": "" } }, { "doc_id": "doc-ff5e9597a5d62112743f642bcb4d8654", "title": "Ensure the Main Navigation Is Accessible", "g_id": "1700", "url": "https://baymard.com/premium/guideline-collections/cb3zzh/1700", "source_type": "guideline", "importance": 75, "summarized_info": { "description": "Users with disabilities may have difficulty navigating a site with hidden menus — especially ones with extensive product categories and subcategories.", "issue": "Users with disabilities may have difficulty navigating a site with hidden menus — especially ones with extensive product categories and subcategories", "advice": "Menus should be organized in the markup as unordered lists, labelled using , ARIA “label”, or “labelledby” attributes, and identified to screen readers using the ARIA role=“navigation” landmark Furthermore, menus with visually hidden submenus should be programmatically identified Navigation should be found in expected locations and be visually distinct from other page elements, with adequate white space and padding around interactive elements with any visual menu items, including text labels Finally, the user’s current page should be identified both programmatically and visually Summary Summary Research Findingschevron-down Video & Quiz Review Tool Audit Performances Implementation Examples Benchmark Performances Changelog", "summary": "Users with disabilities may have difficulty navigating a site with hidden menus — especially ones with extensive product categories and subcategories.", "purpose": "" } }, { "doc_id": "doc-f1ee9ac26937c587f48df13943fd6af0", "title": "Ensure Information in Tables Is Accessible to Screen Readers", "g_id": "1701", "url": "https://baymard.com/premium/guideline-collections/cb3zzh/1701", "source_type": "guideline", "importance": 33, "summarized_info": { "description": "Users aided by screen readers may not be able to access information housed in tables if it is presented as an image, or otherwise not constructed using accessible markup.", "issue": "Users aided by screen readers may not be able to access information housed in tables if it is presented as an image, or otherwise not constructed using accessible markup Complex tables with multiple levels of headers or merged cells can be particularly challenging for screen reader users to understand, even when implemented correctly", "advice": "Tables should be implemented using native HTML table elements (e.g., ,
, ) Table headers should be programmatically associated with their corresponding data cells — either rows (i.e., 'row') or columns (i.e., 'col') — using the scope attribute Merged cells, however, should instead use 'rowgroup' and 'colgroup' for row and column, respectively Especially complex tables may require unique IDs for both primary and secondary headers, which are both then referenced by their relevant data cells — although these should be generally avoided in favor of simpler methods (e.g., multiple simple tables) Summary Summary Research Findingschevron-down Video & Quiz Review Tool Audit Performances Implementation Examples Benchmark Performances Changelog", "summary": "Users aided by screen readers may not be able to access information housed in tables if it is presented as an image, or otherwise not constructed using accessible markup.", "purpose": "" } }, { "doc_id": "doc-30a51c59ace64b77bf76a486de825b4d", "title": "Ensure Filter Interfaces Are Keyboard and Screen Reader Accessible", "g_id": "1702", "url": "https://baymard.com/premium/guideline-collections/cb3zzh/1702", "source_type": "guideline", "importance": 75, "summarized_info": { "description": "Users aided by screen readers can have difficulty understanding and navigating the numerous options and categories of the filtering menu, leaving them unable to narrow the list to their liking.", "issue": "Users aided by screen readers can have difficulty understanding and navigating the numerous options and categories of the filtering menu, leaving them unable to narrow the list to their liking", "advice": "Filter menus — including horizontal drop-downs, expanding sections, and hover actions — must all be keyboard navigable Additionally, screen reader–accessible contextual information should be provided alongside the filter menu and menu options (e.g., number of matching search results, currently applied filters) Summary Summary Research Findings Video & Quiz Review Tool Audit Performances Implementation Examples Benchmark Performances Changelog", "summary": "Users aided by screen readers can have difficulty understanding and navigating the numerous options and categories of the filtering menu, leaving them unable to narrow the list to their liking.", "purpose": "" } }, { "doc_id": "doc-b0353bcfd99c59e6f112b5a750ed8d4f", "title": "Ensure List Items Are Fully Accessible and Easily Navigable by Keyboard", "g_id": "1703", "url": "https://baymard.com/premium/guideline-collections/cb3zzh/1703", "source_type": "guideline", "importance": 75, "summarized_info": { "description": "When users aided by screen readers select a list item, the content, information, or other elements may not all be accessible, or may be structured in a confusing way, making it difficult for users to select appropriate products to explore.", "issue": "When users aided by screen readers select a list item, the content, information, or other elements may not all be accessible, or may be structured in a confusing way, making it difficult for users to select appropriate products to explore Multiple elements within list items often link to the same destination, which can confuse users aided by screen readers If the keyboard focus indicator does not remain visible when applied to any of the list page elements, list pages can quickly become visually overwhelming", "advice": "All list item content should be accessible to screen readers, with links to the same location being consolidated to one focusable element or specialized to different product page locations Further, “Quick View” overlays should be accessible and able to be activated by keyboard navigation Finally, keyboard focus should be clearly visible on all list page elements Summary Summary Research Findings Video & Quiz Review Tool Audit Performances Implementation Examples Benchmark Performances Changelog", "summary": "When users aided by screen readers select a list item, the content, information, or other elements may not all be accessible, or may be structured in a confusing way, making it difficult for users to select appropriate products to explore.", "purpose": "" } }, { "doc_id": "doc-65ce9900036e1f803a41e7781c98cf71", "title": "Deprioritize Search for Small Catalog Sites", "g_id": "1704", "url": "https://baymard.com/premium/guideline-collections/s7fn4d/1704", "source_type": "guideline", "importance": 33, "summarized_info": { "description": "Search is a fallback strategy for users of niche direct-to-consumer sites, making the main navigation and product list a far higher priority for supporting user behavior and improving usability.", "issue": "Users primarily rely on the main navigation and manual product browsing on niche direct-to-consumer sites Search is used as a fallback strategy when browsing fails or product details are lacking Search on direct-to-consumer sites tends to underperform and may lead to a worse user experience", "advice": "Deprioritize investment in on-site search for niche direct-to-consumer sites DTC sites and small catalog retailers should prioritize investing in clear navigation, bespoke imagery, robust FAQs, and detailed product descriptions After optimizing these elements, consider adding on-site search as an additional benefit Summary Summary Research Findings Video & Quiz Review Tool Audit Performances Implementation Examples Benchmark Performances Changelog", "summary": "Search is a fallback strategy for users of niche direct-to-consumer sites, making the main navigation and product list a far higher priority for supporting user behavior and improving usability.", "purpose": "" } }, { "doc_id": "doc-ea8e568cafd05d120fa4545de42155b6", "title": "Have a Link to FAQs in the Footer on DTC Sites", "g_id": "1705", "url": "https://baymard.com/premium/guideline-collections/58zheo/1705", "source_type": "guideline", "importance": 0, "summarized_info": { "description": "Sitewide FAQs serve as a vital resource for a variety of common questions, and users are at risk of abandoning the site when they can’t easily find answers.", "issue": "“I was going to go look at their FAQ section…but they don’t have an immediate nav for that. I guess I would go to maybe ‘Product Care’?” This participant on Milo wanted to browse general FAQs to learn more about the site’s products and intuitively scrolled to the bottom in order to find the link to this resource. However, the site’s footer did not contain a clear path to FAQs, leaving him without an obvious way forward. In fact, the link to “Product Care” led to a more general FAQ section, which was not obvious from the footer links. Unclear link titles make it difficult for users to confidently navigate to answers. Users looking for a link to an FAQ in the CB2 footer (first image, iOS) may assume that none exists. However, there is one (second image) that could answer a lot of important questions. If users overlooked this FAQ they could miss out on information that would make a difference to their purchasing decision. It’s common for users on e-commerce sites searching for help to look in the footer. Indeed, we’ve repeatedly observed participants across multiple research studies scroll to the footer to access information such as details of shipping and returns (see #252). In addition, many participants also sought out sitewide FAQs (see #1706) as a resource for answering questions about a variety of topics, from product information to site policies. Indeed, 62% of participants on DTC sites with small catalogs sought out FAQ information at least once. Given that users tend to seek out FAQs, they may not find them if there is no link from the footers. Of course the first step is to have an FAQ (see #1706), but unless it’s easy to find, some users’ questions will go unanswered. This can be a particularly serious problem on DTC sites with small catalogs where users might be unfamiliar with the brand, its products, and its policies, but less so on mass merchant sites that usually have comprehensive help sections.. Furthermore, if sites just link instead to individual topics within FAQs with links like “Returns Policy”, some users will assume that these topics are the only ones covered and that their own questions wouldn’t be addressed. In addition, while links like “Help” or “Customer Services” are common on larger sites, users on DTC sites with small catalogs tend to look for the specific term “FAQ” and may not follow those other links for more general questions like “Who is behind this brand?” or “Are items made using sustainable materials and processes?” that they may not feel are specifically ‘Help’ topics.", "advice": "“A lot of times I’ll go look at the FAQ to see, like, what’s their return policy? How soon will it ship?” This participant on Monastery sought and found the link to FAQs in the footer, hoping to get an overview of site policies. Supporting this intuition provides an efficient way for users to learn important information about the site and its products. Links to FAQs in the footers of Anine Bing (first image, iOS) and Gucci (second image, iOS) will help users on these sites get quickly to the answers they need. Living Spaces allows users to get quickly to answers by having an “FAQs” link in the footer. Looking for the site’s return policy, this participant on Great Jones immediately scrolled to the footer. Overlooking the “Returns” link under the “Help” section (see #250), she selected “FAQs” instead. When more specific links are either unavailable or overlooked, FAQs serves as a general fallback to finding a variety of answers. “I want to figure out that 30-day trial.” This participant on Caraway specifically sought a link to FAQs in the footer. Supporting this intuition provides users with the quickest and most intuitive access to resources.", "summary": "Sitewide FAQs serve as a vital resource for a variety of common questions, and users are at risk of abandoning the site when they can’t easily find answers.", "purpose": "" } }, { "doc_id": "doc-f97ea171a67f10876523fc55b25ffec0", "title": "Provide Comprehensive Sitewide FAQs on DTC Sites", "g_id": "1706", "url": "https://baymard.com/premium/guideline-collections/58zheo/1706", "source_type": "guideline", "importance": 0, "summarized_info": { "description": "Users on DTC sites with small catalogs often have questions about a brand and its products that may go unanswered by information on product details pages, and may abandon the site if they’re unable to find satisfactory answers", "issue": "While there are various help topics linked from the West Elm footer, there’s no sitewide FAQ section. Some users will therefore have to work harder to find answers to questions related to purchasing decisions. “They’re clearly leather, and I’d want to know how to clean it.” This participant on Greats sought the site’s FAQs to learn more about product care, but the brief list of questions did not cover her concern, leaving her without answers. “Well, that is very disappointing”, she continued. FAQs that fail to address important topics can leave users without recourse for getting key questions answered. “One thing I am interested in is where this stuff is made — how it’s made, is it made in the US or somewhere else?” As users explore DTC sites with small catalogs, many have questions on an array of topics such as product details or the brand in general. For example, users shopping for skincare products may wonder if the product range is vegan, while users shopping for apparel may wonder where the brand is based or where their products are manufactured. Similarly, users may require information on site policies, such as shipping and returns, before they feel comfortable moving forward with purchasing. This is particularly the case with sites or brands that are less well known than leading brands, and which users may not have encountered before. On these sites, some users also need reassurance about company policies before committing to purchasing — questions are less likely to arise on well-known or familiar sites. In many cases, the answers to these questions can determine users’ willingness to purchase products, and many will expect to find answers in FAQs. However, when the FAQs they seek are unavailable or incomplete, there is a risk that they might abandon the site.", "advice": "Victoria’s Secret provides a comprehensive FAQ section that answers a wide variety of questions that users might have. Louis Vuitton also provides a helpful FAQ section that covers product information, delivery and returns information, and company details, among other topics. The Anine Bing FAQ section contains answers to a wide range of questions across many topics like “Product” and “Shipping”. This provides a comprehensive source of helpful information to users. 2 additional examples “[Reading the FAQs] ‘Can I choose what I get?’ ‘You’re free to choose your groceries each week, while we start your cart with what we know you like…you always have the final say.’ All right, okay then, helps answer it a little bit more.” At Imperfect Foods, the embedded FAQs on the “How It Works” page helped the participant answer any lingering questions about the service. “They ship with ‘plenty of dry ice’ and ‘within two days’ and it’ll ‘stay completely frozen’. So that resolves that issue. That worry. That anxiety.” At Crowd Cow, the participant was concerned that their highly-perishable Consumable Subscription Service order might be left out too long and spoil and turned to the FAQ section to find information on how their order is packaged. The answer put their mind at ease about delivery and alleviated a major concern about the subscription service’s product arriving fresh to their door. “‘How much does it cost?’ ‘Meals start at 11.99. View our pricing plan for more details.’ Again I like that.” At Gobble, the participant was able to find pricing information (“Our meals start at $11.99”) and where to look for additional details (“View our pricing plan for more details”) in the embedded FAQs on the “How It Works” page. “Okay, ‘Can I skip [weeks]?’ Oh, okay. It gives you the flexibility about skipping weeks.” At Dinnerly, the participant was able to find information about the Meal Kit subscription service’s flexibility — allowing them to “Skip weeks” instead of canceling the service — which made it more appealing for their busy lifestyle. Therefore, on DTC sites with small catalogs, FAQs should be provided. It was clear from testing on this type of site that participants tended to look to FAQs for different types of information at various stages in the product finding and checkout processes. On other site types such as mass merchants, there was no evidence that they are essential. That said, FAQs can be helpful, but key information should be placed in locations where users are likely to be when they need it,such as on product details pages and linked directly from footers (see #252). During testing of DTC sites with small catalogs, participants were observed seeking FAQ content to both find answers to specific questions (e.g., “What is the return policy? Where are the products manufactured?”) and to browse FAQs as a more general way to learn about the product and see what questions the site has answered more broadly. In effect, FAQs bring together a diverse array of critical product, brand, and policy information into a single place, providing a convenient way to verify or browse important information without needing to visit multiple products or help pages. There are a few reasons that FAQs are a more popular resource on small catalog DTC sites compared to traditional retailers: DTC sites with small catalogs often have a very basic search tool — or no search at all — forcing users to navigate to find answers to their questions. On larger retail sites, the robust search feature for aiding users in exploring their broad catalog can also provide an efficient means to find nonproduct information, such as site policies and help topics (see #342). With a significantly smaller site to navigate, both product- and nonproduct-wise, many DTC sites opt to deprioritize search or discontinue it altogether (see #1704). What’s more, during DTC testing search was rarely sought in general and never sought for finding answers to nonproduct questions (if it was provided at all), with participants seeking information such as return policies and shipping information instead universally going to the site footer for navigation links. DTC products tend to be more homogeneous, making FAQs a logical alternative to product descriptions. For instance, larger retailers may carry hundreds or thousands of different kinds of products from just as many vendors or manufacturers, making product pages the only relevant source of product information. However, the comparatively small array of products on a DTC site likely share certain attributes, such as being manufactured in the same location or made of the same material. Based on these shared characteristics or brand attributes, users may reasonably seek answers to even product-specific questions within the FAQs of a DTC site. The small size of the sites makes FAQs more important to users’ information-seeking strategy. On a larger traditional retailer, the prospect of finding answers with a sitewide FAQ tool can be a daunting task, with a much wider scope of potential questions and answers. However, the smaller product catalog of many DTC sites implies a smaller collection of FAQs, associated with a more conversational and boutique experience (rather than an impersonal corporate one). Seeking information in the FAQs is therefore much less intimidating for users on small DTC sites. It’s important that FAQs are comprehensive and cover all questions users might reasonably have. To ensure this, maintain a list of questions posed by users in user testing and across customer service channels and provide relevant answers in FAQs. These were the the 3 topics for which answers were most commonly sought by test participants accessing sitewide FAQs: Product information Policy information Manufacturing and brand information “I’m drawn to the Frequently Asked Questions just to see if that would [help]”. On sites such as Nespresso, users are likely to seek out FAQ sections to find out basic information, such as in this case how to buy and use coffee pods. This participant on Maya Chia was concerned with whether the beauty products were cruelty free and looked to the sitewide FAQs rather than the product page for answers. “I’d probably just skim through this, see if there’s anything else I want to know about the product.” On Tempo, this participant used FAQs as an alternative means to learn about the brand’s fitness machine. “Maybe I can find my question on the FAQs…” This test participant wanted further confirmation of overall sizing for shoes at Thousand Fell. Scanning the FAQs, they found a question exactly addressing their concern: “Okay, it’s true to size”. On more traditional retail sites, product information such as material, care information, country of origin, etc., naturally varies, making product page descriptions (see #841) the only reliable source for locating the answers to related questions. However, DTC sites with small catalogs typically feature a much narrower and more homogeneous catalog (see #282), making this information generally applicable to the entire site’s offerings. In this sense, seeking product information from a sitewide resource makes logical sense to users who perceive important commonalities among the brand’s products. “I feel like that should have been said in the actual description rather than having to go to another page.” This participant wanted to know if Equal Parts’s cookware was dishwasher safe and found the answer in the FAQs. While she wished this information had been provided earlier in the product-exploration process, she successfully found this information in the sitewide FAQ, an important fallback location for product information during DTC testing. However, robust product FAQs should not be replacements for high-quality product descriptions (see #841) and specifications (#858) on the product page. Information that is critical to the majority of users should always be presented clearly on product pages, avoiding the need to navigate to a separate resource. “Okay so they have a ‘30 day, no-questions-asked’ return policy.” Many participants during testing, such as this participant at Great Jones, sought out FAQs for policy and customer support information. “Let’s go to FAQs, because that would probably tell me what their policy would be.” Wishing to learn if the site offered a product warranty or guarantee, this participant on Caraway navigated to the site’s general FAQs. Additionally, test participants looked to sitewide FAQs for policy information such as shipping and returns policies, warranty information, and membership or subscription information. For instance, one participant from testing shared, “A lot of times I’ll go look at the FAQ to see, like, what’s their return policy? How soon will it ship?” FAQs were sometimes sought when a more specific link to the return policy or shipping information was unavailable or overlooked (see #1705), while other participants took to browsing the full FAQs as a way to get an overview of general policy and help information. What’s more, DTC sites with small catalogs tend to lack the extensive courtesy navigation options available at traditional retailers, where this kind of information might otherwise be linked. Thus, including this information in the sitewide FAQs, even when also available on its own page (see #252), provides convenient access to this important information. For many participants, an overview of common questions regarding manufacturing, ingredients, and brand details was helpful within FAQs, such as this test participant on Milo who was concerned with where the cookware was made. On an unfamiliar DTC site, users are likely to have basic questions about the brand that they are unlikely to have for larger retailers like Amazon. For many users, FAQs serve as an introduction to the brand as a whole, helping to establish a sense of trust and pique their interest in exploring the site and its products in further detail. When FAQs are unavailable or overly brief, it can therefore be difficult for users to form the same initial impression of the brand as one that is interesting and trustworthy. To this end, a subset of participants also sought out information regarding more general brand practices or information, including manufacturing information, ethical practices, and brand history. As with policy information, sites often maintain dedicated pages for a deeper focus of such issues, but a brief summary within the FAQs is also beneficial, helping the sitewide FAQs serve as a comprehensive overview of important brand information. Thus, any supplementary pages should be linked to from within sitewide FAQs, and vice versa.", "summary": "Users on DTC sites with small catalogs often have questions about a brand and its products that may go unanswered by information on product details pages, and may abandon the site if they’re unable to find satisfactory answers", "purpose": "" } }, { "doc_id": "doc-5cf4289d51142ac7f7edb61c132e91d6", "title": "Always Highlight Core Product and Brand Features on the Homepage for Niche DTC sites", "g_id": "1707", "url": "https://baymard.com/premium/guideline-collections/qof2oe/1707", "source_type": "guideline", "importance": 75, "summarized_info": { "description": "Users are quick to evaluate not only a site’s product catalog, but also the brand’s policies, value proposition, and trustworthiness, from the homepage, and lack of clarity towards any of these concerns can result in premature abandonment.", "issue": "Users are quick to evaluate not only a site’s product catalog, but also the brand’s policies, value proposition, and trustworthiness, from the homepage Lack of clarity towards any of these concerns can result in premature abandonment", "advice": "Summarize and highlight core product and brand features, including key product details and attributes, free shipping availability, and return policy information on the homepage Use concise and easy-to-understand language Visual techniques such as subheadings, bullet points, borders or shading, or icons can help draw users’ eyes and help them understand the information being provided Product features and unique selling points can be emphasized through images, brief descriptions, and gifs", "summary": "Users are quick to evaluate not only a site’s product catalog, but also the brand’s policies, value proposition, and trustworthiness, from the homepage, and lack of clarity towards any of these concerns can result in premature abandonment.", "purpose": "" } }, { "doc_id": "doc-80073f0727f7b34588810947f1db0886", "title": "Feature a Representative Sample of Products on the Homepage for DTC, Small Catalog Sites", "g_id": "1708", "url": "https://baymard.com/premium/guideline-collections/qof2oe/1708", "source_type": "guideline", "importance": 75, "summarized_info": { "description": "For direct-to-consumer and other small catalog sites, failing to communicate the site’s product range can cause users to misinterpret the site and delay users’ ability to understand the scope of the product catalog.", "issue": "Users heavily rely on the homepage to gauge a site's offerings, especially on unique e-commerce sites like DTC or subscription sites For direct-to-consumer and other small catalog sites, failing to communicate the site’s product range can cause users to misinterpret the site and delay users’ ability to understand the scope of the product catalog Some users may even immediately abandon the site in hopes of finding an alternative that more clearly carries what they’re looking for", "advice": "Feature a diverse sample of products directly on the homepage to provide efficient navigation allowing users to immediately access products of interest Typical small catalog sites should aim for featuring at least half of the product catalog on the homepage, and at least 1 product for each product type Note that all but the shallowest of DTC sites still need separate product lists for users to explore the full product catalog", "summary": "For direct-to-consumer and other small catalog sites, failing to communicate the site’s product range can cause users to misinterpret the site and delay users’ ability to understand the scope of the product catalog.", "purpose": "" } }, { "doc_id": "doc-19a8db7f69afdb9044e448df0042b649", "title": "Deprioritize User Reviews for Niche DTC Sites", "g_id": "1709", "url": "https://baymard.com/premium/guideline-collections/hwvgrc/1709", "source_type": "guideline", "importance": 33, "summarized_info": { "description": "Users are so skeptical of reviews on niche direct-to-consumer sites that they will nearly always want to seek external reviews before feeling confident with purchasing — regardless of whether the site displays its own reviews or not.", "issue": "Users are so skeptical of reviews on niche direct-to-consumer sites that they will nearly always want to seek external reviews before feeling confident with purchasing — regardless of whether the site displays its own reviews or not Therefore, site-provided reviews, without third-party confirmation, are not enough to sway users’ purchasing decisions on DTC sites", "advice": "Be aware of users’ strong distrust of reviews on niche direct-to-consumer sites Consider instead prioritizing investment in the brand’s off-site presence and perception, including social media and search engine optimization When offering reviews, include reviews features such as star-rating filters and user-generated photos to enhance the perception of authenticity If DTC sites choose to offer reviews, they must present them as authentic and trustworthy to overcome user skepticism Review features that underscore their authenticity, such as the ability to filter for negative reviews and allowing users to attach their own photos, are recommended Summary Summary Research Findings Video & Quiz Review Tool Audit Performances Implementation Examples Benchmark Performances Changelog", "summary": "Users are so skeptical of reviews on niche direct-to-consumer sites that they will nearly always want to seek external reviews before feeling confident with purchasing — regardless of whether the site displays its own reviews or not.", "purpose": "" } }, { "doc_id": "doc-c9d9deb84d398dfc44bc3d27d6332b32", "title": "Invest in Monitoring Off-Site Discussions of Niche DTC Sites", "g_id": "1774", "url": "https://baymard.com/premium/guideline-collections/58zheo/1774", "source_type": "guideline", "importance": 0, "summarized_info": { "description": "Users are keen to confirm brand claims and on-site reviews with external resources, making third-party sites and social media vital sources of information when making their purchase decision.", "issue": "“I would usually go to their Instagram account to see if there are more before and after pictures. I wouldn’t trust one or two pictures on here unless it were a really big company.” This participant in an earlier round of testing on Maya Chia wanted more real-life examples of product effects, seeking Instagram specifically as an external source. In our testing of direct-to-consumer (DTC) sites with small catalogs, we observed that participants were overwhelmingly skeptical about site claims (and user reviews, see #1709). They were quick to point out that brands will always seek to present their products in the best possible light, making any claims or review information inherently biased. It’s understandable that users that are new to a site may hesitate to proceed with purchasing without independent validation of the brand and its products, even if they find potentially suitable items. Therefore, to get a more objective view, many test participants turned to external resources, reasoning that third-party sites would be less prone to bias and manipulation and therefore be more trustworthy. However, if those that decide to seek offsite validation do so in vain, they may not have the reassurance they need to buy on the site.", "advice": "“I would go here [to Google]…just to see all the stuff that comes up with it.” In addition to browsing Monastery’s site, this participant turned to Google to learn more about the brand (first image). She was especially keen to see the brand’s social media presence, opening the search result for Instagram (second image). “I can see that they have a decent following, so that’s pretty important, and they’re followed by people that I know and follow…On Instagram…I get to learn more about the brand and the brand’s image.” Given the importance of these external resources, it makes sense for DTC brands to consider the off-site perception of the brand and what content users might uncover through general internet searches or social media. During testing, the information gleaned from these external sources proved to be extremely valuable, with the potential to change users’ perception of the brand and influence their willingness to purchase. Thus, monitoring search engine and social media results should be a central part of most DTC brands’ overall strategy. In practice, this may involve investing in search engine optimization and proactive outreach to help ensure the results that come up are positive, informative, and beneficial. Additionally, curating the brand’s social media presence and participating in social media outreach or influencer marketing may help ensure quality information surfaces when users search for the brand on platforms such as Instagram. Of course, sites should strive to be transparent and honest in curating any off-site resources. Contributing to sponsored content that seems inauthentic, or censoring negative reviews or press, can tarnish brand perception by lowering perceived trustworthiness. Effectively, all third-party resources on the brand should appear genuine and come with “no strings attached” in order to serve as the independent confirmation users seek. During testing, we observed several types of external resources participants often turned to to learn more about brands and their products. While these weren’t the only external resources mentioned or accessed, they do provide some insight into typical resources users may consult when pursuing information about an unknown brand. The most common external sources observed in testing were: General web searches Instagram Reddit YouTube “I usually trust people writing articles on blogs.” This participant’s Google search (first image) during testing of Equal Parts turned up blog articles that piqued her interest and increased her trust in the brand (second image). External reviews from perceived experts can carry extra weight for users seeking to learn more about a brand and its products. 1 additional example “If I want an honest opinion, I don’t wanna go on their page. So yeah, I Google [the site] and then I would go down, see what places have to say. An honest review from an independent website, cool. I would open that up and then go and take a look down here and see what they have to say.” At Imperfect Foods, participants who saw the users reviews section (first image) often remarked how they would do an offsite search (second image), and search around for more independent sources for reviews, such as blogs (third image). “With all this stuff, too, I’m always Googling outside of their own websites just to see unbiased reviews, or if there’s…a magazine or website that does reviews of things. I feel like that’s a good way to get more info on it.” During testing of DTC sites with small catalogs, the most commonly mentioned or sought-after external resource was a simple internet search, reflecting participants’ desire to cast a wide net and “see what’s out there” in terms of general mentions or reviews of the brand. In practice, a general web search will turn up third-party reviews and social media profiles, as well as relevant media or news mentions (both positive and negative), making it a good starting point for learning about an unfamiliar brand. Given participants’ distrust for site-provided reviews on DTC sites with small catalogs (see #1709), finding third-party feedback from external sources via a general web search serves to verify the accuracy of the brand’s claims and is generally regarded as more trustworthy. Indeed, independent sources, including media and news outlets, blogs, and review sites are likely to be perceived as less biased and more authentic, having “less of a stake” in presenting the brand’s products in a positive light. What’s more, feedback from domain-specific sources or experts (e.g., a chef’s or cooking magazine’s review of cookware) is likely to carry additional weight (see #769). “But I would’ve liked to have seen in here…real people wearing and using this, not necessarily from a review perspective, but even if it’s from like Instagram or something. Just having more of that to make me feel more comfortable with the brand and to decide what to buy.” A participant at Nicce was disappointed not to see real-life examples of users wearing a vest she was considering. Seeing apparel and accessories items worn by real people can help users better understand how items will look and fit, boosting their confidence to purchase. “I just want to see what they’re doing in terms of the community and see what they’re posting, seeing it set up in people’s houses. That’s really cool.” Another participant browsing Tempo navigated to the brand’s Instagram account hoping to see real-life examples of the product in use. “I also like to see if the brand has an Instagram, just to see more pictures and how they interact [with customers].” Among more specific off-site resources, Instagram was by far the most popular among participants on DTC sites with small catalogs. For many participants, Instagram posts and mentions served as real-life examples, often doubling as lifestyle (#744) or human model (#1193) images that provided a deeper understanding of the product in use. What’s more, the third-party nature of social media posts also allows them to serve as a source of independent review content, being perceived as more authentic. As one test participant observed, “[Instagram] is almost another way to look at reviews”. In effect, social media mentions serve as additional social proof of how successful and effective the brand is; as another participant stated on her desire to see a brand’s Instagram, “I can get a sense of how popular the brand is or how trustworthy it is. Sometimes I can see that influencers or people I know are following the brand, and then I would be more interested”. Finally, for many users, Instagram and social media in general provides a unique way to observe how the brand presents itself (see #238) and interacts with its customers. For example, seeing the brand’s responses to posts or comments on its profile provides a proxy for how accessible the brand is and how generous and responsive its customer service might be. In particular, users may be interested in how the brand responds to negative feedback or purported issues (similar to viewing site responses to negative reviews, see #785). “Typically I go straight back to Google…when I’m looking for shopping stuff, I’ll actually just search the brand and see…I would try to find it elsewhere and see what real people are saying…second typically I’ll look on Reddit or something like that, because I often kind of peruse there and see what people have to say.” This participant on Daniel Wellington expressed a preference for using Reddit as a source of seemingly unbiased information on watches and other products he might consider. “I’d probably Google…or go to Reddit, it’s usually pretty good for that.” This participant on Greats was also curious about the sentiment of Reddit users towards the brand. Another popular social media resource mentioned by participants during testing was Reddit. Whereas Instagram as a platform focuses more heavily on visual content, Reddit’s structure around specific topics or communities (“subreddits”) provides an opportunity for finding independent feedback or reviews from experienced users or supposed domain experts — for example, finding a review of a skincare product posted by a top commenter on a skincare-focused subreddit. “If I want to see how something works, I usually just go to YouTube to see a review, because it’s more real, in a way.” This participant on Mahalo greatly valued the independent and unbiased nature of information available through YouTube, making it a more trustworthy source than the brand itself. “I would also go to YouTube to see people who have bought from this website what their experience was like, what the shoes actually look like moving around in a video instead of just the pictures.” YouTube was also mentioned as a popular third-party resource during testing on DTC sites with small catalogs, with participants specifically seeking video reviews and the ability to see products “in action”. As with site-provided video (see #759), YouTube videos can provide important visual information that is hard to glean from static images alone — with the added benefit of perceived authenticity by being from an independent source, making YouTube another potential source of unbiased reviews from real users.", "summary": "Users are keen to confirm brand claims and on-site reviews with external resources, making third-party sites and social media vital sources of information when making their purchase decision.", "purpose": "" } }, { "doc_id": "doc-38719171cbb869dc0f25a84840fdbeb1", "title": "Have Supplementary Pages about the Brand and Product Attributes on DTC, Small Catalog Sites", "g_id": "1775", "url": "https://baymard.com/premium/guideline-collections/58zheo/1775", "source_type": "guideline", "importance": 0, "summarized_info": { "description": "Many users want to “feel good” shopping at a particular site, yet the fundamental information they’re looking for can be hard to find or overly sparse.", "issue": "“I’d want to see who Daniel Wellington is…and where they’re coming from.” This participant, like 62% in our DTC, small product catalog research, was keen to learn information about the brand as a whole. While some information may be gleaned from the homepage or product pages, it’s often not enough to satisfy users’ curiosity. During testing, all DTC, small catalog sites featured some supplementary content that described the “brand story” or provided descriptive details about how products were made or what materials or ingredients were used. Indeed, there was usually some of this content on homepages (see #1707) and on product details pages (see #807). Yet these pages often don’t provide the extent of supplementary content that many users are seeking. Without this information, users can’t “get to know” the site as much as they’d like to and, for some, this might be an impediment to completing a purchase. In fact, a subset of users on DTC, small catalog sites will not have heard of the brand before and won’t have previously purchased their products. New customers in a physical boutique store might stop to chat with the owner or store employees, and some participants on DTC, small catalog sites have the same need to “get to know” the site before making a purchase decision. Without extra insight into the brand, some users will be reluctant to make a purchase.", "advice": "“I like an ‘Our Story’ tab. That interests me…I’m curious often about how the brand started, how old it is, if there’s an interesting story behind it…also, what the mission story of the company is, that’s interesting to me too.” This participant on Farer specifically sought out the “Our Story” link in the global navigation to learn more about Farer as a brand. Many users enjoy the details and personal connection provided by DTC brands’ origin stories and ethos. To satisfy users that need to find out more about the brand and its products, provide comprehensive “About Us” pages. These pages generally performed well in testing when it came to offering participants the background information they were looking for. Furthermore, for DTC small catalog sites, providing supplementary background pages will help users learn about the brand and make them more comfortable with purchasing from the site. In particular, users seeking such supplementary information are likely to be looking to learn about 2 topics: The brand’s story and principles The products’ “story” The “Our Founders” story on Anine Bing (iOS) gives users a good overview of how the brand was founded and developed, making it more likely that they will identify with the brand. Likewise the “Timeline” story on Van Cleef & Arpels will help users who are not familiar with the brand to get to know it better and understand it heritage. “I like good companies who try to give back a little bit…that’s actually really cool, I like this. Just from this information alone I already like what they’re about.” This participant explored and appreciated Thousand Fell’s mission of sustainability, explained in detail within the “About Us” section of the site. Corporate mission statements can set brands apart from competitors and give users a positive message to connect with. “If this is a brand…that I don’t know much about, sometimes I do like to read a little bit more about them and sort of what they do. I’m super interested in corporate social responsibility, so seeing that they are really invested in different communities and helping out people that are in need is something that’s really important to me, because I can see that when I purchase, I help this company make a difference.” This participant formed a positive opinion of Maya Chia as a brand after reading about their charity program on the “Our Brand” page. “I would look at the founder…What the founder does for a smaller company really matters, I think…I can tell she was passionate about it.” A different participant on Maya Chia sought out and read through information about the brand’s founder. “I do love women-owned businesses, so I feel like that’s a selling point.” A participant on Great Jones similarly wanted to learn about the company’s founders and, after reading through the information, was more inclined to view the brand positively. “I’m going to click on this, because I think this is important.” Another test participant on Great Jones was ready to leave the site, after looking at the site products and concluding it “wasn’t for her”. However, spotting a link for “Black Lives Matter” in the footer (first image), she clicked it and, after reading the content (second image), viewed the site much more favorably: “This would probably make me look more, I appreciate when people take a stand on issues…I definitely would take a second look…Whenever possible I try to purchase from companies where my values align with theirs”. If a small catalog, DTC site’s principles align with a user’s, the user is much more likely to consider purchasing from the site, and potentially even overlook other issues they may have with the site or product. 4 additional examples “That’s pretty cool. They’ve got a picture, a little background bio, and a quote from someone who’s taken the tour before. I really like that. That’s even more information than I’m used to seeing, so that’s nice.” A participant shopping for guided walking tours at Fun London Tours was more inclined to book a tour after reading information about the tour guides. “I would probably verify the type of aircraft they are using for these tours because if it’s one of those ‘micro copter’ things, I’d like to know that ahead of time”, remarked a participant shopping for helicopter tours at Zip Aviation. During large-scale Travel Tours & Experiences testing, participants were highly interested in information about the tour operators’ history, their employees, vehicles, etc. “‘Preventing plastic pollution’. So that means these guys are recycling. Okay. Ah, examples, HelloFresh stops ‘37.5 million plastic bottles…from entering the ocean’. Okay. That’s cool.” At HelloFresh, participants who had concerns about the environmental impact of the Meal Kit subscription service visited the “Sustainability” page. “I want to see their values. Which is something I’ve been trying to do more of, you know. All right, well, it’s nice that they have values, but it’s just good food. I thought for like a split second, that it might say, Black Lives Matter. And I’d be like, ‘Okay, sold.’” At Sunbasket, participants who had questions about the company’s ethos and sustainability practices often visited the “Values” page, where there was information about the brand’s Meal Kit ingredients, sustainability, and community involvement. It was clear from observing participants on DTC and other small catalog sites (e.g., Meal Kits, Consumable Subscription Services, etc) that they seek out information on the brand: how it started, who the founders are, and what resonates with them when it comes to values. All sites do this to some extent — for example, larger ecommerce sites often have a “Get to Know Us” section in their footer that has links to information on their charity work, corporate mission, and values. Yet it was particularly important to participants during DTC, small catalog testing who frequently looked for this information — sometimes before even looking at the products. In other words, less-well-known DTC and small catalog sites need to “introduce themselves” to most users. Having a few dedicated pages on this basic brand information — and being specific enough to clearly describe the brand in terms of its values and principles — will satisfy the majority of DTC, small catalog users (many of whom will “double-check” what they read on the site anyway by going to third-party sources; see #1774). For example, for many test participants on DTC, small catalog sites, the brand’s founder and origin story proved to be of high interest. As one user shared, “I like an ‘Our Story’ tab. That interests me…I’m curious often about how the brand started, how old it is, if there’s an interesting story behind it”. Dedicating a page to the brand’s origin story can therefore encourage users to form a personal connection with it. Plus, the brand’s story can also help differentiate it from its competitors — including larger and more established (but for some users, “soulless”) brands. In addition to the brand’s origin story, company values can be a key factor for users hoping to learn more about what makes a brand special or unique. During DTC testing, many participants reacted positively to featured content highlighting the brand’s values and mission statement. While brand values won’t necessarily sway all users to stay and explore products, such content will resonate with many and have a positive impact overall. “They talk a little bit more about their ingredients, which is super cool. I love that. Being a skincare buff, it’s always exciting to learn something new…Even from the perspective of being interested and wanting to learn a little bit more about skincare [in general], I think this is super helpful to know how this is going to provide benefits if I buy it.” This participant on Maya Chia spent a lot of time in “The Lab” section of the site, exploring information on the ingredients and extraction process. “I like this page. I didn’t know shoes could be made out of all these materials.” A participant on Thousand Fell explored information about how the shoes were made and what they were made of. “I like that they have all of the different materials that they use.” A participant at Allbirds explored the page dedicated to the materials used to produce the shoes. “It seems like everything is healthy here. I like how this is breaking down the benefits of each different ingredient.” Another participant used the “Ingredients” page at Monastery to learn more about the composition of the beauty products. “The idea that it’s balanced is kind of a big deal…I have a lot of old cookware that I’ve inherited and…some of my pots are not balanced.” A third participant appreciated the details provided by Equal Parts on the design of the cookware. “Why do they not have this on the homepage? Why so hidden?…I think most people need to see this because…these are so much more interesting than white shoes.” This participant was impressed with the level of information on the product details page but wished the information had been provided earlier, saying she would have been “hooked” much sooner. Most DTC, small catalog brands, in addition to having information to share about the brand’s values and core principles, also have useful information to provide about the products themselves. Given the small, focused product catalog, it’s typical on these types of sites for products to share the same ingredients and manufacturing process. Moreover, it’s also often a key selling point for these brands to highlight the product materials and the production process. In practice, this type of information could include the chemical composition of products in the health and beauty industry, such as makeup and skin care products, or to the textile and material composition of apparel, such as clothing items and athletic shoes. In addition, while many users just want to get an overview, some have specific concerns about particular ingredients — which might be based on allergies or other sensitivities. By outlining its manufacturing process and ethos Harry’s gives users a good insight as to why their products might be more attractive than those of better-known brands. By explaining its commitment to sustainability, Bang & Olufsen will satisfy many users as to the ethical nature of its manufacturing processes. Meanwhile, for some users, supplemental information like manufacturing ethics or production practices is particularly important — and can have a major impact on their decision to purchase from a brand. As with materials and ingredients, providing details about potential product concerns — sustainability, ethics, manufacturing etc. — answers users’ questions and allows them to discern if the product will meet their standards. During testing, it was clear that these product “story” pages resonated with participants, who, after reading the content, typically came away more impressed with the site’s products. In fact, some users may be happy to pay a bit more for products that have a higher degree of craftsmanship and that are ethically and sustainably produced, so it’s important to devote a handful of pages to describing these details. Finally, like with other important auxiliary content (e.g., see #252 and #1705), links to brand and product information pages should be included in prominent locations on the site; in particular, in the footer, in the main navigation, and on the homepage.", "summary": "Many users want to “feel good” shopping at a particular site, yet the fundamental information they’re looking for can be hard to find or overly sparse.", "purpose": "" } }, { "doc_id": "doc-0d52fbe68c213ddb60d39467d76f264c", "title": "Avoid Relying on “Accessibility Plug-Ins”", "g_id": "1776", "url": "https://baymard.com/premium/guideline-collections/cb3zzh/1776", "source_type": "guideline", "importance": 100, "summarized_info": { "description": "Accessibility plug-ins can malfunction, be blocked by ad-blocking browser plug-ins, or just go unnoticed by users with disabilities.", "issue": "Accessibility plug-ins can malfunction, be blocked by ad-blocking browser plug-ins, or just go unnoticed by users with disabilities These plug-ins typically only identify around 30% of WCAG issues due to their automated nature Plug-ins are site-specific, meaning users need to customize each site independently as the settings will not carry over onto new sites Accessibility plug-ins can leave sites open to potential security risks and future litigation as they do not fix a site's underlying code", "advice": "Don’t rely solely on “Accessibility plug-ins” to bring a site into accessibility compliance with WCAG guidelines Summary Summary Research Findings Video & Quiz Review Tool Audit Performances Implementation Examples Benchmark Performances Changelog", "summary": "Accessibility plug-ins can malfunction, be blocked by ad-blocking browser plug-ins, or just go unnoticed by users with disabilities.", "purpose": "" } }, { "doc_id": "doc-179beef0d5945d97826fd2a0d07ef809", "title": "Use “Load More” or Pagination for Product List Loading", "g_id": "1777", "url": "https://baymard.com/premium/guideline-collections/cb3zzh/1777", "source_type": "guideline", "importance": 75, "summarized_info": { "description": "On product or category pages with more items that can fit in a viewport, an endless scrolling list-loading method can make content at the bottom of the screen unavailable.", "issue": "On product or category pages with more items that can fit in a viewport, an endless scrolling list-loading method can make content at the bottom of the screen unavailable Users with cognitive disabilities may struggle with endless scrolling as they may have difficulty remembering where specific products are or may become overwhelmed by the number of product choices Pagination can discourage list exploration as users tend to focus on the first page results rather than compare product list items across many different pages The 'Load More' method can be functionally similar to endless scrolling for keyboard navigation users who have to navigate back through numerous products to find a product they were previously interested in", "advice": "Avoid endless scrolling as a product list loading schema Instead, use a 'Load More' list-loading schema, or a pagination schema, with clearly visible