- From: John M Slatin <john_slatin@austin.utexas.edu>
- Date: Fri, 14 May 2004 12:22:57 -0500
- To: "Jens Meiert" <jens.meiert@erde3.com>, <michaelc@watchfire.com>
- Cc: <w3c-wai-gl@w3.org>
OK-- how does this sound as a practical suggestion for What to Do Today? - Provide the full meaning of each acronym or abbreviation, in context or in markup, the first time the acronym or abbreviation appears in any form that users experience as a "page." John "Good design is accessible design." Please note our new name and URL! John Slatin, Ph.D. Director, Accessibility Institute University of Texas at Austin FAC 248C 1 University Station G9600 Austin, TX 78712 ph 512-495-4288, f 512-495-4524 email jslatin@mail.utexas.edu web http://www.utexas.edu/research/accessibility/ -----Original Message----- From: Jens Meiert [mailto:jens.meiert@erde3.com] Sent: Friday, May 14, 2004 12:18 pm To: John M Slatin; michaelc@watchfire.com Cc: w3c-wai-gl@w3.org Subject: RE: [techs] Acronyms and abbreviations > In principle, I agree that every occurrence of an acronym or > abbreviation should be tagged with the appropriate element. > > In practice, however, what ends up happening is that people using > screen readers/talking browsers never actually hear the acronym or > abbreviation [...] Sounds like a draw anyway, doesn't it? What should we do and recommend now, is there the need to update the corresponding GL items? -- I really challenge this issue since I just had this discussion occupationally (again), and there are of course benefits as well as problems linked with it, as also pointed out by both of you. Jens. -- Jens Meiert Interface Architect (IxD) http://meiert.com/
Received on Friday, 14 May 2004 13:22:57 UTC