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 tag) and have been considered blase web-design for years.</p> <p>So how can you save bandwidth, insure accessibility, and still get all the effects you want? <abbr title="Cascading Style Sheets.">CSS</abbr>. 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:</p> <p><span style="font-weight: bold">1) Frames: Fixed Sidebars</span><br> 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.</p> <p>If you want to do the same thing, use the CSS “position: fixed” definition. For instance:</p> <h1 id="sidebarpositionfixedtop0left0width160pxheight100background00f">sidebar { position: fixed; top: 0; left: 0; width: 160px; height: 100%; background: #00f; }</h1> <p>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 <div> with the <tt>id=&quot;sidebar&quot;</tt> attribute:</p> <div id="sidebar"> ...all your links go here... </div> <p>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.</p> <p><span style="font-weight: bold">2) Images: Positioning Text</span><br> 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 <div>s. For example, let’s say you wanted a 480-pixel wide layout, regardless of the users’ screen resolution, with a right gutter and a title and slogan in the top-left. You might do something like:</p> <h1 id="mainwidth480pxheight100margin0autopadding0positionrelativetop0left0gutterwidth120pxheight100margin0padding0borderleft1pxsolid000positionabsolutetop0right0background2c2colorfffheaderwidth360pxmargin0padding6pxpositionrelativetop0left0fontfamilytahomaarialsanseriffontsize140textaligncenter">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; }</h1> <p>With the corresponding HTML:</p> <div id="main"> <div id="gutter"> ...gutter code here... </div> <div id="header"> <p>Page Title</p> <p>Page Slogan</p> </div> </div> <p>Which gives something like (borders added to show box model):</p> <p><img src="http://jamessocol.com/images/screenshot.png" alt="" loading="lazy"></p> <p>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.</p> <p><span style="font-weight: bold">3) Flash: Cool Navigation Bars</span><br> This gets a little more complicated. In general, it’s hard to define the box around <a> tags, so you’ll probably want to do something like this:</p> <h1 id="navmargin4pxauto0autopositionrelativetop0left0navuldisplayinlineliststyletypenonenavlidisplayinlineborder1pxsolid000padding2px4px04pxmarginauto4px04pxnavlihereborderbottom1pxsolidfffnavlihoverborderbottom1pxsolidffffontweightbold">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; }</h1> <p>Now in each <li> tag you’ll make a link to the page you want. This particular set of code gives you a horizontal list. I use a version of this on my <a href="http://projects.jamessocol.com" title="Projects page.">projects page</a>, so you can see it in action. If you remove the <tt>display: inline</tt> parts, you’ll get the vertical list you need for a column. Of course, the margin, padding, and all the colors can be customized however you want, to make it look right. (I got this from the <a href="http://www.alistapart.com">AListApart</a> article “<a href="http://www.alistapart.com/articles/taminglists/">Taming Lists</a>“, which you should read for more information.)</p> <p><span style="font-weight: bold">So there you go…</span><br> 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.</p> <!--kg-card-end: markdown--> </section> </article> </main> <section class="footer-cta outer"> <div class="inner"> <h2 class="footer-cta-title">Sign up for more like this.</h2> <a class="footer-cta-button" href="#/portal" data-portal> <div class="footer-cta-input">Enter your email</div> <span>Subscribe</span> </a> </div> </section> <aside class="read-more-wrap outer"> <div class="read-more inner"> <article class="post-card post no-image"> <div class="post-card-content"> <a class="post-card-content-link" href="/the-triforce-of-deployment/"> <header class="post-card-header"> <div class="post-card-tags"> </div> <h2 class="post-card-title"> The Triforce of Deployment </h2> </header> <div class="post-card-excerpt">Continuous delivery is great. Fortunately, so are all the tools you need to get there. I've talked [https://github.com/jsocol/talks/tree/master/2013-06-13-firstmark-cd] about this [https://github.com/jsocol/talks/tree/master/2017-05-03-queensjs-cd] a number of times [https://jamessocol.com/speaker.html]—including recently on Software Engineering Radio</div> </a> <footer class="post-card-meta"> <time class="post-card-meta-date" datetime="2022-02-15">Feb 15, 2022</time> <span class="sep">—</span> <span class="post-card-meta-length">4 min read</span> </footer> </div> </article> <article class="post-card post no-image"> <div class="post-card-content"> <a class="post-card-content-link" href="/unclear-asks-are-killing-your-team/"> <header class="post-card-header"> <div class="post-card-tags"> </div> <h2 class="post-card-title"> Unclear Asks are Killing your Team </h2> </header> <div class="post-card-excerpt">We've all been in a meeting, wondering what the goal was, and why we were invited. Some of us have even gotten up, said something, and left. The truly bold may have suggested ending the entire meeting and reconvening with a plan. We've also all gotten an email addressed to</div> </a> <footer class="post-card-meta"> <time class="post-card-meta-date" datetime="2019-01-24">Jan 24, 2019</time> <span class="sep">—</span> <span class="post-card-meta-length">4 min read</span> </footer> </div> </article> <article class="post-card post no-image"> <div class="post-card-content"> <a class="post-card-content-link" href="/remembering-todaysmeet/"> <header class="post-card-header"> <div class="post-card-tags"> </div> <h2 class="post-card-title"> Remembering TodaysMeet </h2> </header> <div class="post-card-excerpt">Nearly 10 years ago, I launched a small chat tool [https://todaysmeet.com]. Somehow, through a lot of luck, and a bunch of hard work, it managed to become popular among classroom teachers as a way to enable new kinds of conversations. Now it's time to say goodbye and move</div> </a> <footer class="post-card-meta"> <time class="post-card-meta-date" datetime="2018-04-28">Apr 28, 2018</time> <span class="sep">—</span> <span class="post-card-meta-length">4 min read</span> </footer> </div> </article> </div> </aside> </div> <footer class="site-footer outer"> <div class="inner"> <section class="copyright"><a href="https://coffeeonthekeyboard.com">Coffee on the Keyboard</a> &copy; 2022</section> <nav class="site-footer-nav"> </nav> <div><a href="https://ghost.org/" target="_blank" rel="noopener">Powered by Ghost</a></div> </div> </footer> </div> <script src="https://code.jquery.com/jquery-3.5.1.min.js" integrity="sha256-9/aliU8dGd2tb6OSsuzixeV4y/faTqgFtohetphbbj0=" crossorigin="anonymous"> </script> <script src="https://coffeeonthekeyboard.com/assets/built/casper.js?v=2677386bb3"></script> <script> $(document).ready(function () { // Mobile Menu Trigger $('.gh-burger').click(function () { $('body').toggleClass('gh-head-open'); }); // FitVids - Makes video embeds responsive $(".gh-content").fitVids(); }); </script> </body> </html>