- From: David Woolley <forums@david-woolley.me.uk>
- Date: Tue, 26 Jul 2011 06:27:44 +0100
- To: Karen Lewellen <klewellen@shellworld.net>
- CC: w3c-wai-ig@w3.org
Karen Lewellen wrote: > forgive the untidy subject line. > button input not implemented? > I am seeking something that explains why this message occurs, and how a > given site might shift this towards accessibility. When I meet with It's a trigger for scripting which was not properly designed to have a fall back. > these, I find them to be script buttons, which sometimes work with > e-links or links, sometimes not. A given that lynx cannot manage them. They are often used to do things like popups. Some text mode browsers recognize the pattern of the scripting code that is often used in these cases, and because there was no fundamental need for scripting are able to pull out the link that they are really implementing. They basically have very shallow "Javascript" processing that doesn't understand the language but can recognize some common patterns. > When in e-links or links too, they may define as harmless buttons as well. > This may have been touched on before, so forgive the question if covered > elsewhere. > thanks, > Karen > > -- David Woolley Emails are not formal business letters, whatever businesses may want. RFC1855 says there should be an address here, but, in a world of spam, that is no longer good advice, as archive address hiding may not work.
Received on Tuesday, 26 July 2011 05:28:29 UTC