[Natty] The default setted true /desktop/gnome/accessibility/keyboard/enable setting disturb with screen reader using

Bug #711131 reported by Attila Hammer on 2011-02-01
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
casper (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: casper

Dear developers,
I see in Natty all 30accessibility script set following accessibility setting with all accessibility modes with true value:
/desktop/gnome/accessibility/keyboard/enable
This setting is setted during live CD boot and installed target system too. So, this setting on the fly setting with true value happening on the fly with live CD boot and installed target system with all accessibility modes.
With motor difficulties users this setting is absolute right and acceptable.

This setting provide to toggle keyboard accessibility functions with hotkeys. But, some accessibility modes I think this setting default enable is not good ydea, for example access=v2, v3 and braille modes. This modes are users possible to using Orca screen reader.
Perhaps why not good default enable this setting with screen reader related modes?
For example if an user want fast muting Orca with fast right Shift key presses, in Natty now a notification message is presenting to would like toggle the sticky keys feature on or off?
This situation need the user interaction to click the proper button, perhaps changing task, but if anytime later doing again some fast shift keypresses because not want hear a text output always but would like listening next informations, the notification is presenting again and this is perhaps disturb the work. With braille mode not possible to determining the visual impaired user using Orca both speech and braille or only braille output, so this situation is happening too if using both speech and braille output and want muting Orca fast shift key presses.

I don't no now Maverick 30accessibility scripts containing this setting or not, I not remember.
Next comment I attaching a patch with remove this setting withscripts/casper-bottom/30accessibility and ubiquity-hooks/30accessibility scripts with access=v2, access=v3, and braille modes.

Attila

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: casper 1.254
ProcVersionSignature: Ubuntu 2.6.38-1.28-generic 2.6.38-rc2
Uname: Linux 2.6.38-1-generic i686
Architecture: i386
Date: Tue Feb 1 09:40:02 2011
LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110130)
ProcEnviron:
 LANGUAGE=hu_HU.UTF-8:hu:en_GB:en
 LANG=hu_HU.UTF-8
 LC_MESSAGES=hu_HU.utf8
 SHELL=/bin/bash
SourcePackage: casper

Related branches

Launchpad Janitor (janitor) wrote :

This bug was fixed in the package casper - 1.260

---------------
casper (1.260) natty; urgency=low

  [ Colin Watson ]
  * Force apt-cdrom's mount point to /cdrom (LP: #723357). I've left the
    /media/cdrom symlink introduced in 1.259 in place anyway, as it's
    harmless on the live CD and may save some effort elsewhere.

  [ Luke Yelavich ]
  * scripts/casper-bottom/30accessibility && ubiquity-hooks/30accessibility:
    - Set the default session to classic GNOME for moderate visual
      impairement, blindness, and braille accessibility profiles (LP: #734659)
    - Fix a few dangling references to user-settings.py (LP: #744214)
    - Don't set /desktop/gnome/accessibility/keyboard/enable for vision
      related profiles (LP: #711131)
 -- Luke Yelavich <email address hidden> Fri, 01 Apr 2011 16:13:07 +1100

Changed in casper (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers