Custom accessibility worth it?
Custom accessibility worth it?
- Subject: Custom accessibility worth it?
- From: Ricky Sharp <email@hidden>
- Date: Wed, 6 Sep 2006 16:08:06 -0500
In going through past e-mails I've posted this list, there are many
that remain unanswered.
Don't get me wrong, I do understand the rules of the list and it's a
bonus to have Apple engineers respond. Having said that, my
questions are piling up to the point where it will be quite costly to
have them all answered via DTS incidents (I only have two free ones
being Select).
So my question now becomes is all this custom accessibility I'm
trying to add to my app worth it?
To summarize what I've got done...
* All custom UI elements that have a direct Aqua equivalent
(checkbox, push button, etc.) are complete.
To summarize what I have not yet done...
* Custom UI elements that have no direct Aqua equivalent. Been
fighting the framework for weeks to get correct behavior to include
correct output via VoiceOver
* Handling of animated views. I want VoiceOver to speak new phrases
as state changes. These are all very low frequency anims and
adjustable by users. Framerates can range from 1 frame per second to
1 frame every 30 seconds. I have not had any success with the
various acc notifications.
Do others have apps with their own UI that you've successfully added
accessibility to? Or, is everyone here making their Aqua apps
accessible? If I'm the only one doing custom stuff, I may choose to
do the bare minimum at this point, and wait to add the rest when
Leopard ships; assuming of course APIs, feature requests, better docs
come in by then.
Thanks,
___________________________________________________________
Ricky A. Sharp mailto:email@hidden
Instant Interactive(tm) http://www.instantinteractive.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Accessibility-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden