CSS: Good; Everything Else: Bad
Images, flash, frames. These are the “traditional” methods for making a web site “more interesting” or “better looking.” But these hold-overs from the AOL era are the bane of bandwidth, text-only browsers, and non-visual users.
HTML, of course, was originally written to define the structure of a web page, never it’s design. In essence, HTML was intended to be much like XML today. But, when HTML was created, there were no style-sheets, so HTML was forced to include some design information, like tags and the bgcolor attribute. Developers quickly turned to images, JavaScript, frames, and Flash to make their lives easier, but in the process made everyone else’s life harder.
Images and Flash will both suck bandwidth, so why would you use them to display text or a navigation bar? Save images and Flash for what they’re supposed to be: pictures and animations. Frames reek havoc on text-only browsers and screen-readers (hence the rarely-used
So how can you save bandwidth, insure accessibility, and still get all the effects you want? CSS. Let’s go over a few of the quick-and-easy ways to use CSS to replace the bandwidth-heavy, inaccessible design you’re using now:
1) Frames: Fixed Sidebars
Perhaps the most common use of frames was the sidebar, a window on the left (or right) that contained anything from helpful information to your site’s navigation, appeared on every page, and didn’t scroll with the rest of the site.
If you want to do the same thing, use the CSS “position: fixed” definition. For instance:
sidebar { position: fixed; top: 0; left: 0; width: 160px; height: 100%; background: #00f; }
This will make a non-scrolling, 160-pixel wide sidebar on the left of the screen. (You could always use “right” and “bottom,” too.) Now, in your HTML file, create a
You can put this anywhere in the HTML source, and it will appear in the correct place. In a good screen-reader, if you put this toward the bottom of the HTML source (for instance, after all the content of the page) then the user would hear the content before having to hear the list of links again.
2) Images: Positioning Text
This is really just poor web-design. Unless it’s desperately important that you use a particular, rare font, you should never use images to display text. If it’s important that the text appear a certain way or in a certain position, make use of the box-model and nested
main { width: 480px; height: 100%; margin: 0 auto; padding: 0; position: relative; top:0; left:0; } #gutter { width: 120px; height: 100%; margin: 0; padding: 0; border-left: 1px solid #000; position: absolute; top: 0; right: 0; background: #2c2; color: #fff; } #header { width: 360px; margin: 0; padding: 6px; position: relative; top: 0; left: 0; font-family: Tahoma, Arial, san-serif; font-size: 140%; text-align: center; }
With the corresponding HTML:
Page Title
Page Slogan
Which gives something like (borders added to show box model):
Now, of course, with just a little editing of the CSS file (and none of the HTML) you can move the gutter, change the background, change the page width, change the font, and it’s all in text-format, that will display correctly to text-only or visually-impaired browsers, and save huge percentages of bandwidth.
3) Flash: Cool Navigation Bars
This gets a little more complicated. In general, it’s hard to define the box around tags, so you’ll probably want to do something like this:
nav { margin: 4px auto 0 auto; position: relative; top: 0; left: 0; } #nav ul { display: inline; list-style-type: none; } #nav li { display: inline; border: 1px solid #000; padding: 2px 4px 0 4px; margin: auto 4px 0 4px; } #nav li.here { border-bottom: 1px solid #FFF; } #nav li:HOVER { border-bottom: 1px solid #FFF; font-weight: bold; }
Now in each
So there you go…
It’s not all the info you’ll ever need, but it solves three of the most heinous wastes of bandwidth I’ve seen on the web, as well as all the problems people have with accessibility. These methods can both look great, and be completely usable by everyone, something Flash, frames, and images can’t.