Re: abbr/acronym - repetitive use

I'm getting to the point where I feel it might be necessary for best
practice and position that user agent developpers develop their own
access solutions rather than relying on third parties to do it.  It
seems that some third party vendors will play favorites for any number
of possible reasons.

----- Original Message -----
From: "Charles McCathieNevile" <charles@w3.org>
To: "Jim Thatcher" <jim@jimthatcher.com>
Cc: "WAI IG" <w3c-wai-ig@w3.org>
Sent: Thursday, November 22, 2001 1:46 AM
Subject: RE: abbr/acronym - repetitive use


I am told Mozilla also does this. Although for the last few years many
screen
reader makers have worked closely with IE, there is now a major project
to
ensure good compatibility between a number of screen readers (and other
assistive technologies) and Mozilla, and work has also been done for
other
browsers.

Chaals

On Thu, 22 Nov 2001, Charles McCathieNevile wrote:

  I use iCab from day to day which renders the things which are abbr and
  acronym elements (It is true that browsers based on IE suffer from the
fact
  that IE never implemented abbr as far as I know, but it has
implemented
  acronym for some time) and when I use Amaya it gives me the ability to
  identify the elements, and to ask for the title attribute value.

  In each case, they visually identify the element (Amaya through style
sheet,
  iCab by default). With iCab, a mouseover will cause the value of the
title
  attribute to be displayed in the status bar, with Amaya I can query
for the
  value with a couple of keystrokes.

Received on Thursday, 22 November 2001 06:06:17 UTC