Skip to Content

Aarron Walter

XHTML | CSS |

Categories

My Book: Building Findable Websites

Building Findable Websites: Web Standards, SEO, and Beyond
Building Findable Websites: Web Standards, SEO, and Beyond
Aarron Walter
Buy on Amazon
Book's Companion Website
Companies waste fortunes seeking a magic bullet for Search Engine Optimization. But the keys to honest, effective web findability are appropriate writing and semantic markup. Aarron Walter’s wonderfully lucid and informative book tells everything you need to know to get your web content (or your client’s) in front of as many appreciative readers as possible.

- Jeffrey Zeldman, founder, Happy Cog Studios author, Designing With Web Standards, 2nd Edition

Now playing on my computer

CNN – CNN=Politics Daily Track | Artist
cnet.com – Buzz Out Loud 857: Dumber than a robot d... Track | Artist
cnet.com – Buzz Out Loud 855: The iPhone changes ev... Track | Artist
NPR – It's All Politics November 19 2008 Track | Artist
MSNBC.com copyright 2008 – MSNBC Hardball with Chri... Track | Artist
My Playlist Feed | My Last.fm Profile

Recent Photos From Flickr

New Fireplace video walk through, Sun, 26 Oct 2008 10:02:55 -0800 View of Completed Fireplace in the living room, Sun, 26 Oct 2008 09:20:12 -0800
View of Completed Fireplace in the living room, Sun, 26 Oct 2008 09:19:59 -0800 Close up of Meredith Paramount Tile, Sun, 26 Oct 2008 09:19:47 -0800
My Flickr Photo Stream | All Photos

Home

Guest Talk on Findability at Macquarium

08 Aug . 2007

Aarron Walter, speaking at Macquarium on FindabilityI recently had the wonderful opportunity to speak to the folks at Macquarium, an award wining interactive design firm located in downtown Atlanta, GA. They do amazing work, and are cool people to boot. The title of my talk was Findability: the Common Thread, and it explored how Findability touches each step of the project lifecycle. With an audience filled with diverse talents in Information Architecture, development, design, copywriting, photography, Usability, Accessibility and project management, my goal was to provide everyone a relevant perspective on the topic and how it relates to the work they do everyday. Findability is the common thread in which all members of a professional web team share responsibility, and can ultimately help drive more traffic to a site, help people find what they were looking for once they’ve arrived, and bring them back again. The net result of an effective Findability initiative is increased ROI (title: return on investment) for the client, and a broader dissemination of their message.

Here are the slides and audio from the talk, which are also archived in the resources section.

Slides | Podcast

I’m currently working on a book for New Riders titled Building Findable Web Sites: Web Standards SEO and Beyond that, as the title suggests, looks at Findability solutions from the developer’s perspective, providing code examples, and best practices. It will be released in February of 2008.

The Power of Contrast in Design

09 May . 2007

As a kid, I was a big fan of Sesame Street. Every show ran a little skit that showed a series of people doing different things, but one was doing something very different. A little song drove home the concept, singing, “one of these kids is doing his own thing, one of these kids is not like the others“. The intended lesson kids were to learn from this is about contrast. Contrast is a powerful, and essential tool in creating designs that communicate to viewers. It tells a viewer where to look, tells them what is most and least important, and creates visual interest. Andy Rutledge has recently written a great article called Contrast and Meaning at A List Apart extolling its virtues, and explaining how you can make effective use of it to build designs that communicate better.

RSS in Plain English

08 May . 2007

In many of my classes we use RSS readers to subscribe to a number of different content sources relating to course topics. Explaining RSS to students who are completely new to the idea is sometimes tricky. Common Craft has recently published a wonderful video explanation of RSS, and how to get started consuming feeds. He doesn’t mention my favorite feed reader, though.

Watch the Video: RSS in Plain English

Deconstructing the Design Process

05 May . 2007

The fear designers experience when confronted with a blank canvas probably comes from being overwhelmed by the plethora of aesthetic and interface design decisions to be made. With too many simultaneous, difficult problems to solve in a design, it can make one freeze up, not knowing which problem to tackle first. It doesn’t help that the design process is often perceived as entirely subjective, as this can also create pressure of having to come up with unique ideas, or identify a compelling style. The perceived subjectivity of design puts the spotlight on the designer. If something is not right with the design, it’s seen as a negative reflection upon the designer personally. It all adds up to a lot of pressure that can keep you from doing your best work, or in some cases, just getting the job done.

The way to overcome the pressure is by breaking the process into smaller parts, and defining a step by step strategy that allows you to address each issue of the design separately rather than as a daunting whole. Instead of one monolithic problem, you have lots of small, more manageable problems. Breaking each problem out will also help you arrive at better design results as you will have given close consideration to all aspects of the problem.

