E-mail List Archives
From: John Foliot
Date: May 26, 2010 3:21PM
- Next message: John Foliot: "Re: abbreviations"
- Previous message: Denis Boudreau: "Re: abbreviations"
- Next message in Thread: John Foliot: "Re: abbreviations"
- Previous message in Thread: Denis Boudreau: "Re: abbreviations"
- View all messages in this Thread
Geof Collis wrote:
> I'm not sure where I read it but that is also the method I have
> adopted because of it.
> I also have to wonder how using it will help someone who can't use a
Sorry Geoff, this is simply the wrong perspective to be taking here: don't
develop for specific devices or software, develop according to standards.
Any other strategy will end up biting you in the back end at some point in
>> It means that Jaws will NOT support the @title in <abbr> and <acronym>.
It means nothing of the sort. It is simply a user setting that can be
adjusted in a particular piece of software, and what JAWS does versus what
NVDA does (versus what Voiceover does, and HAL, and WindowEyes, and...) is
already a hugely different kettle of fish. Again, developing for a piece
of software or a specific device is the wrong way forward - develop to the
standards and let the software/end user make the choice of how and what
they will consume your information.
>> I stand with what I was saying earlier: explain what the acronym or
>> abbreviation means on it's first occurence in the page (other than
>> navigation or headings, for obvious reasons) by presenting it
>> explicitely first, then give out it's acronym or abbreviation in
>> parenthesis. Seems like the best option to me, a win-win situation
>> for everyone.
This is not a wrong strategy, but it is not a complete strategy either