Author Archive

Hex Colors: The Code Side Of Color


  

The trouble with a color’s name is that it never really is perceived as the exact same color to two different individuals — especially if they have a stake in a website’s emotional impact. Name a color, and you’re most likely to give a misleading impression. Even something like “blueâ€� is uncertain. To be more precise, it could be “sky blue”, “ocean blue”, “jeans blue” or even “arc welder blue”.

Descriptions vary with personal taste and in context with other colors. We label them “indigo”, “jade”, “olive”, “tangerine”, “scarlet” or “cabaret”. What exactly is “electric lime”? Names and precise shades vary — unless you’re a computer.

Code Demands Precision

When computers name a color, they use a so-called hexadecimal code that most humans gloss over: 24-bit colors. That is, 16,777,216 unique combinations of exactly six characters made from ten numerals and six letters — preceded by a hash mark. Like any computer language, there’s a logical system at play. Designers who understand how hex colors work can treat them as tools rather than mysteries.

Breaking Hexadecimals Into Manageable Bytes

Pixels on back-lit screens are dark until lit by combinations of red, green, and blue. Hex numbers represent these combinations with a concise code. That code is easily broken. To make sense of #970515, we need to look at its structure:

The first character # declares that this “is a hex number.� The other six are really three sets of pairs: 0–9 and a–f. Each pair controls one primary additive color.

Hex Reading
The higher the numbers are, the brighter each primary color is. In the example above, 97 overwhelms the red color, 05 the green color and 15 the blue color.

Each pair can only hold two characters, but #999999 is only medium gray. To reach colors brighter than 99 with only two characters, each of the hex numbers use letters to represent 10–16. A, B, C, D, E, and F after 0–9 makes an even 16, not unlike jacks, queens, kings and aces in cards.

Diagram showing how hex colors pass above 0-9

Being mathematical, computer-friendly codes, hex numbers are strings full of patterns. For example, because 00 is a lack of primary and ff is the primary at full strength, #000000 is black (no primaries) and #ffffff is white (all primaries). We can build on these to find additive and subtractive colors. Starting with black, change each pair to ff:

  • #000000 is black, the starting point.
  • #ff0000 stands for the brightest red.
  • #00ff00 stands for the brightest green.
  • #0000ff stands for the brightest blue.

Subtractive colors start with white, i.e. with the help of #ffffff. To find subtractive primaries, change each pair to 00:

  • #ffffff is white, the starting point.
  • #00ffff stands for the brightest cyan.
  • #ff00ff stands for the brightest magenta.
  • #ffff00 stands for the brightest yellow.

Mixing additive colors to make subtractives

Shortcuts In Hex

Hex numbers that use only three characters, such as #fae, imply that each ones place should match the sixteens place. Thus #fae expands to #ffaaee and #09b really means #0099bb. These shorthand codes provides brevity in code.

In most cases, one can read a hex number by ignoring every other character, because the difference between the sixteens place tells us more than the ones place. That is, it’s hard to see the difference between 41 and 42; easier to gauge is the difference between 41 and 51.

Diagram emphasizing the first character in each pair of characters

The example above has enough difference among its sixteens place to make the color easy to guess — lots of red, some blue, no green. This would provide us with a warm violet color. Tens in the second example (9, 9 and 8) are very similar. To judge this color, we need to examine the ones (7, 0, and 5). The closer a hex color’s sixteens places are, the more neutral (i.e. less saturated) it will be.

Make Hexadecimals Work For You

Understanding hex colors lets designers do more than impress co-workers and clients by saying, “Ah, good shade of burgundy there.� Hex colors let designers tweak colors on the fly to improve legibility, identify elements by color in stylesheets, and develop color schemes in ways most image editors can’t.

Keep Shades In Character

To brighten or darken a color, one’s inclination is often to adjust its brightness. This makes a color run the gamut from murky to brilliant, but loses its character on either end of the scale. For example, below a middle green becomes decidedly black when reduced to 20% brightness. Raised to 100%, the once-neutral green gains vibrancy.

A funny thing happens when we treat hex colors as if they were increments of ten. By adding one to each of the left-hand character of each pair, we raise a color’s brightness while lowering its saturation. This prevents shades of a given color from wandering too closely to pitch black or brilliant neon. Altering hex pairs retains the essence of a color.

Diagram showing how hex affects brightness and saturation

In the example above, the top set of shades appears to gain yellow or fall to black, even though it’s technically the same green hue. By changing its hex pairs, the second set appears to keep more natural shades.

Faded Underlines

By default, browsers underline text to denote links. But thick underlines interfere with letters’ descenders. Designers can make underlines less obtrusive by scaling back hex colors. The idea is to make the tags closer to the background color, while the text itself gains contrast against the background.

  • For dark text on a bright background, we make the links brighter.
  • For bright text on a dark background, we make the links darker.

To make this work, every embedded link needs a <span> inside of every <a>:

