- From: Jon Gunderson <jongund@uiuc.edu>
- Date: Fri, 9 Jan 2004 08:05:29 -0600 (CST)
- To: Jesper Tverskov <jesper.tverskov@mail.tele.dk>
- Cc: <w3c-wai-ig@w3.org>
The following points you make on the problems of ABBR and ACRONYM are based on present implementation of user agents (browsers). A browser could have a preference which states that all ABBR and ACRONYM should be rendered in place of the abbreviation. The the screen and printing would include the the expansion and there would be no issue with the mouse or keyboard. See UAAG for more information: http://www.w3.org/TR/UAAG/guidelines.html#tech-conditional-content Jon Jesper Tverskov in his article states: 1. The expansion can only be seen on the screen not when the document is printed. 2. The expansion only works for the mouse not for ordinary keyboard users. 3. The expansion is worthless for scanning. It can only be seen if you hover the mouse pointer over the short hand. 4. The browser most people use, IE for Windows, does not support ABBR but only ACRONYM; and even this tag is only rendered with a tool tip. The user must hover the mouse pointer over every single abbreviation to find out where some additional information is hidden. On Fri, 9 Jan 2004, Jesper Tverskov wrote: > > Hi, > > The drafts for WCAG 2.0 and XHTML 2.0 have thrown new light on how to use ABBR and ACRONYM. > > I have just published an article discussing the problems: > > http://www.SmackTheMouse.com/20040108 > > - - - > > Jesper Tverskov > www.SmackTheMouse.com > >
Received on Friday, 9 January 2004 09:05:33 UTC