While working at vision australia I presented at Web Essentials 05 on the HTML title attribute, which lead to a right royal fisking by Joe Clark. I also conducted research on screen reader support and how it (title attribute) was accessed by user’s. These documents became unavailable due to hosting issues. As requested by a few people, I have now made them available again:
- The title attribute – what is it good for?
- Assistive technology users test title attribute access
- Screen reader software support for the title attribute
Comments
Brilliant, thanks for reposting Steve – I often point people to your article and had wondered where it had gone.
no problem Heni! Even though the documents are a few years old, they still provide some useful information (I think). 🙂
Faulkner–
If what Clark is saying that use of the
titleattribute is warranted whether or not a specific user agent supports it, I would have to agree.One of the things that I continually struggle with accessibility is how to communicate perception. Perception is a very substantive part of communication. Imagery is a part of that within design. The
altattribute, from my perspective, should be used to convey a brief description that relays the perception of what the image is attempting to convey. Thetitleattribute is then used to provide succinct image information.I, also, contend that use of the
titleattribute for links has merit particularly when notification of external links and links that open within a new window is warranted. Albeit, additional alternatives should be used in conjunction with it.I have a problem with relying upon a sole method that provides necessary information for either design perceptions or for orientation.
Reliance upon one or a few user agents and their interpretations just doesn’t make sense.
Thacker wrote:
In terms of accessibility the use of the title attribute for this purpose just doesn’t cut it. keyboard access to title attribute content is practically non existent in all browsers (you can access the content in Firefox, but it requires a series of key strokes, and there is no indication prior to interrogation that a title is present, which doesn’t offer equivalency of access with mouse users).
Imprtant information such as if the link opens in a new window needs to be available to all, not just mouse users.
I can’t speak for Joe Clark on this subject, but the recently released WCAG Samuri errata are clear on the matter:
Faulkner–
You get no argument out of me on what you stated above, except for the quote out of context. It does contain a stated caveat, “[…] additional alternatives should be used in conjunction with it.”
What prompted my post was and remains the constant struggle that I face [am sure I am not alone] with accessibility recommendations [Best Practices] … there is no authority that exists or has been published of which I am aware that is comprised solely by those with disabilities on what they need and want.
I am not dismissing you, your disability nor your knowledge. I am just stating that most accessibility recommendations are similar to a Cheney/ Rumsfield analysis of strategy planning for US foreign policy … we all know where that goes.
I am not sure that building accessibility content based upon current state of the art of user agent ability and implementation will create a functional accessible Web for all users. Therefore, my technique of using built-in redundancies on everything.
In all probability, I am wrong.
Thacker wrote:
As a user of one of the few screen readers that does support the TITLE attribute, I’d be very glad to see an end to redundancy. On links I get to hear both the link text and TITLE attribute, The principle being that the TITLE was meant for additional information. Unfortunately it’s rarely used for this, so what is delivered is the link text twice, and because there’s no space between the end of the TITLE value and the beginning of the link text, the last word and first word get joined in the middle. This can seriously spoil the principle of clear link text, for instance a simple link like “Hot hits” is announced as “Hot hitshot hits”. That’s an easy one to decipher, but perhaps it illustrates why redundancy isn’t always good.
Please excuse, the first paragraph of my above comment should have cited Thacker, I must have got my BLOCKQUOTE wrong. 🙁
no worries Bim, have fixed it 🙂
Bim–
As stated, ‘Best Practices” for accessibility between user agents simply doesn’t exist.
Perhaps part of the problem as you describe between link text and the
titleattribute exist in how developers use them. Perhaps, too, screen readers would do well to identify and take advantage of all punctuation when it exists [all informative elements should include punctuation], including use of punctuation within and attributes.Also, redundancy and repetition are not one in the same.
Hey Steve, thanks for reposting your 2005 preso, which was (for me) one of the most informative preso’s on the misconceptions surrounding the title attribute. I had bookmarked the old link from WE05 – but it looks like the old WE05 site is long gone….
Thanks again!