- From: Gregg Vanderheiden <gv@trace.wisc.edu>
- Date: Thu, 30 Oct 2003 13:42:42 -0600
- To: 'David MacDonald' <befree@magma.ca>, w3c-wai-gl@w3.org
- Message-id: <009601c39f1d$fc4bcd40$ae17a8c0@USD320002X>
Ahhh Thanks. Boy - we should make a list of these. Decisions that we made based on what works rather than what we wished or thought best. Then at the end we can walk this carefully to be sure we are happy with these "until user agent" like decisions. Thanks David Gregg -- ------------------------------ Gregg C Vanderheiden Ph.D. Professor - Ind. Engr. & BioMed Engr. Director - Trace R & D Center University of Wisconsin-Madison -----Original Message----- From: David MacDonald [mailto:befree@magma.ca] 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 <http://www.eramp.com/> 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 <http://www.eramp.com/> www.eramp.com
Received on Thursday, 30 October 2003 14:42:49 UTC