a { text-decoration:underline;color:#aaaaff; }

a span { text-decoration:none;color:#0000ff; }

Example of underlines that pale compared to the clickable text

As you can see here, underlines in the same color as the text can interfere with parts of type that drop below the baseline. Changing the underline to resemble the background more closely makes descenders easier to read, even though most browsers place underlines above the letterforms.

Adding spans to every anchor tag can be problematic. A popular alternative is to remove underlines and add border-bottom:

a { text-decoration: none; border-bottom: 1px solid #aaaaff; }

Better Body Copy

A recurring design problem is that a specific color may be technically correct but has an unintended effect. For example, some designs call for headers and body copy to be the same color. We have to keep in mind that the thicker the strokes of large text appears, the darker the small text appears.

Example of text that, while technically correct, appears too bright

h1, p { color: #797979; }

Example of text technically darker but visually the same

h1 { color: #797979; }

p { color: #393939; }

While technically identical, the body of the copy is narrower, and more delicate letterforms make it visually brighter than the heading. Lowering the sixteens places will make the text easier to read.

How To Warm Up Or Cool Down A Background

Neutral backgrounds may be easy to read against, but “neutral” doesn’t have to mean “bland”. Adjusting the first and last byte can make a background subtly warmer or cooler.

Examples with slight background color variations

  • #404040 — neutral
  • #504030 — warmer
  • #304050 — cooler

Is that too much? For a more subtle shift, use the ones places instead:

Examples of very slight variations in background color

  • #404040 — neutral
  • #594039 — warmer
  • #394059 — cooler

Coordinate Colors With Copy-Paste

Recognizing the structure of a hex number’s number/letter pairs gives designers a unique tool to explore color combinations. Unlike color wheels and charts, rearranging pairs in a hex number is a simple process to change hues while keeping values similar. As a bonus, the results can be unpredictable. The simplest technique is to move one pair of characters to a different spot, which trades primary colors.

A common design technique to make text or other visual elements coordinate with a photo is to use colors from within that photo. Understanding hex colors can take that a step further, by deriving new colors that coordinate with the photo without taking directly from the photo.

Examples of how swapping primary colors can yield coordinated but interesting results

Going Forward

Don’t let the code intimidate you. With a little creativity, hex colors are a tool at your disposal. If nothing else, next time someone asks if you can solve a problem with code in any language, you can simply say:

“Shouldn’t be harder than parsing hexadecimal triplets in my head.”

Further Reading

You may be interested in the following articles and related resources:

(il)


© Ben Gremillion for Smashing Magazine, 2012.


Adopting A Responsive WordPress Theme Is More Than Install-And-Go


  

As iOS, Android, and Windows 8 take the Web to smaller screens, designers are adopting techniques to make their websites usable on handheld devices.

Responsive Web designs present different formatting and layout to suit the device on which their pages are displayed. Browsers choose the appropriate styles on page load, freeing website owners from having to maintain different sets of pages for different display scenarios.

Adopting A Responsive WordPress Theme Is More Than Install-And-Go

The most common responsive method is to use CSS media queries to serve different style sheets (or parts of style sheets) based on the number of pixels available. Most often, this is applied to handheld devices such as smartphones, but it could be applied to 13-inch laptops, 30-inch TVs or Kindle-sized readers. Responsive designs respond to their environment.

No Shortage Of Quick Fixes

The term “responsive design� is only two years old, but website owners can choose today from many mobile and widescreen themes for popular content management systems. Third-party developers have created paid and free themes that adapt based on browser width for WordPress, Drupal, Joomla and ExpressionEngine. At the time of this writing there are:

Designers handy with CSS can also find a few do-it-yourself frameworks. But responsive themes are as varied as the problems they are meant to solve. Not all are created with the same technique, features or attention to detail. Aesthetics aside, how should someone choose a theme?

How Do Responsive Themes Perform?

The more files a theme requires, the more time a server must dedicate to retrieving those files. While milliseconds add up to a slower server, kilobytes are the user’s problem. Especially on mobile, where surfing via cell networks costs money, fewer kilobytes make for a better theme.

Aside from using media queries, many themes use variations of techniques to respond to browsers. I’ve tested 40 responsive themes on WordPress.com, comparing them to the stock Twenty Eleven and Twenty Ten themes.

Chart comparing kilobytes to files used for responsive themes.
The weight of each theme and supporting files in kilobytes.

The chart above shows that:

  • The number of files that a theme loads and the theme’s weight in kilobytes have no direct relationship;
  • With few exceptions, most themes make 25 requests or fewer;
  • WordPress’ stock themes perform very well, but a few other themes provide responsive capability and better performance.

Bear in mind that these are empty themes, measured before any content or modifications have increased their load. Because data costs money for people who are accessing the Web through cellular networks, themes that require fewer downloads per page load are more likely to earn repeat visits. Of the themes sampled:

  • Only one theme did not use CSS media queries. This theme’s unusual method was to detect page width with jQuery and then change the body class, which in turn would change the layout with animated transitions. The extra time taken to load and implement JavaScript compromised the goal of responsiveness.
  • More than half had three break points: mobile (480 pixels or less), medium (481 to 1024 pixels) and wide (1025 pixels or more). The medium-sized layouts were most often measured with percentages, ems or min- and max-width, rather than strictly by number of pixels.
  • Left-to-right layouts on wide screens always became top-to-bottom layouts on mobile. That is, the left-most column in a widescreen layout would always appear at the top of the page in a mobile layout, regardless of its width or the type of content. Likewise, right-hand columns would become footers in mobile layouts. This means that the content in your left-most column should not discourage users from scrolling down when it’s formatted for mobile devices.
  • All mobile designs had 10 to 20 pixels of horizontal margin. None deliberately allowed horizontal scrolling or used app-simulating frameworks such as jQuery Mobile.
  • None provided in-page navigation.
  • Two themes used select lists for navigation in their mobile layouts. None used multi-level navigation.
  • Loading a page with three paragraphs of placeholder text, the themes averaged 306.57 KB per page load and 25.4 resources retrieved (including images, CSS files, JavaScript files and the like).
  • The lightest theme weighed only 57.11 KB before the content itself (text and images) loaded. The largest weighed 1382.4 KB before the content loaded.

Remember that screen width does not necessarily equal browser width. Most themes are not built on the assumption that users will have their browser windows open as big as possible; rather, their layouts are designed for screen widths well under common sizes.

Chart comparing common screen sizes to frequently-used web layouts.
Most themes are well under the most common screen widths. The wider the screen, the less likely a user will expand their browser to fill it.

As seen in the graph above, most themes will use max-width media queries to resize layouts when browsers reach 1280, 800, 767 and 480 pixels wide. But most screens surveyed by Lifehacker, StatCounter and W3 Counter start at 1280 pixels wide.

Picking A Theme That Reflects Your Priorities

Making a website responsive is more than about varying the number of columns on a page. The same critical questions emerge for all mobile-friendly websites, regardless of CMS.

  • Does the project merit a mobile layout?
    Increasingly, the answer is yes. But the march towards mobile doesn’t mean that every website should follow suit. Pages that contain complicated tables, multi-month calendars, detailed images, complex navigation and other content unsuitable for small screens could negate any benefit offered by responsive designs. “Can I?� and “should I?� are two different questions.
  • Would the website benefit from mobile-first thinking?
    Designing a website to be mobile forces the content editors to answer hard questions. A screen measuring 320 pixels wide has no room for excess. This brings the design into focus, forcing you to eliminate distractions from whatever the website is meant to convey.
  • How many steps do we need?
    Responsively designed websites often rely on the width of the device on which they’re being viewed. But there’s more to it than asking “Mobile or not?� Responsive designs must address not only how a website handles on narrow screens, but also when wide becomes too wide. But a better option would be to consider using a device-agnostic approach to Web design focusing on content rather than device properties.
  • How do the layout and formatting change?
    Deciding which elements on a given page users should see first, second and third will affect how the widescreen layout functions. For example, the font in headings in the widescreen layouts could be three, four or five times larger than the body copy, whereas giant headings are cumbersome on tiny screens.
  • What should a mobile page not show?
    Multiple columns encourage a hierarchy of information: primary content that is unique to each page, and secondary content (often relegated to sidebars) that appears on more than one page. But mobile design makes multiple columns difficult to pull off. If the secondary content is unnecessary, how should it disappear? If it’s important, how does one design it without letting pages run longer than users are willing to scroll? (A good rule of thumb is that if an element does not support the page’s title, then it is not primary content.)

Think Beyond The Theme

Having a responsive theme does not guarantee a good mobile user experience.

Designing for mobile is not just about cutting material, but also about planning for limited attention. By nature of the medium, mobile users absorb information in limited chunks. Long pages can work if they’re divided into phone screen-sized sections. Unlike widescreen users, mobile users are more inclined to scroll down “below the fold� (i.e. below what they first see when the page loads).

Consider higher-contrast colors for mobile — particularly, the contrast between the body text and the background — for improved legibility outdoors.

Extensive navigation bars with sublevels and sub-sublevels are impractical on mobile devices. Offering search functionality, creating pages dedicated to navigation, and flattening the website’s structure are common solutions; anything that reduces the number of taps between pages helps.

When To Consider A Separate Mobile Website

Responsive designs do more than make a website work well on a variety of screen sizes; they also force the owner to make their website easier, more focused and faster. But they’re a tool, not a requirement. Adaptive layouts and media queries aren’t always the best answer for mobile design problems. When big content simply doesn’t fit on small screens, maintaining a supplemental website would outweigh the benefit of having one website that serves many audiences. The key is to create a companion website that carries essential information organized for mobile use — and then find out what mobile users are missing.

Your website could warrant a separate mobile version if:

  • You find yourself creating duplicate pages for mobile users on the same website;
  • Short pages that look great on mobile phones don’t take advantage of large screens;
  • You plan to phase out the widescreen layout in favor of a more streamlined user experience.

Other Resources

You may be interested in the following articles and related resources:

  • Mobile First, Luke Wroblewski
    This book by the former Yahoo designer discusses the reasons why thinking small from the start makes more sense than cramming later.
  • “Supporting Multiple Screens,â€� Android Developers
    Google’s overview of screen sizes, pixel density, and how (and why) to achieve density dependence.
  • “Platform Characteristics,â€� iOS Developer Library
    Apple’s guidelines on graphics and presentation for apps and Web content for iOS.
  • “Responsive Web Design,â€� Ethan Marcotte
    This article examines the benefits of, and the mental shift required for, Web designs that respond to the user’s browser.
  • “Chrome Developer Tools: Network Panel,â€� Google Developers
    Shows how to activate and use the inspector in Chrome. It also works for most Webkit-based browsers.
  • “Screen Resolution ≠ Browser Window,â€� Chris Coyier
    An explanation of how screen width is a deceptive metric, and what you can do about it.
  • jQuery Mobile
    A framework that simulates app behaviors with JavaScript, CSS and HTML5.
  • Less Framework
    A straightforward desktop-to-mobile CSS grid, with four specific steps.
  • Whiteboard Framework for WordPress
    A barebones theme that serves as a starting point for design, rather than a finished product to be tweaked.
  • Omega, Drupal theme
    “The Omega Drupal 7 base theme is a highly configurable HTML5/960 grid base theme that is 100% configurable.�

(al) (jc)


© Ben Gremillion for Smashing Magazine, 2012.


Adopting A Responsive WordPress Theme Is More Than Install-And-Go


  

As iOS, Android, and Windows 8 take the Web to smaller screens, designers are adopting techniques to make their websites usable on handheld devices.

Responsive Web designs present different formatting and layout to suit the device on which their pages are displayed. Browsers choose the appropriate styles on page load, freeing website owners from having to maintain different sets of pages for different display scenarios.

Adopting A Responsive WordPress Theme Is More Than Install-And-Go

The most common responsive method is to use CSS media queries to serve different style sheets (or parts of style sheets) based on the number of pixels available. Most often, this is applied to handheld devices such as smartphones, but it could be applied to 13-inch laptops, 30-inch TVs or Kindle-sized readers. Responsive designs respond to their environment.

No Shortage Of Quick Fixes

The term “responsive design� is only two years old, but website owners can choose today from many mobile and widescreen themes for popular content management systems. Third-party developers have created paid and free themes that adapt based on browser width for WordPress, Drupal, Joomla and ExpressionEngine. At the time of this writing there are:

Designers handy with CSS can also find a few do-it-yourself frameworks. But responsive themes are as varied as the problems they are meant to solve. Not all are created with the same technique, features or attention to detail. Aesthetics aside, how should someone choose a theme?

How Do Responsive Themes Perform?

The more files a theme requires, the more time a server must dedicate to retrieving those files. While milliseconds add up to a slower server, kilobytes are the user’s problem. Especially on mobile, where surfing via cell networks costs money, fewer kilobytes make for a better theme.

Aside from using media queries, many themes use variations of techniques to respond to browsers. I’ve tested 40 responsive themes on WordPress.com, comparing them to the stock Twenty Eleven and Twenty Ten themes.

Chart comparing kilobytes to files used for responsive themes.
The weight of each theme and supporting files in kilobytes.

The chart above shows that:

  • The number of files that a theme loads and the theme’s weight in kilobytes have no direct relationship;
  • With few exceptions, most themes make 25 requests or fewer;
  • WordPress’ stock themes perform very well, but a few other themes provide responsive capability and better performance.

Bear in mind that these are empty themes, measured before any content or modifications have increased their load. Because data costs money for people who are accessing the Web through cellular networks, themes that require fewer downloads per page load are more likely to earn repeat visits. Of the themes sampled:

  • Only one theme did not use CSS media queries. This theme’s unusual method was to detect page width with jQuery and then change the body class, which in turn would change the layout with animated transitions. The extra time taken to load and implement JavaScript compromised the goal of responsiveness.
  • More than half had three break points: mobile (480 pixels or less), medium (481 to 1024 pixels) and wide (1025 pixels or more). The medium-sized layouts were most often measured with percentages, ems or min- and max-width, rather than strictly by number of pixels.
  • Left-to-right layouts on wide screens always became top-to-bottom layouts on mobile. That is, the left-most column in a widescreen layout would always appear at the top of the page in a mobile layout, regardless of its width or the type of content. Likewise, right-hand columns would become footers in mobile layouts. This means that the content in your left-most column should not discourage users from scrolling down when it’s formatted for mobile devices.
  • All mobile designs had 10 to 20 pixels of horizontal margin. None deliberately allowed horizontal scrolling or used app-simulating frameworks such as jQuery Mobile.
  • None provided in-page navigation.
  • Two themes used select lists for navigation in their mobile layouts. None used multi-level navigation.
  • Loading a page with three paragraphs of placeholder text, the themes averaged 306.57 KB per page load and 25.4 resources retrieved (including images, CSS files, JavaScript files and the like).
  • The lightest theme weighed only 57.11 KB before the content itself (text and images) loaded. The largest weighed 1382.4 KB before the content loaded.

Remember that screen width does not necessarily equal browser width. Most themes are not built on the assumption that users will have their browser windows open as big as possible; rather, their layouts are designed for screen widths well under common sizes.

Chart comparing common screen sizes to frequently-used web layouts.
Most themes are well under the most common screen widths. The wider the screen, the less likely a user will expand their browser to fill it.

As seen in the graph above, most themes will use max-width media queries to resize layouts when browsers reach 1280, 800, 767 and 480 pixels wide. But most screens surveyed by Lifehacker, StatCounter and W3 Counter start at 1280 pixels wide.

Picking A Theme That Reflects Your Priorities

Making a website responsive is more than about varying the number of columns on a page. The same critical questions emerge for all mobile-friendly websites, regardless of CMS.

  • Does the project merit a mobile layout?
    Increasingly, the answer is yes. But the march towards mobile doesn’t mean that every website should follow suit. Pages that contain complicated tables, multi-month calendars, detailed images, complex navigation and other content unsuitable for small screens could negate any benefit offered by responsive designs. “Can I?� and “should I?� are two different questions.
  • Would the website benefit from mobile-first thinking?
    Designing a website to be mobile forces the content editors to answer hard questions. A screen measuring 320 pixels wide has no room for excess. This brings the design into focus, forcing you to eliminate distractions from whatever the website is meant to convey.
  • How many steps do we need?
    Responsively designed websites often rely on the width of the device on which they’re being viewed. But there’s more to it than asking “Mobile or not?� Responsive designs must address not only how a website handles on narrow screens, but also when wide becomes too wide. But a better option would be to consider using a device-agnostic approach to Web design focusing on content rather than device properties.
  • How do the layout and formatting change?
    Deciding which elements on a given page users should see first, second and third will affect how the widescreen layout functions. For example, the font in headings in the widescreen layouts could be three, four or five times larger than the body copy, whereas giant headings are cumbersome on tiny screens.
  • What should a mobile page not show?
    Multiple columns encourage a hierarchy of information: primary content that is unique to each page, and secondary content (often relegated to sidebars) that appears on more than one page. But mobile design makes multiple columns difficult to pull off. If the secondary content is unnecessary, how should it disappear? If it’s important, how does one design it without letting pages run longer than users are willing to scroll? (A good rule of thumb is that if an element does not support the page’s title, then it is not primary content.)

Think Beyond The Theme

Having a responsive theme does not guarantee a good mobile user experience.

Designing for mobile is not just about cutting material, but also about planning for limited attention. By nature of the medium, mobile users absorb information in limited chunks. Long pages can work if they’re divided into phone screen-sized sections. Unlike widescreen users, mobile users are more inclined to scroll down “below the fold� (i.e. below what they first see when the page loads).

Consider higher-contrast colors for mobile — particularly, the contrast between the body text and the background — for improved legibility outdoors.

Extensive navigation bars with sublevels and sub-sublevels are impractical on mobile devices. Offering search functionality, creating pages dedicated to navigation, and flattening the website’s structure are common solutions; anything that reduces the number of taps between pages helps.

When To Consider A Separate Mobile Website

Responsive designs do more than make a website work well on a variety of screen sizes; they also force the owner to make their website easier, more focused and faster. But they’re a tool, not a requirement. Adaptive layouts and media queries aren’t always the best answer for mobile design problems. When big content simply doesn’t fit on small screens, maintaining a supplemental website would outweigh the benefit of having one website that serves many audiences. The key is to create a companion website that carries essential information organized for mobile use — and then find out what mobile users are missing.

Your website could warrant a separate mobile version if:

  • You find yourself creating duplicate pages for mobile users on the same website;
  • Short pages that look great on mobile phones don’t take advantage of large screens;
  • You plan to phase out the widescreen layout in favor of a more streamlined user experience.

Other Resources

You may be interested in the following articles and related resources:

  • Mobile First, Luke Wroblewski
    This book by the former Yahoo designer discusses the reasons why thinking small from the start makes more sense than cramming later.
  • “Supporting Multiple Screens,â€� Android Developers
    Google’s overview of screen sizes, pixel density, and how (and why) to achieve density dependence.
  • “Platform Characteristics,â€� iOS Developer Library
    Apple’s guidelines on graphics and presentation for apps and Web content for iOS.
  • “Responsive Web Design,â€� Ethan Marcotte
    This article examines the benefits of, and the mental shift required for, Web designs that respond to the user’s browser.
  • “Chrome Developer Tools: Network Panel,â€� Google Developers
    Shows how to activate and use the inspector in Chrome. It also works for most Webkit-based browsers.
  • “Screen Resolution ≠ Browser Window,â€� Chris Coyier
    An explanation of how screen width is a deceptive metric, and what you can do about it.
  • jQuery Mobile
    A framework that simulates app behaviors with JavaScript, CSS and HTML5.
  • Less Framework
    A straightforward desktop-to-mobile CSS grid, with four specific steps.
  • Whiteboard Framework for WordPress
    A barebones theme that serves as a starting point for design, rather than a finished product to be tweaked.
  • Omega, Drupal theme
    “The Omega Drupal 7 base theme is a highly configurable HTML5/960 grid base theme that is 100% configurable.�

(al) (jc)


© Ben Gremillion for Smashing Magazine, 2012.


Test Usability By Embracing Other Viewpoints

Smashing-magazine-advertisement in Test Usability By Embracing Other ViewpointsSpacer in Test Usability By Embracing Other Viewpoints
 in Test Usability By Embracing Other Viewpoints  in Test Usability By Embracing Other Viewpoints  in Test Usability By Embracing Other Viewpoints

As Web technology improves, users expect Web-based widgets to be useful, content to be relevant and interfaces to be snappy. They want to feel confident navigating a website and using its functionality. They crave being able to get things done with little friction and on demand. And demand they do.

People are picky. When a website gives them problems, they are less inclined to use it. From a design perspective, testing for a good user experience entails making improvements based as much on critical feedback as on design expertise. As long as your website is around, offering a good user experience is critical. And like the website itself, improving the user experience doesn’t end when the website launches.

A good user experience leaves people with a sense of accomplishment.

User-testing-lifecycle in Test Usability By Embracing Other Viewpoints
Unlike certain other phases of production, testing for user experience is an ongoing process.

Developing a website or app often takes up several phases. These include discovery, design, implementation, internal testing, soft launch and delivery. But unlike the development phases, user testing is ongoing. Certain questions will arise at any time:

  • Does this solve a problem or serve a purpose?
  • Is it easy to use?
  • Is it meaningful?
  • Is it useful?
  • Is it clear?

These questions are relevant when the concept is being refined, half-way through development and six months after launch… in fact, they never stop being relevant.

[Offtopic: by the way, did you know that there is a Smashing eBook Series? Book #1 is Professional Web Design, 242 pages for just $9,90.]

Regular Upkeep And Rigorous Pruning

If a website is to serve its visitors well, then the people who maintain it must address the problem of relevance. Relevant content answers questions that people have right now. But technology advances, events come and go and people’s needs change over time. The information that a website launches with may not be as useful to users six months later.

Regular content audits—asking how well each piece of the website’s information benefits the users—ensures that when visitors come, their trip is worth the effort. To do this, a website manager should ensure that every piece of content addresses these questions:

  • How does it benefit or persuade the end user?
  • How does it support the website’s purpose or agenda?
  • Is it easy to find?

If content might be useful, then it also might be unnecessary. Here are other questions to ask about whether a piece of content deserves a place on the website at all:

  • Who would miss it if we removed it?
  • Could it be combined with something similar?
  • How often do people who don’t visit the website ask about this?

For example, if a website’s “About usâ€� page is only a paragraph long, it might be better served on the home page—unless it could be expanded with meaningful information about company history, staff biographies or contact details. Likewise, a website about, say, soy milk products may not require information about the inhumane treatment of cows—unless the website’s goal was more to promote a viewpoint than to sell soy milk.

Whether content belongs on a website is determined by the website’s purpose. If something doesn’t quite fit, then the website won’t quite work.

Ask “What If� Of Unlikely Scenarios

Sometimes the hardest part about questioning one’s assumptions is determining what those assumptions are. Learning to consider the pros and cons of silly, risky or impractical changes is a creative way to shake up established methods and discover potentially better ideas.

User-testing-change-methods in Test Usability By Embracing Other Viewpoints
Traditional methods of updating content include adding, removing, rearranging and recasting information.

While conventional thinking leads a designer to experiment with, say, the background color, an unlikely “What if� question considers the nature of the background itself. What if the website had more than one background? Would one act as a mid-ground, floating above the very back? Would the background change as visitors wandered through the website?

When you’ve finished asking the obvious, try the unlikely:

  • What if the website’s “Aboutâ€� page became its home page?
  • What if we turned the website’s sidebar into a footer?
  • What if we organized all content with tags instead of in a hierarchy?
  • What if we swapped the colors of the heading and background?
  • What if the contact form was a puzzle that visitors had to solve?
  • What if products were arranged with the least popular at the top?
  • What if we disabled the CSS and images one day per week?

Impractical? Perhaps not. Enlightening? Perhaps. Playing “What if� is about questioning the rules that govern a website’s design. Is there a better way to arrange the information? How else could the content be presented? Is this design really clear enough?

Undertaking to improve the user experience is an admission that the current design has problems. If the problems are unclear or user complaints are vague, then exploring radical changes may force designers to question their initial assumptions. If nothing else, then it’s an exercise in creativity. If it ain’t broke, break a copy.

Case in point: when one business owner in particular wanted to sell products online, the initial website design filled the center of the home page with clickable product categories. This didn’t suit the owner, whose business name was well known in the field. The proposed solution moved categories to a thin left-hand column and put business information, customer registration and contract details in the center.

A week after launch, a long-time customer asked when the website would have products. The categories seemed to have gone unnoticed by an indefinite number of visitors. Fortunately, one decided to speak up.

Interface-problem in Test Usability By Embracing Other Viewpoints
The original design put product categories (the white bars) in the center. The client wanted more emphasis on information about their company (black bars). When customers complained, the client requested an arrow pointing to categories on the left.

This problem could have been prevented if the people involved had put higher priority on the user experience. No further user testing was done. To date, it is unknown how many customers, if any, are still having trouble with the website.

Keep Content In (Other People’s) Perspective

Clever designer don’t attempt to answer these questions themselves. Rather, they ask two types of people: those who use the website often and those who use it casually.

Website designers often begin with certain goals about how a website’s interface and content should be used. Interfaces are designed around particular problems: how do I make it easy for people to navigate or manipulate data? This is natural because many design processes are intended to solve problems in communication.

But visitors will approach the same design from another angle. Given an interface, they ask: how do I use this to get what I want?

To learn how visitors use a website, designers must observe without interference. The designer’s goal isn’t to teach someone how to use a website, but rather to learn how people might interpret its interface.

Once visitors start teaching the designer (pointing out how they accomplish a task, or clicking from page to page), insights emerge about what’s easy and what’s relevant to the people whom the website serves.

Other Points Of View Benefit Everyone

Designers must understand that the refrain “You’re doing it wrongâ€� isn’t always true. Even if someone uses a website the hard way, they’re doing so for a reason. Maybe the easier path isn’t clear to them. Maybe they’re less comfortable with the easier way than what they’re accustomed to. Maybe the hard way has an advantage that the designer hasn’t thought of.

Wrong or right, a user’s view deserves respect for two reasons. First, designs that serve the designer’s ego at the expense of user needs have failed both. Secondly, a great interface today will be average next year. Striving for a good user experience helps designers not just to stay current but to continually improve their work.

A good user experience is reliable, useful, responsive and unambiguous—to the people who use the website. Although users may not follow the anticipated method of accomplishing a defined task, their solution is based on what makes sense to them.

Designers who seek other points of view may find ways to make a website easier for visitors to find the information they want. The better the user experience, the more willingly users will return.

Not Every Perspective Leads To Improvement

Of course, not every viewpoint is always relevant. Sometimes crazy ideas lead to improvements, and sometimes they’re just crazy. Most design conventions exist because they’re genuinely useful, convenient or familiar to designers and users alike.

Seeking to understanding other points of view doesn’t mean trying to keep everyone happy. It means asking if there’s a better way to meet user needs. Catering to every possible view is a recipe for failure. In the end, the website’s owner is responsible for deciding how best to serve their audience.

User-testing-possible-layouts in Test Usability By Embracing Other Viewpoints
Which layout is best? It’s the designer’s call, not the audience’s.

Tips For Testing

  • Ask specific questions.
    “What would you improve?� is helpful only if the user already has gripes. “How would you find (certain information)?� gives users something to focus on.
  • Encourage feedback.
    Incentives for completing a survey, for example, compensate visitors for their input.
  • Ask the “wrongâ€� people.
    If one assumes that only a certain type of person will use a website, then they might only get the feedback they expect. But if one gets feedback from someone with no experience in the website’s subject matter, they might get a fresh point of view.
  • Keep testing.
    Websites and people change over time. If possible, seek new input and review the website’s content every other month.
  • Track visitors.
    Software that records who visits what, such as Google Analytics and Mint, tells you what people are after and what’s easy (and hard) to find.
  • Allow time for changes.
    Feedback may show oversights in the website’s design or structure. Deadline pressure is bad enough without the realization that your initial assumptions have led to problems at the last minute.

Tools For Testing

Do you really know your project? See it from other points of view with these online resources.

  • Color can prevent people from viewing a layout objectively. Check your websites with Graybit.
  • Do you need to check your websites in different versions of Internet Explorer? Regardless of your browser, review your websites in IE 6, 7 and 8 with IE NetRenderer.
  • What exactly are your users looking at? Collect live observations of their experience with Morae and Silverback.
  • How does your website sound to screen readers? Try the University of Washington’s WebAnywhere non-visual interface.
  • Which elements do people see in their first five seconds on your website? Learn more at Five Second Test.
  • Does your website load quickly for people with slow connections? Use the LinkVendor Speed Check or the Aptivate Low Bandwidth Simulator to find out.

Further Reading

How do you test for a good user experience? How far, if at all, should designers go to find other points of view? Share your thoughts in the comments below.

(al)


© Ben Gremillion for Smashing Magazine, 2010. | Permalink | Post a comment | Add to del.icio.us | Digg this | Stumble on StumbleUpon! | Tweet it! | Submit to Reddit | Forum Smashing Magazine
Post tags:


Passing The Holy Milestone: How To Meet Deadlines

Smashing-magazine-advertisement in Passing The Holy Milestone: How To Meet DeadlinesSpacer in Passing The Holy Milestone: How To Meet Deadlines
 in Passing The Holy Milestone: How To Meet Deadlines  in Passing The Holy Milestone: How To Meet Deadlines  in Passing The Holy Milestone: How To Meet Deadlines

For too many projects, there comes a time when every action taken, every decision and sacrifice made, is spurred on by pressure to finish. Tempers seem to shrink along with the available days, talk about “high standards� gives way to “good enough,� and people realize that deadlines are aptly named. During the last-minute crunch, someone may well wonder, how did it come to this? Could it have been prevented? Every Web project has deadlines. But not every designer or developer deals with them the same way.

[By the way, did you know we have a free Email Newsletter? Subscribe now and get fresh short tips and tricks in your inbox!]

What Causes A Deadline To Break?

Because a deadline marks the end of a project, everyone involved in the project must understand the deadline’s role. Most projects follow a schedule or have an estimated date by which they must be completed. The concept is simple then: when the work takes longer than expected, deadlines get missed.

Deadline-extends-past-estimate in Passing The Holy Milestone: How To Meet Deadlines
A deadline is the end point of a time estimate, making it a known quantity. But how long will the work actually take to get done?

Of course, projects can be more complicated in their details. Unexpected technical problems and unanticipated changes will affect the amount of work required. Sometimes other tasks take priority. Sometimes the time estimate wasn’t considered carefully enough.

Whatever the cause, too much work needs to be done in the available time. That’s the problem, but not the challenge.

Rate Deadlines By Severity Of Consequences

The hardest deadlines are tied to events that cannot be moved, such as a date promised to the public, an upcoming trade show or a date stipulated in a contract. Retailers know that their holiday sales must end at Christmas, and theater owners can expect movie-goers to be upset if a 1:00 pm showing doesn’t start until 2:00. Likewise, if a website is tied to a time-sensitive event, its relevance is lost once the event has passed. Hard deadlines have clear consequences when missed.

Deadlines-magnify-trouble in Passing The Holy Milestone: How To Meet Deadlines
Deadlines exist for a reason. The severity of the trouble caused by missing them increases dramatically after they have passed.

Deadlines tied to less public events are no less real, but a project will soldier on if the deadline slips. Company-imposed target dates, for example, rely less on public demand than on the temperament of managers. Meetings routinely start 10 minutes late because “something came up.�

The softest deadlines lack teeth or are set at some vague point in the future. That’s not always bad: not every missed deadline will cause a life-or-death crisis. But the same methods of solving the crisis apply. There are many strategies for handling a last-minute crisis. Most involve planning, setting priorities and knowing one’s limits.

Strategies For Preventing Deadline Crises

The beginning of a project is a great time to prevent problems later on.

The first solution is both obvious and difficult: do not take on a project that cannot be completed in the given time. Declining paid work requires discipline and confidence, but if the deadline is impossible, then the project may not be worth the money. Money cannot replace time.

Because deadlines with consequences are taken more seriously, keep a written list of definitive reasons why certain tasks must be completed by a given date. Losing money, customers and other assets create real incentives to work.

Schedule deadlines as specific tasks, not the ends of phases. Rather than “Content will be completed by 4 April 2010,� state “Review the content over lunch on 4 April 2010.� This ties the deadline to an event at which results must be shown. Mini-deadlines tied to specific events are more powerful than general statements.

Schedule-review-time in Passing The Holy Milestone: How To Meet Deadlines
Making up for minor time discrepancies during the course of a project is easier than facing a big shortfall when no time is left.

Plan For Unpleasant Surprises

Incentive may not be the problem, though. Unexpected problems cause many people to break deadlines. Their unpredictability make these problems hard to plan for, and good intentions don’t help you see the future. The key is to recognize that, whatever their nature, problems will likely occur.

If everything seems accounted for in the project plan, then invent a problem. Keep it realistic: “reshoot staff photos� is more likely than “spontaneous server combustion,� but it doesn’t really matter. The point is to create extra time to allow for a deadline crisis. One rule of thumb is to add between half and all of a project’s expected duration. That is, increase the full time that has been budgeted by between 50 to 100% to allow for surprises.

A plan of time estimates for major tasks in a project could look something like this:

Task:Time allotted:
Content audit15 hours
Develop content strategy15 hours
Make WordPress theme changes20 hours
Import data from old website15 hours
Test on multiple browsers5 hours
Total70 hours

Being conservative, let’s take half of 70, which is 35. Now we invent a problem: say, having to retype all content from print-outs. Is 35 hours for that ridiculous? Perhaps. But obstacles are unexpected by nature, and they always steal time from an otherwise ideal budget.

Add-time-to-the-estimate in Passing The Holy Milestone: How To Meet Deadlines
Scheduling for unknowns is hard, but acknowledging that extra time is required will better align estimates with reality.

A line item needs to be added to the budget. It could be “Time to make changes� or “Allowance for unknowns.� The description isn’t as important as the fact that you have planned for surprises.

Is half of the original budget too much? It may drive cheaper clients away, but overestimating and finishing under the deadline is better than the alternative.

Mitigate A Deadline’s Threat By Adding Other Deadlines

Implement mini-deadlines within a project’s timeline. Mini-deadlines minimize last-minute problems by serving as checkpoints to gauge how far off track the schedule is, if at all, at certain phases.

  1. Start
    While the project is fresh in everyone’s mind, a schedule for the other phases should be set.
  2. First quarter
    Everyone involved should have a sense of whether they can work together. Work begins, and the pristine project on paper comes up against the sticky details of reality.
  3. Halfway point
    The bulk of the work happens here. If you doubled your estimate to account for surprises, you would actually be aiming to launch the project right now.
  4. Third quarter
    If everyone pushed to launch by the halfway point, then almost everything should be done by now. But it rarely is.
  5. Deadline
    Launch the project.
  6. Review
    Win or lose, everyone should ask what should have happened at each phase of the project? What should have been done to meet each mini-deadline along the way?

Notice that mini-deadlines are based on time, not task. Tasks have a way of expanding, of taking up more time than planned, which mini-deadlines should prevent. Think of a mini-deadline as a chance to review the project’s timeline. While this approach may not entirely stave off a deadline crisis, it gives you opportunities to catch and correct problems along the way.

Plan Sacrifices In Advance

Every project has absolute requirements, which are essentially the reasons the project exists at all or the problems it is designed to solve. But many also have supplemental requirements. If a project requires A, B and C, then by all means include D, E and F, but only with the understanding that they might have to wait.

For example, a newsletter is an important marketing tool for an e-commerce website, but less important than an easy-to-use cart and secure log-in page. Likewise, the top priority for a photo gallery should be to present photos. If the deadline is looming and the AJAX is buggy, then perhaps the blog should wait.

Marking certain features as secondary provides relief when things go wrong. These features don’t need to be cut, but their deadlines should be later than those of the core project.

Practice

Measure the rate at which you work by timing how long you take to perform various tasks. You want to figure out how much time you need to comfortably perform each task, not how fast you can get it done.

For example, the schedule might allow for 30 minutes to create a favicon. But in reality, it consumes 8 hours.

Wait a minute. Eight hours for a measly 16×16-pixel graphic? Isn’t that… excessive?

That’s not the point. You’re not learning the rate at which you work so that you can gasp in embarrassment at the result. Workflow efficiency can be improved later. The question is, how much time are you comfortable with right now? In this case, it’s 8 hours.

Deadlines aren’t the problem. Problems arise when the work outweighs the allotted time. Learning how long you take to accomplish certain tasks is the best way to set a realistic schedule.

Conclusion

Not every deadline drama can be prevented, but even the worst can be dealt with professionally. Prepare for surprises, break up large tasks into manageable segments and prioritize. It’s a matter of respect: deadlines mean business. Do you?

How do you prevent deadline emergencies? What’s the worst problem you’ve faced under time pressure? What’s your greatest solution? Share your story in the comments below.

(al)


© Ben Gremillion for Smashing Magazine, 2010. | Permalink | Post a comment | Add to del.icio.us | Digg this | Stumble on StumbleUpon! | Tweet it! | Submit to Reddit | Forum Smashing Magazine
Post tags: , ,


  •   
  • Copyright © 1996-2010 BlogmyQuery - BMQ. All rights reserved.
    iDream theme by Templates Next | Powered by WordPress