Accessibility Tips A collection of tips, guidance, advice and practical suggestions in developing accessible websites

← Using titles on form fields

Avoiding redundant title attributes

The title attribute is one of the overlooked attributes in the HTML collection. It's most often used to mark up abbreviations with their expanded forms. Sometimes it's used to rout around Internet Explorer's tooltip behaviour of image alt attributes.

The attribute itself is meant to supply optional supplementary information. The most beneficial example is in conjunction with the abbr element, providing the knowing user with an expansion of an abbreviation. A second practical example is using it with forms to provide additional relevant information. (We also looked at using titles with form fields.)

But there are many examples of a title attribute being used to provide the same information that's already available and accessible. The most common example is links, especially in navigation you see the following piece of markup:


<a href="/sitemap/" title="Visit our sitemap">Sitemap</a>

Here the title attribute is just a plain duplication of the link text. Sure, it may have two extra words of Visit our which don't appear elsewhere, but this explains what a link does, and is just as redundant and irrelevant to site visitors. Most of them would need to have understood what a hypertext link is and what it does before even arriving at your site. Its just not necessary.

The extra text is a variant of the click here problem, it explains about how to activate a text link rather than succinctly describing the destination.

Some users have their screenreaders configured to read out both the link text and the title attribute. In this case, the above link would read out "Sitemap visit our sitemap", and either prefix that with the word "Link", or switch to a different voice to indicate the presence of a link. The duplication slows down the reading of the page, and is an unnecessary hiccup.

There is very little benefit to the title attribute in this code example. It is better, accessibility wise, to just drop the title attribute altogether in this instance.

Creating barriers for screen magnifiers

Screen magnifiers have the tendancy to make all title attributes appear when they have a titled element within the view of the magnifier. Any title, be it on a div, or a header, or a paragraph or a link, will appear in a tooltip like fashion. A significant use of titles may distract a screen magnifier user, even prevent them from seeing a particular piece of content because it has been obstructed by a tooltip.

There's just no positive accessibility benefit to using a title attribute to duplicate existing content. The title attribute. when it offers no extra value, hinders more than it helps.

April 14th, 2008 / 3 Comments / Tags: accessibility, screenreaders, screen magnifiers, title, links, redundant, understanding, configuration, duplicate / Trackback

Comments on “Avoiding redundant title attributes”

  1. Great post!

    Another point about titles is that by default screen readers like Jaws don't read them. You have to enable this feature. Which most people never do. So if a designer uses inappropriate link text and tries to fix this by using a title most users will never see/hear it.

    Also different browsers display differing amounts of the title text. So you can't even be sure that all of the text you put in a title will be seen by a user.

    Titles have their place but I think at the present time a lot of people are over/miss using them.

    Mark

    Mark McKay on April 18th, 2008 at 2:26 pm
  2. Hi, well, from an SEO perspective the title-attribute is very useful. It provides machine-readable content that fits into the context (both: context of the page and context of the linked site). It´s one of the most overlooked possibilities in onPge-SEO.

    So when I have to decide between SEO an accessibility, I choose SEO, of course. What about microformats? Can´t we use microformats to improve accessibility?

    Andre on May 7th, 2008 at 4:21 pm
  3. "What about microformats? Can´t we use microformats to improve accessibility?"

    As they currently stand, microformats do nothing to improve the accessibility of a page. In two particular cases, the abbr datetime pattern and its geo-location relative, the content added in the name of microformats actually creates an accessibility barrier to screen reader users who chose to take advantage of marked up abbreviations.

    Isofarro on May 12th, 2008 at 2:45 pm