E-mail List Archives
Re: WCAG 2 draft and abbreviations
From: Alastair Campbell
Date: Aug 24, 2007 9:20AM
- Next message: Tim Beadle: "Re: WCAG 2 draft and abbreviations"
- Previous message: Philip Kiff: "Re: WCAG 2 draft and abbreviations"
- Next message in Thread: Tim Beadle: "Re: WCAG 2 draft and abbreviations"
- Previous message in Thread: Philip Kiff: "Re: WCAG 2 draft and abbreviations"
- View all messages in this Thread
Philip Kiff wrote:
> "With respect to the choice of whether to use <acronym> or <abbr>, I
> think you are making far too much of the "semantic" difference
> between <abbr> and <acronym>"
I have to agree. Looking forward, what you 'semantically' want from an
interface point of view is an element that designates some text might
need more explanation, which then leads to (paraphrasing the other
points):
- Enabling user customisation.
- Automatically creating glossaries or other aids based purely on the
content.
In HTML5 terms (*not* trying to stir up Mr Foliot ;), I can't see a
"use-case" for having both.
I used to just use acronym, due to IE's lack of support. Now I'm leaning
towards just using abbr, as it has the more general meaning of the two,
and you can 'fix it' for IE:
http://juicystudio.com/article/fixing-ie-quotes.php
Kind regards,
-Alastair
--
Alastair Campbell | Director of User Experience
Nomensa Email Disclaimer:
http://www.nomensa.com/email-disclaimer.html
- Next message: Tim Beadle: "Re: WCAG 2 draft and abbreviations"
- Previous message: Philip Kiff: "Re: WCAG 2 draft and abbreviations"
- Next message in Thread: Tim Beadle: "Re: WCAG 2 draft and abbreviations"
- Previous message in Thread: Philip Kiff: "Re: WCAG 2 draft and abbreviations"
- View all messages in this Thread