W3C home > Mailing lists > Public > spec-prod@w3.org > October to December 2001

RE: anchors in W3C specs

From: Charles McCathieNevile <charles@w3.org>
Date: Thu, 6 Dec 2001 13:54:26 -0500 (EST)
To: "Ishida, Richard" <Richard.Ishida@gbr.xerox.com>
cc: "'Paul Grosso'" <pgrosso@arbortext.com>, Susan Lesch <lesch@w3.org>, <spec-prod@w3.org>
Message-ID: <Pine.LNX.4.30.0112061350590.16737-100000@tux.w3.org>
Well, alt text is required by HTML, and by WCAG - 2 W3C recommendations.
Putting the same thing into a title attribute that is in an alt attribute
isn't an intrinsically bad thing, but it isn't the best way to go in some
circumstances either. Title doesn't seem to mean the same thing as alt
(although it isn't so well defined what title _does_ mean).

title is probably about the closest thing to a 'tooltip' attribute that there
is (although the concept plays a little differently in a voice-based system,
of course).



On Wed, 5 Dec 2001, Ishida, Richard wrote:

  I believe it is also the case that where Netscape 4x would display alt text
  as a tooltip, but not title text, Netscape 6x displays title text in the
  tooltip, but not alt text.  Do people think we should (on practical grounds)
  apply the same text to both alt and title elements, or is it better practise
  to wean people off the idea that alt text will appear in a tooltip?


  Richard Ishida
  Globalisation Consultant,
  International Document & User Interface Design
  Xerox GKLS
  tel: +44 1707 353395 (Voicemail always available)

  > -----Original Message-----
  > From: Paul Grosso [mailto:pgrosso@arbortext.com]
  > Sent: 04 December 2001 17:28
  > To: Susan Lesch; spec-prod@w3.org
  > Subject: anchors in W3C specs
  > What is the accepted way of doing links in the published
  > HTML for W3C specs?
  > Specifically, I'm concerned with the use link targets such
  > as <div id="foo"> that are expected to be the target of a
  > link such as <a href="#foo">.  While this is allowable in
  > XHTML, this is not compatible with HTML and does not follow
  > the XHTML guidelines for compatibility with HTML browsers;
  > such links do not work, for example, in Netscape 4.x browsers.
  > I have noted an increasing number of such links in W3C
  > documents, and I note with great concern that the W3C link
  > validator does not even so much as give a warning for such
  > links which are effectively BROKEN for all Netscape users.
  > Personally, I'd like to see our pub styles indicate that
  > W3C specs should follow the XHTML compatibility guideline
  > that suggests targets of the form <a id="foo" name="foo">
  > are used, and I'd like to see the link validator give
  > errors (or at least warnings) for link targets using an
  > id since that won't work in many of the deployed browsers.
  > paul

Charles McCathieNevile    http://www.w3.org/People/Charles  phone: +61 409 134 136
W3C Web Accessibility Initiative     http://www.w3.org/WAI    fax: +1 617 258 5999
Location: 21 Mitchell street FOOTSCRAY Vic 3011, Australia
(or W3C INRIA, Route des Lucioles, BP 93, 06902 Sophia Antipolis Cedex, France)
Received on Thursday, 6 December 2001 13:58:30 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:42:16 UTC