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 663687 - Missing accessible label names on tracker-needle widgets
Missing accessible label names on tracker-needle widgets
Status: RESOLVED FIXED
Product: tracker
Classification: Core
Component: Needle
git master
Other Linux
: Normal normal
: ---
Assigned To: tracker-general
Jamie McCracken
Depends on:
Blocks:
 
 
Reported: 2011-11-09 12:20 UTC by Brian Nitz
Modified: 2014-12-27 16:07 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Proposed patch which adds accessible lables to radio buttons and other tracker-needle widgets. (3.11 KB, patch)
2011-11-09 12:20 UTC, Brian Nitz
committed Details | Review

Description Brian Nitz 2011-11-09 12:20:34 UTC
Created attachment 201054 [details] [review]
Proposed patch which adds accessible lables to radio buttons and other tracker-needle widgets.

While using the Aegis accessibility tests inside the aegis accessibility test tinderbox: https://code.launchpad.net/a11ytesting

I found that many of the tracker-needle widgets do not have accessible label names.  You can also see these problems by running accerciser's validator plug-in.

This means that certain accessibility devices such as screen readers and braille displays will not be able to display information about these widgets.  I've attached a proposed patch.
Comment 1 Martyn Russell 2011-11-10 10:11:35 UTC
Hi Brian, thank you for the patch. Are you saying there is more work needed here?
Comment 2 Brian Nitz 2011-11-10 10:34:55 UTC
The patch is nearly complete except for 2 things:

1) I haven't been able to find where the history menu is instantiated.  Atk sees it as ROLE_MENU but I don't see anything in your vala or .ui files which constructs a Gtk_menu.  Looking at the patch, can you figure out where I can grab this (what appears to be a Gtk_Menu) widget and add a label to it and its menu_item children?

2) (Optional) Someone more familiar with Gtk/Atk might suggest using RELATION_LABELLED_FOR and RELATION_LABELLED_BY relationships instead of redundant labels for children of widgets.
Comment 3 Brian Nitz 2011-11-16 11:34:30 UTC
Please hold off on applying this patch.  Some of these issues may be caused by a bug in gtk3's Gtk::Builder.  I'll reference that bug here as soon as I know enough to log that bug.
Comment 4 Martyn Russell 2011-12-06 14:46:44 UTC
I am still holding ;) any ETA on this work Brian?

Thanks for the patch btw. I will set this as NEEDINFO for now.
Comment 5 Akhil Laddha 2012-01-19 09:13:57 UTC
Brian, ping
Comment 6 Brian Nitz 2012-01-19 10:31:14 UTC
Hi.  Sorry about that. I'm trying to recreate the environment now.  To be honest I'm not an expert on the way labels should work for comboboxes.  I'll try to ask on #a11y.
Comment 7 André Klapper 2012-02-02 21:12:47 UTC
Comment on attachment 201054 [details] [review]
Proposed patch which adds accessible lables to radio buttons and other tracker-needle widgets.

[Setting "patch" flag and correcting mime type so this can actually be queried for.]
Comment 8 Tobias Mueller 2012-07-07 20:04:42 UTC
Brian, ping
Comment 9 Tobias Mueller 2012-11-24 01:16:53 UTC
Hm. Shall we reject the patch and close as WONTFIX?
Comment 10 Brian Nitz 2012-11-26 09:54:40 UTC
Sorry I was pulled off of desktop. I don't have anything near the environment to be able to test this now. If no one else has reported this error, go ahead and close it as won't fix. It may have been fixed in another software layer.
Comment 11 André Klapper 2014-07-11 16:04:24 UTC
No open question => resetting status
Comment 12 Martyn Russell 2014-07-22 10:08:54 UTC
Comment on attachment 201054 [details] [review]
Proposed patch which adds accessible lables to radio buttons and other tracker-needle widgets.

Thanks for the patch, please go ahead and commit!
Comment 13 Martyn Russell 2014-12-27 16:07:55 UTC
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.