frustrated with the state of linux accessibility

kendell clark coffeekingms at
Thu Mar 19 20:58:39 UTC 2015

Hash: SHA512

You guys sure have. Gnome 3 is already quite accessible, and turning
on orca "just works". My rant was mainly aimed at developers who, for
one reason or another, either don't know how to, don't want to, or
will not fix accessibility issues. There are some unlabeled controlls
in gnome, lots of unlabeled buttons in the settings parts of gnome, as
well as duplicate buttons and combo boxes in the power settings. I'll
 wait for gnome 3.16 before I start filing bugs since you guys are
busy trying to get that out the door. I will raise one issue now
though. I've heard that the message tray is gone, and in f22, it is.
Notifications have been moved to the calendar, which is accessible,
I've used it. But how do I get to applications that formally resided
in the message tray without resorting to the mouse? Could a keyboard
shortcut be added in 3.16 that would jump to that area? I only ask
because if a blind person has to resort to a mouse to get to status
applets, it will seriously slow us down
Kendell clark
Sent from Fedora GNU/Linux

Bastien Nocera wrote:
> Hey,
> As Zbyszek commented, your best bet is to file bugs (preferably
> upstream) against those applications which break accessibility.
> We also have a number of changes planned to various parts of GNOME
> to make it easier to start a screen reader during installation, or
> on existing installations.
> We've already made great strides in GNOME 3, where enabling
> accessibility features doesn't require restarting applications or
> the desktop. That makes it easier for users to use, and developers
> to test applications.
> In short, file bugs. For GNOME at least, they will be fixed.
> Cheers
> ----- Original Message -----
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
>> hi You know, that's a fantastic idea. For the most part though, 
>> accessibility just works. There are exceptions, but as long as
>> you follow the gtk standards, like providing labels for custom
>> widgets, making sure your button is really set as a button in gtk
>> and doesn't just draw an image of a button on screen or similar,
>> orca and similar just work. Gnome does have issues with unlabeled
>> controls, mostly buttons, and duplicate controlls where orca will
>> read a control twice, and it's usually the second instance of
>> that control that's actually sensitive and actionable. But it
>> definitely cannot hurt to have an accessibility rating for
>> applications. There remain some serious issues in some toolkits,
>> such as wxgtk. List boxes in linux are not presentable by orca.
>> This is probably either a toolkit error or an orca one that can
>> be solved. Qt works for the most part. I would like eventually,
>> but am not holding my breath, for applications being run using
>> wine to be usable by orca. This would require some kind of 
>> windows accessibility to linux accessibility translator or
>> mapper. LIke I said, I want only to be equal among sighted
>> people. I don't want special treatment. If you're designing a
>> product or software, just consider accessibility. It isn't magic
>> or a hard thing to do, it's just something that';s often not done
>> by hardware and software manufacturers. That said, linux is much
>> much better at this than windows, who leaves the blind people to
>> their own devices when installing stuff. There are actually
>> driver install programs that are inaccessible, so you can't even
>> read the thing that installs your hardware drivers. Linux's
>> device model is different, and superior imo and doesn't require
>> this Thanks for reading Kendell clark Sent from Fedora GNU/Linux
Version: GnuPG v1


More information about the desktop mailing list