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

Re: screen reader reporting of negative values

From: Sailesh Panchang <sailesh.panchang@deque.com>
Date: Sat, 17 Aug 2013 16:25:02 -0400
Message-ID: <CAJi9CqpHy7WGtJZsR=bC_1-uLN1cqhDemX2_6OtZMPnUw=TJ0Q@mail.gmail.com>
To: "Foliot, John" <john.foliot@chase.com>
Cc: Roger Hudson <rhudson@usability.com.au>, "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
It is not unusual to use parenthesis too for negative numbers like in
financial statements. It is standard practice and depends on the org.
Screen readers can be configured to announce dashes and (, ) etc. by
adjusting punctuation verbosity.
Authors should not spend time  on this issue.
Maybe, simply notify the users that negative numbers are denoted by
parenthesis or the minus sign.
The users will do the needful depending on data being consumed and how
it is important to the reader.
Surely it should not be denoted using CSS or &hyphen; &dash;, etc.
Regards,
Sailesh Panchang


On 8/17/13, Foliot, John <john.foliot@chase.com> wrote:
> Hi Roger,
>
> 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? If so could you share that data (as
> clearly that is a concern to my organization <smile>) - note we seemingly
> always use the standard keyboard "-" (dash) as opposed to the &mdash; or
> &#8212 (which, AFAIK, should not be being used for negative values anyway).
> Do you have a "support" matrix handy?
>
> Cheers!
>
> JF
>
> From: Roger Hudson [mailto:rhudson@usability.com.au]
> Sent: Friday, August 16, 2013 10:27 PM
> To: w3c-wai-ig@w3.org
> Subject: screen reader reporting of negative values
>
> Hi,
>
> I am interested in finding the best way to include negative values in a
> table. For example a table showing an overdrawn bank account or a
> temperature below zero (c or f).
>
> It seems that there is some variability in the level of screen reader
> (and/or browser) support for coded &mdash; and &#8212; or the standard
> keyboard dash.
>
> One possibility would be to combine one of the above with the word 'minus'
> which is positioned off-left so that it is not visible but will still be
> read by a screen reader. However, this could result in some screen reader
> users hearing "minus dash $40.00. Would this be worse than risking some just
> hearing $40.00?
>
> Thanks,
>
> Roger
>
> Roger Hudson
> Web Usability
> Mobile: 0405 320 014
> Phone: 02 9568 1535
> Web: www.usability.com.au<http://www.usability.com.au>
> Blog: www.dingoaccess.com<http://www.dingoaccess.com>
> Twitter: http://twitter.com/rogerhudson
> Email: rhudson@usability.com.au<mailto:rhudson@usability.com.au>
>
>
>
> This transmission may contain information that is privileged, confidential,
> legally privileged, and/or exempt from disclosure under applicable law.  If
> you are not the intended recipient, you are hereby notified that any
> disclosure, copying, distribution, or use of the information contained
> herein (including any reliance thereon) is STRICTLY PROHIBITED.  Although
> this transmission and any attachments are believed to be free of any virus
> or other defect that might affect any computer system into which it is
> received and opened, it is the responsibility of the recipient to ensure
> that it is virus free and no responsibility is accepted by JPMorgan Chase &
> Co., its subsidiaries and affiliates, as applicable, for any loss or damage
> arising in any way from its use.  If you received this transmission in
> error, please immediately contact the sender and destroy the material in its
> entirety, whether in electronic or hard copy format. Thank you.
>
Received on Saturday, 17 August 2013 20:25:30 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:49 UTC