Voice markup

[poretsky]

Just an idea. It seems, user interactions would be noticeably more
effective if there was a capability to assign different voices for
speaking elements of different types, for instance, changing voice
pitch. Such changes are detected instantly, thus, listening to an
element content, user would already know its role. It is especially
valuable when browsing web pages.

Of course, earcons serve just the same purpose and they really help in
many cases, but not everywhere. On the other hand, when user attention
is concentrated on a content, voice pitch changes generally have less
chances to be overlooked.

[svtsvet]

i suppose it's interesting and useful feature.
It can accelerate interaction with app. But it's very difficult for the most of users because there are many different voices. may be it will be easier with the different sounds?

[poretsky]

There are many sounds already in use and they serve their purpose. I do not consider voice pitch variation as a replacement. I only suggest it as an additional option for those who might be concerned.

[svtsvet]

I discovered situation when this function helped me. It was in “Ya taxi” app. Because of voice mark function I understood quickly what tariff was active. thank you. From: Igor B. Poretsky Sent: Monday, March 23, 2020 2:44 AM To: google/talkback Cc: svtsvet ; Comment Subject: Re: [google/talkback] Voice markup (#12) There are many sounds already in use and they serve their purpose. I do not consider voice pitch variation as a replacement. I only suggest it as an additional option for those who might be concerned. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[liangxiwei]

I want to say,If the project can not build with Android-Studio like third part app,do not open source.

[devinprater]

This would be a very good feature, especially for formatting changes in text, like italics and bold.

[poretsky]

I agree. I've revised my pull requests and closed totally outdated ones. This one is outdated as well, but I leave it mainly as a feature suggestion. Of course, I could easily update it not only for rebasing to the current code state, but now I have better implementation. And I have yet more ideas to suggest, but doubt that it does matter since it seems that nobody from the development team pays any attention.

[PatrykMis]

Great feature, I love your idea. Considering merge (cherry-pick) to TalkBack FOSS fork.

Unfortunately, Google doesn't have interest and attention to PRs on this repo, according to this comment

[amirmahdifard]

@poretsky hi. Can you please tell me how to build this in windows android studio?