1) What Are Your Goals?

Design is inherently connected to specific goals, which are often, but not always, business focused. Clearly define what you are trying to achieve with your design. Are you trying to increase sales of a product, establish brand credibility, or build a community? Be specific, be clear, be concise. You can not evaluate the success of a design without first knowing what your goals are. It is also not very logical to start a design without knowing what you are trying to achieve. If you do, you can bank on the results being off their mark.

2) Conceptualization, What is the Message?

The central focus of any type of design work, whether it’s architecture, print, web design, or industrial design, is the message. The goal of design is to lead the viewer to a predefined message. Always start with the question “What am I trying to say?”. Once you have established clarity on this issue, you can define how you want to say it.
The how part of the design is the concept, and concept is king. Think about the designs that you find most inspiring and memorable. Chances are that it was a strong concept that made the impact upon you.

A good concept poorly executed is better than a bad concept well executed.

- Curt Cloninger

Concepts vary broadly from overt metaphors that are immediately recognizable, to subtle allusions to design history that establish authority in the message. A concept can provide an interesting hook into your message, or simply provide needed support. Either way, defining the message and concept of your design should always be priority number one and should be completed before you start wrestling with aesthetics.

3) Define the User Experience

A list of keywords that sum up the experience users might have helps keep you focused on the big picture. You might include concrete words such as “usable”, and “intuitive”, or more abstract words such as “environmental”, and “trustworthy”. Think about what design techniques could invoke such experiences. Sticking to navigation conventions may help you build the first two experiences, while a natural color palette, photography, and classic serif typefaces may help achieve the second two. No matter how abstract your keywords might be, visual design can communicate your message.

4) List All Elements and Assign Hierarchy

Identify all of the elements that need to be included in your interface. Include the exact labels for the navigation, headings and subheadings, logos, local navigation, utility navigation, content areas (promo spaces, call outs, etc.), and anything else that needs to be included. With your detailed inventory compiled, rank each item according to importance considering your business goals. Now you are ready to position them on the page.

5) Solve the Interface With Wireframes

A wireframe is a simple drawing of a web page that focuses on optimal placement to achieve goals. It is a visualization of the above content inventory, but it does not address aesthetics at all. Don’t get caught up in color, typography, form, and shape. Stick to grayscale and simply position the elements on the page according to their importance. Do consider scale and proportion, though, as you don’t want to have less significant elements occupying an inordinate amount of space. You may want to check out Jakob Nielsen’s research on common eye paths in web pages to determine where the important elements need to be placed. Jason Santa Maria has a great article on wireframes, and shares a helpful case study of a client project.

Here’s what a wireframe might look like: Daniel Richards Home Wireframe | Daniel Richards Interior Wireframe. You can compare it to the completed design mockups: Daniel Richards Home Page | Daniel Richards Interior Page, and the final web site.

I find the wireframe process the most valuable part of the design process as it allows me to really solve the interface design issues without getting bogged down in type, color, and other aesthetic decisions. You can make significant progress fast. It’s also a great time to check in with a client to ensure that you are still addressing their needs correctly before gettings tarted with teh design mockups.

6) Isolate Aesthetic Decisions

With a solid set of wireframes, you are ready to tackle the aesthetics. Start by considering the grid system you want to use. A 12 unit grid is exceptionally flexible, allowing you to create 2 columns of 6, 3 columns of 4, or 4 columns of 3. If you have a number of different content display scenarios in your site, a flexible grid system like this can be exceptionally valuable. Define your grid unit scale in the preferences of Photoshop, Illustrator, or your favorite design software. As a quick example, if you have a 1000 pixel wide canvas, the individual grid units of a 12 column grid would be approximately 83 pixels. For more on how to use grids in your design, see the Khoi Vinh and Mark Boulton presentation on the topic at South By Southwest, or read Josef Muller’s Grid Systems in Graphic Design.

With your grid system solved, next consider the most appropriate typography. The first consideration would be what typeface best relates to the content. If your content is humorous, informal faces may work best. If your content is authoritative, a classic face like Trajan or Garamond convey tradition, and credibility. Knowing a bit about the history of typography is extremely useful in this endeavor. Consider typographic contrast as well. Rather than setting all of the type in the same face, use a complimentary pair or a family if possible (remember that font availability is still a problem on the Web, but we can use CSS font-family lists for ideal preferences). Make sure that heading, subheading, and general copy have unique treatments that effectively communicate the information hierarchy. The type and treatment of copy text needs to, of course, maintain legibility if your readers are going to stick around. When you are setting type, be sure to provide generous margins with a limited line length (around 70 words is ideal) so the content is legible, and feels comfortable to read. Daunting blocks of copy with narrow margins is a sure way to keep your audience from reading a single line.

