Explore By Touch only speaks a very limited number of ancestors when users touch an item. Sometimes, too limited. For example: 1. Open my blog http://www.marcozehe.de. 2. Touch any of the headings that contain links, for example each of the blog post headings. Result: TalkBack will say "Link Quick Navigation Keys now in Firefox for Android nightly builds". The information that this is also a heading, is not spoken, but should be, IMO. I know this is hard to fine-tune, but I think in cases where there's a heading involved, we should speak that, too. Likewise (untested) a graphic that is contained within a link, we want to speak the fact that this is a link, too.
Created attachment 637564 [details] [diff] [review] Provide full context for explore by touch events like we do for focus. This makes the utterances identical to linear nav.
Comment on attachment 637564 [details] [diff] [review] Provide full context for explore by touch events like we do for focus. r=me. Thanks, I believe this makes more sense than to artificially filter the ancestry.
http://hg.mozilla.org/integration/mozilla-inbound/rev/752842e054ee
https://hg.mozilla.org/mozilla-central/rev/752842e054ee
Verified fixed in Firefox/Android 16.0a1 2012-07-01.
or
