Mimsy Were the Borogoves

Mimsy Were the Technocrats: As long as we keep talking about it, it’s technology.

42 Astoundingly Useful Scripts and Automations for the Macintosh

Work faster and more reliably. Add actions to the services menu and the menu bar, create drag-and-drop apps to make your Macintosh play music, roll dice, and talk. Create ASCII art from photos. There’s a script for that in 42 Astounding Scripts for the Macintosh.

A new, accessible Mimsy

Jerry Stratton, February 2, 2006

I recently attended a web conference and heard Sarah Horton, author of Access by Design: A Guide to Universal Usability for Web Designers. Sarah’s presentation inspired me to take the final plunge I’ve been meaning to take for a while: simplify the back-end design on Mimsy and use CSS2 positioning to put my navigation menu after the content on this site.

I originally designed the back-end HTML to be as “universal” as possible. I ended up settling for a table-based layout solution because CSS2 positioning wasn’t yet fully supported by visual, graphical browsers. However, I don’t like setting up a side-door entrance for a text-only or other accessible version. Horton reminded me of that compromise, and that it isn’t necessary any more.

Horton recommends “universal design”, which is to say, make one design that is flexible enough to support all users. This ends up being more reliable--you don’t need to remember to change multiple versions. And it ends up being more satisfying to people visiting your site: they don’t have to go to a side entrance to consume your content.

Today, pretty much all in-production graphical, visual browsers support CSS2, and quite a few older, out-of-production versions do, too. Switching to a CSS2 solution rather than tables assists those using alternative browsers, such as voice readers and small screens, by putting the content first. They don’t have to wade through the long list of other articles on the site.

Before CSS2 Positioning

A sample Walkerville Weekly Reader article using tables for layout. The menus go on for more than two pages before the text of the article shows up.

I’ve included some examples of what alternative browsers used to have to wade through, and what they now “see” when coming to this site. I used Lynx to create them. Lynx strips pretty much everything from a web page that isn’t usable in non-visual browsers. You can see that the article shows up immediately in the “after” shot and not at all in the “before” shot. As a side-bonus, the site is now also much more usable in cell phone browsers.

Alternatives to Internet Explorer

In the process, I’ve discovered that there are still people using Internet Explorer 5.2 on Mac OS X. CSS2 was ratified on May 12, 1998. That’s not just eight years ago, it’s three years before Mac OS X was introduced and three years before Internet Explorer for Mac OS X was introduced.

Explorer for the Macintosh was abandoned by Microsoft in June 2003, nearly three years ago. Even they recommend that you switch to another browser. Now, one of the advantages of the new design is that you don’t need to switch. The site is perfectly readable even in Explorer 5.2. With style sheets turned on, you can read the articles, though you’ll need to scroll horizontally.

However, Explorer’s support of style sheets is so poor that you may find it easier to browse the web by turning style sheets off in Explorer’s preferences. You can set this option in Explorer’s Web Browser:Web Content preference area. With the redesign, you will definitely find that Mimsy articles are easier to read; you’ll probably find that other sites are, too.

After CSS2 Positioning

After replacing tables with CSS2 positioning the article text shows up immediately in alternative browsers.

If you are going to choose to use a visual, graphical browser you might choose to use a browser that understands an eight-year-old standard. You have a lot of options. Safari supports it. Netscape, Mozilla, Camino, and Firefox support it. So does Opera. And OmniWeb. Even iCab now supports CSS2.

Firefox works under Mac OS X 10.3. Mozilla and Netscape work on OS X as far back as OS X 10.1. Camino, Opera, and Omniweb work back to 10.2. Even the older versions of Camino and Opera for 10.1 support CSS2. Opera’s older version for Mac OS 8 and 9 support CSS2 as well. iCab--the latest version--supports Mac OS 8.5 as well as OS X 10.2. For just about any Mac OS computer that can run Internet Explorer, there is a better alternative for browsing the web.

We’ve fortunately moved away from rendering headlines to an image, and to rendering entire pages as images (iWeb notwithstanding). Using tables for layout rather than for tabular data is also generally bad design and not likely to return to these pages.

  1. <- Disney Does Pixar
  2. Google vs. Users ->