Re: Example Scrolling Div

On 17/11/2015 11:12, Alistair Garrison wrote:
> Hi Patrick,
>
> The issue I experienced was on an iPhone 4s / Safari.
>
> The problem being that voiceover's visual focus tracks down through
> the content but does not scroll the content in the div, the focus
> appears to move out of the bottom of the scrollable box and down the
> page below the other content - scrolling the page down and down as it
> goes.  Once the content in the scrollable box is completely read the
> focus moves to the next item (the checkbox), however, the checkbox is
> now at the top of the page (due to the large amount of scrolling).

Ah yes, the visual focus tracking in iOS/VoiceOver has historically been
quite broken in iOS. They've introduced some fixes in iOS 9 not long ago
(see https://bugs.webkit.org/show_bug.cgi?id=147700) but there are still
remaining issues. It may be worth filing a follow-up bug?

> My experience was that the checkbox was so high up the page that when
> the focus shifted to it the focus was now partially over the
> browser's url entry box, and a double tap thinking I was on the
> checkbox meant that the url selection functionality was opened
> instead - which was very confusing.

For what it's worth though, on iPhone5c/iOS9 although the div didn't 
correctly scroll, VoiceOver's focus rectangle didn't go beyond the 
bottom of the screen or adversely affect the position of other elements 
in the page. The checkbox, at least for me, remained in its original 
position. Is your iPhone4s up to date with the latest iOS release?

> Hope this is enough of an explanation.
>
> In context, the example was presented in light of a conversation on
> gesture traps - and it was there to indicate that explore by touch
> may not always be a reliable mechanism to get you free - as the focus
> might not be where you think it should be.
>
> Ideally, there should be a certain amount of predictability to where
> you think you are focused on a page - which is not the case if
> content such as scrollable divs are used.

Thanks for the context, that makes more sense now. As noted above, in my 
case iOS/Safari/VoiceOver behaved appropriately though, so wondering if 
it's just an issue on older phones/iOS versions. More generally, this 
seems to be a browser/AT bug (so perhaps UAAG territory?), rather than 
something an author has control over (other than simply not using divs 
with overflow/scroll behavior).

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

Received on Tuesday, 17 November 2015 11:32:37 UTC