Swipeable hides components from VoiceOver

[SpasiboKojima]

I have a list of chats where 1-to-1 chats can be deleted with Swipeable actions and group chats can not. For group chats I do enabled={false} and the underlying button keeps working and receives focus as it should, but items with Swipeable enabled get skipped by VoiceOver completely.
It shouldn't happen, should it? Or is it the GestureDetector that does it, since I can see that enabled only disables gestures in it, as it should?

[fahmiridho07]

This is expected with the current implementation, but there is a clean workaround.

When enabled={false}, Swipeable still renders its gesture wrapper around your row content. That wrapper view ends up hidden from the accessibility tree, so VoiceOver skips the whole row even though touch still works on the inner button.

Do not mount Swipeable at all for rows without actions. Conditional rendering keeps VoiceOver intact:

{item.hasActions ? (
  <Swipeable renderRightActions={renderActions}>
    <ChatRow item={item} />
  </Swipeable>
) : (
  <ChatRow item={item} />
)}

If you must keep one tree (e.g. list virtualization), make sure the inner content explicitly opts back in:

<Swipeable enabled={false}>
  <View accessible accessibilityRole=button>
    {/* row content */}
  </View>
</Swipeable>

If the inner accessible view is still skipped, that is worth opening as an issue with a minimal repro (RNGH version, iOS version, enabled toggling only), because enabled should only disable gestures, not remove the row from VoiceOver.

[SpasiboKojima]

Thanks for the reply! Maybe I tripped somewhere at the time, because as you pointed that would be easy to work around, but now I see that it's the other way around - elements with Swipeable enabled get skipped by VoiceOver, and accessibility props don't really help with this. Again I could detect the VoiceOver being enabled and not add Swipeable at all, but it shouldn't be skipped at all, right? I can open an issue with repro.
Updated the original post.