WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Accessibility of + and -

for

From: steve.noble
Date: Dec 8, 2016 9:30AM

Well, I think the more limited Unicode support in NVDA has been an identified issue. See for instance:
https://github.com/nvaccess/nvda/issues/3805
There's little question that JAWS, as a premium product, does a better job.

But if these symbols are really being used to represent mathematical constructs, I would suggest embedding them in MathML and using MathJax to render the content. This would expand the accessibility options at the user end, as one will get then get much better Unicode character support in NVDA when MathPlayer is running on the machine, and should also be picked up by ChromeVox and perhaps other speech AT.

--Steve Noble
<EMAIL REMOVED>
502-969-3088
http://louisville.academia.edu/SteveNoble



From: WebAIM-Forum [ <EMAIL REMOVED> ] on behalf of Jim Allan [ <EMAIL REMOVED> ]
Sent: Thursday, December 08, 2016 10:50 AM
To: WebAIM Discussion List
Subject: Re: [WebAIM] Accessibility of + and -

here is a site of many if not all hex codes to test with screen readers in
browsers
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.alanwood.net_unicode_supplemental-5Farrows-5Fb.html&d=AwIGaQ&c=SgMrq23dbjbGX6e0ZsSHgEZX6A4IAf1SO3AJ2bNrHlk&r=4WMck1ZVLo4tV0IVllcBNKXCSGU6lUERtx_4HD4DqmE&m=FUvBBKCUdf8SzmvElfdRUsc2kHG94mCAjAWKlSosAxo&s=2ZGMkaC5Orbd5ONIN1mrA9takXcN-ED0YoPfzzgZiMI&echeck the menu button to see a list of various categories of fonts and
symbols.
JAWS read most of them. NVDA- nada.

On Thu, Dec 8, 2016 at 9:40 AM, Preast, Vanessa < <EMAIL REMOVED> >
wrote:

> I think I just found the answer to my question on a Penn State site (
> https://urldefense.proofpoint.com/v2/url?u=http-3A__archive.tlt.psu.edu_suggestions_international_web_&d=AwIGaQ&c=SgMrq23dbjbGX6e0ZsSHgEZX6A4IAf1SO3AJ2bNrHlk&r=4WMck1ZVLo4tV0IVllcBNKXCSGU6lUERtx_4HD4DqmE&m=FUvBBKCUdf8SzmvElfdRUsc2kHG94mCAjAWKlSosAxo&s=ewyp1IEE916EwFtytA4EVF5U26QdJnFXJgsaJ4oaYjU&e> tips/unicodefourdigit.html). I'll post it here in case it is helpful to
> others are new to Unicode like me, or in case experienced folks want to
> correct what I've posted.
>
> It sounds like there are decimal and hexadecimal codes. The hex codes use
> the format &#x<hex-number>; and decimal codes use the format
> &#<dec-number>; when coding HTML
>
> The Em Dash uses the decimal of 8212 but the hex of 2014 (
> https://urldefense.proofpoint.com/v2/url?u=http-3A__unicodelookup.com_-23em&d=AwIGaQ&c=SgMrq23dbjbGX6e0ZsSHgEZX6A4IAf1SO3AJ2bNrHlk&r=4WMck1ZVLo4tV0IVllcBNKXCSGU6lUERtx_4HD4DqmE&m=FUvBBKCUdf8SzmvElfdRUsc2kHG94mCAjAWKlSosAxo&sQTu8SAvtCsNhfGg3agNPvWnSBuw6PURjNZKWp3NStk&e= dash/1). That's why the same number was
> resulting in different results in the HTML code. I was identifying the
> first as "decimal" and the second as "hexadecimal" by adding the x.
>
> What is my Word 2016 using? It appears to be the Unicode Hexadecimal:
> When I type 8212 into Word and then press Alt-X, I get the Han symbol
> When I type 2014 into Word and press Alt-X I get the em dash
>
> Best,
> Vanessa
>
>
>