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 projects. 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)? Thoughts? 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): libgnome-2.12.0.1-2
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.
Good idea. I've posted some ideas about this upstream here: http://mail.gnome.org/archives/desktop-devel-list/2005-November/msg00037.html