Times, Telephone etc.
Are there recommended ways to input times, telephone numbers, postcodes etc. which a screen reader will render in a sensible way.
For "Telephone: (01274) 305380", Fangs interpreted it as:
"Telephone colon left paren seven hundred right paren three hundred five thousand three hundred eighty", which seems a long way off being correct.
And, the office was open until "five point three zero".
Maybe the fault lies with Fangs.
Share: 
it's the responsibility of the screen reader and of the user to work out how to read/interpret such information. i would shy away from trying to "tweak" the standard way times, phone numbers, etc are written just to coax a "better" aural rendering out of assistive technology._________________
Patrick H. Lauke / webmaster / University of Salford
co-lead: WaSP Accesibility Task Force
take it to the streets ... WaSP Street Team
personal: splintered | photographia | redux
co-author: Web Accessibility - Web Standards and Regulatory Compliance
Share:
Modern readers have enough intelligence built in to them so that they can render phone numbers and times in a natural way.
e.g.
http://www.gododdin.demon.co.uk/... (56k)
.
Share:
You might also consider a microformat. In the future UA's might be able to get extra ques about what to do with content when its structured in a microformat, but that may just be wishful thinking._________________
Jonathan Worent
The early bird gets the worm, but the second mouse gets the cheese.
Share:
| jw_developer wrote: |
| You might also consider a microformat. In the future UA's might be able to get extra ques about what to do with content when its structured in a microformat, but that may just be wishful thinking. |
That depends on the takeup of Microformats. Standards is as standards does. If we all employ it there's justification to build UAs to read it.
Share:
Most screen readers have a mode for reading something out one character at a time, so if it's obvious that something is a phone number, for example, the user should be able to read it one number at a time.
There was a related post from a while back on bank account numbers.
Incidentally, JAWS makes a valiant effort to understand dates and times in context. So long as you include useful commas to separate content.
As a rough example, "6 September 1:10am" could be read as "six september the 1st colon ten a.m." which is not what you mean. "6 September, 1:10am" is read as "sixth september, 1:10 a.m."...
_________________
Jon Gibbins :// blogs at dotjay.co.uk, works with Analog.
Share:
| Ed. wrote: | ||
That depends on the takeup of Microformats. Standards is as standards does. If we all employ it there's justification to build UAs to read it. |
Off topic, but I heard a rumour somewhere (Simon Willison's blog, maybe?) that Yahoo are already using Microformats in their services.
Here's a link about Yahoo! Local.
http://www.niallkennedy.com/...
_________________
Jim O'Donnell
work: Royal Observatory Greenwich
play: eatyourgreens
Share:
Page 1 of 1
All times are GMT
You cannot post new topics in this forumYou cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum