Interaction design

All about web user experience and good design practice

Archive for the ‘patterns’ Category

Pattern: fixed toolbar

Posted by Dan on August 2, 2010

Use when

You need to give your users constant access to useful functions that need to be quickly accessible without scrolling. Think of it like the toolbar in Word or any other application for that matter.

Fixed toolbars contain functions which are:
- commonly used (share, add to wishlist)
- useful (search)
- or even promotional links (´Donate/join now´ or ‘give your feedback’)
- or branding fixed elements
Toolbar functions that need to be accessed at any time, with direct or indirect relation to the context on the page. The functions are accessible from a fixed position on the screen that holds its fixed position if the page is scrolled.

 

Form
Anything could go on the toolbar. Icons (if conventional and understood by users), pulldown menus, links, textfields. It depends what the tools are.
In CSS fixed elements are achieved by using position:fixed
- The toolbar could be present on almost all pages on your site, or only on pages where it makes sense with certain cha.
- Beware: They take up space, especially on low resolutions such as mobiles. More scrolling is needed to uncover the part of the page that it obscures.
- Keep it small. If it´s a horizontal toolbar, reduce the height. If it´s vertical, keep it narrow.
- Provide a ´close´ option if you think users will find it more annoying that useful. Consider how and when to show the toolbar again.
- Add tooltips or contextual help (on mouse-over show a hint)  to facilitate learning, or help balloons to encourage use (see UXmatters example).

Examples

Pricegrabber’s “ribbon” - read about it and Comet.co.uk ribbon

Tripadvisor.com – bottom toolbar

Cnet.com (browse the Reviews tab) – bottom toolbar

UXmatters – Top toolbar appears only when scrolled a certain amount down the page untill  the site header is no longer in site. Powered by Apture.

eConsultancy (blog) – Side toolbar with commercial-promotional function. Left toolbar is home-built, the corner toolbar is the ´Give feedback´ button by Kampyle

The http://www.conversion-rate-experts.com/buzz/ use a fixed side-bar :

uipatterns use a ‘you might like’ pop-over in the bottom-right corner. This could be useful for cross-sell, but it shouldn’t obscure other elements or it will have the adverse effect of annoying users.

More examples

From webdesignerdepot.com : “There are plenty of situations in which a fixed element (such as persistent navigation) could serve the owner’s business objectives and make the website more usable. Fixed elements are memorable and enhance the user experience. They have countless creative uses, and we will continue to see designers take advantage of them.”

For more examples, search google for ‘fixed position web design trends’

Related articles

http://www.linkedin.com/groupAnswers?viewQuestionAndAnswers=&discussionID=62855696&gid=3754&trk=EML_anet_di_pst_ttle

Posted in Interaction Design, patterns | Leave a Comment »

Dropdown usability issues and solutions

Posted by Dan on August 2, 2010

Keywords:  SELECT,drop-down list, drop down, pull-down menus, combobox (is not a dropdown, but many misuse the term)

Problem #1 - Long dropdown lists fall outside the browser viewing area

When the user clicks to open the dropdown the value that he wants to select falls off the screen, outside the browser viewport. If the user tries to scroll, chances are that the dropdown will close again. In worst case the user won’t be able to select his value with the mouse at all.

Solutions
In Firefox (3.6.8), Landsend.com product detail quantity dropdown seem to position the dropdown list above or below where the dropdown control, depending on position of the viewport.
If this is browser dependant behaviour, are there researches or sites that force this behaviour?

Other solutions:
- Dynamically shorten height of dropdown list (drawback is that you must scroll more to find something at the end of the list)
- Dropdowns are suitable for common lists such as country, but for long lists HTML links are preferred.
- Autosuggest (e.g. Hotels.com, Google Suggest) allows user to type and select from a dynamic list, but has its own issues…
- Add a ‘show more…’ link to bottom of dropdown

Problem #2 – Dropdowns pull attention

In one eye-tracking study

, the dropdown menu grabbed the user’s eyeball attention, no matter where it was positioned. Probable cause is that the dropdown is situated among empty textfields in a form, but looks as if it is prefilled which makes the user curious.
<h2>Problem #3 – Dropdowns are often skipped</h2>
In one usability test

, a dropdown was the first element in a form. Likely this is because it looks like a textfield that is already filled, so hasty users will skip it.

Recommendations

- Use a label with good copy. I prefer ‘(select your country)’ over ‘ — select your country —’

- For this label, use a grayshade that is distinctly lighter than the black text colour used for filling in textfields.

- Add a form label in front of the dropdown, just like you do for textfields. Example:  ’Country:     (select your country)’

- Keep the width of the dropdown equal to the width of textfields above and below it.

- Don’t make the dropdown (or radiobutton or checkbox) the first element in a form.

Are dropdowns problematic?

In favour of dropdowns:

- US users are more used to dropdowns, because they are used to selecting their State. International sites often ask for country.

Opposed to dropdowns:

- …

More issues

General usabililty issues of  dropdown menus

- Avoid long dropdown lists.Elderly have difficulty or annoyance of using dropdowns, especially if they are long. In some cases users don’t know that you can scroll inside the menu.

(source needed)

- Dropdowns affect user performance and error rate. Using the mousewheel you can change the selection inside the dropdown if the mouse cursor is over the dropdown menu. The dropdown is prone to accidentally change the value. In one form usability test the most common user error was the user had selected the wrong expiry year for his creditcard.

[/source]

- Dropdowns z-index obscure other elements such as custom tooltips, lightboxes, Flash applets

More issues:

http://baymard.com/blog/drop-down-usability

http://www.ixda.org/node/17094

Alternatives to dropdown

Radiobuttons - http://stackoverflow.com/questions/3339110/autocomplete-vs-drop-down-when-to-use


Articles/research:

http://www.useit.com/alertbox/20001112.html

http://listserv.acm.org/scripts/wa.exe?A2=ind0009D&L=CHI-WEB&P=R3784&1=CHI-WEB&9=A&J=on&d=No+Match;Match;Matches&z=4 – discussion about various issues and usability test results of  dropdowns

Related

autocomplete (e.g. Gmail To field), autosuggest (e.g. many latest browser and Google Auto-suggest)

http://usabilitydesk.com/10-autosuggest-and-autocomplete-demos/

http://www.webappers.com/2010/01/04/easy-and-slick-way-to-do-auto-complete-auto-suggest/  and http://www.webappers.com/2007/06/08/ajax-auto-suggest-auto-complete-textfield/

Posted in Interaction Design, patterns | Leave a Comment »

Scrolling shopping baskets

Posted by Dan on December 7, 2009

Some quick thoughts..Scrolling SB has comes with risks. If the shopping basket is too long, the totals and ‘checkout’ call-to-action button could appear below the fold. This is especially the case if many products have been added and at lower resolutions or non-maximized screens. Users would have to scroll to the bottom of the page to get the ‘checkout’ button in view.

I recommend:
- non-scrolling SB.
- if it must scroll, then make sure it anchors to the bottom of the page, so the checkout button is always in view (the top the basket then won’t be though..)
- make it scroll along slowly 
- either keep the product descriptions short (or empty) or consider removing the totals. test the worst-case scenario if it is a likely one.

Anybody seen any examples?

Posted in E-commerce, Interaction Design, patterns | Leave a Comment »

Tooltips and title (and a bit about alt tags)

Posted by Dan on January 9, 2009

Subject

Tooltips

Also known as

title attribute, titles, link title

See also

Variants of tooltip: click-tip  (user must click to view tooltip), super-tooltip (richt-text styled tooltip)

Similar to tooltip: ALT-tag   (see below for differences of ALT tags)

Screenshots

tooltips

 draglink
Above: NiceTitle is a JS/CSS implementation by somebody

Applies to

- Links <a> and navigation links
- Form elements and controls
- Buttons and controls
- Images and logo’s  (could contain tagline)

Use

- The goal of the link title is to help users predict what will happen if they follow a link.
- It’s a navigation aid to decrease disorientation of links. For example, tooltips on the home page allow the user to quickly preview the underlying content behind a link, without having to drill down into the page.
- Tooltips can save user time, avoid waiting for pages to load, especially those of badly named links.

- People often ignore embedded links. They don’t want to be interrupted by having to wait for another page to load. Tooltips can increase motivation to visit a link (if written well and not overused).
- In Web Apps, use tooltips as a descriptive text to tell user what the object under the mouse does. If you don’t need them, that’s great -you have a self-describing design- but many users expect tooltips anyway. [3]. “Minesweeping” is the irritating activity of moving the pointer across icons to uncover ToolTips or rollovers in order to figure out what the icons represent. Such designs require the user to actively decipher the interface, probing and testing the meaning of each interface element, rather than the interface elements being self-apparent.
- For form controls?? (e.g. the +/- buttons in a shopping cart)
- For images use the alt attribute, not the title attribute.

Design

- Beware, tooltips can obscure the view of any elements under it.
- Mac browsers show web tooltips in [balloon tooltip] style instead of rectangular PC style [Nielsen, 1998].

- Tooltips appear after 0,5 seconds and dissappear after ~5 seconds

 Accessibility

- Title attributes are by default NOT read by screen-readers (as oppossed to what Nielsen says), but if the user has turned it on can be read out loud by auditory browsers.
- There are some notes that state that the title attribute can be harmful to accessibility.

SEO

There are no known SEO beneficial effects to using TITLE attributes. If any benefits are mentioned, they are often myths. Further research is needed.

Copywriting

Do:
Appropriate information to include in a link title can be:   
- name of the site the link will lead to (if different from the current site)
- name of the subsite the link will lead to (if staying within the current site but moving to a different part of the site)
- added details about the kind of information to be found on the destination page and how it relates to the anchor text and to the context of the current page
- warnings about possible problems at the other end of the link (for example, “user registration required” when linking to The New York Times) 

Don’t:
- Don’t add link titles to all links: if it is obvious from the link anchor and its surrounding context where the link will lead, then a link title will reduce usability by being one more thing users have to look at.
- The user should not have to read the whole tooltip text. The first few words should give the user a good idea of what the link is about.
- Tooltips have to be brief. Some browsers (FF) can show only a limited amount of tooltip text and often disappear after 5 seconds. Limit to 60-70 characters.
- Tooltips on links should be used to enhance website usability through information scent.
- Use tooltips only when they provide the supplementary information about the link that they’re intended for – don’t use it to say ‘Click Here’ and don’t repeat the link text redundantly (although Amazon and Landsend do do this for their image-based commerce buttons).
- Don’t use title attributes for anything not supplementary, definately don’t use it for site critical information.
- make the link anchor and its surrounding text understandable without seeing the link title. Users should not have to point to a link to understand what it means: the link title should be reserved for supplementary information.
- There is no proof that titles affect SEO.

Process of identifying alt/title tags

Next time we define tooltips, maybe we should first carefully identify if each link/button we want to give a TITLE tag/attribute is not in fact a button image. For example, I’ve found that the buttons in an Order Process I was working on were not images, but (copy-able) text. To check this, right-click an image or try to select the text characters in the link (would this work for all cases?). However, what to do in such cases where there is a clickable, copyable link on top of a clickable image button? I suppose that the former should receive a TITLE tag that has the exact text as the ALT tag of the button below it..

Differences with ALT-tag

Whereas the TITLE tag can be used for practically all HTML elements (<a>, <span>, etc), the ALT tag or attribute is used for images (<img>) only.

All the above guidelines apply to the ALT tag also, with the following exceptions:

  • All images should have an ALT tag. All clickable images should have an ALT tag which describes the text on that button, usually just a repeat of the exact text of the button itself.
  • Possible SEO benefits of using ALT tag versus none for using an TITLE tag.
  • Accessibility benefits of ALT tag has been proven over and again, whilst those for the TITLE tag are over overrated.
  • Possible design (look) differences.

Links and further reading

[1] Jakob Nielsen’s “Using Link Titles to Help Users Predict Where They Are Going” @ http://www.useit.com/alertbox/980111.html
[2] Presentation about Title attribute at Web Essentials 05 @ http://www.paciellogroup.com/resources/articles/WE05/
[3] Designing interfaces (book)
[4] Microsoft (Windows) tooltip guidelines @ http://msdn.microsoft.com/en-us/library/aa511495.aspx

 For Developers

