Re: Ignore HTML elements in mobile devices

Rodrigo,

Please paste a bit of the HTML for context.

I'd like to know: Is the decorative image nested inside a clickable
element, such as a link (A with HREF) or a button element?

Or is the image just plain content, inline or in a block?

The advice already given is technically good and correct. However I've seen
occasions in Android TalkBack, swiping to read in document order (DOM
order), when arriving at a hidden node doesn't skip the node, but instead
causes the screen reader to be silent for one swipe.

This is worst when the hidden node is the first child node of a link,
causing the reader to announce "link" with no content. This happens even
when the hidden node is followed by text content inside the link.

This behavior I described appears to be a bug in the Android browser or
TalkBack, so you might not want to code around it. But it would be good if
we can find code examples to help document it, and I'm wondering if yours
is one of those examples.

Cheers,
Mitchell

Mitchell Evan
mtchllvn@gmail.com
@mitchellrevan
On Sep 8, 2014 7:29 AM, "Patrick H. Lauke" <redux@splintered.co.uk> wrote:

> On 08/09/2014 15:16, deborah.kaplan@suberic.net wrote:
>
>> How does VoiceOver  decide the "flick right to go to the next element"
>> order?
>>
>
> Source order, I believe.
>
>  I would have assumed it used tabindex.
>>
>
> From what I remember testing a few months ago, VoiceOver/Safari (and other
> WebView browsers) and Talkback/Chrome completely ignore tabindex (for
> instance setting a specific tabindex > 0 order for elements has no effect
> in these situations).
>
> 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
>
>