28.06.2013 Views

Papers in PDF format

Papers in PDF format

Papers in PDF format

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

the navigation tools from every document <strong>in</strong> your web site.<br />

The l<strong>in</strong>ks to the navigation tools should be clearly labeled and consistently located. While some icons are likely to be<br />

recognized by most people, most graphical symbols that stand for abstract concepts are ambiguous, unclear, and even<br />

mislead<strong>in</strong>g. You may th<strong>in</strong>k that users can learn what your icons represent, but you shouldn't depend on it: always label<br />

your icons with helpful text.<br />

If all of your documents are very brief (about one screenful), then you can place the l<strong>in</strong>ks to your navigation tools at the<br />

beg<strong>in</strong>n<strong>in</strong>g or end (consistently one place or the other!) of each document. If many of your documents are two or more<br />

screenfuls <strong>in</strong> length, then I recommend that you place l<strong>in</strong>ks to your navigation tools at both the beg<strong>in</strong>n<strong>in</strong>g and end of<br />

each document.<br />

L<strong>in</strong>k to the Home Page and Reference Pages of Your Web Site<br />

It is customary to offer a l<strong>in</strong>k to the first document (home page) of your web site as a navigation aid. Users expect to be<br />

able to orient themselves by return<strong>in</strong>g to this top-level document because good home pages typically provide useful<br />

<strong>in</strong><strong>format</strong>ion about and l<strong>in</strong>ks <strong>in</strong>to the web site.<br />

If your web site provides other documents dom<strong>in</strong>ated by useful l<strong>in</strong>ks--reference tables for example--you can help users<br />

by offer<strong>in</strong>g standard l<strong>in</strong>ks to those documents along with your other navigation tools.<br />

When To Use "Previous" and "Next" L<strong>in</strong>ks<br />

Many web sites are easy to organize <strong>in</strong>to a l<strong>in</strong>ear sequence because that is how they were conceived and implemented. If<br />

your site provides <strong>in</strong><strong>format</strong>ion <strong>in</strong> a well-def<strong>in</strong>ed order, and if this order is necessary for users to obta<strong>in</strong> full benefit from<br />

your site, then a "previous" l<strong>in</strong>k at the beg<strong>in</strong>n<strong>in</strong>g of the document and a "next" l<strong>in</strong>k at the end of the document is<br />

appropriate.<br />

However, just because you can def<strong>in</strong>e a sequence for all the documents <strong>in</strong> your site does not mean that you should<br />

<strong>in</strong>clude previous and next l<strong>in</strong>ks. These l<strong>in</strong>ks imply to users that the l<strong>in</strong>ear sequence is important for understand<strong>in</strong>g the<br />

material. You should <strong>in</strong>clude them only if this is true.<br />

A Table of Contents is Highly Recommended<br />

A table of contents is an almost universally understood navigation tool. It outl<strong>in</strong>es any body of work by list<strong>in</strong>g<br />

document titles, head<strong>in</strong>gs, and sometimes subhead<strong>in</strong>gs. Low-level subhead<strong>in</strong>gs are normally not <strong>in</strong>cluded <strong>in</strong> the table of<br />

contents because they can expand the table of contents to an unwieldy length.<br />

Many users who are new to hypertext documentation feel welcome when they f<strong>in</strong>d a web site's table of contents because<br />

it is comfortable and familiar to them. It also helps <strong>in</strong>troduce them to the benefits of hypertext l<strong>in</strong>ks because they no<br />

longer have to look for page numbers to f<strong>in</strong>d the <strong>in</strong><strong>format</strong>ion they need.<br />

The l<strong>in</strong>ear-sequence model of your web site provides your table of contents.<br />

You can add levels of mean<strong>in</strong>g to your table of contents by <strong>in</strong>dent<strong>in</strong>g subord<strong>in</strong>ate or support<strong>in</strong>g titles and head<strong>in</strong>gs<br />

under the more general titles and head<strong>in</strong>gs. An <strong>in</strong>dented table of contents maps perfectly to a hierarchy chart, and vice<br />

versa. That is, if you can organize your documents <strong>in</strong>to an <strong>in</strong>dented table of contents or a hierarchy chart, then you can<br />

and should! provide both for your users.<br />

Hierarchy Charts Offer Numerous Benefits<br />

Hierarchy charts may differ from tables of contents <strong>in</strong> the amount of l<strong>in</strong>ks they provide. Hierarchy charts can provide a<br />

spatially organized overview of an entire web site: users can see the structure of the site <strong>in</strong> a s<strong>in</strong>gle overview. And<br />

through image mapp<strong>in</strong>g, you can let users move directly to any document <strong>in</strong> the web site by po<strong>in</strong>t<strong>in</strong>g and click<strong>in</strong>g on<br />

the titles <strong>in</strong> the chart. But for larger web sites, there is no room for long titles or too many entries on the chart.<br />

So titles will need to be shortened for use on the chart. And more head<strong>in</strong>gs will probably need to be omitted. But even if

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!