[Natty or perhaps Ocelot] Please enable default the caret navigation mode for Yelp application with all blindness related profiles

Bug #752503 reported by Attila Hammer on 2011-04-06
This bug affects 1 person
Affects Status Importance Assigned to Milestone
casper (Ubuntu)
Luke Yelavich

Bug Description

Binary package hint: casper

Dear Developers,

With Webkit GTK based Yelp application the caret navigation is not enabled by default, but this is very need if a visual impaired user using Webkit GTK based Yelp version for Orca Screen Reader and Magnifier.
the default enabled caret navigation for Yelp is need when visual impaired users using Orca and want reading help topics for example with up and down arrow keys. If caret navigation is not enabled, this is the default setting, Orca does'nt spokening actual selected lines for Webkit GTK based Yelp.

I maked a combined patch for casper 30accessibility scripts to creating a minimalist default Webkit based Yelp configuration file and enabling the caret navigation only for access=v2, v3 and braille profiles.
This problem fix I think is critical important for blindness related profiles, because without this fix manual need enabling the caret navigation mode after first launched the Yelp application. This is only one key press (F7 key), but if possible accepting my fix or a modifyed fix with your instructions, this is a good news and help this fix for beginner users with not known this keystroke.

New Scripts/casper-bottom/30accessibility script added code part creating required configuration directory and configuration file with live user home directory/.config/yelp folder if the configuration directory is not exist, and creating similar directory/config file with live CD /etc/skel folder for important blindness related profiles (v2, v3 and braille) if the Yelp related configuration directory is not exist already with /etc/skel folder.
With ubiquity-hooks/30accessibility script new added code part copying the target system the first user home directory/.config/yelp folder the proper created configuration file from live user home directory. This is happening both access=v2, v3 and braille blindness profile. I choosed this method for installation because perhaps the user possible doing another preferences with Yelp before installation.
Another disabilities I don't no need enabling default the caret navigation for Yelp (for example motor difficulties), this parts I not handle this problem because not known need the caret navigation support for other disabilities users.

I documented the patch code what part I why doed.
If possible and not a big request, please not reject the /etc/skel part related code, I examine not existing already a yelp related configuration file in the /etc/skel directory, configuration file is created only if not existing the configuration directory in the /etc/skel folder.

If have a chance to accept this fix before Natty beta2, but need doing modification my fix, please tell me what part I need modifying or removing the code.
If you not accepting only the /etc/skel related configuration file creation, but accept another fix parts, I removing of course the skel related code if have a chance to land this problem fix before Natty beta2 with Casper package.


ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: casper 1.263 [modified: usr/share/initramfs-tools/scripts/casper-bottom/30accessibility]
ProcVersionSignature: Ubuntu 2.6.38-8.41-generic
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
Date: Wed Apr 6 15:06:40 2011
LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110405)
SourcePackage: casper
UpgradeStatus: No upgrade log present (probably fresh install)

Related branches

Attila Hammer (hammera) wrote :

Please don't surprise, I modifyed my local build with the indicated 30accessibility script to try my patch with real environment for live system and real installation.
Both two situations the patched script working right.


I forgot wrote the bug triaging steps:
1. Please you launch Natty live CD for access=v2, v3 or braille mode.
Access=v3 is screen reader mode.
2. When Orca Screen Reader is started, click the help button.
3. Try moving for example the main index help page with Up or Down arrow
key. Because caret navigation is not enabled by default for Webkit GTK
based Yelp, you will be not hear any actual highligted line.


Luke Yelavich (themuso) on 2011-04-06
Changed in casper (Ubuntu):
assignee: nobody → Luke Yelavich (themuso)
status: New → In Progress
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package casper - 1.264

casper (1.264) natty; urgency=low

  * scripts/casper-bottom/30accessibility && ubiquity-hooks/30accessibility:
    - Enable yelp carrot navigation by default in the moderate visual
      impairment, blindness, and Braille profiles, thanks to Attila Hammer
      for the patch (LP: #752503)
 -- Luke Yelavich <email address hidden> Thu, 07 Apr 2011 10:17:52 +1000

Changed in casper (Ubuntu):
status: In Progress → Fix Released
Luke Yelavich (themuso) wrote :

Thanks very much for your patch, I have reviewed it, and tweaked it slightly, and uploaded it. A few comments:

1. You don't need to comment what the code is doing in such great detail. If the code is relatively simple, reading the code alone should be explanation enough as to what it does. The only time I tend to use comments is if I want to tell the reader that what follows is complicated, and explanation of the logic is needed, or, that something needs fixing, or that its an ugly hack. :)
2. I still don't agree that when a new user creates an account, that they will want carrot navigation enabled by default, because they may wish to use the arrow keys to move through the document. We don't enable accessibility by default for any new user creating an acount, so I don't see a reason for the yelp carrot navigation mode being enabled, just because accessibility isn't.

I do understand your point of view regarding this matter, and longer term, I think we need a good accessible control panel application that allows people to tweak these settings for their account, and/or newly created user accounts.

Thanks again.

Hy Luke,

Thanks the patch reviewing and the commit, I full agree the /etc/skel
related part with your openion to keep with upstream compatibility.
Future, absolute agree need found a solution this problem to have
possibility the admin privilege user setting what type accessibility
profile would like enabling the new would like creating user.
Need carefuly future if this feature perhaps implementing don't kill
/etc/skel related other customizations if derivative distros using this
way to store another customizations.


To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers