- From: Charles F. Munat <chas@munat.com>
- Date: Thu, 17 Jan 2002 10:29:53 -0800
- To: kynn-eda@idyllmtn.com
- Cc: w3c-wai-ig@w3.org
Forget to take your medicine again, Kynn? Here is what I meant by my questions: Which browsers or AT support longdesc and how do they indicate that a longdesc is available? How does one follow the longdesc to the image description? I'm not sure how I could make them any clearer. Though the questions were posed in response to your post, they were posted to the list, not to you personally. The reason is simple: I don't know the answers and I think it is important to know. I can't evaluate how the presence of a longdesc description should be indicated until I know how longdesc is implemented. To paraphrase Freud: Sometimes a question is just a question... Charles F. Munat Seattle, Washington kynn-eda@idyllmtn.com wrote: > Charles Munat wrote: > >>kynn-eda@idyllmtn.com wrote: >> >>>Therefore, anything which has a longdesc SHOULD be explicitly >>>identified as an image, and thus the user should expect to look for >>>further description of that image via longdesc links. >>> > >>Which browsers or AT support longdesc and how do they indicate that a >>longdesc is available? How does one follow the longdesc to the image >>description? >> > > I'm not sure what you're getting at here. Are you saying that longdesc > attributes should not be used, because there is not AT support? Or are > you going to claim you are not asking leading questions, and you really > do desire to know information on longdesc? > > I guess mainly this post is about how I don't like Mr. Munat's method > of attack and debate, rather than anything else. Someone who is more > expert in AT is free to answer the questions of why and how assistive > technologies comply with the W3C HTML 4.01 (et al) specifications. > > --Kynn > > >
Received on Thursday, 17 January 2002 13:28:36 UTC