Give your content context

Giving links purpose such that they can be under­stood when read out of context—a feature many screen readers offer—has long been an acces­si­bil­ity rec­om­men­da­tion. It’s comes as part of many acces­si­bil­ity guide­lines, includ­ing W3C’s WCAG 1.0 and of course also remains part of WCAG 2.0 (§ 2.4).

A common mistake in think­ing when approach­ing acces­si­bil­ity is that the work and time will only benefit a small number of your users. Quite the oppo­site: healthy font sizes, good con­trast between ele­ments and good descrip­tions for mul­ti­me­dia will benefit many more of your users.

This rec­om­men­da­tion does not only come from acces­si­bil­ity gurus; infor­ma­tion archi­tects think long and hard about the most appro­pri­ate and polit­i­cally correct attrib­utes for labels—it’s a must when con­cern­ing con­tex­tual links to ensure users end up where they expect to.

“To be more rep­re­sen­ta­tional of the content they connect to, con­tex­tual links rely instead upon, nat­u­rally, context. If the content’s author suc­ceeds at estab­lish­ing that context in his writing, then the label draws meaning from its sur­round­ing text. If he doesn’t, the label looses its rep­re­sen­ta­tional value, and users are more likely to expe­ri­ence occa­sion­ally rude surprises.”

Links aren’t the only labels that could do with a good descrip­tion. Section titles, head­ings and sub head­ings in par­tic­u­lar could benefit from good phrase­ol­ogy as these label the content that follows them. Users look to labels for struc­ture as they browse your content, in par­tic­u­lar helping skim readers who may be looking for a small scrap of infor­ma­tion buried deep on your page.

This respon­si­bil­ity however often falls from infor­ma­tion archi­tects to authors. Style guides (e.g. names should always link to profile cards) and aes­thetic visual dis­tinc­tions for content markers through good typog­ra­phy (known as hier­ar­chy) are the best ways of sup­port­ing authors in this process.

For more on hier­ar­chy and web typog­ra­phy see A Guide to Web Typog­ra­phy on iLT.

An example of typographic hierarchy

Fol­low­ing this think­ing, your can further add context to your links, labels and even obscure content through the page design and graph­ics. It may seem obvious to you that your website deals with your product or hobby topic, but con­sider a user landing on a page deep within your website. With strong direct linking to very spe­cific content you should not rely on the author who pro­vided the link to ensure the user knows exactly what they are in for.

3 comments

  1. 1. Alex Biddle
    Jun 21, 05:18

    And don’t use click here!

  2. 2. Jon Tan
    Jun 24, 21:20

    A good, valu­able summary Simon. Inter­est­ingly, we know headers as a hier­ar­chy as you rightly point out, but in the HTML5 draft they’re referred to as having a rank. Just one example where the tra­di­tional term is not prop­erly carried through to the Web. The terms should cor­re­spond better: “hierarchical rank”, perhaps.

  3. 3. Pascal
    Jun 24, 22:36

    @Jon Tan: Thanks.

    In the example above hier­ar­chy and rank have such similar mean­ings that they become almost inter­change­able and are bound to cause little confusion—but you are right.

    I think as time passes the tra­di­tional terms will begin to fade and be replaced with syn­onyms or “inventive” new terms. The Inter­net has created sit­u­a­tions (and occu­pa­tions) wherby many aca­d­e­mic fields overlap causing a blend of terms, some of which could cause embar­rass­ing and prob­lem­atic mis­un­der­stand­ings.

Post a comment

Please share your thoughts or add a note if I missed something.

Required fields are marked by an asterisk (*). Your e-mail address is never published nor shared. You can use common text formatting XHTML elements (e.g. a, acronym, blockquote, code, em, strong, …). If you’d like to directly respond and link to another comment, you can do that using the Twitter-style @reply (i.e., @Randy Bender: …).

*
*