W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > October to December 2003

RE: [TECHS] Londesc paragraph, and Text based menus

From: John M Slatin <john_slatin@austin.utexas.edu>
Date: Thu, 30 Oct 2003 09:03:19 -0600
Message-ID: <C46A1118E0262B47BD5C202DA2490D1A1DFB7A@MAIL02.austin.utexas.edu>
To: "David MacDonald" <befree@magma.ca>, <gv@trace.wisc.edu>, <w3c-wai-gl@w3.org>, "Wendy A Chisholm" <wendy@w3.org>
Cc: "Michael Cooper" <michaelc@watchfire.com>, "Ben Caldwell" <caldwell@trace.wisc.edu>
Speaking strictly for myself, I don't see much use for the LONGDESC
attribute where the <frame> element is concerned-- I've never found
myself wanting such a description.  I agree with David that the title
attribute is more important, and it seems to me that all three of the
tools mentioned-- IBM Home Page Reader, Window-Eyes, and JAWS-- do now
support the title attribute for frames.  So I think we're good there.
 
John
 
 


"Good design is accessible design." 
Please note our new name and URL!
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/> 


 

-----Original Message-----
From: w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org] On
Behalf Of David MacDonald
Sent: Wednesday, October 29, 2003 11:08 pm
To: gv@trace.wisc.edu; w3c-wai-gl@w3.org; 'Wendy A Chisholm'
Cc: 'Michael Cooper'; 'Ben Caldwell'
Subject: RE: [TECHS] Londesc paragraph, and Text based menus



Hi Gregg

[Tech doc] Longdesc works fine for Images etc. We wouldn't deprecate
that use of LongDesc in "straight" documents. It is when the Londesc
command is used to describe frames where its support breaks up.  So it
is only as a description of Frames where we are not recommending it.  At
this point WindowEyes, Jaws and Home Page Reader don't have predictable
or clean support of Londesc in Frames. We've tested this quite
extensively.  I'd be fine with calling these companies up and lobbying
them for us.  (Perhaps I could get them to clean up with their flaky
"Title" attribute support also.)  If someone has some contact names I'd
be glad to pursue it in a nice and diplomatic way. (On the other hand,
it seems Frames are on their way out anyway)

Cheers

David MacDonald

=========================

 Access Empowers People...

       ...Barriers Disable Them

         www.eramp.com <http://www.eramp.com/> 

 

  _____  

From: Gregg Vanderheiden [mailto:gv@trace.wisc.edu] 
Sent: October 29, 2003 6:43 PM
To: 'David MacDonald'; w3c-wai-gl@w3.org; 'Wendy A Chisholm'
Cc: 'Michael Cooper'; 'Ben Caldwell'

 

Looks good.

By the way. If you don't use Longdesc - what do you use?

 For pictures - longdesc can be required as level 1 but d-link cannot.
So if you recommend against longdesc, then we must make  descriptions be
level 2 items.     (unghh)

We really should get longdesc supported!!!.   

Also, this is one of those things where - if we recommend against
longdesc, are we tailoring our recommendations based on bad user agents?

 

Hmmmmmm.  Tough one.

 


Gregg

 -- ------------------------------ 
Gregg C Vanderheiden Ph.D. 
Professor - Ind. Engr. & BioMed Engr.
Director - Trace R & D Center 
University of Wisconsin-Madison 

-----Original Message-----
From: w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org] On
Behalf Of David MacDonald
Sent: Wednesday, October 29, 2003 5:16 PM
To: w3c-wai-gl@w3.org; 'Wendy A Chisholm'
Cc: 'Michael Cooper'; 'Ben Caldwell'
Subject: [TECHS] Londesc paragraph, and Text based menus

 

I was to write two paragraphs on the use of long descriptions in frames
and 

Long Descriptions in Frames:

The use of "Longdesc" (Long Description) in Frames is not recommended
because the "Longdesc" command is currently not well supported by User
Agents.

Here is a paragraph on Text Based Menus: 

Although graphical based menus are accessible when "alt text" is used,
there are advantages to creating menus that are completely text based.
Graphical text is not easily scalable. The size of graphical text cannot
be increased easily by those who may need a larger font. Alternatively,
text based menus allow for relative font sizes to be used on menu links.
Relative font sizes can be easily increased in most browsers without the
use of assistive technology. (WCAG Principle, Perceivable)

Cheers

David MacDonald

=========================

Access Empowers People...

       ...Barriers Disable Them

        www.eramp.com <http://www.eramp.com/> 

 
Received on Thursday, 30 October 2003 10:03:21 GMT

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