Front and Center: Graphics, Multimedia, and the Web

The introduction of graphics and multimedia to the Web was what caused its initial exponential growth curve. People had been accessing text content online for years through bulletin boards and online services, but the introduction of images to the online presentation made all the difference in the world.

One day after the introduction of multimedia to the Web came the introduction of multimedia abuse to the Web. Graphics were suddenly placed everywhere regardless of whether they belonged and pages suddenly got bigger and messier. Sound and effects were added to bring attention to pages that did little more than cause headaches to the viewer.

My mom once told me, "Just because you can doesn't mean you should," and her advice rings true to this day. The desire to fill Web content with as many graphics moving as many directions as possible needs to be overcome with a strong desire to produce content that does what it is supposed to do without leaning on technology to "make it cool."

When you design for the Web, certainly make use of everything it has to offer. If graphics or multimedia can be used to explain or emphasize, certainly use them and use FrontPage to make the most of them.

However, if you find yourself looking at a Web page, hoping to "add some zip" to it, ask yourself if it is really necessary.

In addition to this call for basic common sense, consider the following other issues:

Not everyone can view the multimedia elements you have placed on your Web site. There are thousands of potential causes of these restrictions, ranging from a browser that doesn't support it (you trying to watch flash files on your cell phone) to people who don't have the time or bandwidth to view it.

In addition, despite the marketing machines behind many popular multimedia options for the Web, not everyone has all the plug-ins installed on their browsers and don't intend on ever waiting for the download. They will, instead, simply pass over your site, causing you to have jumped from trying to impress to losing a customer.

This is also the simple issue of Web site accessibility. For some, it isn't a question of which plug-in is installed, it is the reality of a disability that might prevent them from viewing or hearing your content as you originally designed it.

Adding a link with information on how to download the appropriate player is not enough: Some users won't, some users are prevented by technology from doing so, and others simply are unable to do so. Make sure that you design for them as well.

For more on FrontPage's accessibility features and how you can make sure that your site can be seen by everyone, see "FrontPage's Accessibility Features," p. 235.




Special Edition Using Microsoft Office FrontPage 2003
Special Edition Using Microsoft Office FrontPage 2003
ISBN: 0789729547
EAN: 2147483647
Year: 2003
Pages: 443

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net