Alec Flett wrote: > Heikki Toivonen wrote: > >>The first one is keyboard access. Everything in the application should >>be usable with keyboard only. Besides being a requirement for people who >>can't use a mouse, this helps usability overall. This is our 0.6 goal, >>but there are a fair number of bugs on our way. There are also issues in >>wxWidgets, but those are out of the scope for 0.6. >> > wait, as I understood it, complete keyboard access is NOT a goal for > 0.6. We punted a lot of calendar bugs based on that. Making the calendar > (a central part of the 0.6 release) keyboard accessible is a big > undertaking, something that is not accounted for in the 0.6 planning...
Well, yes and no. Let me clarify: we should make 0.6 to be as keyboard-friendly as possible without a) touching wxWidgets and b) slipping 0.6 because of accessibility. There are simple things that we can easily do for 0.6, like providing keyboard accelerators or menu entries for actions. Also, there are clearly differences between platforms. Windows is afaik the most accessible OS we are providing Chandler for. Mac and Linux are quite a ways behind in terms of advanced accessibility APIs and tools. Therefore I worry about accessibility the most on Windows. On the other hand, keyboard access is one of the things Linux users really expect to have. And fixing wx is definitely out of scope for 0.6 - there are just too many broken things. -- Heikki Toivonen
signature.asc
Description: OpenPGP digital signature
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Dev" mailing list http://lists.osafoundation.org/mailman/listinfo/dev
