One more clarification - I don't expect you to do all the work while I
just shout from the sidelines. If your schedule has no room for
accessibility work at all, that is fine.

I will be testing accessibility features, and filing bugs, and will take
a stab at the ones that seem doable for 0.6.

But I would hope that you try to keep these guidelines in mind and try
to avoid constructs that make the problem worse.

Bryan Stearns wrote:
> 
> Ditto the detail view.
> 
> There are also significant platform issues: on Mac, the native widgets
> don't accept focus (at least, by default: there seems to be a
> system-wide preference about this, but I haven't tried turning it on to
> see whether wx supports it).
> 
> 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...

-- 
  Heikki Toivonen

Attachment: signature.asc
Description: OpenPGP digital signature

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev

Reply via email to