0

Situation:

What happens:

  1. Select and activate the link
  2. A border appears on the target element (which is halfway down the screen)
  3. The page scrolls so that the target element is at the top of the screen, but the border stays halfway down the screen.
  4. The closest element to the border is then selected and bordered, so reading starts halfway down the page instead of at the target element.

Closest reference that I can find to this issue is item 1 here, so maybe it is fixed in iOS 8.

But I'm trying to work out why it's happening and how to avoid it on as many devices possible. I've tried linking both to the main content div (which fills most of the page), and inserting an empty a tag, both of which behave the same.

EDIT: I've tried to force the reading position by setting focus or scrolling with JavaScript, but VoiceOver still ignores this and reads from the wrong place.

David Cook
  • 483
  • 7
  • 25
  • Is the content you are focussing always present in the DOM or are you adding the content dynamically? – unobf Dec 24 '14 at 12:56
  • This is static content from the HTML. There's other minor DOM changes on page load, but nothing that I can see has an effect. – David Cook Dec 26 '14 at 00:06
  • It works fine for me in iOS 8.1 but when I get to the content, I cannot navigate through it. I would suggest setting the target of the content link to the h1 inside the main div. There were some really quirky iOS 7.x bugs with focus, so its possible this was one of them http://unobfuscated.blogspot.com/2013/08/messed-up-ios-focus-management-with.html – unobf Dec 26 '14 at 12:32

0 Answers0