WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: why would a desktop app not work with a screen reader?

for

From: Jerra Strong
Date: Dec 10, 2020 2:46PM

I have seen mobile apps created with certain engines which are basically
"invisible" to the screen reader. It's about how the developer put the app
together, and whether any text, buttons, etc. are "exposed" to the
accessibility tools built into the system.

On Thu, Dec 10, 2020 at 12:49 PM glen walker < <EMAIL REMOVED> > wrote:

> The accessibility tree is a subset of the HTML DOM. A similar concept
> exists for any application running on the desktop. For example, on Windows
> platforms, the elements of an app should be surfaced through MSAA (or maybe
> it's UI Automation).
>
> In this case, since the Accessibility Insights tool doesn't work (which
> lets you inspect the MSAA), the app is not surfacing any information to
> assistive technology. I just found out the app is bundled with Adobe Air,
> which is typically used for Flash applications. I've done lots of Flash
> accessibility work so I know Flash apps can be accessible, but it's not
> pretty. If you build your Flash app without the accessibility option in
> the compiler, nothing will be surfaced to AT. I haven't confirmed yet if
> that's the exact problem but wanted to give an update.
> > > > >


--
Jerra Strong
Interim Accessible Conformance and Design Specialist
UNLV|Office of Accessibility Resources
Office of the Vice Provost for Academic Programs
<EMAIL REMOVED>
*Pronouns: He/Him/His*