WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Character reference chart for JAWS, Window-Eyes

for

From: Jason Kiss
Date: Sep 18, 2012 4:41PM

Hi Bevi,

I'm the one who performed that research with JAWS, Window-Eyes and
character references all those years ago. The issue is with the screen
readers. There's no reason (that I know of) that they couldn't, out of
the box, announce some kind of reasonable output for each character.

On a side note, I wouldn't say that VoiceOver identifies the
characters without errors. While VoiceOver's support for the
characters is excellent and impressive, I would quibble over the way
it identifies a few characters. And at least one character is, I would
argue, incorrectly identified. The acute accent character, ´ (´
or ´) VoiceOver misrepresents as the "prime" character. The
actual prime character is similar, but it is not the same, and is
denoted by ′ or ′. Still, compared to JAWS and
Window-Eyes, this is a very small matter.

Jason

--
Jason Kiss
Web: www.accessibleculture.org
Mobile: +64 21 929 238
Email: <EMAIL REMOVED>
Twitter: @jkiss

On Wed, Sep 19, 2012 at 10:18 AM, Bevi Chagnon < <EMAIL REMOVED> > wrote:
> Thank you, Jared, for reviewing the chart.
> This chart will be so helpful for my government clients.
>
> Interesting that VoiceOver with Safari (Mac) identified the characters
> without errors, but JAWS and WindowsEyes had errors.
> Do you know if this has anything to do with Windows itself, or is it JAWS
> and WE?
>
> --Bevi
>
> -
> Bevi Chagnon, <EMAIL REMOVED>
> PubCom - Trainers, consultants, designers, and developers
> Print, Web, Acrobat, XML, eBooks, and Federal Section 508 Accessibility
> -
> * It's our 30th Year! *
>
> -----Original Message-----
> From: <EMAIL REMOVED>
> [mailto: <EMAIL REMOVED> ] On Behalf Of Jared Smith
>
> I went through the characters with JAWS 13 with IE9 and Firefox. The
> findings presented in the table are entirely accurate with the default
> verbosity settings in both browsers. Of note is that many of the symbols are
> not read and some are read incorrectly. Nothing has changed since this was
> last tested in 2008 with JAWS 9.
>
> For comparison, I went through the characters with VoiceOver on Safari and
> *all* of the characters were appropriately identified.
>
> Jared Smith
> WebAIM
>
>
> > >