WebAIM - Web Accessibility In Mind

E-mail List Archives

Thread: VoiceOver on iPhone and iFrames

for

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

From: Craig Haydon
Date: Wed, Jan 28 2015 2:54PM
Subject: VoiceOver on iPhone and iFrames
No previous message | Next message →

Hi Gang,
Does anyone have any experience with VoiceOver/iPhone and iFrames??
I have an issue when scrubbing down the page that voiceover simple
skips-over the iframe.
No amount of aria goodness will make voiceover stop on the iframe and read
out the contents.
You can of course click the iframe to interactive with itŠ which is not
ideal.

So how can one make the iframe voiceover friendly??

-Craig

From: Jonathan Avila
Date: Thu, Jan 29 2015 7:04AM
Subject: Re: VoiceOver on iPhone and iFrames
← Previous message | Next message →

> So how can one make the iframe voiceover friendly??

I see the same thing with iOS 8. Adding a tabindex="0" did not appear to help. I'd consider this a bug.

Jonathan

-- 
Jonathan Avila 
Chief Accessibility Officer
SSB BART Group 
= EMAIL ADDRESS REMOVED =
Phone 703.637.8957  
Follow us: Facebook | Twitter | LinkedIn | Blog | Newsletter


From: Craig Haydon
Date: Thu, Jan 29 2015 3:15PM
Subject: Re: VoiceOver on iPhone and iFrames
← Previous message | Next message →

It seems that its a combination of iOS8 and safari.
Chrome actually works correctly.

Tested on iPad Air (latest), iOS8.1, Safari and Chrome

On 30/01/2015 1:04 am, "Jonathan Avila" < = EMAIL ADDRESS REMOVED = > wrote:

>> So how can one make the iframe voiceover friendly??
>
>I see the same thing with iOS 8. Adding a tabindex="0" did not appear to
>help. I'd consider this a bug.
>
>Jonathan
>
>--
>Jonathan Avila
>Chief Accessibility Officer
>SSB BART Group
> = EMAIL ADDRESS REMOVED =
>Phone 703.637.8957
>Follow us: Facebook | Twitter | LinkedIn | Blog | Newsletter
>
>
>

From: Patrick H. Lauke
Date: Thu, Jan 29 2015 4:01PM
Subject: Re: VoiceOver on iPhone and iFrames
← Previous message | No next message

On 29/01/2015 22:15, Craig Haydon wrote:
> It seems that its a combination of iOS8 and safari.
> Chrome actually works correctly.

As an aside, Safari uses iOS8's new WKWebView, while Chrome still uses
the old UIWebView. Expect future Chrome to have the same issue as Safari
once they switch.

P
--
Patrick H. Lauke

www.splintered.co.uk | https://github.com/patrickhlauke
http://flickr.com/photos/redux/ | http://redux.deviantart.com
twitter: @patrick_h_lauke | skype: patrick_h_lauke