Guidelines for using tables

Whenever you are considering using a table, ask yourself these questions:

  • Can the content be better presented another way?

    Consider alternative ways of presenting the same content. For example, you may have a table of names addresses and phone numbers. It's laid out with one row per person. This information would be better presented on a small screen in one column of regular text (with a <BR> tag at the end of each line) in which name, address, and phone number are stacked for each person, looking more like a mailing label.

  • Would a simulated table work just as well for the content?

    If the content looks best in tabular form, would it work just as well to render it with a fixed width font, with columns of data aligned by filling the space in between with the appropriate number of spaces? The <PRE> tag does this quite nicely, as long as you provide the right number of spaces to maintain column alignment.

  • If you do use a table, try to:

    • Eliminate horizontal scrolling on smaller screens. Be sure you test it on a small Palm OS screen and keep adjusting the table tagging as necessary until any horizontal scrolling is eliminated.

    • Let columns size dynamically, so that the table width can expand and contract to fit the available screen width.

    • Keep it lean and simple – for example, set parameters at the table level and avoid using both CELLPADDING and CELLSPACING, avoid nesting tables.