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 557010 - [a11y] Broken/incorrect accessibility hierarchy
[a11y] Broken/incorrect accessibility hierarchy
Status: RESOLVED DUPLICATE of bug 545282
Product: empathy
Classification: Core
Component: Contact List
2.24.x
Other All
: Normal normal
: ---
Assigned To: empathy-maint
Depends on:
Blocks: 557009
 
 
Reported: 2008-10-20 00:06 UTC by Joanmarie Diggs (IRC: joanie)
Modified: 2008-10-20 08:19 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Screenshot of examining Empathy's contact list using Accerciser (110.12 KB, image/png)
2008-10-20 00:08 UTC, Joanmarie Diggs (IRC: joanie)
Details

Description Joanmarie Diggs (IRC: joanie) 2008-10-20 00:06:45 UTC
Steps to reproduce:

1. Launch Orca and Empathy
2. Arrow around in the contact list.

Expected results: Orca would correctly speak each contact and group.

Actual results: Orca speaks different contacts and groups (i.e. items other than those which are displayed).

Disclaimer: We (Orca team) have not yet implemented support for Empathy; we're just getting started on doing so. However, even "out of the box" things shouldn't be quite this wonky. :-)

A useful tool when getting to the bottom of such issues is Accerciser. When I used it to compare what was being exposed to assistive technologies by Empathy with what Orca was saying, I found that the two corresponded. Somehow Empathy's accessible hierarchy is broken. I will attach a screenshot which will hopefully help illustrate what I'm talking about.

Thanks!
Comment 1 Joanmarie Diggs (IRC: joanie) 2008-10-20 00:08:39 UTC
Created attachment 120895 [details]
Screenshot of examining Empathy's contact list using Accerciser
Comment 2 Frederic Peters 2008-10-20 08:19:22 UTC
Joanmarie, could you confirm this looks like the same as bug 545282 ?

*** This bug has been marked as a duplicate of 545282 ***