W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > January to March 2006

RE: technique to overcome meaningful link text

From: John M Slatin <john_slatin@austin.utexas.edu>
Date: Fri, 13 Jan 2006 10:07:11 -0600
Message-ID: <6EED8F7006A883459D4818686BCE3B3B01248D46@MAIL01.austin.utexas.edu>
To: "Loretta Guarino Reid" <lguarino@adobe.com>, "David MacDonald" <befree@magma.ca>, "WCAG" <w3c-wai-gl@w3.org>
Loretta wrote:
 
<blockquote... .). AT would need to provide an option to use the title
text in lists of links, to make this most effective.

</blockquote>JAWS allows users to choose between alt and title (for
images and image links) or screen text and time (for text links). Or you
can choose "longest" in both cases. Currently these are global settings,
and they are binary: you get *either* alt or titlebut not both. Same for
text links: either screen text or title, but not both.
 
I have sent a feature request to Freedom Scientific asking them to
support both/and instead of either/or, both as a global setting and as
an on-demand option.
 
I'm not sure about Window-Eyes, HAL, or Home Page Reader. Will try to
check.
However, I believe the techniques Loretta and Michael describe *should*
be sufficient because they *should* be supported by AT.
 
UT Austin is testing a new version of its home page, and they are using
a CSS stye class="nodisplaytext" which seems to make the text invisible
but audible in JAWS.
I'm going to ask them if they'll show me the style sheet 'cause I don't
understand how it works and would like to!
 
John
 
 
Joh

"Good design is accessible design." 
John Slatin, Ph.D.
Director, Accessibility Institute
University of Texas at Austin
FAC 248C
1 University Station G9600
Austin, TX 78712
ph 512-495-4288, f 512-495-4524
email jslatin@mail.utexas.edu
web http://www.utexas.edu/research/accessibility/
<http://www.utexas.edu/research/accessibility/> 


 

 


________________________________

	From: w3c-wai-gl-request@w3.org
[mailto:w3c-wai-gl-request@w3.org] On Behalf Of Loretta Guarino Reid
	Sent: Friday, January 13, 2006 9:43 am
	To: David MacDonald; WCAG
	Subject: Re: technique to overcome meaningful link text
	
	
	As a technique, I don't really like this much. Images of text
can't satisfy lots of UA requirements for text, like the ability to
resize the text or control the font used.
	
	Fundamentally, though, I get the sense that the group is
converging on requiring meaningful link text, directly associated with
the link, not in its  surrounding context. We would opt for having a
verbose reading of the links as the page is being read (which is what
would happen with this technique).
	
	In that case, shouldn't we recommend using the title of the link
to specify the complete text? (In PDF, we can provide Alt text for the
link, but we need an HTML technique, too). AT would need to provide an
option to use the title text in lists of links, to make this most
effective.
	
	Loretta
	
	
	On 1/12/06 4:06 PM, "David MacDonald" <befree@magma.ca> wrote:
	
	

		
		I think this technique (below) could also be used for
single word links like "more" and "click here" in those instances when
one word links might be appropriate. 
		 
		If this is ok with the group I think we could overcome
the "justified" exceptions for meaningful links.
		 
		This is a proposed technique for how to create
meaningful link text for SC 2.4.5. when there is an array of links to
multiple versions of the same content. I hope this overcomes the
exception for arrays of links. 
		 
		1)       Create images of text that say "HTML", "PDF",
"XML" etc.
		2)       Create links from the images of text to the
corresponding documents.
		3)       Create "alt text" using meaningful descriptions
of the corresponding destinations for each of the images.
		I think the technique could also be written in a
non-technology specific format.
		Regards
		David MacDonald
		...Access empowers people
		           ...barriers disable them...
		www.eramp.com <http://www.eramp.com>
<http://www.eramp.com>  
		
		
		

	
	
Received on Friday, 13 January 2006 16:07:21 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:42 GMT