- From: David Poehlman <poehlman@clark.net>
- Date: Tue, 17 Feb 1998 20:31:20 -0500 (EST)
- To: Liam Quinn <liam@htmlhelp.com>
- cc: w3c-wai-gl@w3.org, w3c-wai-ig@w3.org
as you described it reading seemlessly, we won't know what a clickable thing is. if it is an immage of a button that you have to click on, I've found that saying so let's me know where to click. e.g. "submit button". On Tue, 17 Feb 1998, Liam Quinn wrote: > At 08:52 AM 17/02/98 -0500, David Poehlman wrote: > >comments marked with dhp below. > > My comments are prefixed with LQ:: > > >dhp if it is a button, say it is a button. > > LQ:: Why? How does knowing it's a button provide you with any information > about the *content* of the page? The fact that a button is on the page > provides no more information than knowing that the text is in Times New > Roman and fuchsia. What is needed is to know what the button represents, > and for that the presence of the button itself is just a distraction if you > can't actually see it. > > >> ALT text should not be used with the APPLET element since richer alternate > >> content can be provided as the content of the element. > >dhp Is this backward compatible? > > LQ:: Completely, moreso than if the ALT attribute is used, since a > pre-HTML 3.2 browser won't get the ALT text but it will get the APPLET's > content and present it as an alternative. And the APPLET's content can > contain HTML elements like STRONG and A, whereas ALT is limited to plain > text. As I mentioned before on this list, I don't understand why ALT was > ever added to the APPLET element. > > -- > Liam Quinn > Web Design Group Enhanced Designs, Web Site Development > http://www.htmlhelp.com/ http://enhanced-designs.com/ > Hands-On-Technolog(eye)s touching the internet voice: 1-(301) 949-7599 poehlman@clark.net ftp://ftp.clark.net/pub/poehlman http://www.clark.net/pub/poehlman
Received on Tuesday, 17 February 1998 20:31:41 UTC