- •Taking Your Talent to the Web
- •Introduction
- •1 Splash Screen
- •Meet the Medium
- •Expanding Horizons
- •Working the Net…Without a Net
- •Smash Your Altars
- •Breath Mint? Or Candy Mint?
- •Where’s the Map?
- •Mars and Venus
- •Web Physics: Action and Interaction
- •Different Purposes, Different Methodologies
- •Web Agnosticism
- •Point #1: The Web Is Platform-Agnostic
- •Point #2: The Web Is Device-Independent
- •The 18-Month Pregnancy
- •Chocolatey Web Goodness
- •’Tis a Gift to Be Simple
- •Democracy, What a Concept
- •Instant Karma
- •The Whole World in Your Hands
- •Just Do It: The Web as Human Activity
- •The Viewer Rules
- •Multimedia: All Talking! All Dancing!
- •The Server Knows
- •It’s the Bandwidth, Stupid
- •Web Pages Have No Secrets
- •The Web Is for Everyone!
- •Swap text and code for images
- •Prune redundancy
- •Cache as Cache Can
- •Much Ado About 5K
- •Screening Room
- •Liquid Design
- •Color My Web
- •Thousands Weep
- •Gamma Gamma Hey!
- •Typography
- •The 97% Solution
- •Points of Distinction
- •Year 2000—Browsers to the Rescue
- •Touch Factor
- •Appropriate Graphic Design
- •User Knowledge
- •What Color Is Your Concept?
- •Business as (Cruel and) Usual
- •The Rise of the Interface Department
- •Form and Function
- •Copycats and Pseudo-Scientists
- •Chaos and Clarity
- •A Design Koan: Interfaces Are a Means too Often Mistaken for an End
- •Universal Body Copy and Other Fictions
- •Interface as Architecture
- •Ten (Okay, Three) Points of Light
- •Be Easily Learned
- •Remain Consistent
- •Continually Provide Feedback
- •GUI, GUI, Chewy, Chewy
- •It’s the Browser, Stupid
- •Clarity Begins at Home (Page)
- •I Think Icon, I Think Icon
- •Structural Labels: Folding the Director’s Chair
- •The Soul of Brevity
- •Hypertext or Hapless Text
- •Scrolling and Clicking Along
- •Stock Options (Providing Alternatives)
- •The So-Called Rule of Five
- •Highlights and Breadcrumbs
- •Consistent Placement
- •Brand That Sucker!
- •Why We Mentioned These Things
- •The year web standards broke, 1
- •The year web standards broke, 2
- •The year web standards broke, 3
- •The year the bubble burst
- •5 The Obligatory Glossary
- •Web Lingo
- •Extranet
- •HTML
- •Hypertext, hyperlinks, and links
- •Internet
- •Intranet
- •JavaScript, ECMAScript, CSS, XML, XHTML, DOM
- •Web page
- •Website
- •Additional terminology
- •Web developer/programmer
- •Project manager
- •Systems administrator (sysadmin) and network administrator (netadmin)
- •Web technician
- •Your Role in the Web
- •Look and feel
- •Business-to-business
- •Business-to-consumer
- •Solve Communication Problems
- •Brand identity
- •Restrictions of the Medium
- •Technology
- •Works with team members
- •Visually and emotionally engaging
- •Easy to navigate
- •Compatible with visitors’ needs
- •Accessible to a wide variety of web browsers and other devices
- •Can You Handle It?
- •What Is the Life Cycle?
- •Why Have a Method?
- •We Never Forget a Phase
- •Analysis (or “Talking to the Client”)
- •The early phase
- •Design
- •Brainstorm and problem solve
- •Translate needs into solutions
- •Sell ideas to the client
- •Identify color comps
- •Create color comps/proof of concept
- •Present color comps and proof of concept
- •Receive design approval
- •Development
- •Create all color comps
- •Communicate functionality
- •Work with templates
- •Design for easy maintenance
- •Testing
- •Deployment
- •The updating game
- •Create and provide documentation and style guides
- •Provide client training
- •Learn about your client’s methods
- •Work the Process
- •Code Wars
- •Table Talk
- •XHTML Marks the Spot
- •Minding Your <p>’s and q’s
- •Looking Ahead
- •Getting Started
- •View Source
- •A Netscape Bonus
- •The Mother of All View Source Tricks
- •Doin’ it in Netscape
- •Doin’ it in Internet Explorer
- •Absolutely Speaking, It’s All Relative
- •What Is Good Markup?
- •What Is Sensible Markup?
- •HTML as a Design Tool
- •The Frames of Hazard
- •Please Frame Safely
- •Framing Your Art
- •<META> <META> Hiney Ho!
- •Search Me
- •Take a (Re)Load Off
- •WYSIWYG, My Aunt Moira’s Left Foot
- •Code of Dishonor
- •WYS Is Not Necessarily WYG
- •Publish That Sucker!
- •HTMHell
- •9 Visual Tools
- •Photoshop Basics: An Overview
- •Comp Preparation
- •Dealing with Color Palettes
- •Exporting to Web-Friendly Formats
- •Gamma Compensation
- •Preparing Typography
- •Slicing and Dicing
- •Rollovers (Image Swapping)
- •GIF Animation
- •Create Seamless Background Patterns (Tiles)
- •Color My Web: Romancing the Cube
- •Dither Me This
- •Death of the Web-Safe Color Palette?
- •A Hex on Both Your Houses
- •Was Blind, but Now I See
- •From Theory to Practice
- •Format This: GIFs, JPEGs, and Such
- •Loves logos, typography, and long walks in the woods
- •GIFs in Photoshop
- •JPEG, the Other White Meat
- •Optimizing GIFs and JPEGs
- •Expanding on Compression
- •Make your JPEGS smaller
- •Combining sharp and blurry
- •Animated GIFs
- •Creating Animations in ImageReady
- •Typography
- •The ABCs of Web Type
- •Anti-Aliasing
- •Specifying Anti-Aliasing for Type
- •General tips
- •General Hints on Type
- •The Sans of Time
- •Space Patrol
- •Lest We Fail to Repeat Ourselves
- •Accessibility, Thy Name Is Text
- •Slicing and Dicing
- •Thinking Semantically
- •Tag Soup and Crackers
- •CSS to the Rescue…Sort of
- •Separation of Style from Content
- •CSS Advantages: Short Term
- •CSS Advantages: Long Term
- •Compatibility Problems: An Overview
- •Working with Style Sheets
- •Types of Style Sheets
- •External style sheets
- •Embedding a style sheet
- •Adding styles inline
- •Fear of Style Sheets: CSS and Layout
- •Fear of Style Sheets: CSS and Typography
- •Promise and performance
- •Font Size Challenges
- •Points of contention
- •Point of no return: browsers of the year 2000
- •Absolute size keywords
- •Relative keywords
- •Length units
- •Percentage units
- •Looking Forward
- •11 The Joy of JavaScript
- •What Is This Thing Called JavaScript?
- •The Web Before JavaScript
- •JavaScript, Yesterday and Today
- •Sounds Great, but I’m an Artist. Do I Really Have to Learn This Stuff?
- •Educating Rita About JavaScript
- •Don’t Panic!
- •JavaScript Basics for Web Designers
- •The Dreaded Text Rollover
- •The Event Handler Horizon
- •Status Quo
- •A Cautionary Note
- •Kids, Try This at Home
- •The Not-So-Fine Print
- •The Ever-Popular Image Rollover
- •A Rollover Script from Project Cool
- •Windows on the World
- •Get Your <HEAD> Together
- •Avoiding the Heartbreak of Linkitis
- •Browser Compensation
- •JavaScript to the Rescue!
- •Location, location, location
- •Watching the Detection
- •Going Global with JavaScript
- •Learning More
- •12 Beyond Text/Pictures
- •You Can Never Be Too Rich Media
- •Server-Side Stuff
- •Where were you in ‘82?
- •Indiana Jones and the template of doom
- •Serving the project
- •Doing More
- •Mini-Case Study: Waferbaby.com
- •Any Size Kid Can Play
- •Take a Walk on the Server Side
- •Are You Being Served?
- •Advantages of SSI
- •Disadvantages of SSI
- •Cookin’ with Java
- •Ghost in the Virtual Machine
- •Java Woes
- •Java Woes: The Politically Correct Version
- •Java Joys
- •Rich Media: Exploding the “Page”
- •Virtual Reality Modeling Language (VRML)
- •SVG and SMIL
- •SMIL (through your fear and sorrow)
- •Romancing the logo
- •Sounds dandy, but will it work?
- •Promises, Promises
- •Turn on, Tune in, Plug-in
- •A Hideous Breach of Reality
- •The ubiquity of plug-ins
- •The Impossible Lightness of Plug-ins
- •Plug-ins Most Likely to Succeed
- •Making It Work: Providing Options
- •The “Automagic Redirect”
- •The iron-plated sound console from Hell
- •The Trouble with Plug-ins
- •If Plug-ins Run Free
- •Parting Sermon
- •13 Never Can Say Goodbye
- •Separation Anxiety
- •A List Apart
- •Astounding Websites
- •The Babble List
- •Dreamless
- •Evolt
- •Redcricket
- •Webdesign-l
- •When All Else Fails
- •Design, Programming, Content
- •The Big Kahunas
- •Beauty and Inspiration
- •Index
Taking Your Talent to the Web |
65 |
TOUCH FACTOR
When designing a book, your choice of materials and textures is limited only by the client’s budget. When designing a website, you have no textures whatsoever. There is no “touch factor” in work designed for the digital screen. But this lack of sensory input does not mean that the site must be a cold, detached, clinical object. There are many tools to help you bring humanity and warmth to the Web.
Appropriate Graphic Design
Interactivity can go a long way toward simulating the effect of the “touch.”
For instance, when you move your mouse over or press the buttons at www.k10k.net, they seem to respond to your touch—like buttons in the real world. Intuitive, user-centered navigation helps as well. If the architecture is designed the way users think, navigating the site will be simple pleasure. There will be more on all that in Chapter 3. Smart, appropriate copywriting, which reads the way people talk, also can go a long way toward bringing warmth and humanity to the onscreen experience.
These approaches enable anyone to create a site that feels like a living entity. Failure to use these tools results in a site that feels cold and dead— high tech, but not high touch.
ACCESSIBILITY, THE HIDDEN SHAME
OF THE WEB
The framers of the Web intended it to be a medium of universal access—a medium whose wealth of information would be accessible to anyone, regardless of physical, mental, or technological disability. Anything that stands in the way of that accessibility is contrary to the purpose of the Web. It is also inhumane, and, as we alluded to earlier, it is now against the law:
66 WHY: Designing for the Medium: Accessibility, the Hidden Shame of the Web
Section 508 of the Workforce Investment Act (www.usdoj.gov/crt/ 508/508law.html) requires all United States Federal Agencies with websites to make them accessible to individuals with disabilities. Inaccessible sites can be shut down by the government. In the private sector, inaccessible sites face lawsuits. In 1999, a group of blind citizens successfully sued America Online because its service was not accessible to them.
How do you design for the blind? It sounds like a paradox, but on the Web it is actually fairly easy.
The Web Content Accessibility Guidelines of the W3C (www.w3.org/TR/ WAI-WEBCONTENT/) spell out everything designers must do to make their sites accessible to all.
Here are some of the things you can do to make your site accessible:
■Your <IMAGE> tags should include <ALT> text for the benefit of the visually impaired; adding <TITLE> attributes is a good idea as well. <ALT> and <TITLE> attributes can be spoken by audio browsers used by the blind, so they don’t have to miss out on any content. For example, your web page on the wreck of the Titanic includes a photograph of that ill-fated ship. A bad <ALT> attribute reads “Image, 24K.” Well, what good is that to the disabled user? So your site has an image, so what? A good <ALT> tag will read “S.S. Titanic.” The <TITLE> attribute can provide additional description: “Photograph of the Titanic on her maiden voyage.”
■If you use frames, include <NOFRAMES> content in the frameset document. <NOFRAMES> text shows up in browsers that cannot view frames. Old browsers fall into this category, but so do text browsers such as Lynx and special browsers for the blind. By copying your text and pasting it into the <NOFRAMES> area, you guarantee that anyone can access the information on your site, even if he or she cannot view your spectacular visual design efforts.
■Even if most users will be navigating via snazzy visual menu bars at the top of your site, be sure to include simple HTML links somewhere on the page so that the disabled—or folks with older, non-JavaScript- capable browsers—can still find their way around the site.
Taking Your Talent to the Web |
67 |
For more on accessibility and the law, see Alan Herrell’s article in A List Apart, “Accessibility: The Clock is Ticking” (www.alistapart.com/stories/ access/).
USER KNOWLEDGE
A website must be designed so novice users can find their way through it without trouble. At the same time, a good site offers shortcuts and power tools for more experienced users. How do you serve these two very different audiences at the same time? We’ll discuss that in the very next chapter.
chapter 3
Where Am I? Navigation
& Interface
“I LEFT MY BABY DAUGHTER in the car while I went to buy dope. Then I drove away. I’d gone about five blocks when I realized my daughter wasn’t in the car any more.”
So begins a brief personal narrative that fills most of the screen of a web page. At the conclusion of this woeful tale, we see a link or button labeled More Stories. We are likely to click it.
Before doing so, we notice that a small Narcotics Anonymous logo appears in the upper left area of the screen and that four menu items appear in a column on the right. The Face of Addiction, reads one. There Is a Solution, reads another. Meetings, says a third, and Membership, reads the fourth.
Meetings takes us to a map of the United States. Clicking any city takes us to a schedule of Narcotics Anonymous meetings in that city. The Narcotics Anonymous logo, consistently placed at the upper left of every screen on the site, takes us back to the first page, with its riveting personal narrative and easily understood menu structure. Perhaps when we return to the home page we are served a different personal story. This story may be a bit longer than the first we encountered. After all, our attention is now engaged because we have committed at least a few minutes of our time to the site. At this point we are ready to involve ourselves with a slightly more elaborate narrative.