report change of status (online, offline or typing) of a contact in personal chat and of a member in group chat in Whatsapp Messenger

[GoogleCodeExporter]

What steps will reproduce the problem?
1.  Install Whatsapp Messenger 
(https://play.google.com/store/apps/details?id=com.whatsapp&hl=en).
2. Go into a personal/group chat screen.
3. If the contact in personal chat is typing, goes offline, or comes online, or 
if a member in group chat is typing...

What is the expected output? What do you see instead?
Talkback should automatically report when a contact goes offline, becomes 
online, or is typing in personal chat, and when a member in a group chat is 
typing. Presently, a user has to manually keep tapping the top area of the chat 
screen to determine the status of a contact or if a member is typing or not. It 
is impractical for a user to keep constantly checking to gain this information. 
Thus, Talkback should automatically announce this information.

What version of the product are you using? On what operating system?
The test environment is any version of Whatsapp Messenger (preferably a recent 
version) in conjunction with any version of Talkback (preferably a recent one) 
on any version of the Android operating system.

Please provide any additional information below.
The automatic reporting in the change of a contact's status or if a member is 
typing, should be automatically reported by Talkback, eliminating the need for 
a constant manual check by tapping on the top area of a chat screen.
However, during continuous reading AKA say all, I propose the change of status 
shouldn't be reported and shouldn't interrupt speech, since if the 
contact/group is active at that time, due to constant change of status, it will 
be impossible to perform an undisturbed continuous reading/say all. Moreover, 
the change of status shouldn't be reported while playing/recording an audio. 
Though the information about the status is important, it shouldn't disturb 
during continuous reading and playing/recording audios.

Original issue reported on code.google.com by [email protected] on 13 Mar 2015 at 4:21