WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: VoiceOver Weird Reading of HTML

for

From: Jamous, JP
Date: Aug 20, 2016 5:31PM

Yeah it is a royal pain in the neck.

I'll definitely file a bug with them. Once I do, feel free to join me and add to my ticket. I'll send you the URL after filing the bug.

There is no reason for blind users to handle excessive swiping especially, when VoiceOver does not give any feedback if the font is bolded or has other attributes.




**************************************************

Jean-Pierre Jamous
Digital Accessibility Specialist & Developer
UI Accessibility Team

The only limitations in life are those we set for ourselves

**************************************************

-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Birkir R. Gunnarsson
Sent: Saturday, August 20, 2016 6:01 PM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] VoiceOver Weird Reading of HTML

Voiceover has always done that, as far as I can remember. It treats each element as a swipe stop, sometimes special characters as well.
You see a little bit of the same in Jaws where if you have a <div> element in a heading it is read on a separate line when navigating by arrow keys, but when you move to the heading using the h key it reads the whole heading.
This seems to be how the screen reader vendors think users prefer to browse. I guess if we think different we need to file a bug.
I kind of agree with you with he Voiceover thing, so I would support/comment on a ticket (if public).


On 8/20/16, Jamous, JP < <EMAIL REMOVED> > wrote:
> Does anyone know why in the world VoiceOver on iPhone reads HTML in a
> goofy way? Here is what I mean.
>
> <h1>
> Welcome to Jepelsy &reg;
> </h1>
>
> If I swipe left to right or right to left. VoiceOver selects the text
> in the
> H1 and reads it without the registered sign. I have to swipe again for
> it to select and read the registered sign.
>
> The same occurs with text that is bolded in a paragraph, a span in a
> paragraph, etc.
>
> In other words, whenever it notices any HTML markup in a parent, it
> separates it as a different swipe, which makes the user think it is a
> word on a separate line. In reality, it is breaking the structural
> layout of the paragraph or heading.
>
> It is really quite annoying because it leads to excessive swiping for
> no reason.
>
> I got a hold of Apple about it and they sent me to their Safari ticket
> dashboard. I did not notice anything related to my issue. They asked
> me to file a bug there.
>
> Does anyone know why it does this by default? I have an iPhone 5
> running
> 9.3.4 It even does it on my iPhone 6 and 6S.
>
>
>
> **************************************************
>
> Jean-Pierre Jamous
> Digital Accessibility Specialist & Developer UI Accessibility Team
>
> The only limitations in life are those we set for ourselves
>
> **************************************************
>
>
> > > archives at http://webaim.org/discussion/archives
> >


--
Work hard. Have fun. Make history.