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 118339 - Need accessible names, roles, and some custom work for accessibility support
Need accessible names, roles, and some custom work for accessibility support
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Accessibility
unspecified
Other All
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
AP3
: 87308 123019 126723 132678 (view as bug list)
Depends on: 132745
Blocks:
 
 
Reported: 2003-07-25 23:02 UTC by korn
Modified: 2013-02-04 05:24 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description korn 2003-07-25 23:02:01 UTC
The color chooser dialog contains several controls that are not fully
accessible:

1. The 20 color squares in the Palette group box are all objects of unknown
role - they should probably have the role ATK_ROLE_PUSH_BUTTON

2. The Opacity slider is lacking an AccessibleRelation (the
LabelFor/LabeledBy relation) connecting it to the static text "Opacity:".

3. The custom control for manipulating color setting in color space (the
triangle inside the annulus), while wonderfully keyboard accessible (yea!),
doesn't implement ATK and therefore doesn't provide appropriate feedback to
the blind user when being manipulted from the keyboard.  This control
presents an interesting challenge (and we should probably discuss it some
in this bug report before anyone tries to implement anything).  The desired
feedback to the blind user when manipulating it is to have spoken (or
Brailled) the name or trio of HSV/RGB values when they change. 
AccessibleValue doesn't exactly work here as there are three (or six!)
values changing.  Perhaps we could set and re-set the AccessibleName -
synthesizing the color name as a best-match reverse lookup of RGB values in
the list of named X colors.  This feels like the best approach to me.  The
other challenge is for the low-vision user, who wants to have the little
white annulus within the color triangle always shown in the magnified view.
 At high magnification levels, the entire triangle won't fit within the
screen, so we want to pan the magnified view to that annulus.  So long as
the low-vision user uses the mouse to manipulate the control, mouse
tracking will work (making this a lower priority issue).  Still, it'd be
nice if our accessibility architecture could support this.


To experience these problems, run the color chooser under Gnopernicus with
speech (and Braille and magnification) feedback turned on.  Tabbing through
the items in the Palette will give you the speech feedback of "unknown"
each time a new color gets focus.  Likewise when you tab to the opacity
slider, you are only told "Slider current value <number>", and not "Opacity
slider current value <number>".  Finally, tabbing and manipulating the
color triangle/wheel gives you no feedback (besides "unknown").
Comment 1 Glynn Foster 2003-11-06 20:23:00 UTC
This probably affects the gtk api now, although chances are it's
already fixed.
Comment 2 padraig.obriain 2003-11-07 08:49:49 UTC
This is probably a gail bug. I will transfer it there until I have had
a chance to evaluate it.
Comment 3 padraig.obriain 2003-11-07 10:07:57 UTC
*** Bug 87308 has been marked as a duplicate of this bug. ***
Comment 4 padraig.obriain 2003-11-07 10:59:32 UTC
1. The color squares do not give any indication what color they
contain. I can probably get the RBG value and store it in the
Accessible Name.

When you say object should have role PUSH_BUTTON I assume that you are
also expecting an action called click to be implemented.

2. I see a relation bweteen the label "Opacity:" and the slider.
What I do not see is an accessible description of the text field
adjacent to the slider. I have logged bug #126426 about this.

Can a priority be assigned to this bug?
Comment 5 padraig.obriain 2003-11-12 13:39:07 UTC
*** Bug 126723 has been marked as a duplicate of this bug. ***
Comment 6 padraig.obriain 2004-01-30 13:29:11 UTC
*** Bug 132678 has been marked as a duplicate of this bug. ***
Comment 7 padraig.obriain 2004-03-22 17:49:43 UTC
*** Bug 123019 has been marked as a duplicate of this bug. ***
Comment 8 Calum Benson 2004-10-21 16:43:18 UTC
Apologies for spam-- ensuring Sun a11y team are cc'ed on all current a11y bugs.
 Filter on "SUN A11Y SPAM" to ignore.
Comment 9 Matthias Clasen 2013-02-04 05:24:35 UTC
obsoleted by a new color chooser