OS: iOS 8.3 Screen reader: VoiceOver It appears that when the new content is loaded dynamically onto the web page during the infinite scroll, VoiceOver fails to refresh its navigation buffers, thus making the user believe that there is nothing more to read. Steps to reproduce: 1. Start VoiceOver via Settings->General->Accessibility->VoiceOver. 2. There is a Gist at: http://output.jsbin.com/zazayi/1/ 3. Switch the rotor to "headings", then begin swiping down to move between headings on the page. 4. When you reach each 2nd heading, notice that VoiceOver does not let you scroll down to load more content even though this is possible without it on. We have tried aria-busy and various combination of DOM events to force VoiceOver "pay attention", but nothing seems to work.
<rdar://problem/21466398>
/cc a few folks who might be interested. Note that this is actively affecting accessibility of Google products on Safari.
Does the test content use -webkit-overflow-scrolling: touch?
The test uses BODY scrolling, not DIV. But I believe overflow-scrolling:touch doesn't change the behavior in this case.
Since iOS 12 the situation is worse: new content is even not loaded dynamically. This still happens in iOS 12.4 beta 2 (May 20).
(In reply to Frédéric Wang (:fredw) from comment #5) > Since iOS 12 the situation is worse: new content is even not loaded > dynamically. This still happens in iOS 12.4 beta 2 (May 20). Likely I made a mistake when I tested with iOS 12: In order to focus the last child and get more content loaded, one need to *double-tap* the element (when VoiceOver is on). In any case, I tried the testcase again in iOS 13.0 beta 2 (17A5508m) and I can now navigate the new content when navigating by headings.