Bug. The speeck element ids for unlabled buttons feature in talkback does not work as intended

[amirmahdifard]

ok so yet I cannot build talkback and contribute my self, So I can't investigate this my self, But i've tested and gathered as much as needed information for who is going to try to fix this. This bug is really bad, and it's the only bug that is preventing me from using newer versions of talkback completely. I hope you guys fix it.
In older versions of talkback, such as 8.2, 7, or even 9.1 As I've just tested 9.1, if we turn on the speeck element ids for unlabled buttons, it does a really good job. It speecks the id of every type of unlabled element if it has access to the id of that element. As you know, we have a type of element that after speecking its name, talkback says button, which means those are button elements. But also, there are some elements, that are called option elements, that after reading it, talkback does not says button. Now, In older versions of talkback as I tested up to 9.1, talkback reads the id of all elements, wether it's an option or button or whatever, but after 9.1 I think it's starts from 12 or so, when this option is turned on, talkback only speecks elements of the buttons and does not speecks the ids of other type of elements, such as options, etc, even tho it has access to their ids, it does not read them when focused on them, and to understand the id of a non button element, you must go to the dialog where you lable elements with talkback, and then you can see the title which says something like this. Enter the lable which will be used for this element. Element id: blaablaablaa. But, in older versions, It was really good. That really, really helps when working with an app that has unlabled buttons and options much. @PatrykMis hopefully, you can check and give a result comment. So much I tryed to report this to google, But finally I didn't manage, And now I reported hear, lets see what happens. Thanks

[PatrykMis]

Hey,

Thanks for your detailed report and for taking the time to test and document the issue. I appreciate that – it’s clear you care about improving TalkBack, and that’s great to see.

Current status

This particular issue is an upstream bug — meaning it originates directly from Google’s version of TalkBack, not from this fork.

• This fork focuses primarily on removing closed-source dependencies, improving privacy, and ensuring the project stays buildable in FOSS-friendly environments.
• Core behavior related to how element IDs are spoken has not been modified in this fork.

What does that mean here?

• Ideally, this would need to be addressed upstream by Google.
• This fork doesn’t have the resources to rewrite or overhaul core TalkBack behavior on its own — that’s simply outside the primary scope of the project.
• That said — if someone from the community investigates this, prepares a well-tested fix, and submits a clean PR, I’ll absolutely review and merge it, provided it works and doesn’t break anything else.

My personal stance

• I need to be upfront that I don’t currently have the time or capacity to personally work on this issue, as it touches areas of TalkBack that go far beyond the core goals of this project.
• This isn’t a case of ignoring the problem — it’s simply a matter of prioritizing what this fork was created to do, and what’s realistic given the resources available.
• Contributions are always welcome — but I can’t promise to personally fix every upstream bug, especially ones like this that require deeper investigation.

Next steps

• I’ll mark this issue with the upstream label and leave it open for tracking.
• If you (or anyone else) gathers more information, logs, or potential solutions, feel free to share them here.
• If a solid PR ever comes in to address this, I’ll absolutely consider it.

Thanks again for raising this — and for your interest in making TalkBack better. Even if we can’t directly fix this today, having it documented here helps keep attention on it.