WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Running ChromeVox as a library in a web page?

for

From: Robert Fentress
Date: Aug 31, 2017 9:25AM

I've *really* gotta make the time to explore UIA. I've heard you mention
it before and it seemed intriguing, but I just haven't gotten around to it
yet.

On Wed, Aug 30, 2017 at 9:26 PM, Jonathan Avila < <EMAIL REMOVED> >
wrote:

> > absent something like this, how you keep moving forward in terms of UI
> patterns.
>
> Ultimately we need a way to communicate the patterns a control supports,
> the actions associated with a control, and a method to activate those
> actions. Instead of solely relying on all sorts of keystrokes if there was
> a programmatic way to communicate this and perform the actions like those
> provided through the actions rotor on VoiceOver it would provide
> consistency and flexibility. Accessibility APIs like UIA support the
> above at some depth but the ARIA semantics still need to catch up as they
> are focused on roles and not patterns and there are not great ways of
> communicated in the DOM the different actions and perform those. Web
> accessibility will in time be moving into where we can access the
> accessibility API through JavaScript and these areas will be better
> supported. The challenge has been up to this point to get the assistive
> technology and user agents updated to support the current ARIA consistently
> -- which has taken years to get where we are today.
>
> Jonathan
>
> Jonathan Avila
> Chief Accessibility Officer
> Level Access, inc. (formerly SSB BART Group, inc.)
> (703) 637-8957
> <EMAIL REMOVED>
> Visit us online: Website | Twitter | Facebook | LinkedIn | Blog
> Looking to boost your accessibility knowledge? Check out our free webinars!
>
> The information contained in this transmission may be attorney privileged
> and/or confidential information intended for the use of the individual or
> entity named above. If the reader of this message is not the intended
> recipient, you are hereby notified that any use, dissemination,
> distribution or copying of this communication is strictly prohibited.
>
>