WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Time formatting

for

From: Karl Brown
Date: Apr 18, 2017 4:11AM

Speaking content-wise, I avoid saying "8am-12pm" and go with "between 8am
and 12pm" or "8am to 12pm".

I know some people, who don't use screen readers, who get slowed down when
reading a page as the dash looks like a minus symbol. They think they have
to do some maths before remembering it's representing "to" and switching
their mental context back to time ranges.

Speaking plainly usually wins out for me.

On Mon, Apr 17, 2017 at 9:06 PM, Birkir R. Gunnarsson <
<EMAIL REMOVED> > wrote:

> I once managed to screw up a job interview when I said I had a lot of
> experience coding in "C number" (i.e. c# which, apparently, is
> pronounced "C sharp").
> Seeing as I didn't even know how to pronounce it, I did not make it
> past that interview,
>
> As for the question, I agree with the other commenters. Just go with
> standard formats, let the screen reader vendor and users handle how to
> communicate them.
> If there is a minor bug and your website helps solve it, it will ake
> the screen reader experience on all websites using that standard
> technique in future.
>
>
>
> On 4/17/17, Lucy Greco < <EMAIL REMOVED> > wrote:
> > well said Tim. this speaks to the criticleness of using reel people in
> > your testing. and yes i often speak words the way a screen reader does it
> > took one of my coworkers 8 months to ask me what i was saying when i kept
> > saying seo not S E O smile. actually i did not even know what seo
> > meant the first time i herd it so it was always seo for me even though i
> > new it was S E O
> > lucy
> >
> > Lucia Greco
> > Web Accessibility Evangelist
> > IST - Architecture, Platforms, and Integration
> > University of California, Berkeley
> > (510) 289-6008 skype: lucia1-greco
> > http://webaccess.berkeley.edu
> > Follow me on twitter @accessaces
> >
> >
> > On Mon, Apr 17, 2017 at 12:19 PM, Tim Harshbarger <
> > <EMAIL REMOVED> > wrote:
> >
> >> Here is something to keep in mind for anyone who tests with a screen
> >> reader...
> >>
> >> For those of us who depend on screen readers and use them all the time,
> we
> >> tend to become use to how the screen reader reads text. As long as you
> use
> >> common formats for text information, we should be able to pick up that
> >> information--even if the way the screen reader speaks it sounds unusual.
> >>
> >> In fact, sometimes if you listen very carefully to a screen reader user
> >> talking, you can catch that we will pronounce words the same as our
> screen
> >> readers do--and we are not even aware of it.
> >>
> >> However, it might also be worthwhile to test the time element to see if
> it
> >> influences how a screen reader reads time information. While using a
> >> common
> >> time format for the text works--there is nothing wrong with using
> another
> >> method if it produces a better user experience.
> >>