BillyRayPreachersSon
Programmer
I'd like to find out what the general consenus is for wording of anchor title attributes from an accessibility perspective.
I've read many sites that show how they would do things, but none seem to list good arguments for having the titles their way.
At present, on the site we're building, all links have attributes that begin with "This link takes you to", and then a description of the page. If the link points to an external site, the name of the site is appended.
For example:
- an internal link to the "About us" page would have link text saying "About us", and a title attribute of "This link takes you to the 'About us' page"
- an external link to the "National Weather Maps" page would have link text saying "National Weather Maps", and a title attribute of "This link takes you to the 'National Weather Maps' page of the Met Office website"
However, you can't please all of the people all of the time. It has been mooted that the title attributes should have only the simple text contained in the link ("About Us", "What we do", etc)... but this seems pretty pointless to me. After all - if the title attribute were only to repeat the link text, there'd be no point in having it.
As far as I am concerned, title attributes should be descriptive. They should give the user a description of what activating the link will do, or where it will take them. Notice I say "activating", because the user will not always be clicking (voice recognition, keyboard users, etc - which is why I have avoided using "Click this link to..." at the beginning of the title attribute).
But, some people might view the title attibutes I've proposed as being too long and unweidly.
I realise that for screen readers, having a whole navigation structure read out with long descriptions each beginning with "This link takes you to..." might be a bit of a pain, but AFAIK, readers like JAWS don't enable this option by default.
So - what do I do? Keep the long "This link takes you to..." structure? Have a pointless simple structure ("About us", etc), or is there a happy medium?
Thanks!
Dan
[tt]Dan's Page [blue]@[/blue] Code Couch
[/tt]
I've read many sites that show how they would do things, but none seem to list good arguments for having the titles their way.
At present, on the site we're building, all links have attributes that begin with "This link takes you to", and then a description of the page. If the link points to an external site, the name of the site is appended.
For example:
- an internal link to the "About us" page would have link text saying "About us", and a title attribute of "This link takes you to the 'About us' page"
- an external link to the "National Weather Maps" page would have link text saying "National Weather Maps", and a title attribute of "This link takes you to the 'National Weather Maps' page of the Met Office website"
However, you can't please all of the people all of the time. It has been mooted that the title attributes should have only the simple text contained in the link ("About Us", "What we do", etc)... but this seems pretty pointless to me. After all - if the title attribute were only to repeat the link text, there'd be no point in having it.
As far as I am concerned, title attributes should be descriptive. They should give the user a description of what activating the link will do, or where it will take them. Notice I say "activating", because the user will not always be clicking (voice recognition, keyboard users, etc - which is why I have avoided using "Click this link to..." at the beginning of the title attribute).
But, some people might view the title attibutes I've proposed as being too long and unweidly.
I realise that for screen readers, having a whole navigation structure read out with long descriptions each beginning with "This link takes you to..." might be a bit of a pain, but AFAIK, readers like JAWS don't enable this option by default.
So - what do I do? Keep the long "This link takes you to..." structure? Have a pointless simple structure ("About us", etc), or is there a happy medium?
Thanks!
Dan
[tt]Dan's Page [blue]@[/blue] Code Couch
[/tt]