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 354782 - [blocked] gnome-system-monitor "Resources" tab is inaccessible
[blocked] gnome-system-monitor "Resources" tab is inaccessible
Status: RESOLVED DUPLICATE of bug 400484
Product: orca
Classification: Applications
Component: general
1.0.x
Other All
: Normal normal
: ---
Assigned To: Orca Maintainers
Orca Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-09-07 14:56 UTC by Willie Walker
Modified: 2012-08-14 21:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Attachments
Image snapshot of Resoruces window (32.36 KB, image/png)
2007-05-28 20:46 UTC, Willie Walker
Details

Description Willie Walker 2006-09-07 14:56:54 UTC
The gnome-system-monitor "Resources" tab is inaccessible via focus tracking mode, most likely due to poor label-for and labelled-by relations.  Flat review allows one to read the text in this window, however.  This is listed in the Sun internal bugster database as CR 6459778.
Comment 1 Rich Burridge 2006-10-06 17:56:05 UTC
I've filed bug #360230 against gnome-system-monitor for this
problem and adjusted the summary of this one to indicate that
we are currently blocked on it.
Comment 2 Willie Walker 2006-10-15 00:25:34 UTC
Add accessibility keyword.  Apologies for spam.
Comment 3 Patrick Wade 2007-02-05 08:06:31 UTC
Not reproducible with gnome-system-monitor 2.17.6. Closing.
Comment 4 Joanmarie Diggs (IRC: joanie) 2007-02-05 08:30:45 UTC
Actually.... I *can* still reproduce it with gnome-system-monitor 2.17.6 under Ubuntu Feisty Fawn (fully updated, latest Orca from svn trunk).

When I tab among the buttons on the Resources page using focus tracking mode, I see labels like:

* CPU: 7.9%
* User Memory:  156.2 MB of 1011.5 MB 15.5%

And so on.

What I hear from Orca are 

* CPU History button
* Memory and Swap History button

Etc.

