This is interesting, but a rather pragamitc approach? Are we changing
our coding practice to suit the technological limitations of current
user agents. Is some of the power of a standards based approach the idea
that we do what is considered best practise given the current standards?
I use titles where possible because the spec allows for them and I can
see them adding value to an image (a link less so?) for certain user
groups. If jaws chooses to lock this information away in a preference,
then this is unfortunate, but when the next screen reader that does
honour this form of content comes along perhaps its market share will
grow accordingly.
I am not necessarily arguing that the spec is right - to a large extent
I agree that content belongs in the document where it can be seen/read,
but how do we link them meaningfully?
Stephen mentioned the label element which at the moment AFAIK is only
linked to a form control. Other elements such as caption and legend
exist to perform a similar role. Perhaps a more generic role for the
label element would be good, adding a rel attribute to describe the
relationship the label has to the associated element?
Kim Kruse wrote:
Hi Christian,
From: http://www.sf.id.au/WE05/indexa.html
* Users that rely upon the keyboard to access web content cannot
access the TITLE text.
* Some users of screen magnifiers will not be able to read the
TITLE text.
* Most users of screen reader software will not be aware of the
TITLE text, some will not be not able to read the TITLE text even if
they know it is there.
I used to have this misconception about title attributes too, that I
could assume every browser displayed them the same and screen readers
would read them. That's not the case. Now I hardly use title
attributes, and instead I put the content into the document where it
belongs.
Excellent. Thanks for the explanation :)
Kim
--
--
Christian Montoya
christianmontoya.com ... rdpdesign.com ... cssliquid.com
******************************************************
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
******************************************************
******************************************************
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
******************************************************
