The content on the screen though visually looks as a single statement, while navigating with the screen readers bring them in separate swipes. The below content
Song Name : Name of the song
Singer : Name of the singer
Duration: 4 minutes
May be read by the screen reader as
Song Name :
Name of the song
Singer :
Name of the singer
Duration:
4 minutes
This navigation pattern will disconnect the user’s ability to relate the content. Content authors must make sure that the reading order of the content is meaningful.
How to provide a meaningful connection between the content
Android
Instead of providing separate focus for each views which is the default behavior, provide a container for the views you require a single focus. Set android:focusable to true to this container. Alternately content authors can also use android:contentDescription attribute to overwrite the default reading pattern of talkback.
IOS
By default the children of the container’s are read as single item by voiceover. To avoid this, set the following method,
var shouldGroupAccessibilityChildren: Bool { get set }
to the container of the group.