After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 617040 - Chat partner status changes (typing, away, etc.) are not accessible
Chat partner status changes (typing, away, etc.) are not accessible
Status: RESOLVED OBSOLETE
Product: empathy
Classification: Core
Component: Accessibility
2.30.x
Other All
: Normal normal
: ---
Assigned To: empathy-maint
empathy-maint
Depends on:
Blocks:
 
 
Reported: 2010-04-28 07:07 UTC by Joanmarie Diggs (IRC: joanie)
Modified: 2018-05-22 14:11 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Joanmarie Diggs (IRC: joanie) 2010-04-28 07:07:06 UTC
When you're chatting with someone, you're alerted when that person starts typing, goes away, etc. by a change in the appearance of the page tab which contains the person's id. If you see a keyboard, it means he/she is typing; if you see a yellow chat bubble, it means he/she is away; etc.

When this occurs, a couple of events seem to be emitted by the accessible associated with that page tab:

* object:property-change:accessible-name
* object:visible-data-changed

I believe that I can reliably use those events as a way to detect a status change. However, I am not seeing anything which tells me what the status has changed to. As a result, the status changes are inaccessible to users who are blind.  If you could expose the new status as the description of the AtkObject, that would be awesome.

I'm afraid I've not yet had time to get familiar with your code to try this (sorry!), but here's what in theory should work: When you're changing the icon to reflect the status change, also

* Get the accessible AtkObject for the page tab widget via
  gtk_widget_get_accessible()
* Set the description on that object via atk_object_set_description()

That should do it....

I'd ask that the string you use for the description not be localized. The reason being that some users might only be interested in, say, the typing status.

Thank you *very* much in advance for taking a look at this issue.
Comment 1 Joanmarie Diggs (IRC: joanie) 2010-04-28 14:22:09 UTC
Having given this some more thought (after having slept), while the above will certainly work, perhaps the more appropriate thing to do would be to add the unlocalized status string as an object attribute of the AtkObject associated with the page tab widget.
Comment 2 GNOME Infrastructure Team 2018-05-22 14:11:34 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/empathy/issues/230.