The approach you're suggesting might solve other problems. One of the
considerations with Accessibility and Focus is with how the
Screen-Reader decides which label to read. Setting Focus on a control
that then triggers a toolTip / validation message . Alert Window, for
example, drives the Screen-R
The ANE is something I'm developing under contract, so it is not something
I can release at this time. The biggest problem when working with ANEs is
that when you make a call out (for example, the function to send to
the accessibility subsystem in iOS, it happens asynchronously (actually, in
its o
Nicholas,
Is the ANE something you could share?
I had a problem with Focus on an accessible control, where setting
focus on the control crashed the browser (without an error).
There might be options to dealing with your focus issue. For example,
there's an operation available in FP (getNextFocus
Changing Thread Name
On Thu, Jan 26, 2012 at 10:00 PM, Nicholas Kwiatkowski
wrote:
> I've been doing a lot of work with Michigan State University's Research
> Center for Persons with Disabilities (RCPD for short). Their
> recommendation for the blind up until two years ago was JAWS with IE. The
