WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: screen reader versions for testing

for

From: JP Jamous
Date: Nov 3, 2016 2:54AM


NVDA has always supported it since Windows 10 came out. I tested it with NVDA 2015. JAWS is the one lagging behind. Let's hope it is full robust support and not something that will be hair-pulling.

-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Kevin Chao
Sent: Wednesday, November 2, 2016 10:50 PM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] screen reader versions for testing

Edge is supported by NVDA and JAWS 18 will be supported in December

On Wed, Nov 2, 2016 at 5:38 PM Sean Murphy < <EMAIL REMOVED> > wrote:

> That is interesting in relation to EDGE. I will have to check out the
> status of Edge support with Jaws. I believe NVDA provides some support now.
>
> Sean
> > On 3 Nov. 2016, at 8:13 am, Mallory < <EMAIL REMOVED> > wrote:
> >
> > One thing to be aware of for the future is, even JAWS might not be
> > able to do some of this later on. I know both JAWS and NVDA do some
> > sniffing around of the DOM and heuristics to make guesses of things,
> > but for example this isn't allowed any more on Edge (for security
> > reasons they've said) and I would expect most of the other browser
> > vendors to do the same, for the same reasons. I'm not sure what SRs
> > and other AT will do about that, since the reason they do it is poor
> > authoring.
> >
> > _mallory
> >
> > On Sat, Oct 29, 2016, at 03:45 AM, Beranek, Nicholas wrote:
> >> We test primarily with the latest versions of NVDA and Firefox.
> >> We've found that JAWS will compensate for bad coding practices
> >> (e.g. A missing programmatic label but adjacent text was present)
> >> and there were possibilities that it missed certain issues. If
> >> there is ever any question about the results from NVDA; then we'll
> >> try another browser. If it persists, we try another screen reader
> >> such as JAWS. Sometimes, we'll find that it's simply a user agent
> >> issue and we'll do our best to file a bug.
> > > > > > archives at http://webaim.org/discussion/archives
> > >
> > > archives at http://webaim.org/discussion/archives
> >