Next, consider a color system for the design. Color has many powerful, psychological associations to be considered. The color system you choose should relate very closely to your user experience keywords, and your design concept. Also consider how your color system can help communicate information hierarchy, or tell the viewer where to look. If you use a monochromatic color system, an accent color will capture the viewer’s attention quickly, as it is clearly different from the rest. Use the accent color sparingly to draw the viewer’s attention to key elements such as the logo, navigation, or an important heading.

7) Refine

As your design builds, inevitably you will have elements that at first seemed important, but soon became superfluous. Refine the design to remove all elements that are unnecessary. If you can take away an element and the design still functions well, then the element is not needed.

8) Revisit Your Message, Goals, and Concept

Design is an iterative process (that’s part of the fun too). You make a design, evaluate it, then make changes, and repeat. A good design is one that has been distilled down to the essentials, and functions as well as it looks. When your design appears to be complete, take another look at your goals, message, and concept. Does the design do what was intended, or does it need to be realigned with the message? It’s a good idea to continually revisit the goals along the way too, to ensure you are not being seduced by discrete design decisions rather than keeping your eye on the big picture. Pin up the goals, user experience, and concept in your work space to keep them in your periphery at all times.

Conclusion

The more you can subdivide the design process into individual problems rather than facing a Mount Everest of a problem, the less you will be intimidated by starting your design. You can tackle design in a rational manor that will help ensure that your designs are more functional, more attractive, and more memorable for your viewers.

How to Convince Your Employer or Teacher to Adopt Web Standards

24 Apr . 2007

It can be a tough task trying to convince your boss that the company or department should adopt Web Standards when building projects. Change is often seen as time consuming, inconvenient, tedious, expensive, and not worth the effort. Chances are that if you are trying to make the case to follow Web Standards to your boss by arguing from the “moral high ground” by saying “it’s the right thing to do”, you are not going to have much success. If you want to make real change in the industry, you have to speak to the bottom line: Profit.

Designing with Web Standards (2nd Edition)Jeffrey Zeldman provided us with some compelling examples in his book Designing With Web Standards that can be presented to head honchos to convince them to make the change. Jeff Veen has also made a strong case that would convince most any business to get on the band wagon. Andy Budd has done a nice job of arguing the business case for Accessibility. Though all of these guys have said most of this already with precision and eloquence, here are the arguments I hope you are using to make a change in your company, school, or organization.

  • A more Accessible site is a more findable site. Search engines can better index a web site that is built to follow WCAG and/or Section 508 guidelines. Google is the biggest blind user on the Web!
  • Accessibility includes more customers, which leads to more profits. Accessibility is not just about disabilities. It’s about alternate devices for viewing a site too.
  • Target.com was sued by blind users who could not use their in-Accessible site. Do you want your business to be the subject of the next class action law suit and all of the bad PR that comes with it?
  • Using semantically meaningful markup improves Search Engine Optimization, which drives more traffic to the site, and generates more revenue
  • Using Microformats (again, semantically meaningful markup) also improves Search Engine Optimization because search engine spiders can better understand the content on the page
  • By keeping your formatting (CSS) separated from structure (XHTML), you will use less code, which make your site download faster for your users. Your external CSS files will also cache in the browser’s temporary memory so the code that handles formatting doesn’t have to download each time a page is viewed.
  • Maintenance times can be dramatically decreased by building sites without verbose nested tables, which can be a nightmare to try to modify. Changes can be made site-wide in a design by modifying one external style sheet, saving time and money.
  • Following Web Standards improves proper cross-browser display, and helps ensure that a site is forward compatible with future browsers
  • Server bandwidth fees are decreased when less code is required to download for the page to display (cached style sheets, less redundant markup)
  • If you are doing any contract work with US government agencies, your site will need to be Section 508

In my mind, the most compelling arguments relate to SEO, as every company wants to be found by new customers, regardless of your business goals. Web Standards are a huge part of achieving optimal SEO results.

None of the above arguments are new, but yet there are still so many businesses and schools that are not on board. That means either the case is not being made to them, or it’s not being made effectively. Although you may encounter opposition to your initiatives to make change, persist, and make your arguments clearly. The argument that it’s “the right thing to do” is nice, but it’s not going to get you far with those who don’t want to be convinced. Speak to how the organization will profit, and you can make a change. We each have the power to make changes in our own way, all of which add up to larger benefits for the Web. If you share in the spirit of altruism, people are generally pretty receptive to what you have to say. If we try to make changes by forcing it upon people, or condescending, people will not react well to your advice. Think from their perspective. How would you feel if someone told you you were building pages “the wrong way”? You’d probably be put off. Remember your grandma’s advice.

You catch more flies with honey than vinegar.

- Your wise ol’ grandma