[Bug]: Accessibility: a couple of issues

[shortwavesurfer2009]

Contact Details

No response

What happened?

• [x] On the nodes screen, the node chip at the top right hand corner just before the overflow menu button reads as unlabeled. #2688
• [x] It is no longer possible for a talkback user to get to the navigation bar to access messages, nodes, map, etc. #3914
• [ ] Elements are not being read top to bottom properly on the chat screen. See video with audio included below.

https://github.com/user-attachments/assets/efa47dc2-4ead-410a-89d2-2e1c56a0143f

To reproduce

1. Open app to a chat channel such as LongFast
2. In the accessibility section of the Android system settings, turn on TalkBack.
3. Return to Meshtastic by swiping up with two fingers from the bottom of the screen to open the app switcher. Swiping right or left with two fingers to scroll between apps. Tap the Meshtastic app and then double tap to activate.
4. Tap the back button at the top left of the screen.
5. Flick to the right with one finger, which will navigate you forward by one element.
6. Continue flicking right. One element at a time.

App Version

2.6.24

Phone

OnePlus Nord N200

Device

Seeed tracker t1000e

Firmware

2.6.12

Relevant log output

Code of Conduct

• [x] I agree to follow this project's Code of Conduct

[shortwavesurfer2009]

Oh, absolutely not.

[DaneEvans]

Just remove the stale tag and reopen it.

[DaneEvans]

After the refactor, the bottom bar is still not included in talkback. Haven't looked at the ordering, as the emulator doesn't let you do a 2 finger swipe

[shortwavesurfer2009]

The two finger swipes is only if you were on a physical device. If talkback is already on, you don't need to do any of the two finger gestures.

[DaneEvans]

I literally can't scroll through them on an emulator, either help, or leave it to us. And no, creating issues complaining about accessibility across dozens of repos is not helping

[shortwavesurfer2009]

I don't appreciate your tone. My "complaining" as you describe it are real issues faced by real users. You don't need to be snapish at someone attempting to give you information about how the software is used on physical devices.

[DaneEvans]

I invite you to read your own git history. And past warnings. You may find it enlightening.

In the meantime, I've blocked you and won't see your tickets again.

Good luck finding a Dev to pick it up.

[shortwavesurfer2009]

problem still exists as of 2.7.3

[github-actions[bot]]

This issue hasn not had any comment or update in the last 30 days. If it is still relevant, please post update comments. If no comments are made, this issue will be closed in 7 days.

[shortwavesurfer2009]

This issue hasn not had any comment or update in the last 30 days. If it is still relevant, please post update comments. If no comments are made, this issue will be closed in 7 days.

It is still relevant, Mr. Bot. Please do not close it.