WEB I 08 - Usability

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    5 Favorites

    WEB I 08 - Usability - Presentation Transcript

    1. INFORMATION ARCHITECTURE Usability
    2. Designing a Web Site
      • Part 1: Site Design / Engineering
        • concerned with usability
      • Part 2: Page Design / Art
        • concerned with aesthetics (visual attractiveness)
    3. What Do You Dislike About the Web? or, what do you hate to see on a web page?
    4. Usability Matters
      • Many of the things we don't like about the web pertain to the usability of web sites.
      • Usability is:
        • Designing things so that they make sense to the people who use them.
        • How easy is a web site to understand and use.
    5. Usability in real life http://www.flickr.com/photos/rdolishny/2760207306
    6. Usability in real life http://www.flickr.com/photos/johnswords/2717108560/ http://www.flickr.com/photos/11759181@N04/1176026705/
    7. Usability and Audience Types
      • People visit a site for different reasons.
      • Thus, the type of audience affects usability.
        • Also, how people use the web has changed significantly over the past ten years
          • users who are looking for a particular piece of information.
            • informavores
          • concerned chiefly with usability (how easy is it to find information).
          • Information Foragers
    8. Information Foragers
      • Will rely on search engine to get to the “information patch” (i.e., web site)
        • Will be seeking very specific “prey” (information)
        • Because search engines make it easy to find patches, hunters will spend little time looking for prey
      • Even if hunters visit a site more often, they will still leave it quicker.
          • users who "stumble" across a site.
          • concerned chiefly with aesthetics (does this site look professional or interesting enough to continue exploring this site).
          • Minority
          • Surfers
    9. Types of Information Foraging
      • A given user can, at different times, engage in different types of information foraging
        • Known item seeking
        • Exploratory seeking
        • Don’t know what you need to know
        • Re-Finding
      http://www.boxesandarrows.com/view/four_modes_of_seeking_information_and_how_to_design_for_them
    10. Known item seeking
      • Users who know what they are looking for, can describe it, and may know where to start.
        • the user may be happy with the first answer they find
      • Prefer:
        • Search
        • a-z indexes
        • navigation
      • Main virtue of site:
        • able to answer user’s query fast
    11. Exploratory seeking
      • Users who know roughly what they are looking for, can’t describe it, and likely don’t know where to start.
        • They will usually recognize when they have found the right answer, but may not know whether they have found enough information (i.e., may forage more)
      • Prefer:
        • Navigation
        • related links
        • search
    12. Don’t know what you need to know
      • Sometimes we don’t know exactly what we need to know.
        • We may think we need one thing but need another
        • or, we may be looking at a website without a specific goal in mind.
      • Prefer:
        • Interesting content
    13. Re-Finding
      • Users looking for things they have already seen.
        • They may remember exactly where it is, or only remember what site it was on, or even have little idea about where it was.
        • ~40% of an individual’s searches are re-finding searches (performing a search they have already performed in the past).*
      • Prefer:
        • breadcrumbs, recently viewed items, cookie support, etc
        • Wishlists, shopping carts, etc
      * Teevan et al, “ Information Re-Retrieval: Repeat Queries in Yahoo’s Logs ”, SIGIR 2007
    14. Other Browsing Behaviors
      • Velocity of web navigation*
        • 25% of all documents displayed for less than 4 seconds
        • 52% less than 10 seconds
          • “ they [the participants] regularly just seemed to glimpse over most of the information offered, before they perform their next navigation action.”
        • Consequence for usability?
      * Weinreich et al, “ Off the Beaten Tracks: Exploring Three Aspects of Web Navigation ”, IW3C2 2006
    15. Velocity of web navigation Weinreich et al, “ Off the Beaten Tracks: Exploring Three Aspects of Web Navigation ”, IW3C2 2006
    16. Other Browsing Behaviors
      • Web site re-visitation is very common
          • ~70%*-80%** of a user’s page visits are re-visits to a site.
          • ~45% of a user’s page visits are re-visits to a page. * ***
          • ~1 in 6 (16%) of visits are to Google***
          • ~ 60% of visits are to user’s top 10 site***
        • However, this data does vary markedly for different individuals
        • Consequence for usability?
      ** Cockburn et al, "Improving Web page revisitation: Analysis, design and evaluation," IT & Society 2003 *** Weinreich et al, “ Off the Beaten Tracks: Exploring Three Aspects of Web Navigation ”, IW3C2 2006 * Weinreich et al, “ Web Page Revisitation Revisited: Implications of a Long-term Click-stream Study of Browser Usage ”, CHI 2007
    17. Part 1: Site Design
      • Usability is perhaps the most important goal in web design.
        • If users cannot figure out how to use your site easily, some will leave your site, never to return.
          • Perhaps more importantly, a good user experience creates trust in a site.
        • In the web, users experience usability first and pay later; thus if site not usable, they will not purchase (or revisit) from your site.
          • in contrast, outside the web, users generally buy first, then experience usability (think DVDs) later.
    18. Factors Determining Usability
        • i. The response time (i.e., download time) for site/pages.
        • ii. The organization system for site.
        • iii. The navigation system used throughout the site.
        • iv. The content of the site.
    19. i. Response Time
      • If your pages take a long time to download, users will leave your site.
      • How long is too long?
        • 1 second response-time between action (e.g., mouse click) and response (page loaded) is ideal.
          • For most broadband users, that means about 200 KB
        • 10 seconds is the upper limit for keeping user in site.
      • That means, any given page should be functionally loaded in no more than ten seconds.
      Source: Jakob Nielsen, Designing Web Usability , 1999 Nov. 1998, www.emarketer.com 2006, webdesign.about.com
    20. Factors Determining Response Times
      • Average response time is determined by:
        • the speed of the user's connection to Internet
        • the speed/load of the web server
        • the speed of the server's connection to Internet
        • load on the Internet (2-4 pm peak loads in North America)
        • cumulative file size of the images and objects in web page
      • Which of these factors do you have control over as a web designer?
    21. Understanding Page Size
      • Again, page size is the cumulative file sizes of all the elements on a web page. This includes:
        • the HTML file
        • the image files
        • object files (video, Flash)
      s
    22. main.htm 4K randyc.gif 1K bar.gif 3K bio.gif 1K bio_over.gif 1K site.gif 1K site_over.gif 1K idea.gif 1K idea_over.gif 1K for.gif 1K for_over.gif 1K TOTAL 16K Download time @ 28.8 Kbps = 5 seconds 128 Kbps = 1 second First Page of Site Response Time
    23. TOTAL 8K Download time @ 28.8 Kbps = 1.5 seconds 128 Kbps = 1 second Subsequent Page of Site Response Time cv.htm 4K cv.gif 1K bio_bar.gif 3K Other images still in cache so no need to re-download
    24. menu.htm 1K main.htm 1k frameset.htm 1K 5 images + roll-overs 60K imagebar.gif 1K imagmap.gif 17K rollovers 4K logo.gif 1K TOTAL 95K Download time @ 28.8 Kbps = 32 seconds 128 Kbps = 7 seconds First Page of Site Response Time
    25. Subsequent Page of Site Response Time TOTAL 41K Download time @ 28.8 Kbps = 15 seconds 128 Kbps = 3 seconds artist.gif 8K artbar.gif 2K byname.gif 2K alphabet.gif 8K artist.htm 20K dot.gif 1K Other images still in cache so no need to re-download
    26. ii. Organization System
      • The way a site is organized also affects usability.
        • Organization is important because a web site is about information.
        • Organization refers to the grouping of information .
        • Grouping:
          • providing paths to information by showing relationships .
          • The trouble with relationships is that they are subjective.
    27. Grouping Exercise
      • Group (organize) the following information:
        • refrigerator
        • socks
        • bureau
        • living room
        • dictionary
        • kitchen
        • milk
        • bookshelf
        • bedroom
    28. Grouping Possibilities
      • Alphabetically
        • bedroom
        • bookshelf
        • refrigerator
        • bureau
        • dictionary
        • kitchen
        • living room
        • milk
        • socks
      • By Size
        • Large
          • kitchen
          • living room
          • bedroom
        • Medium
          • refrigerator
          • bureau
          • bookshelf
        • Small
          • socks
          • dictionary
          • milk
      • By Room
        • Kitchen stuff
          • refrigerator
          • milk
        • Living Room stuff
          • dictionary
          • bookshelf
        • Bedroom stuff
          • socks
          • bureau
      • By hierarchical location
        • Kitchen
          • refrigerator
            • milk
        • Living Room
          • bookshelf
            • dictionary
        • Bedroom
          • bureau
            • socks
      Source: Fleming, J, Web Navigation , 1998
    29. Subjective Organizing
      • Because organizing information is subjective, there are innumerable ways of organizing information.
        • While this means there is no "perfect" way of organizing your information, there are still "better" and "worse" ways of organizing information.
      • How you organize information in a web site should be a balance between how the information "wants" to be organized and how the user "wants" to find it.
      Source: Fleming, J, Web Navigation , 1998
    30. Organization System
      • Refers to the "philosophy" and to the "execution" used to organize a site's information.
      • In other words, an organization system refers to both its:
        • Organization scheme (how a site is subdivided into sections) and
        • Organization structure (the relationships between these sections).
    31. Organization Schemes
      • Defines the shared characteristics of content items and determines their logical grouping.
      • Types of organization schemes:
        • exact
        • ambiguous
        • hybrid
      Source: Rosenfeld & Morville, Information Architecture for the Web , 1998
    32. Exact Organization Schemes
      • Divide information into well-defined, mutually exclusive sections.
        • Alphabetic
        • Chronological
      • Of limited use. Why?
      Source: Rosenfeld & Morville, Information Architecture for the Web , 1998 Courses Astronomy Biology Chemistry Drama Fencing Press Releases Nov 4, 1999 Oct 21, 1999 Oct 10, 1999 Sept 3, 1999 Aug 18, 1999
    33. Ambiguous Organization Schemes
      • Divide information into categories that defy exact definition.
      • Much more subjective, and as well, more useful. Why?
        • Answer: we don't always know what we are looking for.
      • The success of an ambiguous organization scheme depends on the usefulness of the classification to the user.
      Source: Rosenfeld & Morville, Information Architecture for the Web , 1998
    34. Types of Ambiguous Organization Schemes
      • Topical
        • E.g., yellow pages, college calendars
        • Challenging to design, yet very help to users
      • Task-oriented/Functional
        • Used by software (File, Edit, Format, View)
        • Useful for web-based applications
      • Metaphor-driven
        • metaphor can help make the unfamilar seem familiar (think of Windows folders, trash can, and desktop)
        • Can be difficult to maintain over entire site
      • Audience-specific
        • Makes sense if more than clearly-definable audience
      Source: Rosenfeld & Morville, Information Architecture for the Web , 1998 Faculties Sciences Humanities Social Sciences Fine Arts ABC College Register in a Course Locate an Instructor Meet the Students Choose a Loan Plan ABC College Registrar’s Office Lecture Theatre Student Pub Bank Machine ABC College Potential Students Faculty Existing Students Broke Students
    35. Hybrid Organization Schemes
      • A mixture of several different organization schemes.
        • Generally, a very bad thing; yet sometimes difficult to avoid
      • The point of an organization scheme is to provide the user with a mental model to help user understand structure of data.
        • Hybrid usually results in confusion.
        • If you must use hybrid scheme, try to visually separate the different schemes.
      ABC College Humanities Sciences Locate an Instructor Students Parents Get a Library Card Student Pub Services for Students Find a Student Loan Get a Library Card Visit the Student Pub Academic Areas Fine Art Humanities Sciences Students Parents Faculty Fine Arts Humanities Sciences Health Studies
    36. Hybrid Schemes Sears separates topical and functional Topical Functional/Metaphor Functional/Metaphor/Topical Topical Functional/Metaphor Functional Metaphor Topical/Functional/ Metaphor Topical
    37. Designing Schemes
      • The danger with hybrid schemes is that they can utterly confuse user.
      • Make sure your categories are clear as possible.
      Audience Specific/Functional/Topical/Metaphor = BIG MESS Topical Where do I click if I'm a student looking for the schedule for Introduction to Computers? What does this do? What does this do?
    38. Designing Schemes
      • Categories generally should be mutually exclusive
        • However, sometimes it it sensible to cross-list an item in more than one branch of a scheme
        • Too much cross-listing, then scheme loses its value
      Academic Sciences Humanities Social Sciences Scholarships Students Register Student Union Scholarships Fine Arts Services Registering Visiting Parties Scholarships
    39. Designing Schemes
      • Be cautious of metaphors
        • A metaphor is something that is used to represent something else.
      • advantages:
        • metaphor can provide a unifying framework to entire site
        • users can make use of their knowledge they already have
          • e.g., the shopping cart metaphor in e-commerce sites
      • disadvantages:
        • often difficult to make site sections "fit into" your metaphor
        • If connection between metaphor and content is tenuous then user will have difficult time finding information.
    40. The whole world's a Metaphor Example of the difficulty of making all of a site's main sections fit into a single metaphor. In the above example, why is the "New" section up in the attic? This seems to be a clever metaphor, but the placement of categories with shifter position is arbitrary: why is "Images" section in the Reverse position?
    41. Organization Structures
      • The structure of information defines how different categories defined by the scheme relate to one another
        • Structure defines way users navigate through information
        • It is the plan or map of the pages in a site
    42. Types of Organizational Structures
      • Linear
      • Hub and Spoke
      • Web
      • Hierarchical
      • Facets
    43. Linear Organization
      • Pages in a sequence
        • Wizards, checkouts, and other pipelines
    44. Hub and Spoke
      • Start from landing page, and navigate to individual pages.
        • Extension of linear
    45. Web
      • Many pages linked together without levels or sequence
        • Each page is potential hub and spoke
        • E.g., MySpace
    46. Hierarchy
      • Pages are arranged in a parent-child (tree) relationship.
        • Most sites are hierarchical
    47. Facets
      • A page belongs to one or more facets.
      • A facet is a unique category that describes a property of a page
        • Each facet might be arranged hierarchically
        • Allows a user more freedom in finding information
      Kalbach, Designing Web Navigation (O’Reilly, 2007)
    48. Example Facets Source: Uta Priss, Elin Jacob, “ Utilizing Faceted Structures for Information Systems Design”, http://www.upriss.org.uk/papers/asis99.pdf
    49. Designing Hierarchies
      • Try to balance breadth and depth
        • Users don't like having to "drill-down" endlessly to find an item, nor do they like having to read through hundreds of menu choices.
      • Key question is what is the right balance?
      breadth depth
    50. Memory Implications
      • Most people can only manage seven, plus or minus two, items of information at a time.
      • Thus, some researchers have suggested that your site should have 5 to 9 major sections.
      • If we have limitations with short-term memory, shouldn't we then try to have less breadth, and more depth?
        • NO!
    51. Research on Breadth vs Depth Source: Zaphris & Mtei, "Depth vs Breadth in the Arrangement of Web Links," 1997 User's Ranking of Difficulty Average access time Mean # of Errors 2x6, Breadth=2, Depth=6 4x3, Breadth=4, Depth=3 8x2, Breadth=8, Depth=2 4x1, 16x1 1st page Breadth=4, 2nd page=16 16x1, 4x1 1st page Breadth=16, 2nd page=4
    52. Research on Breadth vs Depth Source: Larson & Czerwinski, "Web Page Design: Implications of Memory, Structure and Scent for Information Retrieval," 1998 Average access time Worst Best Lostness Worst Best User Preference Worst Best
    53. Research on Breadth vs Depth Users greatly preferred this TOC to ... ...this one
    54. Conclusions on Breadth vs Depth
      • access time is proportional to depth of hierarchy
        • i.e., the deeper the menu, the more time the user will spend and the less happy she/he will be.
        • Try to avoid a depth of more than 2 or 3
      • increases in breadth do not seem to affect speed
        • i.e., one well-organized, moderately-broad information space gives optimal user performance.
    55. Information Scent
      • However, if the category labels (the organization scheme) are not well organized, broader structures can have just as poor performance (or even worse) as deeper structures.
      • Information has a "scent" that users can pick up through category labels.
        • i.e., scent is the amount of remote indication a user can derive from a site's organization scheme and labeling about the relative location of a target.
        • A well-designed organization scheme improves the scent of information, thus making it easier for users to find their information.
    56. iii. Navigation Systems
      • When a user enters a web site,
        • he/she is usually trying to find something, and
        • he/she must decide whether to search or to browse
          • some users are "search-dominant," others are "link-dominant"
          • thus, every web site should provide both :
            • A way to find information via a search facility,
            • A way to find information via clicking on a hierarchical series of links, also called a navigation system .
      Source: Steve Krug, Don't Make Me Think , 2000; Jakob Nielsen, Designing Web Usability , 1999
    57. Navigation Conventions
      • We rely on conventions in physical space (in cities, on the freeway, at the airport, etc) and in information spaces (within a book or newspaper) that speed up the navigation process.
      • Likewise, various conventions have emerged in the web that help users in their navigation.
        • In general, it is sensible to work within these conventions.
        • If not, you should have a good reason (e.g., potential audience is avant-garde, new non-conventional way is clear and self-explanatory, etc).
        • Remember how briefly most users view a page!!
      Source: Steve Krug, Don't Make Me Think , 2000; Jakob Nielsen, Designing Web Usability , 1999 ßêÿš¥ We understand the meaning of these signs, even though we can't read their language, because of our knowledge of traffic sign conventions. Even though I can not read the language used on this page, I can still navigate it due to its use of web conventions.
    58. Navigation Conventions Company ID Main sections (global navigation) Utilities (functional or action oriented) sub sections Local Navigation You are here indicators Small text footer links Page Title
    59. Navigation Conventions Company ID Utilities Local Navigation Small text footer links Page Title Main sections (global navigation) You are here indicator
    60. Navigation Conventions Global Local Global Local Global Local Inverted-L Horizontal Embedded Vertical Conventional arrangements of navigation elements Kalbach, Designing Web Navigation (O’Reilly, 2007)
    61. Searching
      • About 50% of users will use search rather than navigation system.
        • However, if your search facility is not very accurate, adding a search facility may be counter-productive.
      Source: Louis Rosenfeld, Information Architecture , 1998; Steve Krug, Don't Make Me Think , 2000
    62. Search Interface Guidelines
      • Available on every page
      • Text box plus button with label “Search”
      • Located top right (preferred) or top left of page
      • Text box size ~25 characters wide
    63. Search Engine Results Page (SERP)
      • Should be paginated into chunks of about 10 results
        • Almost everyone (~93%) will stick to first SERP
        • In Google, about 75% stick to first SERP
      • Almost everyone will choose the 1 st or 2 nd choice
        • In Google, almost 70% pick 1 st or 2 nd choice in SERP
        • In Google, over 50% pick 1 st
      Source: Nielsen + Loranger, Prioritizing Web usability , 2006
    64. Google as Entry Point to Site
      • One of the key changes in user behavior over the past 5 years is that users often don’t visit “good” sites but look for “good” answers.
        • As a result, many (or even most) people will be using Google (and not the home page) as the portal into any page in your site.
    65. General Navigation Questions
      • A site's navigation system should answer these three user questions:
        • Where am I?
        • Where have I been?
        • What’s here?
        • Where can I go?
      Source: Jakob Nielsen, Designing Web Usability, 1999
    66. Where Am I?
      • In any page in your site, users should be able to tell:
        • where on the web they are
        • where in the site they are
    67. Where am I (on the web)?
      • Every page in your site should contain the company name or logo.
        • This is generally placed in the upper-left corner
        • It is usually made into a link to the home page as well
      • You may also want to indicate who is the author, when it was created or last modified, copyright info, privacy messages, security options, etc.
        • This usually is placed at the bottom or footer of a page.
    68. Company logos in the upper-left corner is extremely common on the web.
    69. Where am I (on the web)?
      • Home pages should allow user to quickly determine the site's purpose in a quick scan of the page.
        • People will visit the home page more often than any other page in your site.
        • But studies show that users will spend less time viewing a home page than an interior content page.
      This home page provides few clues as to what Acer does (build and sell computer equipment)
    70. Where am I (in the site)?
      • You should specifying where the user is within the site by:
        • giving each page a name.
        • highlighting, within the navigational menu, the location of the current page within the larger hierarchy of the site.
        • Breadcrumb trail
          • Shows the user where she is in the site hierarchy.
          • e.g.,
            • Home | Products | Shoes | Athletic | Nike
    71. Where am I ? Company ID Page Title Navigation Highlight
    72. The amazon site, in contrast, visually shows which section and subsection we are in (the Award Winners subsection of the Books section). In the Slate Magazine site, we can easily tell that this particular page is part of the Culture section. Unfortunately, the Culture section is quite large with many subsections (this page is part of the Dialogue subsection); however, there is no way to tell this without exploring the Culture link. Note: in general, if your are indicating current location via change in navigation banner, the link should be disabled. In this example, the Award Winners isn't a link.
    73. Sometimes the indicator of the site's current location is overly vague. Can you find it in this example? Unless you are trying to impress users with your originality (which often is the case for designers and artists), try to make location indicators reasonably obvious (but not obnoxious).
    74. What’s Here? – Page Titles Page Name Source: Steve Krug, Don't Make Me Think, 2000 Page Name Content here Page Name Page Name Make the page title big and prominent: typically it should be the largest text on the page. Content here Content here Content here
    75. Where have I been?
      • Since the web is state-less (the server doesn't keep track of the last page you were on), it is difficult to indicate this.
        • the browser's Back button and History button help
          • Though less than 1% of users use the history feature
      • One partial solution is to use different link and visited link colors.
      Source: Nielsen + Loranger, Prioritizing Web usability , 2006
    76. Breadcrumbs Breadcrumb links Notice that each step in trail is a link. Most sites do not make the last step in the trail (i.e., the current section) a link.
    77. Can you tell which color is the visited link and which is the non-visited link?
    78. Visited Link Color
      • Using the default colors for links (blue for unvisited, purple for visited) is best choice for usability.
            • "Of all the graphic design elements we looked at, the only one that is strongly tied to user success was the use of browser-default link color ... Our theory is that use of the default colors is helpful because users don't have to relearn every time they go to a new site.” Spool, 1999
            • “ Unchanging link colors create navigational confusion because users don’t quite understand their different choices or where they are. This is as serious a usability problem as it ever has been.” Nielsen, 2006
      Source: Jared Spool, Web Site Usability , 1999 Source: Nielsen + Loranger, Prioritizing Web Usability , 2006
    79. Visited Link Color
      • Other strategies:
        • use red as non-visited link color (our eyes look at red first)
        • use as non-visited link color the same color as primary color scheme in site as whole; visited link color would then be a lighter, less-saturated version of that color.
      Source: Jared Spool, Web Site Usability , 1999
    80. Whatever you do, don't use too many link colors in one page or site. The Slate Magazine main page (below) uses three different link colors (plus another for visited link). Internal pages in the site (at left) use 3 different link colors plus two different visited link colors.
    81. Another solution to the "Where Have I Been?" question is to provide " bread-crumbs " — that is, some visual indication of which choices the user has made, usually via hyperlinks
    82. Where can I go?
      • Indicated by the page's links
      • Every Web page should contain at least one link
        • never have Dead-end pages (pages with no links to any other local page in the site)
      • the site's links should form a navigation system that has consistency from page to page.
      Source: Jakob Nielsen, Designing Web Usability , 1999 Remember, not every visitor to a page comes through the front door; they might arrive from a search engine link or a bookmark. hyperlink
    83. Types of Navigation Systems
      • global
        • provides access to first-level section pages.
        • available in all pages
      • local
        • in a complex site, provides access to pages within a section or sub-site.
      • contextual
        • additional embedded links
        • only for non-critical links or for repeating main links
        • Might also be a series of related content links
      Global system provides links to these pages local system might provide links to these pages
    84. global navigation system local navigation system contextual navigation
    85. Navigation Design: First Screen
      • The first screen the user sees must be as good as it can be.
        • This first screen might not be the home page — the user might come to a page from an external link or search engine.
      • The part of a web page that is visible without vertical scrolling (“above the fold”) is extremely important.
    86. Navigation Design: First Screen
      • About 50% of users will almost never scroll
          • The majority of users scan what they see on the browser and then make their navigation choice.
          • Users will scroll vertically if there is some compelling content (e.g., a listing of products, an article they are reading, search engine results, etc).
          • Home pages will only be scrolled between 14-23% of the time.
          • Almost no one will use the horizontal scroll bars. NEVER require users to use the horizontal scroll bars to see important navigation elements!!!
        • Of those that do scroll, most will only scroll about a screen full.
      • Thus, you must try to fit the most important parts of your site—that is, the navigation system, company name, page title, and search option—above the fold.
      Source: Nielsen + Loranger, Prioritizing Web Usability , 2006
    87. Scrolling Research
    88. Navigation: First Screen
      • Most users have monitor resolution set to 1024x768 or 1280x1024.
        • Recall, however, that browser buttons, status bar, window title, etc also take up space.
      http://www.hobo-web.co.uk/tips/25.htm (March 2008 visit stats)
    89. Navigation: First Screen
      • Users with higher resolution generally do not have their browser window maximized.
        • Why?
    90. Navigation: First Screen
        • They may have:
          • multiple monitors of different sizes
          • multiple windows opened
          • Sites often don’t take advantage of widescreen/maximized space
    91. Navigation: First Screen
      • Repeating backgrounds can cause problems at higher resolution.
      800 x 600 1600 x 1200
    92. Navigation: First Screen
      • Thus, design your page with the 1024 x 768 resolution in mind.
        • This means content area is about 1004 x 598
      1024x768 Screen Size 1024x738 Browser Window 1004x598 Content Area
    93. Designing Pages
      • Ideally, your pages should work at any resolution, from 800x600 to 1280x1024 and beyond.
    94. These vital navigational elements are off-screen at smaller window size.
    95. This site is optimized for larger size but is still usable at smaller size
    96. This site is optimized for larger size but is still usable at smaller size
    97. Guidelines for screen size
      • Optimize for 1024x768
      • Do not design solely for a specific monitor size because screen sizes vary among users.
      • Use a liquid layout that stretches to the current user's window size (that is, avoid frozen layouts that are always the same size).
      • Even better, use an elastic layout that sensibly adapts to window size.
    98. Examples of frozen layout
    99. Examples of fluid layout Notice how filling entire window might make text hard to read.
    100. Examples of elastic layout Notice how size increases but doesn’t fill entire window in order to maintain readability
    101. Navigation: Where can I go?
      • Your global navigation system should provide a way to return to the site's home page.
      • Methods:
        • provide an explicit home link to navigation bar, or
        • make the company logo a link back to home page.
          • In this case, it is nice to also add the word &quot;Home&quot; to the logo or use the alt attribute of the <img> tag for the logo to provide feedback to the user that logo is clickable.
      home Go To Home Page
    102. Navigation Elements
      • There are many different user interface elements by which you can construct a navigation system.
        • Navigation bars
        • Text menus
        • Dynamic menus
        • Trees
        • Action buttons
        • Drop-down menus
        • Tag clouds
        • Step + paging links
        • Site maps and indexes
        • Directories
      Kalbach, Designing Web Navigation (O’Reilly, 2007)
    103. Navigation Bars
      • A chain of horizontal links made from
        • Images
        • Text
    104. Navigation: Text
      • In order to improve download speed, many sites have replaced all-graphic menu systems with text-based menu systems that combine small, reusable graphics with text links using CSS or within tables.
    105. Navigation Bars
      • It is often best to place navigation bars at top of page, since users scan web pages using same pattern as when reading: from top-left to right, then down.
        • Tests have shown that users perform slightly better with main navigation system at top (or bottom).
        • However, there is less vertical screen space than horizontal, so placing links on left-side of screen will maximize available screen space.
      Source: Jared Spool et al, Web Site Usability: A Designer's Guide , 1999
    106. Navigation: Tabs
      • Tests have shown that users find tabbed interfaces very easy to use.
      Ideally, the tab for the current section should be coloured to indicate the current section.
    107. Navigation: Tabs
      • If you are going to use a tab metaphor, make sure they operate as tabs.
      • Have a tab selected when you enter the site.
      Neither the Quicken or the petsmart sites have a tab initially selected... … but both the chapters and circuit city sites do. In both of these sites, the tab metaphor only extends to the current area, which loses the meaning cues provided by tabs. 
    108. Navigation: Icons
      • Icons are metaphors
      • Be sure to provide text labels to help clarify the meaning of icons.
        • One way to do this to show label only when you roll-over icon. However, this is not an ideal solution from a usability perspective.
      These two examples use a rollover text explanation to help (somewhat) clarify the icon's meaning These icons are not exactly obvious.
    109. A picture is worth a thousand words ... User's Interpretation Designer’s Intended Meaning State of your account Fixing your order What's new E-mail us A picture maybe indeed be worth a thousand words, but for a usable iconic system, we want the user to associate only one meaning/word to the image, not a thousand !
    110. Imagemaps vs. Individual Graphics
      • A image-based navigation system can be created via single graphic using an image map, or by breaking into individual graphics.
    111. Imagemaps vs. Individual Graphics
    112. Navigation & Images
      • Some users with slow connections will turn off the display of images in their browser.
      • You can still make your site usable for these users by filling out the alt attribute of the <img> tag.
        • <img src='abc.gif'>
        • <img src=&quot;abc.gif&quot; alt=&quot;Products&quot;>
      Products 
    113. Better Homes and Gardens web site doesn't use the ALT attribute for their images. Since the menu in the blue bar is an image map, it is unusable for browsers with images turned off. Metropolis's site, on the other hand, does use the ALT attribute. The navigation elements are still usable here even with images turned off.
    114. Navigation: Footer
      • It is important to provide the user with text equivalents for navigational graphics (especially for image maps) since graphics turned off or the user might have might press the Stop button on their browser.
      • Common practice to place text-versions of links at bottom of pages.
    115. Navigation: Text Menus
      • Vertical series of text links
      • Try to avoid wrapping a text link over two or more lines.
        • This typically confuses users into thinking there is more than one link.
      Source: Jared Spool et al, Web Site Usability: A Designer's Guide , 1999 Wines Merlot Zinfandel Muscat Cabernet Sauvignon Nebbiolo Wines Merlot Zinfandel Muscat Cabernet Sauvignon Nebbiolo  How many wines are listed here?
      • Wines
      • Merlot
      • Zinfandel
      • Muscat
      • Cabernet Sauvignon
      • Nebbiolo
      If space is a problem, try using bullets
    116. Navigation: Text
      • Remember that most users will ignore embedded text links.
        • Because users initially scan web pages (rather than carefully read), embedded links are typically missed.
        • if it is an important link, be sure to provide an alternative to embedded links.
      This embedded link will probably be ignored. Source: Jared Spool et al, Web Site Usability: A Designer's Guide , 1999 This is still an embedded link because it is followed by text, and will probably be ignored. This is not really an embedded link . Why? because it is on a line by itself. The following text is on a separate line.
    117. Navigation: Text
      • Avoid using blue text for anything other than web links
      • Avoid underlining anything except web links
      • Avoid using red + green as link color pairs
        • Color blindness amongst 8% of males
      • Use the title attribute to provide more information about the link.
        • <a href=&quot;privacy.html&quot; title=&quot;Read our privacy policy&quot;>privacy</a>
    118. Navigation: Dynamic Menus
      • Advantages
        • Can display more choices in a single space
        • Familiar interaction (similar to desktop applications
      • Disadvantages
        • Dynamic menus from a vertical menu requires precise mouse movement (not as much as problem from a horizontal menu)
      Can be frustrating to use Not a problem to use
    119. Navigation: Tree
      • Good for site with strong hierarchical organization
        • Potentially problem with horizontal space when many nodes are opened.
    120. Navigation: Action Buttons
      • Text hyperlinks are sometimes not the best choice for representing actions that do something important.
        • Text hyperlinks should be clickable with no consequences
      • Buttons are better choice for indicating transactions
    121. Navigation: Action Buttons
      • Two types:
        • Graphical action buttons
          • An image that (hopefully) looks like a button
        • HTML buttons
          • Created via <input> tag
    122. Navigation: Pull-Down Menus
      • While a good way to save on screen space, pull-down menus force user to act to find out navigation options
      • Works best in conjunction with button bar or text links.
    123. Sun Microsystems main page uses a pull-down menu at top, with duplicate images at bottom.
    124. Navigation: Tag Clouds
      • Provides a snapshot of various categories in a site and their relative importance/frequency.
        • Each word is a link
        • Sorted alphabetically
        • Perhaps less useful for corporate sites or other sites without categories or tags
    125. Navigation: Stepping and Paging
      • Allow users to step through a linear series of pages, or move back and forth between multiple related pages.
    126. Navigation: Directories
      • Provides access to a wide variety of non-hierarchical information that can be organized via categories.
    127. Navigation: Site maps and indexes
      • A site map is a representation of a site’s structure
        • While not heavily used by users, they are an important part of SEO (search engine optimization).
      • Indexes are alphabetic guide to a site’s content.
        • Can be combined with sitemap
    128. Navigation: Site maps and indexes
    129. Page Types
      • Different page types will change the elements and organization of a page’s navigation.
      • They are:
        • Navigational
        • Content
        • Functional
      Kalbach, Designing Web Navigation (O’Reilly, 2007)
    130. Page Types: Navigational
      • Directs people to content
        • e.g., home pages, landing pages, search results, galleries
      Landing pages are like home page for a subsection of a site Many stores combine gallery views with search engine results
    131. Page Types: Content
      • For most users, this is the page they are looking for.
        • e.g., single article, product, story, blog entry, etc.
      • The focus of this page should be the content, not advertising, navigation, etc.
    132. Page Types: Functional
      • Pages that perform a function/action/task
        • e.g., search forms, submission forms, web applications.
        • Often other navigational elements are missing if it is important for the user to finish the task.
    133. Data-Entry Usability
      • The data-entry section of a web application lets users enter, save, delete, and modify data, usually stored in databases or XML files on the web server.
      Source for this and the following slides: Susan Fowler and Victor Stanwick , Web Application Design Handbook , 2004
    134. Conceptual Model: Lists versus Objects
      • Data-entry pages generally have two views for data:
        • Lists (also called tables )
        • Objects (also called records or data entry forms ).
    135. Data-Entry Forms
      • Contain:
        • Users enter information using a set of fields (also called text boxes ) and controls such as checkboxes, radio buttons, and dropdown boxes for selecting items from lists.
        • Users act on the information using buttons.
    136. Guidelines for fields
      • Use standard unprotected fields to accept unpredictable text entry (names, street addresses, and so on).
      • Use protected fields (fields into which users cannot type) to show system values, values saved elsewhere in the system, or calculated values.
      • Use required fields when you have to be sure that the form contains all necessary information.
        • Don't have too many required fields
      • Use validated fields when business rules must be ensured.
    137. Guidelines for fields
      • Make entry areas the right size
        • <input type=&quot;text&quot; name=&quot;cpt&quot; maxlength=&quot;6&quot; size=&quot;6&quot;>
      • Don't make users format the text
      • Provide keyboard and mouse navigation
        • <label for=&quot;fix&quot;>Fi<u>x</u>:</label>
        • <input type=&quot;text&quot; name=&quot;fix&quot; accesskey=&quot;x&quot;>
    138. Guidelines for labelling forms
      • Fields should be organized in columns and groups, not in one long scrollable list down the screen.
        • If there are too many fields to fit on one screen, then provide multiple screens and a method, such as tabs or pop-up windows, to move between them.
      • Labels should be close to their data fields and controls.
      • Align labels consistently, either left or right
    139. Guidelines for labelling forms
      • If you expect to internationalize your application, put the field labels above the fields, not at the left.
        • Other languages may require more space for labels
        • Right-to-left languages won't make sense if labels are to the left of the fields.
    140. Using defaults
      • Use a default whenever there is a likely one.
        • In fields, show the default entry in the field.
        • In a set of checkboxes or radio buttons, set the most likely choice
        • In a dropdown list, pick the mostly likely entry.
      If most of your customers are from North America, then why not put Canada or United States as the default value (rather than just list them alphabetically)
    141. Using Defaults
      • Set defaults so that they benefit your site's visitors, not your organization.
      Source: Jeff Johnson, Web Bloopers, 2003
    142. Indicating a required field
      • Approaches:
        • changing the background color of the required fields
        • making the labels bold,
        • putting a symbol (asterisk, arrow) in front of the field.
      • However:
        • Bold or coloured labels won't help those who use screen readers.
    143. Providing feedback for required fields
      • Approaches:
        • show an error message on a separate error page and ask people to go back to the earlier page.
        • return to the page, show the error message, and list the missing fields.
        • return to the page, show the error message, and highlight the missing fields.
        • Indicate errors as user enters data.
    144. Validated Fields
      • If a field must follow a specific format (e.g., date, postal code, credit card, etc), then:
        • Tell the user what is the expected format
        • Be as forgiving as possible
          • Why do so many sites reject credit card numbers, etc. if they contain spaces?
        • Change the form so that it avoids user formatting mistakes
      Enter Date: Enter Date (yyyy/mm/dd): Source: Jeff Johnson, Web Bloopers, 2003
    145. Other Controls
      • Use check boxes for entering binary (yes/no) data.
      • Use radio buttons for choosing an option from a small list of choices.
    146. Using Tabs
      • If form has too many fields, split them into several related tab pages.
        • Each tab page will need a way to move to the next tab page
    147. Using Tabs
      • Tab pages provide an alternate way to navigate a linear series (also called a pipeline or Wizard ).
    148. Using Popups
      • Popup windows can also be used for:
        • Collecting secondary information and settings for an object or record
        • Holding tools such as calendars, toolbars, and palettes.
        • Delivering messages, providing feedback, or showing background (non-essential) information.
        • Asking questions, confirming actions, and warning of problems
    149. Lists
      • In many sites, users generally start from lists, selecting and opening individual objects they wish to examine or change.
      • When they’re done with the objects, they close them and return to the list view.
    150. How to Select and Open Objects from Lists
      • Approaches
        • Turning field data in list into links
        • Action buttons/links within each list &quot;row&quot;
        • Images within each list &quot;row&quot;
    151. How to Select and Open Objects from Lists Field data in list is made into a link Action buttons/links within each row Action buttons/links within each row Images within each list &quot;row&quot;
    152. Concluding Caveats on Usability
      • In traditional software testing, usability scores (success at finding information) and user preferences (how much did the user like the site) are very strongly linked.
          • i.e., users almost always prefer software they find easiest to use
      • In web testing, however, usability and user preferences are not nearly as strongly linked.
        • When asked, users like the sites the provide interesting and relevant content .
        • &quot;…these results may mean that good content is so important to users that other factors are secondary.&quot;
      Source: Jared Spool et al, Web Site Usability: A Designer's Guide , 1999

    + randyconnollyrandyconnolly, 8 months ago

    custom

    941 views, 5 favs, 1 embeds more stats

    Usability for Web Development 1 Course suitable for more

    More info about this document

    © All Rights Reserved

    Go to text version

    • Total Views 941
      • 940 on SlideShare
      • 1 from embeds
    • Comments 0
    • Favorites 5
    • Downloads 38
    Most viewed embeds
    • 1 views on http://do.notuse.me

    more

    All embeds
    • 1 views on http://do.notuse.me

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories