WebAIM - Web Accessibility In Mind

E-mail List Archives

Thread: Good explanation for Down/Up arrow behavior in JAWS and NVDA?

for

Number of posts in this thread: 2 (In chronological order)

From: Robert Fentress
Date: Mon, Sep 21 2015 9:45AM
Subject: Good explanation for Down/Up arrow behavior in JAWS and NVDA?
No previous message | Next message →

I'm trying to write a tutorial that explains the differences between
JAWS and NVDA and am having a difficult time describing in a clear and
accurate way why they behave the way they do when using the Up and
Down Arrow keys. For instance, right now, I'm saying that they will
each read "something like" a line of text (content?) and that that
line of text tends to be longer in JAWS than in NVDA. I'm already
explaining that holding down the control key will read an entire
"block of text" (better phrase?). Can anybody point me to something
that describes more precisely what is actually going on here?

Thanks,
Rob

--
Robert Fentress
Senior Accessibility Solutions Designer
540.231.1255

Technology-enhanced Learning & Online Strategies
Assistive Technologies
1180 Torgersen Hall
620 Drillfield Drive (0434)
Blacksburg, Virginia 24061

From: Jonathan C. Cohn
Date: Tue, Sep 22 2015 3:21PM
Subject: Re: Good explanation for Down/Up arrow behavior in JAWS and NVDA?
← Previous message | No next message

Make sure to try the new web reading in JAWS 17. Perhaps the read by line instead of web element will put the two systems on par.


Jonathan Cohn

> On Sep 21, 2015, at 11:45 AM, Robert Fentress < = EMAIL ADDRESS REMOVED = > wrote:
>
> I'm trying to write a tutorial that explains the differences between
> JAWS and NVDA and am having a difficult time describing in a clear and
> accurate way why they behave the way they do when using the Up and
> Down Arrow keys. For instance, right now, I'm saying that they will
> each read "something like" a line of text (content?) and that that
> line of text tends to be longer in JAWS than in NVDA. I'm already
> explaining that holding down the control key will read an entire
> "block of text" (better phrase?). Can anybody point me to something
> that describes more precisely what is actually going on here?
>
> Thanks,
> Rob
>
> --
> Robert Fentress
> Senior Accessibility Solutions Designer
> 540.231.1255
>
> Technology-enhanced Learning & Online Strategies
> Assistive Technologies
> 1180 Torgersen Hall
> 620 Drillfield Drive (0434)
> Blacksburg, Virginia 24061
> > > >