Skip to content

Conversation

jmartinesp
Copy link
Member

@jmartinesp jmartinesp commented Aug 27, 2025

Content

What the title says. These can now be read aloud as 'ongoing call', 'new messages', 'new mentions'.

Motivation and context

Closes https://github.com/element-hq/customer-success/issues/573.

Tests

Enable a TTS solution like Talkback, then tap on different room list items/summaries.

  • Tap on one without indicators: it should read just the room, timestamp and last message.
  • Tap on one with an ongoing call: it should say also 'ongoing call'.
  • Tap on one with mentions: it should say 'mentions', possible also 'new messages'.
  • Tap on one with new messages: it should say 'new messages'.
  • Tap on a muted one: it should say 'muted'.

Tested devices

  • Physical
  • Emulator
  • OS version(s): 14

Checklist

  • 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 define 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

These can now be read aloud as 'ongoing call', 'new messages', 'new mentions'.
@jmartinesp jmartinesp requested a review from a team as a code owner August 27, 2025 11:08
@jmartinesp jmartinesp requested review from bmarty and removed request for a team August 27, 2025 11:08
@jmartinesp jmartinesp added A11y Accessibility PR-Change For updates to an existing feature labels Aug 27, 2025
Copy link
Contributor

github-actions bot commented Aug 27, 2025

📱 Scan the QR code below to install the build (arm64 only) for this PR.
QR code
If you can't scan the QR code you can install the build via this link: https://i.diawi.com/Zdsp9V

Copy link

codecov bot commented Aug 27, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 80.21%. Comparing base (f4708a4) to head (991e0af).
⚠️ Report is 3 commits behind head on develop.

Additional details and impacted files
@@           Coverage Diff            @@
##           develop    #5236   +/-   ##
========================================
  Coverage    80.21%   80.21%           
========================================
  Files         2241     2241           
  Lines        61484    61491    +7     
  Branches      7791     7793    +2     
========================================
+ Hits         49319    49326    +7     
  Misses        9310     9310           
  Partials      2855     2855           

☔ View full report in Codecov by Sentry.
📢 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.

Copy link
Member

@bmarty bmarty left a comment

Choose a reason for hiding this comment

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

Thanks! 2 suggestions that may be handled later.

@@ -29,8 +33,10 @@ fun UnreadIndicatorAtom(
color: Color = ElementTheme.colors.unreadIndicator,
isVisible: Boolean = true,
) {
val contentDescription = stringResource(CommonStrings.a11y_notifications_new_messages)
Copy link
Member

Choose a reason for hiding this comment

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

UnreadIndicatorAtom is also used for invitation, so maybe let contentDescription be a parameter and add a string a11y_notifications_new_invitation?

Copy link
Member

Choose a reason for hiding this comment

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

image

Maybe the indicator should be read first, and then the last message? It will require some change in the layout, but I believe that it will allow a faster screen reader navigation between rooms. We may handle this later though.

Note: happy to see that the a11y screenshot test is useful!

Copy link
Member Author

Choose a reason for hiding this comment

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

Maybe I can play with the traversalIndex here, but something tells me it'll be harder than that 😅

Copy link
Member Author

Choose a reason for hiding this comment

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

In the end I had to use zIndex again. It seems like traversalIndex won't work for nodes that merge their descendants.

@jmartinesp jmartinesp added the Record-Screenshots Runs the 'Record Screenshots' CI job and adds a commit with any new screenshots found. label Aug 27, 2025
@github-actions github-actions bot removed the Record-Screenshots Runs the 'Record Screenshots' CI job and adds a commit with any new screenshots found. label Aug 27, 2025
Copy link

@jmartinesp jmartinesp merged commit cc3d04a into develop Aug 27, 2025
30 of 31 checks passed
@jmartinesp jmartinesp deleted the a11y/add-content-description-to-room-list-item-indicators branch August 27, 2025 15:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A11y Accessibility PR-Change For updates to an existing feature
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants