Skip to content

Conversation

@PatrykMis
Copy link
Contributor

This change adds a no-op .clickable {} modifier to our custom ClickableText implementation.
Previously, the component relied solely on pointerInput for tap handling, which does not expose a clickable action in the Compose semantics tree. As a result, screen readers like TalkBack often failed to recognize these elements, leading to:

  • Missing or incomplete announcements (e.g., reading only the bullet, not the text).
  • Unstable focus navigation when moving through lists/items.

By adding .clickable {} — even with an empty click handler — we ensure that:

  • Screen readers see the element as a proper focusable target with a click action.
  • All list items and changelog entries are consistently read aloud.
  • Focus no longer “jumps” or gets stuck on decorative bullets.

No changes to visual appearance or business logic; purely an accessibility fix + dependency updates.

Signed-off-by: Patryk Miś <foss@patrykmis.com>
Signed-off-by: Patryk Miś <foss@patrykmis.com>
Signed-off-by: Patryk Miś <foss@patrykmis.com>
Signed-off-by: Patryk Miś <foss@patrykmis.com>
Signed-off-by: Patryk Miś <foss@patrykmis.com>
Signed-off-by: Patryk Miś <foss@patrykmis.com>
Copy link
Member

@soupslurpr soupslurpr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for noticing this issue and working around it, improving accessibility.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants