design and development for the web


Javascript Styles

Sunday, August 2nd, 2009

Here's a quick tip for anyone trying to maintain graceful degradation of javascript. Keep all your javascript-dependent styles in a separate stylesheet and use javascript to load those styles immediately in the head of the document.

Read the rest of this »

Mozilla Javascript Option Object

Saturday, January 26th, 2008

I was trouble-shooting a friend's DOM-Script the other day. It consisted of a form select element that was working in Firefox, but not in Explorer.

"Suprise, surprise," was my first thought. But, actually... Explorer had the correct behavior. For once.

Read the rest of this »

Semantically speaking…

Saturday, January 26th, 2008

Still using div id's like "header", "footer", "left_bar", "right_bar", "sidebar", and so on? Then, you need to read on.

Division ID's like the ones listed above are about as dead as using table layouts. I can say it in a nutshell, but it doesn't seem like designers really understand what's going on...

Read the rest of this »

An experiment with relative units

Wednesday, January 23rd, 2008

I had this great idea to test out relative units. What if you defined the body's font-size based off of the window's width (or height). So, now you've got a dynamic font-size setting for the body tag... big deal, right? Absolutely!

With a little DOM-Scripting, some creative CSS, and a little elbow grease, we can make a fully scalable page!

Read the rest of this »

Organizing CSS Files

Thursday, November 15th, 2007

Every designer has their own way of formatting and organizing style sheets. Let's take a look at a few different methods. Technically, there is no correct solution. But, depending on the project at hand, you may decide to choose one method over another.

Read the rest of this »

Quality, Privacy, and Accessibility Testing

Thursday, November 15th, 2007

Ever wonder what it really takes to be ADA Compliant? Short of sifting through w3c specs, there's a great site I've found where you can submit single pages to see if they pass the test.

It's called WebXACT by Watchfire. Just paste in your URL. It shows errors and warnings. The interface can be a little sketchy at first, but once you notice the tab at the top labeled "Accessibility" you can go to a page that has tons of information on what you're missing.

WebXACT will give you warnings as well as errors, so it's really like a debug utility for web developers. Not only will you get rid of all your errors, but it will help you find out other ways to make your site more accessible.


Recommended Materials