RE: Link Text and Metadata

Johnny Appleseedd wrote:
<blockquote>


I meant to say that with screen readers, if link text is present, at
least 
with jaws, it will always be spoken instead of title.  If title is in
the 
search request and there is no link text, title will be spoken.
</blockquote>
Yes, that's the default behavior for JAWS. However, users can configure
JAWS to (a) read the title attribute instead of the screen text or (b)
read whichever is longer.  

I'm *hoping* that they will provide a new option to (c) read both screen
text and title when they are different.  (This option is already
available for form controls: JAWS can be configured to read the label
element and the title attribute when they're different.

John
Johnnie Apple Seed

----- Original Message ----- 
From: "Patrick H. Lauke" <redux@splintered.co.uk>
To: "WAI Interest Group" <w3c-wai-ig@w3.org>
Sent: Thursday, October 14, 2004 3:22 AM
Subject: Re: Link Text and Metadata



Matthew Smith wrote:

> My thinking is that using the extended description will allow the link

> to make sense, even if taken totally out of context.  Would this, 
> however, create confusing clutter?

I would go for a title that combines the normal link text and the
DC.description (as, depending on verbosity settings, I think that
certain screenreaders and user agents may only choose to announce the
link text or the title - so having the link text in both places would be
the belt and braces approach):

<a href="contact.html" title="Contact Us - contact information for xyz
company">Contact Us</a>

Patrick H. Lauke _____________________________________________________
re*dux (adj.): brought back; returned. used postpositively [latin : re-,
re- + dux, leader; see duke.] www.splintered.co.uk |
www.photographia.co.uk http://redux.deviantart.com

Received on Thursday, 14 October 2004 13:12:36 UTC