Are there other packages I should have installed?
Comment 5 Patrick Wade 2007-02-05 08:49:37 UTC
Peculiar. I heard the full labels being spoken, not just the sub-headings on the Resources tab.
Comment 6 Willie Walker 2007-05-24 14:03:25 UTC
(In reply to comment #5)
> Peculiar. I heard the full labels being spoken, not just the sub-headings on
> the Resources tab.
> 

In testing with gnome-system-monitor v2.18.1.1, I get the same results as described in comment #4 when I tab around.  When I look at the CPU button area via at-poke, the LABEL_FOR and LABELLED_BY relations are not being set.  

I believe the button should have a LABELLED_BY relation for each of the two labels, and this is most likely the case for the rest of the buttons on the page.

Patrick, how are you navigating the page?
Comment 7 Willie Walker 2007-05-25 16:27:32 UTC
Removing target milestone from [blocked] bugs.  We have little control over them, so we're better off letting priority and severity be our guide for poking the related components.
Comment 8 Patrick Wade 2007-05-28 09:57:20 UTC
> When I look at the CPU button area via at-poke, the LABEL_FOR and LABELLED_BY
> relations are not being set.  
>
> I believe the button should have a LABELLED_BY relation for each of the two
> labels, and this is most likely the case for the rest of the buttons on the
> page.

Will - I see (via at-poke) that the expected relations are present.


> Patrick, how are you navigating the page?

Simply 'tab'-ing around.
Comment 9 Patrick Wade 2007-05-28 10:23:04 UTC
(gnome-system-monitor 2.18.1.1)

In interface.cpp, the relevant atk relationship calls are made in create_sys_view (). 
Comment 10 Willie Walker 2007-05-28 20:46:42 UTC
Created attachment 88965 [details]
Image snapshot of Resoruces window

Let's make sure we're talking about the same window and objects.  Attached is a snapshot of the "Resources" tab of gnome-system-monitor 2.18.1.1.  Under the CPU History graph at the stop of the page tab, you'll see a blue button.  To the right of it are two labels: "CPU:" and "11.9%".  I don't see any relation between the button or the labels.  Making the button be labeled by the "CPU:" and "11.9%" labels might help assistive technologies more easily provide this information as the user tabbed around.

Are you saying that using at-poke, you actually see these relations?  If so, something is definitely different between our machines.
Comment 11 Willie Walker 2007-07-10 16:01:19 UTC
Patrick, any comments on comment #10?
Comment 12 Willie Walker 2008-01-06 00:21:36 UTC
Tested this with gnome-system-monitor 2.18.2 on my Solaris Express b79 machine.  Works fine now for me.  Joanie, since you seemed to run into this (see bug 360230), can you please give it a shot on your machine(s)?  I'd like to close this and the blocker bug if we can.
Comment 13 Joanmarie Diggs (IRC: joanie) 2008-01-06 00:57:36 UTC
This isn't fixed.  At least not in Ubuntu. Running 2.21.4.   

There is no relationship between the labels and the buttons.  There is no indication that the buttons are for color choosers.  The only way to access the contents is via flat review.

Question is, did the Ubuntu (or Debian) folks patch this dialog into inaccessibility as they did with the Add to Panel dialog?  I'll build it from svn in a bit and see.
Comment 14 Joanmarie Diggs (IRC: joanie) 2008-01-06 08:41:39 UTC
I just completely removed 2.21.4 and built the current gnome-system-monitor (2.21.5) from svn trunk.  It does look slightly different from the official Ubuntu one.  Most notably, I cannot even use Tab to move among the items on the Resources "tab" to see if Orca will speak them correctly when they are given focus. :-(  But according to Accerciser, there are still no relationships between labels and the buttons (or non-buttons I suppose) for the color chooser dialogs.

Perhaps this bug should be reopened??
Comment 15 Willie Walker 2008-01-06 16:17:45 UTC
(In reply to comment #14)
> I just completely removed 2.21.4 and built the current gnome-system-monitor
> (2.21.5) from svn trunk.  It does look slightly different from the official
> Ubuntu one.  Most notably, I cannot even use Tab to move among the items on the
> Resources "tab" to see if Orca will speak them correctly when they are given
> focus. :-(  But according to Accerciser, there are still no relationships
> between labels and the buttons (or non-buttons I suppose) for the color chooser
> dialogs.
> 
> Perhaps this bug should be reopened??
> 

When I look at it as it comes with Solaris, the label for/by properties are indeed set.  A possibility is that Sun made some fixes in the version it ships.  I guess we need to reopen this.  Sigh -- I have a feeling this is going to be one of those things we sink our time into when there are more pressing things that need our focus right now.  :-(
Comment 16 Willie Walker 2008-01-07 01:03:31 UTC
Aha!  I dug through the Solaris spec file for gnome-system-monitor and it looks like there's a patch for Solaris that sets the LABEL_FOR and LABELLED_BY properties:

http://cvs.opensolaris.org/source/xref/jds/spec-files/trunk/patches/gnome-system-monitor-01-solaris.diff

I'm not sure what in the patch needs to stay with just Solaris and/or why the patch just cannot be contributed back to the community.  I'll ask on the blocking bug.
Comment 17 Tim Miao 2008-01-08 03:02:58 UTC
I got the information from Sun engineer that gnome-system-monitor owns Sun internal patches, they will be put back to community some day. Adding Henry Zhang to CC list.
Comment 18 Willie Walker 2008-01-08 14:21:42 UTC
(In reply to comment #17)
> I got the information from Sun engineer that gnome-system-monitor owns Sun
> internal patches, they will be put back to community some day. Adding Henry
> Zhang to CC list.
> 

Thanks Tim!  We'll assume that you or Henry will take it from here.  Can we assign this bug to one of you?
Comment 19 Tim Miao 2008-01-09 02:17:46 UTC
I think this bug can be duplicated to #400484.

*** This bug has been marked as a duplicate of 400484 ***
Comment 20 Willie Walker 2008-01-09 13:59:36 UTC
Reopening this bug since it is a tracker bug for bug 360230.  When 360230 is closed, we will re-evaluate Orca's ablity to do the right thing and will close this bug accordingly.  I see also that bug 400484 was recently opened, and it seems to be a duplicate of 360230.

Here's the two bugs:

bug 360230: [a11y] gnome-system-monitor "Resources" tab is inaccessible
bug 400484: Resource don't support accessibility

If these are duplicates, my recommendation would  be that the newer bug 400484 be marked as a duplicate of the older bug 360230 since older bugs generally have a longer history of comments.

In any case, Tim and Henry seem to have them under control (thanks!), so I'll just block this bug on both of those.
Comment 21 Joanmarie Diggs (IRC: joanie) 2010-04-03 20:24:10 UTC
Bulk reassigning Will's bugs to the default assignee. (Sorry for the spam!)
Comment 22 Joanmarie Diggs (IRC: joanie) 2012-08-14 21:32:15 UTC

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