<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://www.tigerheron.com" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>graphic design</title>
 <link>http://www.tigerheron.com/category/graphic-design</link>
 <description>The taxonomy view with a depth of 0.</description>
 <language>en-US</language>
<item>
 <title>An alternative to the &lt;noscript&gt; tag.</title>
 <link>http://www.tigerheron.com/article/2007/10/alternative-noscript-tag</link>
 <description>&lt;p&gt;
Ideally, when you use &amp;lt;script&gt; to create dynamic Web pages, you will also support browsers where scripting is disabled or unavailable. The &amp;lt;noscript&gt; tag lets you supply the alternate code. But  while &amp;lt;script&gt; can be used inline, &amp;lt;noscript&gt; is strictly a block element, potentially forcing you to duplicate large  amounts of code. I&#039;ll show you an easy alternative to the &amp;lt;noscript&gt; tag for inline uses.&lt;/p&gt;&lt;!--break--&gt;
&lt;p&gt;
If Javascript is your scripting language, insert the following code into the &amp;lt;head&gt; section of your Web page:
&lt;/p&gt;&lt;xmp&gt;  &lt;script type=&quot;text/javascript&quot;&gt;
    document.write(&#039;&lt;style&gt;.noscript { display:none }&lt;/style&gt;&#039;);
  &lt;/script&gt;&lt;/xmp&gt;
&lt;p&gt;
When you need to use &amp;lt;noscript&gt; inline, use &amp;lt;span class=&quot;noscript&quot;&gt; instead.&lt;/p&gt;
&lt;p&gt;
If that went by too fast, consider:
&lt;ul&gt;
&lt;li&gt;If scripting is enabled, the noscript CSS class will be created and will remove any contents tagged with that class.&lt;/li&gt;
&lt;li&gt;If scripting is not enabled, the style is not created and the contents are displayed.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;You many not have noticed a problem using &amp;lt;noscript&gt; inline, as many browsers support this. But if you&#039;d like your code to validate while retaining the convenience of an inline &amp;lt;noscript&gt; tag, use the trick above.</description>
 <comments>http://www.tigerheron.com/article/2007/10/alternative-noscript-tag#comments</comments>
 <category domain="http://www.tigerheron.com/category/css">CSS</category>
 <category domain="http://www.tigerheron.com/category/graphic-design">graphic design</category>
 <category domain="http://www.tigerheron.com/category/tip">tip</category>
 <category domain="http://www.tigerheron.com/category/web-design">Web design</category>
 <pubDate>Fri, 05 Oct 2007 00:36:22 +0000</pubDate>
 <dc:creator>designer</dc:creator>
 <guid isPermaLink="false">89 at http://www.tigerheron.com</guid>
</item>
<item>
 <title>Recommendations for improving fixed-width designs</title>
 <link>http://www.tigerheron.com/article/2007/05/recommendations-improving-fixed-width-designs</link>
 <description>&lt;p&gt;
  &lt;span class=&quot;dropcap&quot;&gt;T&lt;/span&gt;his article focuses on overcoming
  some of the drawbacks of fixed-width designs. These are suggestions
  based on my experience rather than hard-and-fast rules. Feel free to
  critique my suggestions and propose improvements or additional
  guidelines.
&lt;/p&gt;
&lt;!--break--&gt;

&lt;h2&gt;Use a CSS reset stylesheet&lt;/h2&gt;

&lt;p&gt;&lt;span class=&quot;pullquote&quot;&gt;&lt;span style=&quot;font-weight: bold;&quot;&gt;Fixed-width design&lt;/span&gt;: A design
  in which the Web page elements maintain their size and position
  regardless of the browser window&#039;s width.&lt;/span&gt;Each
  browser has a default stylesheet that is used when no styles are
  defined, but the default is not the same for all browsers. A CSS reset
  stylesheet provides a consistent base style for all browsers, which
  is valuable for fixed-width designs, where layouts are dependent on
  pixel-perfect positioning. &lt;a href=&quot;http://meyerweb.com/&quot;&gt;Eric
  Meyer&lt;/a&gt; has been working on this problem for years. Take a look at
  his most recent &lt;a
  href=&quot;http://meyerweb.com/eric/thoughts/2007/05/01/reset-reloaded/&quot;&gt;CSS
  reset file&lt;/a&gt;. Yahoo! also provides a &lt;a
  href=&quot;http://developer.yahoo.com/yui/reset/&quot;&gt;CSS reset file&lt;/a&gt; as
  part of their UI library.
&lt;/p&gt;

&lt;h2&gt;Select the design width based on your intended audience&lt;/h2&gt;

&lt;p&gt;
  For a fixed-width design, one of your most important decisions is selecting the design width. Your choice should work well
  for your targeted audience. Make it too narrow and much of the
  visitor&#039;s screen goes to waste; make it too wide and visitors will
  need to scroll horizontally (which people hate to do&lt;sup&gt;&lt;a
  href=&quot;#c1&quot;&gt;1&lt;/a&gt;&lt;/sup&gt;).
&lt;/p&gt;

&lt;p&gt;
  For almost all the sites I work on, my clients prefer not to exclude
  any significant chunk of the population. This results (today) in
  choosing an 760-pixel-wide design for an 800-pixel-wide screen. Once
  a Web site is in operation, you can use the server log files to
  validate your decision. For example, in the last five months
  12.5% of all visitors to my Tiger Heron site used an 800x600
  display&amp;mdash;not a large number, but still significant. No one used
  a smaller screen size.
&lt;/p&gt;

&lt;p&gt;
  An alternative approach is to create more than one design and use
  Javascript to select the corresponding stylesheet based on the
  visitor&#039;s screen size. In practical terms, one 800- and one
  1024-pixel-wide design is probably sufficient for almost every site.
  For screens larger than 1024 pixels wide, maximizing the
  browser window becomes a matter of preference rather than necessity, so the
  browser width won&#039;t always be the same as the screen width.
  Even if maximized on the largest of today&#039;s displays, a
  1024-pixel-wide design does a good job of filling the screen.
&lt;/p&gt;

&lt;p class=&quot;captionedImage&quot;&gt;
  &lt;a href=&quot;http://www.yahoo.com/&quot;&gt;&lt;img src=&quot;/files/blogs/designer/node43/yahoo.jpg&quot; alt=&quot;Yahoo&#039;s 1024-pixel-wide Web site&quot; title=&quot;&quot; height=&quot;183&quot; width=&quot;300&quot; onload=&quot;imageSizeToEms(this, pixelToEms)&quot;&gt;&lt;/a&gt;
  &lt;span class=&quot;imgCaption&quot;&gt;Yahoo&#039;s 1024-pixel-wide Web site on a 1920x1600 display.&lt;/span&gt;
&lt;/p&gt;

&lt;p&gt;
  What about smaller displays, such as phones and PDA&#039;s? I don&#039;t have
  much experience with these, but my instincts say that creating an
  effective Web site for small displays involves more than just
  switching a stylesheet. Suggestions, anyone?
&lt;/p&gt;

&lt;h2&gt;Select appropriate font sizes&lt;/h2&gt;

&lt;p&gt;
  Font sizes are a design choice. But here&#039;s a problem: in
  print, 12 point text is the same size everywhere. On the Web, the
  size of 12 point (or even 12-pixel) text depends on the pixel
  density of the display&amp;mdash;the higher the density, the smaller the
  text. If you use a single stylesheet, your fonts need to be large
  enough to be readable on high-pixel-density displays, but not so
  large as to overwhelm a viewer on a low-pixel-density display. If
  you select your stylesheets based on the monitor&#039;s resolution, you
  can choose larger font sizes for monitors with higher resolution.
&lt;/p&gt;

&lt;h2&gt;Select the line length&lt;/h2&gt;

&lt;p&gt;
  In print, the typical line length is 10 to 12 words. If that sounds
  like a small number, pick up some books and start counting&amp;mdash;you
  might be surprised. At an average word length of five characters
  plus a space, this translates to 60 to 72 characters per line
  (CPL).
&lt;/p&gt;

&lt;p&gt;
  While the print world has a time-tested rule for line lengths, I&#039;m
  not yet convinced that we have the answer for Web pages. In a
  study&lt;sup&gt;&lt;a href=&quot;#c2&quot;&gt;2&lt;/a&gt;&lt;/sup&gt; about the effects of line
  lengths when reading from a computer display, researchers found that
  reading speeds &lt;em&gt;increased&lt;/em&gt; with line lengths up to 95 CPL
  without affecting comprehension (about 16 words per line). Despite
  this, the study participants were split on which line length they
  preferred.
&lt;/p&gt;

&lt;p&gt;
  I checked a number of other sources for recommendations and
  the only conclusion I can draw is that a range of 60 to 95 CPL is
  probably fine. Much longer or shorter lines can be unpleasant,
  although I suspect you can go somewhat over 95 CPL when information
  density is critical and the typical visitor will read only a portion
  of the text.
&lt;/p&gt;

&lt;div style=&quot;display: none;&quot;&gt;
&lt;p&gt;
  The rule for line length is supposedly based on the arc of the
  visual field&amp;mdash;outside of this arc, eye and head movements make
  for slower and more tiring reading. When I chose some books from
  my library and measured the text width, I saw line lengths from 3.5 inches
  (paperback) to 4 inches (hardback). The average reading distance for
  a book is about 15 inches but it&#039;s 24 inches for a computer display. The same
  visual arc used when reading books covers a range of 5.6 inches to 6.4 inches on a monitor.
&lt;/p&gt;

&lt;p&gt;
  Given a targeted display size, we can determine the line length in
  pixels. For example, over the last four months, about 50% of the visitors
  to the Tiger Heron Web site used a 1024 x 768 display. Guessing a
  17 inch display size, we get a pixel density of 75 pixels-per-inch. So
  our 5.6 inch to 6.4 inch range becomes 420 to 480 pixels. With a 12-pixel
  Verdana font, this yields from 53 to 60 CPL. Larger displays could
  accommodate more characters within the same visual arc.
&lt;/p&gt;

&lt;/div&gt;

&lt;h2&gt;Set the leading&lt;/h2&gt;

&lt;p&gt;
  Leading is the typesetter&#039;s term for the line-to-line spacing.
  Studies&lt;sup&gt;&lt;a href=&quot;#c3&quot;&gt;3&lt;/a&gt;&lt;/sup&gt; indicate that tight leading doesn&#039;t affect
  reading speed or comprehension, but people still find it
  uncomfortable. On sites where information density is of primary
  importance, you may opt to use tight leading. I&#039;ve found a
  1.2 to 1.4 range works well for comfortable reading.
&lt;/p&gt;

&lt;h2&gt;Use an appropriate amount of white space&lt;/h2&gt;

&lt;p&gt;
  The usability studies I&#039;ve seen have been contradictory on the topic
  of white space. For example, one study&lt;sup&gt;&lt;a href=&quot;#c4&quot;&gt;4&lt;/a&gt;&lt;/sup&gt;
  found that reducing white space also reduced the time it took for
  people to locate information on a Web site. A second study&lt;sup&gt;&lt;a
  href=&quot;#c5&quot;&gt;5&lt;/a&gt;&lt;/sup&gt;, however, found that it also decreased
  comprehension. I suspect that the results in the first study,
  conducted in 2002, were due to the advantage of squeezing more
  information onto a small screen.
&lt;/p&gt;

&lt;p&gt;
  My advice on whether to increase or decrease white space depends on
  the amount of time a visitor is expected to spend on a page. Blogs
  should use white space to increase the readability and appeal of a
  page. A search results page, on the other hand, could sacrifice
  white space to increase the useful content on the screen.
&lt;/p&gt;

&lt;h2&gt;Center the design&lt;/h2&gt;

&lt;p&gt;
  &lt;span class=&quot;floatRight&quot;&gt;
    &lt;a href=&quot;http://www.csszengarden.com/?cssfile=/185/185.css&amp;amp;page=2&quot;&gt;
      &lt;img src=&quot;/files/blogs/designer/node43/left-aligned.png&quot; alt=&quot;A left-aligned design&quot; title=&quot;&quot; height=&quot;183&quot; width=&quot;300&quot; onload=&quot;imageSizeToEms(this, pixelToEms)&quot;&gt;
    &lt;/a&gt;
    &lt;span class=&quot;imgCaption&quot;&gt;A left-aligned design from the
    &lt;a href=&quot;http://www.csszengarden.com/&quot;&gt;CSS Zen Garden Web site &lt;/a&gt;&lt;/span&gt;
  &lt;/span&gt;
  I was a fan of left-aligned designs right up until I purchased my
  24-inch 1920x1200 display. Now I&#039;m a fan of centered designs. When I
  maximize the browser window, a left-aligned design puts the content
  uncomfortably on the left. I prefer to maximize the window to focus on a page
  without distractions. In the case of left-aligned designs,however, I can
  only center them if the window is not maximized, which reveals the
  background clutter.
&lt;/p&gt;

&lt;h2&gt;Integrate the design with the background&lt;/h2&gt;

&lt;p&gt;
  A fixed-width design in a large or maximized window is going to have
  some unused area. This area is sometimes ignored, but it should be
  treated as part of the overall design. It can be left plain when
  appropriate to the site. I tend to spend more time on pages with
  visually exciting designs.
&lt;/p&gt;

&lt;p&gt;
  Two techniques that work well for me. Perhaps you have others?
&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;
    Compose the design so that the page looks like a piece of paper on
    a desk. Shading or a complementary background pattern (or both)
    can improve the visual appearance.&lt;br&gt;
    &lt;span class=&quot;captionedImage&quot;&gt;
    &lt;a href=&quot;http://www.csszengarden.com/?cssfile=194/194.css&quot;&gt;&lt;img src=&quot;/files/blogs/designer/node43/css%20zen%20garden%203%201920x1200.jpg&quot; alt=&quot;A paper-on-desk style design&quot; title=&quot;&quot; height=&quot;183&quot; width=&quot;300&quot; onload=&quot;imageSizeToEms(this, pixelToEms)&quot;&gt;&lt;/a&gt;&lt;br&gt;
    &lt;span class=&quot;imgCaption&quot;&gt;A paper-on-desktop style design from the &lt;a href=&quot;http://www.csszengarden.com/&quot;&gt;CSS Zen Garden Web site&lt;/a&gt;&lt;/span&gt;
    &lt;/span&gt;
  &lt;/li&gt;

  &lt;li style=&quot;clear: both;&quot;&gt;
    Use design elements (e.g. banners, footers) that extend the full
    width of the browser window.&lt;br&gt;
    &lt;span class=&quot;captionedImage&quot;&gt;
    &lt;a href=&quot;http://osc.templatemonster.com/wordpress_11732/?cat=5&quot;&gt;&lt;img src=&quot;/files/blogs/designer/node43/ART%201920x1200.jpg&quot; alt=&quot;A fixed-width design with some stretchable elements&quot; title=&quot;&quot; height=&quot;183&quot; width=&quot;300&quot; onload=&quot;imageSizeToEms(this, pixelToEms)&quot;&gt;&lt;/a&gt; &lt;br&gt;
    &lt;span class=&quot;imgCaption&quot;&gt;A WordPress fixed-width design with some
    stretchable elements (from &lt;a href=&quot;http://www.templatemonster.com/&quot;&gt;TemplateMonster&lt;/a&gt;)&lt;/span&gt;
    &lt;/span&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;h2 style=&quot;clear: both;&quot;&gt;Keep the content area at least the full height of the screen&lt;/h2&gt;

&lt;p&gt;
  Fixed-width designs with little content tend to look weak and
  insubstantial (in slang, &quot;lame&quot;). If all site pages have a lot of
  content, then you don&#039;t need to do anything to overcome this
  problem.
&lt;/p&gt;

&lt;p&gt;
  Here&#039;s an example of a fixed width design (from my ISP&#039;s Web site,
  &lt;a href=&quot;http://www.iinet.com&quot;&gt;iinet.com&lt;/a&gt;). It looks OK in an
  800x600 window:
&lt;/p&gt;

&lt;p class=&quot;captionedImage&quot;&gt;
  &lt;img src=&quot;/files/blogs/designer/node43/Fixed%20800x600.jpg&quot; alt=&quot;Sample low-content site at 800x600&quot; title=&quot;&quot; height=&quot;225&quot; width=&quot;300&quot; onload=&quot;imageSizeToEms(this, pixelToEms)&quot;&gt;
&lt;/p&gt;

&lt;p&gt;
  Maximized on my 1920x1200 display, it looks as though the designer
  left before completing the page.
&lt;/p&gt;

&lt;p class=&quot;captionedImage&quot;&gt;
  &lt;img src=&quot;/files/blogs/designer/node43/Fixed%20Left%201920x1200.jpg&quot; alt=&quot;The same site on a 1920x1200 display&quot; title=&quot;&quot; height=&quot;183&quot; width=&quot;300&quot; onload=&quot;imageSizeToEms(this, pixelToEms)&quot;&gt;
&lt;/p&gt;

&lt;p&gt;
  The easiest solution is to create a content area with 100% height
  and fill it with a pattern or color. What I prefer to do, however,
  is to use some CSS magic to keep a footer at the lower part of the window
  or content bottom. SolarDreamStudios has a &lt;a
  href=&quot;http://solardreamstudios.com/learn/css/footerstick/&quot;&gt; nice
  tutorial&lt;/a&gt; with samples. I&#039;ve tested their technique on IE6, IE7,
  Firefox 2 and Opera 9. It works on all but Opera&amp;mdash;on Opera it
  works sporadically (in my testing, it fails when the window is
  resized vertically, but fixes itself if you resize horizontally).
  An alternate approach is to use Javascript as described in &lt;a
  href=&quot;http://alistapart.com/articles/footers&quot;&gt;this article&lt;/a&gt; on
  &lt;cite&gt;A List Apart&lt;/cite&gt;.&lt;/p&gt;
&lt;p&gt;
  Below, I&#039;ve taken the same design and moved a few elements to the
  bottom. Although it still has the same content, the site looks much
  more substantial.
&lt;/p&gt;

&lt;p class=&quot;captionedImage&quot;&gt;
  &lt;img src=&quot;/files/blogs/designer/node43/Fixed%20Fake%20Stretched%201920x1200.jpg&quot; alt=&quot;The previous design, stretched to fill the height&quot; title=&quot;&quot; height=&quot;183&quot; width=&quot;300&quot; onload=&quot;imageSizeToEms(this, pixelToEms)&quot;&gt;
&lt;/p&gt;

&lt;h2&gt;Avoid large expanses of undifferentiated text&lt;/h2&gt;

&lt;p&gt;
  Without contrast, long areas of text give the eye nothing to use as
  a reference point and prove unappealing to viewers. Print designers
  are familiar with this. On the Web, designers sometimes stop
  designing when the page template is complete; someone else takes
  care of providing content. Sites designed this way are sometimes
  easy to spot&amp;mdash;they have a lovely layout wrapped around a mass of
  text.
&lt;/p&gt;

&lt;p&gt;
  One of the main advantages of a fixed-width design is the ability to
  fully lay out the page. We should take advantage of this
  opportunity.
&lt;/p&gt;

&lt;h1&gt;References&lt;/h1&gt;
&lt;ol class=&quot;references&quot;&gt;
&lt;li&gt;&lt;a name=&quot;c1&quot;&gt;&lt;/a&gt;&lt;cite&gt;&lt;a href=&quot;http://www.amazon.com/Web-Site-Usability-Designers-Guide/dp/0966064100&quot;&gt;Web Site Usability, A Designer&#039;s Guide&lt;/a&gt;&lt;/cite&gt;, Jared M. Spool and Tara Scanlon&lt;/li&gt;
&lt;li&gt;&lt;a name=&quot;c2&quot;&gt;&lt;/a&gt;&lt;cite&gt;&lt;a href=&quot;http://psychology.wichita.edu/surl/usabilitynews/72/LineLength.htm&quot;&gt;The Effects of Line Length on Reading Online News&lt;/a&gt;&lt;/cite&gt;, A. Dawn Shaikh&lt;/li&gt;
&lt;li&gt;&lt;a name=&quot;c3&quot;&gt;&lt;/a&gt;&lt;cite&gt;&lt;a href=&quot;http://psychology.wichita.edu/surl/usabilitynews/62/whitespace.htm&quot;&gt;Reading Online Text: A Comparison of Four White Space Layouts&lt;/a&gt;&lt;/cite&gt;, Barbara Chaparro, J. Ryan Baker, A. Dawn Shaikh, Spring Hull and Laurie Brady&lt;/li&gt;
&lt;li&gt;&lt;a name=&quot;c4&quot;&gt;&lt;/a&gt;&lt;cite&gt;&lt;a href=&quot;http://www.amazon.com/Web-Site-Usability-Designers-Guide/dp/0966064100&quot;&gt;Web Site Usability, A Designer&#039;s Guide&lt;/a&gt;&lt;/cite&gt;, Jared M. Spool and Tara Scanlon&lt;/li&gt;
&lt;li&gt;&lt;a name=&quot;c5&quot;&gt;&lt;/a&gt;&lt;cite&gt;&lt;a href=&quot;http://psychology.wichita.edu/surl/usabilitynews/72/LineLength.htm&quot;&gt;The Effects of Line Length on Reading Online News&lt;/a&gt;&lt;/cite&gt;, A. Dawn Shaikh&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;Related reading&lt;/h2&gt;
&lt;ul class=&quot;references&quot;&gt;
&lt;li&gt;&lt;cite&gt;&lt;a href=&quot;http://psychology.wichita.edu/surl/usabilitynews/42/text_length.htm&quot;&gt;The Effects of Line Length on Children and Adults&#039; Online
Reading Performance&lt;/a&gt;&lt;/cite&gt;, By Michael Bernard1, Marissa Fernandez, &amp;amp; Spring Hull&lt;/li&gt;
&lt;li&gt;&lt;cite&gt;&lt;a href=&quot;http://www.humanfactors.com/downloads/nov02.asp&quot;&gt;Optimal Line Length&lt;/a&gt;&lt;/cite&gt;, Bob Bailey&lt;/li&gt;
&lt;li&gt;&lt;cite&gt;&lt;a href=&quot;http://psychology.wichita.edu/surl/usabilitynews/71/page_setting.html&quot;&gt;Reading Online Text with a Poor Layout: Is Performance Worse?&lt;/a&gt;&lt;/cite&gt;,
Barbara S. Chaparro, A. Dawn Shaikh and J. Ryan Baker&lt;/li&gt;
&lt;li&gt;&lt;cite&gt;&lt;a href=&quot;http://www.ischool.utexas.edu/~adillon/Journals/Reading.htm&quot;&gt;Reading from paper versus screens: a critical review of the empirical literature&lt;/a&gt;&lt;/cite&gt;, Andrew Dillon&lt;/li&gt;
&lt;/ul&gt;
</description>
 <comments>http://www.tigerheron.com/article/2007/05/recommendations-improving-fixed-width-designs#comments</comments>
 <category domain="http://www.tigerheron.com/category/graphic-design">graphic design</category>
 <category domain="http://www.tigerheron.com/category/tutorial">tutorial</category>
 <category domain="http://www.tigerheron.com/category/web-design">Web design</category>
 <pubDate>Fri, 25 May 2007 03:19:12 +0000</pubDate>
 <dc:creator>designer</dc:creator>
 <guid isPermaLink="false">43 at http://www.tigerheron.com</guid>
</item>
</channel>
</rss>
