Should the app focus on non-readable elements?

[Irineu333]

At present, Speak Touch, unlike other screen readers such as Talkback and Jieshou, does not focus on non-legible elements, even if they are clickable or focusable.

This approach was chosen because when focusing on an element with no content or child to be read, there is nothing to present to the user. In the case of Talkback, for example, it says "no label" for clickable elements and remains silent for focusable elements.

This left me with doubts because important elements of the interface may not have descriptions of their content. This is particularly concerning for clickable elements, so perhaps we should focus on all clickable elements, at least, and only notify the user with "no content" when there is no data to be read.

[Irineu333]

A solution for these elements without descriptions would be support for custom identifiers. Through a file, provide descriptions of elements based on the element's ID. I think Talkback has this functionality, along with icon identification.

[PatrykMis]

I often use this function in TalkBack. Personally I've turned on setting to speak Ids of unlabeled elements and this often helps a lot. Nothing is worse than the button which you even don't know it exists on the screen, so all clickable elements should be listed and announced regardless if they are properly labeled or not.

[Irineu333]

I understand, so you suggest the "speak ids" option as a solution. This feature is usually optional, so it depends on the settings screen ¹ under development.

How does this functionality behave in applications made with JetPack Compose?

Footnotes

1. Settings screen #39 ↩

[Irineu333]

What do you think of the “custom identifiers” functionality? Talkback has it but I haven't tested it. I believe it works by associating descriptions with the element's id (if it has an id).

[PatrykMis]

I think it's a good solution, especially in rare cases when a button doesn't have proper description and also no proper ID. Screen readers says just "button" then.

"Custom identifiers" is also good feature, especially if app has a lot of improperly labeled controlls and the user does not want to remember the role or meening each time. Personally I almost don't use that feature, as for me buttons which have IDs like IcNotificationBtn are pretty descriptive but I know some people who always describing that kind of controlls in screen reader options, either TalkBack on Android or VoiceOver on iOS.

[Irineu333]

I understand, so there are three issues:

1. Focus on non-legible buttons ¹
2. Speak ids option ²
3. Custom identifiers ³

Footnotes

1. Focus on non-readable elements #88 ↩

2. Speak ids option #89 ↩

3. Custom identifiers #90 ↩