On 10 May 2007, at 16:55:01, Thierry Koblentz wrote:
From: "Nick Fitzsimons"
On the other hand, screen-readers are generally configured by
default to always read out the expansion of text marked up as an
abbreviation (that is, the contents of the title attribute), so
using <abbr> (or the non-standard <acronym>) repeatedly will
force users of such assistive technologies to listen to the full
version on every occurrence in the page. From what I've heard,
this gets irritating pretty quickly, and could be seen as
diminishing the accessibility of the page.
Then I think it is a screen-reader issue as I believe there is no
point to have this as default setting since documents are supposed
to contain the expansion in plain text already...
That's not what WCAG says:
"Specify the expansion of each abbreviation or acronym in a
document where it first occurs. [Priority 3]"
http://www.w3.org/TR/WCAG10-TECHS/#tech-expand-abbr
... is followed by
"HTML Techniques: Acronyms and abbreviations"
which links to
<http://www.w3.org/TR/WCAG10-HTML-TECHS/#text-abbr>
which says
'Checkpoints in this section:
4.2 Specify the expansion of each abbreviation or acronym in a
document where it first occurs. [Priority 3]
Mark up abbreviations and acronyms with ABBR and ACRONYM and use
"title" to indicate the expansion'
So the checkpoint is stating the the <abbr> or <acronym> element
should be used for this purpose, _not_ that the abbreviation or
acronym should be expanded _in_the_text_of_the_page_ (although that
isn't necessarily a bad thing, even if it means a screen-reader user
will hear the expansion twice - that's still better than hearing it
every time it's used).
Regards,
Nick.
--
Nick Fitzsimons
http://www.nickfitz.co.uk/
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
