E-mail List Archives

Search E-mail List Archives for

Number of posts in this thread: 9 (In chronological order)

From: Mike Warner
Date: Tue, May 05 2015 9:13AM
Subject: superscript
No previous message | Next message →

Hi all,

during testing yesterday, I noticed that NVDA reads a superscript number,
coded using the html sup tag, as just part of the whole number. For
example: 2² is read as twenty two. Google searches tell me that
JAWS reads them the same way. Is that true?

There are three html entities for the common superscript numbers (1, 2, and
3), but what to do with any others so they're read correctly?

Thanks,
Mike

From: Olaf Drümmer
Date: Tue, May 05 2015 9:22AM
Subject: Re: superscript
← Previous message | Next message →

First of all, I would check whether there are settings in NVDA (and JAWS) that may impact whether a superscript is presented as such or not. A good source in this regard is the NVDA mailing list.

If it turns out NVDA (and / or JAWS) do not present HTML superscripts as such the story is simple: it needs to be fixed. Without further research though it is not obvious whether the API on which NVDA (or JAWS) are relying is insufficient, or whether NVDA (or JAWS) as such need to fix something.


Olaf


On 5 May 2015, at 17:13, Mike Warner < = EMAIL ADDRESS REMOVED = > wrote:

> Hi all,
>
> during testing yesterday, I noticed that NVDA reads a superscript number,
> coded using the html sup tag, as just part of the whole number. For
> example: 2² is read as twenty two. Google searches tell me that
> JAWS reads them the same way. Is that true?
>
> There are three html entities for the common superscript numbers (1, 2, and
> 3), but what to do with any others so they're read correctly?
>
> Thanks,
> Mike
> > > >

From: Ricardo Sánchez Velázquez
Date: Tue, May 05 2015 10:57AM
Subject: Re: superscript
← Previous message | Next message →

Mike:

If font attributes report is enabled in Document Formatting settings, NVDA
reads superscript and subscript in Word documents but not in HTML documents.

Regards.
Ricardo

-----Mensaje original-----
From: Mike Warner
Sent: Tuesday, May 05, 2015 5:13 PM
To: WebAIM Discussion List
Subject: [WebAIM] superscript

Hi all,

during testing yesterday, I noticed that NVDA reads a superscript number,
coded using the html sup tag, as just part of the whole number. For
example: 2² is read as twenty two. Google searches tell me that
JAWS reads them the same way. Is that true?

There are three html entities for the common superscript numbers (1, 2, and
3), but what to do with any others so they're read correctly?

Thanks,
Mike

From: _mallory
Date: Tue, May 05 2015 2:23PM
Subject: Re: superscript
← Previous message | Next message →

Orca does the same as well.

If it recognises a shorthand like "2nd" it'll say "second", but otherwise
whole numbers are read out. subs and sups are ignored as far as the SR is
concerned.

_mallory
On Tue, May 05, 2015 at 11:13:16AM -0400, Mike Warner wrote:
> Hi all,
>
> during testing yesterday, I noticed that NVDA reads a superscript number,
> coded using the html sup tag, as just part of the whole number. For
> example: 2² is read as twenty two. Google searches tell me that
> JAWS reads them the same way. Is that true?
>
> There are three html entities for the common superscript numbers (1, 2, and
> 3), but what to do with any others so they're read correctly?
>
> Thanks,
> Mike
> > > >

From: Steve Faulkner
Date: Tue, May 05 2015 8:39PM
Subject: Re: superscript
← Previous message | Next message →

On 5 May 2015 at 16:22, Olaf Drümmer < = EMAIL ADDRESS REMOVED = > wrote:

> Without further research though it is not obvious whether the API on which
> NVDA (or JAWS) are relying is insufficient, or whether NVDA (or JAWS) as
> such need to fix something.


Firefox exposes Ia2 text attribute: text-position sub, baseline, sup.

--

Regards

SteveF
HTML 5.1 <http://www.w3.org/html/wg/drafts/html/master/>;

From: Mike Warner
Date: Wed, May 06 2015 12:46PM
Subject: Re: superscript
← Previous message | Next message →

Thanks for the responses, everyone. It's pretty sad that Orca and NVDA
don't play nice with superscripts. You'd think that this would be one of
the first things that developers would build into the software when working
on numbers. Especially on html pages, where the code is a bit easier to
digest than in, say, a Word document. I did see a closed bug report for
this in NVDA, and it seems that I'd have to change a setting or two to get
it to read superscripts correctly. I'll leave mine as-is, so I can
replicate what the average NVDA users has.

Does anyone know whether VoiceOver reads superscripts correctly?

Mike

From: Ricardo Sánchez Velázquez
Date: Wed, May 06 2015 2:52PM
Subject: Re: superscript
← Previous message | Next message →

With the default settings,
VoiceOver + Safari: 1 sup 1 reads "one one"
Talkback + Chrome: 1 sup 1 reads "eleven"

Regards
Ricardo



-----Mensaje original-----
From: Mike Warner
Sent: Wednesday, May 06, 2015 8:46 PM
To: WebAIM Discussion List
Subject: Re: [WebAIM] superscript

Thanks for the responses, everyone. It's pretty sad that Orca and NVDA
don't play nice with superscripts. You'd think that this would be one of
the first things that developers would build into the software when working
on numbers. Especially on html pages, where the code is a bit easier to
digest than in, say, a Word document. I did see a closed bug report for
this in NVDA, and it seems that I'd have to change a setting or two to get
it to read superscripts correctly. I'll leave mine as-is, so I can
replicate what the average NVDA users has.

Does anyone know whether VoiceOver reads superscripts correctly?

Mike

From: Mike Warner
Date: Thu, May 07 2015 7:02AM
Subject: Re: superscript
← Previous message | Next message →

Thanks, Ricardo. As a programmer, I say shame on the teams responsible for
overlooking this basic item. Any programmer worth his/her salt (and
familiar with the source code for these readers) should be able to add
support for this in a few minutes.


>With the default settings,
>VoiceOver + Safari: 1 sup 1 reads "one one"
>Talkback + Chrome: 1 sup 1 reads "eleven"
>
>Regards
>Ricardo



Mike Warner
Director of IT Services
MindEdge, Inc.

From: Moore,Michael (DARS)
Date: Thu, May 07 2015 8:00AM
Subject: Re: superscript
← Previous message | No next message

I encourage everyone to file bug reports with the screen reader development teams. I have previously also reported the lack of support for <ins> and <del> as a bug. If they receive a sufficient number of reports the defects will be escalated in the production process.

Mike Moore
Accessibility Coordinator,
Texas Department of Assistive and Rehabilitative Services
(512) 424-4159 (Office)
(512) 574-0091 (Cell)

-----Original Message-----
From: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Mike Warner
Sent: Thursday, May 07, 2015 8:02 AM
To: WebAIM Discussion List
Subject: Re: [WebAIM] superscript

Thanks, Ricardo. As a programmer, I say shame on the teams responsible for overlooking this basic item. Any programmer worth his/her salt (and familiar with the source code for these readers) should be able to add support for this in a few minutes.


>With the default settings,
>VoiceOver + Safari: 1 sup 1 reads "one one"
>Talkback + Chrome: 1 sup 1 reads "eleven"
>
>Regards
>Ricardo



Mike Warner
Director of IT Services
MindEdge, Inc.