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 639784 - AccessX features don't work (or just the sound?)
AccessX features don't work (or just the sound?)
Status: RESOLVED FIXED
Product: mutter
Classification: Core
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: mutter-maint
mutter-maint
Depends on:
Blocks:
 
 
Reported: 2011-01-17 21:09 UTC by Matthias Clasen
Modified: 2014-12-29 06:32 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Matthias Clasen 2011-01-17 21:09:01 UTC
Here is a number of things I noticed while playing with a11y settings today:

Seeing:

- The "Show Universal Access status" checkbox should probably go away - we always show it

- The "Zoom" control should control the shell magnifier, and be in sync with the zoom setting in the a11y panel

- "Screen reader" - no way to enable, should this go for 3.0 ?

- "Beep when Caps ... used": could get any beeps to happen here


Hearing:

- Closed Captioning: no way to enable, should this go for 3.0 ?

Typing:

- Typing Assistant: this doesn't exist, does it ?

- Does 'Turn on a11y features from the keyboard' control the accessx features ? then they should be sensitive/insensitive accordingly

- More seriously, I could not get any accessx features to work, might be a problem with the gsd plugin ?


Pointing and Clicking:

-  Video mouse: no way to enable, should this go for 3.0 ?

- Hover Click: Options are not wired up, should the button go for 3.0 ?
Comment 1 Thomas Wood 2011-02-05 18:01:35 UTC
I've hidden most of the options that are currently unavailable in commit f629b13 and hidden the "Options" buttons that don't have any implementation in commit 222103b.
Comment 2 Bastien Nocera 2011-02-25 18:25:04 UTC
(In reply to comment #0)
> Here is a number of things I noticed while playing with a11y settings today:
> 
> Seeing:
> 
> - The "Show Universal Access status" checkbox should probably go away - we
> always show it

That's gone.

> - The "Zoom" control should control the shell magnifier, and be in sync with
> the zoom setting in the a11y panel

That's implemented.

> - "Screen reader" - no way to enable, should this go for 3.0 ?

That's implemented as well.

> - "Beep when Caps ... used": could get any beeps to happen here

Doesn't seem to work indeed.

> Hearing:
> 
> - Closed Captioning: no way to enable, should this go for 3.0 ?

Hidden.

> Typing:
> 
> - Typing Assistant: this doesn't exist, does it ?

Starts the on-screen keyboard, and should work (once Caribou's .desktop file is fixed).

> - Does 'Turn on a11y features from the keyboard' control the accessx features ?
> then they should be sensitive/insensitive accordingly

Fixed.

> - More seriously, I could not get any accessx features to work, might be a
> problem with the gsd plugin ?

That's possible.

> Pointing and Clicking:
> 
> -  Video mouse: no way to enable, should this go for 3.0 ?

Hidden.

> - Hover Click: Options are not wired up, should the button go for 3.0 ?

Probably, yes.
Comment 3 Bastien Nocera 2011-02-25 18:28:58 UTC
(In reply to comment #2)
<snip>
> > - More seriously, I could not get any accessx features to work, might be a
> > problem with the gsd plugin ?
> 
> That's possible.

I'll rename this bug and investigate.

> > - Hover Click: Options are not wired up, should the button go for 3.0 ?
> 
> Probably, yes.

That's "dwell click", which should be implemented. Bug 643320 to track this.
Comment 4 Bastien Nocera 2011-02-28 17:43:58 UTC
Peter, would you have any idea why the sound effects from AccessX aren't getting through the end user?

Does it use the X11 Bell? Does it use its own thing?
Comment 5 Peter Hutterer 2011-03-01 01:51:50 UTC
Bell has been tricky in the past though I thought it was working these days. What call does it use?
Comment 6 Matthias Clasen 2011-03-01 05:17:57 UTC
This works in the fallback session under metacity.
Something wrong with mutters bell handling...
Comment 7 Matthias Clasen 2011-03-01 05:22:59 UTC
Looks like our mutter may simply not be built against libcanberra ?
And on top of that, the ifdef in meta_bell_notify seems a bit too radical - I believe the XkbForceDeviceBell call should be outside the ifdef.
Comment 8 Matthias Clasen 2011-03-01 15:46:32 UTC
Building with libcanberra fixes AccessX audible feedback, so this is probably not a blocker anymore. Should eventually be fixed anyway.
Comment 9 Jasper St. Pierre (not reading bugmail) 2014-12-29 06:32:03 UTC
bell.c has been rewritten since, I assume this is fixed.