NiceTitle by http://www.kryogenix.org/code/browser/nicetitle/
Similar examples to Nicetitle here
A gallery of 50+ Tooltip scripts also useful for designers

Posted in patterns | Tagged: , , , , , , , , | Leave a Comment »

Patterns

Posted by Dan on July 28, 2008

This article contains any pattern libraries I have come across. The list is frequently updated.

I´ll start with introducing patterns for those who aren´t familiar with their purpose. If you already know what patterns are, scroll down to the big patterns libraries.

What are patterns?

Repository of conventions.
Collections of common UI elements, or a grouping thereof.
With discussion on why/when to use and visual examples.

Why use patterns?

The tricky thing about (interaction) design is that the answer is often ‘it depends’, as there is generally no reapplicable solution to a specific problem; the answer depends on the larger context, the flow of pages, the other elements in display, or the broader user experience.

Patterns try to get rid of this trickyness. In a way, they are ridding of interaction designers ;) At times patterns are so abstractly defined (in text), so generic. The bottom line is, study and understand patterns, don’t just copy them.

Pattern crawlers

http://www.uxforthemasses.com/design-patterns-search/
See also Visual Fox (?)  (A-B test result search) in other post

Pattern libraries

(in approximate order of popularity and personal preference)

http://patterntap.com   +

http://ui-patterns.com/  +  (down Feb2012)

http://quince.infragistics.com

Welie.com
http://konigi.com/

http://patternry.com/patterns/ +

http://www.userplus.com/design-patterns-2/
Yahoo! patterns (down but to be replaced by other site soon)
http://wiki.forum.nokia.com/index.php/Category:Mobile_Design_Patterns (mobile design patterns)
http://darkpatterns.org/ (anti-patterns)
http://www.bbc.co.uk/guidelines/gel/
http://www.designmeltdown.com/
http://www.interaction-patterns.org
http://www.smashingmagazine.com/category/showcase/
http://www.smileycat.com/design_elements/ (incl. mega dropdown menu’s  and mini shopping carts)
http://graffletopia.com/
http://box.mepholio.com/ - mainly graphical, some patterns  (404, calendars, pagination, …)
http://codeidol.com/ajax/ajaxdp/
http://flickr.com/photos/factoryjoe/
http://www.flickr.com/photos/morville/
http://www.vimeo.com/album/17554
Forms @ http://www.flickr.com/photos/squaredeye/sets/72157594526698707/
Sign-up Form conventions @ http://www.smashingmagazine.com/2008/07/04/web-form-design-patterns-sign-up-forms/
http://www.jankoatwarpspeed.com/post/2010/02/26/table-ui-patterns.aspx – Tables
http://osdpl.fluidproject.org/ (open-source design pattern library)

http://patterns.endeca.com/content/library/en/home/patterns.html TIP – Faceted Nav, etc. Well structured with ´solution elements´

More

@Google link: that refer to a relevant page if you have already found one

@ RollYo.. / Google Custom Search GCS  (see links below)

More – Pattern link directories

Smashing Magazine interface patterns resources TIP!
http://www.uxpond.com/sites.html

http://www.visi.com/~snowfall/InteractionPatterns.html

Templates

Templates are kind of like patterns, but for whole pages and predesigned. Lots of inspiration for generic standard solution.

http://www.templatemonster.com

Top best website designs

There are ample blogs and sites dedicated to collecting, what is to their professional opinion, the most beautiful designs. Emphasis on graphical design or minimalism.

Smashing Magazine

http://www.atrickdesign.com/

Writing patterns

 http://www.uie.com/articles/elements_of_a_design_pattern/
http://www.visi.com/~snowfall/InteractionPatterns.html

Search all patterns

Rollyo.com

http://www.google.com/cse/home?cx=002511809528603050287:g97sidtolmw

Books with patterns

Forms

Forms that work
Luke W

Posted in patterns, Resources | Tagged: | Leave a Comment »

 
Follow

Get every new post delivered to your Inbox.