E-mail List Archives

Search E-mail List Archives for

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

From: Rakesh P
Date: Fri, Jul 04 2014 6:32AM
Subject: Announcing Superscript value with voiceover on IOS
No previous message | Next message →

Dear all,

In one of our applications we have a superscript value. This value is
perfectly reading and getting identified as superscript element with
JAWS 15 on the desktop browsers. When the same content is read with
Voiceover on IOS device (iPhone 7.1.1, iPad 7.0.2) the behavior is not
as expected. Voiceover is reading the content first and the
superscript value in the next swipe without pronouncing it as a
superscript element. This leaves an ambiguity to the user.

We want to understand if any one of you have experienced this and what
could be a possible approach to resolve without impacting the
experience for desktop screen reader users experience and also should
be working with talkback on Android.

To have an experience of the same find it in the below link.

http://jsfiddle.net/9bb69/6/show/

Thanks & Regards
Rakesh Paladugula

From: Jonathan C. Cohn
Date: Sat, Jul 05 2014 3:08PM
Subject: Re: Announcing Superscript value with voiceover on IOS
← Previous message | No next message

On the Macintosh this shows up as a group of two items. When I ask VO to read text attribute changes VO does not indicate differences when changing position however the command-Option-T command will indicate that the 1 is in 13 point superscript.

I did not look at your HTML.

Best wishes,

Jonathan



On Jul 4, 2014, at 8:32 AM, Rakesh P < = EMAIL ADDRESS REMOVED = > wrote:

> Dear all,
>
> In one of our applications we have a superscript value. This value is
> perfectly reading and getting identified as superscript element with
> JAWS 15 on the desktop browsers. When the same content is read with
> Voiceover on IOS device (iPhone 7.1.1, iPad 7.0.2) the behavior is not
> as expected. Voiceover is reading the content first and the
> superscript value in the next swipe without pronouncing it as a
> superscript element. This leaves an ambiguity to the user.
>
> We want to understand if any one of you have experienced this and what
> could be a possible approach to resolve without impacting the
> experience for desktop screen reader users experience and also should
> be working with talkback on Android.
>
> To have an experience of the same find it in the below link.
>
> http://jsfiddle.net/9bb69/6/show/
>
> Thanks & Regards
> Rakesh Paladugula
> > >