Expose the timeline item long press and swipe to reply as TalkBack actions

[hayaksi1]

Content

A timeline item carries two gesture-only actions: long press opens the message action list, and a horizontal swipe starts a reply. Neither is reachable with TalkBack enabled, so a screen reader user cannot reach the action list at all — this is what the issue reports.

Publish both as accessibility custom actions on the event row, reusing the existing "Message actions" and "Reply" strings so no new translations are needed. The reply action is only offered when the user is allowed to reply, matching the condition that enables the swipe.

The scope is deliberately limited to restoring actions that already exist for sighted users. The larger list discussed on the issue — react, edit, share, links, view profile — is a product decision about which actions deserve to be surfaced directly rather than through the action list, so it is left out.

Motivation and context

Part of #4600.

Tests

No new automated test: the module's timeline view tests assert on rendered content, and Robolectric does not run the accessibility delegate that turns customActions into TalkBack actions, so a test here would only re-assert the semantics property I just set.

Manual check: with TalkBack on, focus a message and open the local context menu — "Message actions" and "Reply" are listed, and each performs the same action as the gesture.

Tested devices

• Physical
• Emulator
• OS version(s):

Checklist

• I am aware of the etiquette.
• This PR was made with the help of AI:
  • Yes. In this case, please request a review by Copilot.
  • No.
• Changes have been tested on an Android device or Android emulator with API 24
• UI change has been tested on both light and dark themes
• Accessibility has been taken into account. See https://github.com/element-hq/element-x-android/blob/develop/CONTRIBUTING.md#accessibility
• Pull request is based on the develop branch
• Pull request title will be used in the release note, it clearly defines what will change for the user
• Pull request includes screenshots or videos if containing UI changes
• You've made a self review of your PR

[github-actions]

Thank you for your contribution! Here are a few things to check in the PR to ensure it's reviewed as quickly as possible:

• If your pull request adds a feature or modifies the UI, this should have an equivalent pull request in the Element X iOS repo unless it only affects an Android-only behaviour or is behind a disabled feature flag, since we need parity in both clients to consider a feature done. It will also need to be approved by our product and design teams before being merged, so it's usually a good idea to discuss the changes in a Github issue first and then start working on them once the approach has been validated.
• Your branch should be based on origin/develop, at least when it was created.
• The title of the PR will be used for release notes, so it needs to describe the change visible to the user.
• The test pass locally running ./gradlew test.
• The code quality check suite pass locally running ./gradlew runQualityChecks.
• If you modified anything related to the UI, including previews, you'll have to run the Record screenshots GH action in your forked repo: that will generate compatible new screenshots. However, given Github Actions limitations, it will prevent the CI from running temporarily, until you upload a new commit after that one. To do so, just pull the latest changes and push an empty commit.

[jmartinesp]

Thanks, this is quite handy.

[bmarty]

@hayaksi1 can you record the screenshots please? We have screenshot with a11y details.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ hayaksi1
❌ ElementBot
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[hayaksi1]

Done!

[bmarty]

@copilot resolve the merge conflicts in this pull request

[hayaksi1]

@bmarty Done.

[bmarty]

@bmarty Done.

I do not see updated screenshot in the PR. I'll trigger the workflows again.

[hayaksi1]

@bmarty Done.

[codecov]

Codecov Report

❌ Patch coverage is 80.00000% with 5 lines in your changes missing coverage. Please review.
✅ Project coverage is 80.83%. Comparing base (6ab3d73) to head (a140b63).
⚠️ Report is 220 commits behind head on develop.

Files with missing lines	Patch %	Lines
...s/impl/timeline/components/TimelineItemEventRow.kt	80.00%	4 Missing and 1 partial ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #7458      +/-   ##
===========================================
- Coverage    80.86%   80.83%   -0.03%     
===========================================
  Files         2771     2771              
  Lines        81398    81421      +23     
  Branches     11168    11170       +2     
===========================================
- Hits         65822    65819       -3     
- Misses       11273    11300      +27     
+ Partials      4303     4302       -1     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.