In a typical use case the content is paginated only while user scrolls towards the bottom of the list. This way we show the loading indicator only at the bottom while the next page is being fetched from the network API call. However, as you can see from the attached screenshots in our use case pagination is happening both at the top and bottom. In a typical accessibility(VoiceOver) usage scenario, when the user is in the first item of the list and she swipes right to left, the back/close button would be selected. Now in our special use case, when the user swipes from right to left the previous page loading indicator will get selected and then it fetches the data to load more items on top. My question now is: - How do we address this use case for an accessibility user, such that using one or more swipe gestures she can decide whether to load the previous page or go back?