Hi,
It might also be good to have a page listing the various accessibility problems, shortcomings and useful enhancements of the accessibility in Ubuntu. So let me begin with three points: - The incompatibility of gksu with at-spi: There are applications like the Synaptic Package Manager that use gksu to get root privileges. However, gksu is not compatible to at-spi, resulting in a partially freezed desktop when there is an application that actively uses at-spi. Thus, if Maverick is not shipping at-spi2, I might be good considering whether it would make sense and be feasable to replace gksu with something compatible to at-spi. Some time ago, I started a thread about this on the Ubuntu development discussion list: https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2010-March/010770.html - Dwell click during GDM: The Ubuntu desktop ships the dwell click feature, that enables users to do clicks by software. (In other words, it enables users to perform the various mouseclicks without using a hardware button.) This feature is not yet available during GDM and the problem has already been discussed and a patch provided in GNOME: https://bugzilla.gnome.org/show_bug.cgi?id=589906 The solution chosen in the patch adds an icon to the panel in GDM; this item activates dwelling when the user hovers with the mouse over the icon. Another solution would have been to make the already available accessibility icon dwellable; this would however also require a dwellable item in the accessibility dialog of GDM; and above all, I have been told that because of the nature of the accessibility icon on the GDM panel, this solution would require considerably more work. (Unfortunately, I don't know the exact details.) - Do not hide the Universal Access menu: Each time I submit a new version of onboard to the sponsors of main, the package gets patched to hide the desktop file and the Universal Access menu. I would appreciate if the Universal Access menu and the items in it would be visible by default. This might especially be important for new users (not only disabled users, but for example also TabletPC users) that do not know that Ubuntu ships some accessibility tools or that do not know how to make them appear. If these points (especially the first) might be relevant during UDS, it would be great if there would be somebody to represent them. Thanks in advance for reading this, Francesco. PS: Cc'ing Gerd Kohlberger,the author of mousetweaks and the patch to add dwelling to GDM. On 05/10/2010 04:52 PM, Penelope Stowe wrote: > Hiya! > > So we met last meeting and I just wanted to post to the list notes > from the last meeting (I'll also put this up on the wiki). > > The main reason for this meeting was to start thinking about things we > wanted to have covered in the session this week at the Ubuntu > Developer Summit. > > Here are some things which people came up with. I'd like some feedback > on list as well as it would be wonderful if as many people as possible > could make the session! So you know, the Accessibility Team session > that I set up is in the community track, however, there is also a > desktop track session that I think Luke is doing. I'll post the > information for both sessions to the list in a separate e-mail. > > The main things we discussed as needing to work on for the Maverick > cycle (in no particular order): > > 1) Organizing and getting structure to the team > > 2) Creating a statement of where the team is and where we want to be. > > 3) Documentation (ranging from how-tos to basic information about what > accessibility programs are in universe and what other things might be > useful) > > 4) structure for the team > > Please feel free to discuss any of these things here on the list > (especially if you can't make the sessions) and we'll try to discuss > any concerns. > > Also if you have any other things you think might be good to discuss > specifically to be done during the next 6 months (during the Maverick > cycle), please send them to list. > > Please note that the track that I am running at UDS is really based on > community and getting the team working as a functioning group and less > on specific development. I certainly think it would be good for as > many developers interested in accessibility to attend as possible, > however, this particular session is community driven. > > Thank you! > Penelope > -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
