WebAIM - Web Accessibility In Mind

E-mail List Archives

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

for

From: chagnon@pubcom.com
Date: Dec 9, 2020 3:51PM

It's probably the app, not the screen readers. Especially if none of them
work with the app.
Quoted from www.access-board.gov

"The Section 508 Standards apply to electronic and information technology
procured by the federal government, including computer hardware and
software, websites, multimedia such as video, phone systems, and copiers."

Including hardware and software.
Most likely the developer of the app didn't make it accessible.

--Bevi

- - -
Bevi Chagnon | Designer, Accessibility Technician | <EMAIL REMOVED>
- - -
PubCom: Technologists for Accessible Design + Publishing
consulting . training . development . design . sec. 508 services
Upcoming classes at www.PubCom.com/classes
- - -
Latest blog-newsletter - Simple Guide to Writing Alt-Text

-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of glen
walker
Sent: Wednesday, December 9, 2020 5:01 PM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: [WebAIM] why would a desktop app not work with a screen reader?

Perhaps too broad of a question and probably depends on the technology, but
we installed a desktop app on both the PC and the Mac and NVDA, JAWS, and
VoiceOver could not be used with the app. You couldn't navigate to any
elements with VO (ctrl+opt+shift+downarrow didn't do anything) and when
tabbing on the PC, the screen reader was silent. Even Microsoft's
Accessibility Insights couldn't find any elements in the app. Kind of hard
to test when nothing registers with assistive technology.
http://webaim.org/discussion/archives