W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > July to September 2013

Re: screen reader reporting of negative values

From: Alastair Campbell <alastc@gmail.com>
Date: Wed, 21 Aug 2013 09:46:52 +0100
Message-ID: <CAC5+KCEq-cwrJXQvMERneGKPN=Y48pAhJnofh0MqRLNh4kfMiw@mail.gmail.com>
To: "Foliot, John" <john.foliot@chase.com>
Cc: "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
Foliot, John wrote:

>  Roughly a year ago I filed the following bug at NVDA:
> http://community.nvda-project.org/ticket/2625 - it was subsequently
> fixed.  Are you aware of any screen reader that is not announcing the dash
> as a negative when combined with a numeral?

This came up for me a few weeks ago, with default punctuation VoiceOver
doesn't announce dash or minus for a regular dash. It does if you set
punctuation to maximum. I asked on a VoiceOver list and few people do that,
or would know to change for a particular page (as discussed on this thread).

I hadn't come across &minus; before (thank you Adam Zerner!), which seems
to be the best candidate. It is read out as 'minus' by all the ones I've
- VoiceOver (10.7 on Safari)
- Jaws 14 / IE 10
- NVDA 2013.1.1 / FF 23

&#8722; also worked across those user agents, but I think &minus; is easier
to remember!

It also looks like a regular minus, instead of a long dash.

I'll post my test page and results when I get home tonight.


Received on Wednesday, 21 August 2013 08:47:21 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:36:45 UTC