# Accessibility iOS traversal order inconsistent?

**URL:** <https://discuss.kotlinlang.org/t/accessibility-ios-traversal-order-inconsistent/30779>\
**Category:** Multiplatform\
**Created:** [October 2, 2025, 3:12am UTC](https://discuss.kotlinlang.org/t/accessibility-ios-traversal-order-inconsistent/30779 "2025-10-02T03:12:48Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![sousaepedro](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.kotlinlang.org/sousaepedro/32/11294_2.png) [@sousaepedro](https://discuss.kotlinlang.org/u/sousaepedro)\
**Post date:** [October 2, 2025, 3:12am UTC](https://discuss.kotlinlang.org/t/accessibility-ios-traversal-order-inconsistent/30779/1 "2025-10-02T03:12:48Z")

</div>

I’m not sure if I’m opening this in the right place but I’ve been banging my head against the wall for over a month on this

I’ve got a compose scrollable column with some items, and I can’t make accessibility navigation go through them in the order they’re laid out - specifically on iOS. Android works perfectly whether I define traversalIndex or not.  
What’s worse is it’s inconsistent. The slower I traverse (with accessibility swipes) the better it works, but never 100% and eventually it just gets completely stuck.

I have no idea where I could be messing this up.