On Wed, Apr 28, 2010 at 6:07 PM, Dani Iswara <daniisw...@gmail.com>
wrote:
> In some blog machines/engines/themes, title attribute usually has
> the same text as in anchor link. Eg. in post title with
> rel="bookmark".  Redundant information, based on Web accessibility
> point of view. But
> http://www.w3.org/2003/12/semantic-extractor.html, Semantic Data
> Extractor tool built by W3C needs the title information for the
> bookmarkable points.
>
> So, is there a way to make it accessible and semantic properly?

Short answer: omit redundant "title" attributes.

The W3C hosts some formal standards endorsed by its membership
(Recommendations). But they also host a load of tools and documents
that have no special formal status. This tool is one of those.

I think you are being misled by a bad user interface decision on the
part of whomever built the tool.

When the tool says "[Unknown title]", I suspect it is telling you
that you have not added a "title" attribute to the link, not that
you /must/ or even /should/ add a title to the link.

If the developer *did* mean to tell you to add the attribute, then
they were wrong and trumped both by your users' needs (which should
always come first) and also by the formal Recommendations that tell
you how to use the "title" attribute".

The W3C HTML 4.01 Recommendation is clear: "title" provides
"advisory information about the element for which it is set":

   http://www.w3.org/TR/REC-html40/struct/global.html#adef-title

If you don't have any useful advisory information to add, then
"title" should be omitted or empty ("title=''").

In fact, because of the usability problems with common
implementations of "title", even if you do have useful advisory
information, it may not be the best place to put it.

    http://www.paciellogroup.com/blog/?p=37

--
Benjamin Hawkes-Lewis


*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
*******************************************************************

Reply via email to