[$250] FlashList accessibility confusing order Android

[sharabai]

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.

---

Action Performed:

1. Open Android build
2. Open some chat with messages
3. Turn on Talkback
4. Try navigating to the next and previous element

Expected Result:

The swipe that corresponds to 'next' should go to the next message in the list, the swipe 'back' to the previous one

Actual Result:

The swipe that corresponds to 'next' goes to the previous message in the list, the swipe 'back' to the next one

Workaround:

Use reversed gestures for correct navigation

Area issue was found in:

A review to a PR linked with a similar issue

Failed WCAG22 checkpoints

1. SC 1.3.2: Meaningful Sequence (Level A)
   The Requirement: When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined.
   Why it failed: In a chat application, the chronological order of messages is critical to understanding the context of the conversation. Because the standard "next" navigation reads the messages in reverse order, the app fails to programmatically expose the conversation in a logical, meaningful sequence to assistive technologies.
2. SC 2.4.3: Focus Order (Level A)
   The Requirement: If a user interface can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability.
   Why it failed: On mobile devices using screen readers, performing a swipe-right gesture to go to the "next" element is the direct equivalent of pressing the Tab key for sequential keyboard navigation. Because swiping "next" shifts focus to the previous message instead of the next message, the focus order directly breaks intuitive operability and meaning. The fact that the user must utilize a workaround ("reversed gestures") confirms a failure of this criterion.

User impact:

A momentary confusion in that the order reversed for swiping gestures seemingly out of nowhere

Suggested resolution:

A patch of the FlashList that sorts items according to inverted prop.

Platforms:

Which of our officially supported platforms is this issue occurring on? Please only tick the box if you have provided a screen-recording in the thread for each platform:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari

Screenshots/Videos

Version Number: NA
Reproducible in staging?: Yes
Reproducible in production?: Yes
Notes/Photos/Videos:

bug.mp4

Issue reported by: @TaduJR

View all open jobs on GitHub

[sharabai]

I will take care of this one in the near future with a small targeted FlashList patch PR.
@TaduJR would be the best person for review as @chuckdries suggested here and @TaduJR was the one who discovered the issue in the first place.

[TaduJR]

👋

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @truph01 (External)