Should display the StickyKeys status in some way (a11y)

This is probably something to do with the indicator whitelist used in Natty. Finding out the name of the indicator used would help in determining if this is the cause.

I am an LTS user, intending to migrate from Lucid to Precise next year. In that regard, this bug is a regression to me. Given that Mark Shuttleworth stated "First-class accessibility for those with special interaction needs" [1] as a goal for Precise, it is my personal opinion that fixing this bug would get Ubuntu closer to the above mentioned goal.

When a modifier key is locked and there is no indication of it, it is not only annoying to try out modifiers in an attempt to unlock the locked key, but it is potentially harmful, e.g. when accidentally locking the alt key without noticing, pressing 'q' doesn't type that letter anymore but quits the application.

As I see it there are two solutions: either add an indication as it was with Gnome 2, or add the option to the sticky key preferences to not have keys lock. (Perfect would be both).

For the above stated reason I'd be grateful if someone with permission could nominate this bug for the Precise release to ensure it doesn't get overlooked as it happened with the last release (Oneric, not an LTS version).

Thanks

[1] http://www.markshuttleworth.com/archives/810

Extremely well put, David, I second that request.

From a related bug report's comments [1] I gather the solution would be to code a new application indicator. There are tutorials on how to code an indicator using Python. Since I speak Python that's something I would be capable of doing. Could someone from Canonical confirm this is the right way to solve this issue? I don't want to code something just to have it labeled "doesn't fit our concept/doesn't apply anymore". There is also work in integration such an indicator; the accessibility preferences should have a checkbox 'show key stats' or something like that. The latter would have to be done by someone else; porting a panel to an indicator is one thing, but starting an indicator and setting it to launch with Unity and such would require knowledge of Unity workings and related technologies I don't have.

[1] https://bugs.launchpad.net/ubuntu/+source/unity/+bug/751207

Seems like a valid unity feature request (or new indicator but let's keep it on unity it's closer than the other sources it could be opened on).

The gnome-shell ui has the same issue it seems: https://bugzilla.gnome.org/show_bug.cgi?id=647711

Luke, do you know how important that info is for a11y usage? Do we know how other platforms like windows, macos, etc handle that feature and the feedback on screen for it?

Without this indicator, StickyKeys is basically unusable. Obviously you can use it, but if you lose track of which keys are locked/latched, it's really tricky to find out what's going on. I have in the past been forced to reboot just to clear a state of confusion. I would rate this bug as at least Important, possibly Critical, especially considering Canonical's statements regarding making the next LTS as accessible as possible.

Windows handles it very poorly, with a teeny tiny systray indicator for all four meta keys.

MacOS, last I used it, handled it very well with a relatively large overlay appearing graphic screen-left for each latch/lock key composited on top of the desktop and open apps.

What would also be very useful in these days of Unity and Gnome Shell using Super/Windows as a Start-button-a-like would be the ability to exclude the Super/Windows key from being sticky. It really breaks the UX for both Unity and Shell to have that key locking (turn on StickyKeys and see what I mean).

Hope this helps. If there is anything I can do to be more useful, please let me know. I'm not much of a programmer, but I do have some UI design experience.

Windows indicator: http://disability.illinois.edu/sites/default/files/win_sticky_keys_icon.png

MacOS: http://i.imgur.com/YNZPU.png

Unfrotunately this is somewhat out of my relm, and I don't have quite enough vision to be able to determine what is changing if sed feature is enabled in other operating systems

Oh well, if "First-class accessibility" as a goal for a release isn't gonna put this one the radar, then what is? Guess there are more important thing(s) now. Yes, I'm disappointed. Ignore this comment.

I've been pursuing this upstream in Gnomeland (not that Gnome Shell is really upstream of Unity any more) and met with a similar "oh what?" kind of response there too. Seb links to my bug report a few comments up from here.

The annoying thing is that StickyKeys is - in my experience at least - by far the most used accessibility feature. I just don't have it any more, which although doesn't stop me using my computer, it does make it a lot less comfortable.

If it helps, from http://www.apple.com/accessibility/macosx/physical.html

"When Sticky Keys is active, OS X visually displays each modifier key in the sequence in the upper-right corner of the screen, accompanied by a sound effect, so you can verify the sequence and correct it (if needed) before it’s entered. When you press the last key in the sequence, OS X plays a sound, enters the keys as a chord, and removes the visual representation from the screen."

Note that both of those behaviors are configurable. Key modifiers are actually overlaid on the screen, rendered semi-transparent, and can be dragged around with the mouse. Amazingly, I could find no screnshot of OSX online, so I include one here:

https://plus.google.com/photos/102359747730797411333/albums/5834442142323280017?authkey=COm2pcqp847vLA

Please let me know if that link doesn't work. I shan't remove it, but you're welcome to re-host it somewhere more sensible.

I will reiterate that this is a serious issue for some, including me. It is the difference between disability and health. Currently, OS X and Windows appear to take such issues far more seriously - this has actually been a problem with linux (and thus Ubuntu) now for years. But if you got the right person (perhaps the person who coded sticky keys in the first place?) I imagine this is a couple hours of work to address.

Hi Dav,

This bug has also been reported upstream, and some progress is happening there.

See here: https://bugzilla.gnome.org/show_bug.cgi?id=647711

Whether a Gnome Shell fix will make it into Unity is another question, but as I use Shell anyway, it's not a question I'm personally concerned about.

Thanks!

I do very much like unity (I know that makes me a weirdo). But maybe I'll
give gnome shell a try if they get this sorted out.

D

On Thu, Jan 17, 2013 at 1:07 PM, truant <email address hidden> wrote:

> Hi Dav,
>
> This bug has also been reported upstream, and some progress is happening
> there.
>
> See here: https://bugzilla.gnome.org/show_bug.cgi?id=647711
>
> Whether a Gnome Shell fix will make it into Unity is another question,
> but as I use Shell anyway, it's not a question I'm personally concerned
> about.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/773078
>
> Title:
> Should display the StickyKeys status in some way (a11y)
>
> Status in Unity:
> Confirmed
> Status in “unity” package in Ubuntu:
> Confirmed
>
> Bug description:
> Binary package hint: indicator-application
>
> Following an upgrade to Natty, I can no longer determine what state my
> stickykeys are in. No special steps are needed to reproduce this
> issue, just being in a Unity session.
>
> Previously this information was provided by the gnome-panel-applet
> called "AccessX Status" which displayed a row of icons which would
> show either latched or locked for each modifier key. In GNOME 2.x, I
> would right click a panel, select "Add to Panel" and choose "Keyboard
> Accessibility Status"
>
> This would give me a line of 6 square icons representing Alt, Ctrl,
> Super etc. These icons change state depending on which keys are being
> (temporarily or permanently) locked by stickykeys.
>
> While stickykeys seems to work - in that keys are latched/locked as
> one would expect - the lack of information about their state renders
> the feature considerably less usable. For some users, myself
> included, this is a critical a11y failure and requires using the GNOME
> 2.x environment instead of Unity.
>
> This is now the third time I've reported this bug/problem, hopefully
> I've got it in the right place this time! Apologies if not, and
> please do let me know where I should be reporting this if not here.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 11.04
> Package: indicator-application 0.3.2-0ubuntu1
> ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
> Uname: Linux 2.6.38-8-generic x86_64
> Architecture: amd64
> Date: Fri Apr 29 10:28:52 2011
> ExecutablePath:
> /usr/lib/indicator-application/indicator-application-service
> InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64
> (20100827)
> ProcEnviron:
> SHELL=/bin/bash
> LANGUAGE=en_GB:en
> LANG=en_GB.UTF-8
> SourcePackage: indicator-application
> UpgradeStatus: Upgraded to natty on 2011-04-28 (0 days ago)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/unity/+bug/773078/+subscriptions
>

Another vote for this as a critical accessibility issue. I've been trying to get more physically disabled people like myself using Linux as the price is excellent and it can be a start for job-training that can lead to gainful employment. This is a small fix that would mean the difference between Ubuntu being usable or not for many people.

Original bug report: “Reported by truant on 2011-04-29”
Ubuntu 11.10 Oneiric Ocelot release date: 2011-10-13
Ubuntu 12.04 LTS Precise Pangolin release date: 2012-04-26
Ubuntu 12.10 Quantal Quetzal release date: 2012-10-18
Ubuntu 13.04 Raring Ringtail release date: 2013-04-25
Ubuntu 13.10 Saucy Salamander release date: 2013-10-17
Ubuntu 14.04 LTS Trusty Tahr release date: 2014-04-17
Today's date: 2014-06-28

I am astonished to discover that this “bug report” has been languishing here unaddressed for three years and two months. So despite...
• the very valid comments about the crippled usability of Sticky Keys without a modifier key status indicator, from multiple end users (which I fully endorse – there are times when only logging out and logging in again will rectify an unknown and non-viable modifier key latched/locked combination);
• “First-class accessibility for those with special interaction needs” being a publicly stated aim for Ubuntu 12.04 LTS Precise Pangolin since at least 2011-10-20; [1]
• SIX missed opportunities to address this critical accessibility problem between Ubuntu 11.10 Oneiric Ocelot and Ubuntu 14.04 LTS Trusty Tahr
...it seems that Canonical either have a worse than useless bug-tracking system (less likely) or assign the needs of people with disabilities a rock bottom priority (more likely, but depressingly disappointing).

I've been using Sticky Keys on Apple Mac OS X for a decade, and occasionally on Micro$oft Windoze, and on both OS's the modifier key status indicators are a crucial component in making Sticky Keys work for unidextrous typing and computer control. The OS X technique of 'sound on modifier key-press' plus 'user-positionable translucent modifier key icon overlays' to show the current latched/locked modifier key combination is far more user friendly than the tiny panel icon in Windoze. Yet a 'one icon per modifier key' panel applet for Ubuntu, integrated into the System Settings > Universal Access > Typing > Sticky Keys, ought to be relatively easy to implement; indeed one end user has coded a 'one icon per modifier key' panel applet, and although it doesn't work on the Gnome Flashback environment I'm using, it does show what's needed:

pic: » http://i.stack.imgur.com/TnURl.png
caption: Image starting from left: Icon, Shift, Locked Caps, Ctrl, Alt, Super, Locked AltGr (Small circle to indicate locked state)
source: » http://askubuntu.com/questions/402315/how-to-add-a-keyboard-modifier-state-applet-to-unity-panel

As an Ubuntu noob, I'm unfamiliar with how best to get Canonical's attention drawn to fixing this problem. If more experienced Ubuntu community members can suggest ways in which to get this long-overdue error corrected, those of us who need a fully functional Sticky Keys implementation would be most grateful.

[1] “First-class accessibility for those with special interaction needs” being a publicly stated aim for Ubuntu 12.04 LTS Precise Pangolin since at least 2011-10-20 – see 'Precision Planning; Prepping for 12.04 LTS' by Mark Shuttleworth » http://www.markshuttleworth.com/archives/810

As part of the big bug review for 16.04 LTS I have tested this on 15.10 and the bug is still there.

I think it's a shame not implement such important feature.