Bug 172955 - Suggestion: Enable a11y by default in Fedora
Suggestion: Enable a11y by default in Fedora
Product: Fedora
Classification: Fedora
Component: libgnome (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Ray Strode [halfline]
Depends On:
Blocks: 169147 FC5Target
  Show dependency treegraph
Reported: 2005-11-11 11:08 EST by Dave Malcolm
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-11-11 11:48:46 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Dave Malcolm 2005-11-11 11:08:12 EST
There's a large amount of code in many packages that provides accessibility
hooks.   Most of this code is only run if a11y is enabled.  This has been
disabled by default as it incurs a runtime cost.

Fedora is a distribution which champions the latest software, and advanced
features, such as SELinux, Xen, GNU Classpath/gcj, GCC4 etc have been/are being
integrated into Fedora with great benefits to both Fedora and to the upstream

Should we do the same for accessibility?  I think a11y has matured to the point
where it ought to be enabled by default, and only disabled if people are in a
low-memory situation.

Or maybe we could enable it for the first FC5 test release(s) and disable it for
the later release(s)?


Going lower-level:
Filing against the libgnome package as it provides the schema for the 
/desktop/gnome/interface/accessibility GConf key

This is in /etc/gconf/schemas/desktop_gnome_interface.schema
it defaults to false

Version-Release number of selected component (if applicable):
Comment 1 Ray Strode [halfline] 2005-11-11 11:48:46 EST
Hi I think rather than doing this for test releases of Fedora, you should lobby
upstream about getting it enabled by default for the development releases of
gnome.  You'll get a wider testing audience that way, and a larger interested
developer community to help fix the problems that pop up.
Comment 2 Dave Malcolm 2005-11-11 12:22:01 EST
Good idea.  

I've posted some ideas about this upstream here:

Note You need to log in before you can comment on or make changes to this bug.