Platinum Edition Using HTML 4, XML, and Java 1.2
(Publisher: Macmillan Computer Publishing)
Author(s): Eric Ladd
ISBN: 078971759x
Publication Date: 11/01/98

Other technology concerns influence design decisions, as well. These include

•  Monitor—Because the Web is largely a visual medium, it helps to know for which monitors you are designing. If you are not certain, it is still best to design to a lower-end standard: a 14-inch monitor, set at 640×480, with the standard 256-color Windows palette. Remember that not everyone has the sophisticated monitors that many designers have, although more and more users tend to have monitors set at 800×600 pixel resolution.

---

NOTE:  Lynda Weinman explains the notion of the “browser safe” color palette on her Web site at http://www.lynda.com/hex.html. The palette comprises colors that will be rendered the same way on Macintosh and Windows platforms, so you’ll have an assurance that all users will see the exact same thing.

---

•  Browser software—Netscape Navigator and Microsoft Internet Explorer support all the latest extensions to HTML, but not every browser does. Some browsers, such as Lynx, are text only, which means users won’t be able to see your graphics. Additionally, a good number of your users will be visiting your site from America Online (AOL), Compu-Serve, Prodigy, or some other online service. Each service’s browser has its own quirks that you must consider when designing; AOL’s browser could not process the HTML table tags for the longest time, for example, so AOL users missed out on some attractive layouts that used tables.
Visually impaired users may be using Braille or speech-based browsers, which means that all your visible content will be lost on them unless you provide text alternatives for graphics, Java applets, and other embedded content. The World Wide Web Consortium has expanded the accessibility of many HTML constructs for users with speech-based browsers. Many HTML 4 additions for the form tags, for example, were driven by the need for forms to be more usable by the blind or visually impaired.
Remember that if you design to a higher-end graphical browser, you need to make alternative content available to people using less capable browsers as well.

•  Helper applications and plug-ins—Even though many of today’s browsers are incredibly powerful, they can’t do it all alone. Audio clips, video clips, multimedia content, and some image formats require the use of a separate viewer program (a helper application) or a program that works with the browser to display content inline (a plug-in). Before you load up your site with these elements, make sure your audience has (or at least has access to) the additional software needed to view them.

	The home page of many sites provides a notice that informs users of combinations of browser software and plug-ins the site is best viewed with (see Figure 1.3). Many of these notices also include links to pages where you can download the software. This is a helpful service that can maximize a user’s experience when he or she visits your site.

•  Connection speed—Some designers put together pages on a local drive and browse the pages right on the same machine. Other designers may port finished pages to a server and view them over a high-speed connection. Neither type of designer will appreciate the exasperation of having to wait for a page to download over a 14.4Kbps modem. Consider the types of connections your users will have and design appropriately. This may compel you to scale back on multimedia content and perhaps even some graphics content as well. Another way you can show respect for those with slower connections is to make available versions of your pages that are largely text, with minimal or no graphics.

---

NOTE:  More and more Web page authoring programs come with tools that estimate how long it will take a given page to download. The FrontPage 98 Editor, for example, displays an estimated download time over a 28.8Kbps connection for whatever page you are editing. This time displays near the bottom right of the Editor window along the status bar.

Allaire’s HomeSite includes a Document Weight function that computes estimated download times for 14.4Kbps, 28.8Kbps, and 57.6Kbps connections.

---

FIGURE 1.3  Coca-Cola’s site tells users which browsers and plug-ins will enhance their visit and gives them the option to visit different versions of the site, depending on which technology they have.

	Set up separate links to large multimedia items and indicate the file size somewhere close to the link (see Figure 1.4). This enables users to decide whether they want to download the file.

FIGURE 1.4  DOWNLOAD.COM always lets you know how big the file is that you’re about to download.

Considering Your Own Objectives

It is possible to spend so much time assessing audience factors that you can forget your reasons for wanting to create a Web site. User considerations are of paramount importance, but during the design process, you should not lose sight of your own motivations.

When planning your site, you should compose a mission statement, requirements document, or list of objectives that articulates why you want to create a Web site. This statement or list is another factor that should contribute to the site’s design.

Use your mission statement or objective list to ground yourself during the design process. Keep checking your design against your reasons for designing the site in the first place. By balancing end-user considerations with your own objectives, you will produce a site that has broad appeal and that helps you attain your communications goals.

	Post your mission statement, requirements summary, or objective list in a public place on a whiteboard or on newsprint so that you and your design team (if you have one) can always be reminded of why you’re doing what you’re doing.