Re: Problems with NVDA and latest Windows 10 1803


chris miles
 

On 17/05/2018 08:19, Steve Nutt wrote:

Well if I was on NVDA only today, I couldn�t do my job.� This is why it�s always good to have more than one screen reader.

�

Besides, you�re probably not on Windows 10 1803 Spring Creators, which is where these issues started for me.

�

But saying I should be using NVDA and not JAWS doesn�t really add value to this thread, I merely reported that NVDA is broken for me on several machines.

�

All the best


Steve

�

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Walker, Michael E
Sent: 16 May 2018 17:51
To: nvda@nvda.groups.io
Subject: Re: [nvda] Problems with NVDA and latest Windows 10 1803

�

NVDA is broken? How so? I am on NVDA 2018.1.1. I always tell people thinking about using JAWS that they should be long on NVDA and short on JAWS, since NVDA is free and open source, and provides the same quality. It is kind of like John Wayne�s advice to be long on ears and short on jaws, but with my screen reader twist.

�

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Steve Nutt
Sent: Wednesday, May 16, 2018 11:48 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Problems with NVDA and latest Windows 10 1803

�

Hi,

�

I have to say, over all, Windows 10 is snappier than Windows 7 ever was.

�

It�s just these glitches that get us.

�

What�s odd with this particular issue is that NVDA and Narrator are quite broken, but JAWS is a happy screen reader.� So they are obviously doing some serious hacking to get UIA to work as well as it does with JAWS.

�

All the best

�

Steve

�

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gene
Sent: 16 May 2018 17:00
To: nvda@nvda.groups.io
Subject: Re: [nvda] Problems with NVDA and latest Windows 10 1803

�

That is only true if a lot of users, sighted users, get annoyed enough to matter.� A lot of the changes that inconvenience blind users until they learn how to use them may be intuitive and quickly understood by sighted users.� and, in the case of screen-reader problems, sighted people wouldn't have any of those problems.� Also, as in the new feature of sets, they may not be on by default.� As I recall what I read, sets is off by default.

�

But every time a new major update to Windows comes out, I see enough blind users have problems that I'm in no hurry to get Windows 10.� Even if the problems are temporary, such as screen-reader problems that are dealt with not too long after the upgrade, Windows 10 has nothing I want that justifies even relatively minor inconveniences time after time.

�

I'll get it when I get a new computer.� I won't upgrade a machine that is working very well with an earlier version of Windows.

�

Gene

----- Original Message -----

Sent: Wednesday, May 16, 2018 10:47 AM

Subject: Re: [nvda] Problems with NVDA and latest Windows 10 1803

�

I think the one thing I'm really annoyed about is that Microsoft keep on
fiddling with things that used to work and making them not work. I have
actually given� up on 10 as a working platform, unless Microsoft can simply
provide a system stable and just with security updates like windows 7. They
are not doing themselves any good by bringing out new versions of windows
every6 months or so in my view, they are going to make Windows 7 into the
keep hold of system just like XP if they are not more careful. Fine have new
features but do not change the whole concept and still call it windows 10.
that is just silly. That is my feeling after being exposed to their messing
about. its as if the developers who used to regularly screw up Skype have
been let loose on the innards of Windows!
�Hides behind sofa.� Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Steve Nutt" <steve@...>
To: <nvda@nvda.groups.io>
Sent: Wednesday, May 16, 2018 3:44 PM
Subject: Re: [nvda] Problems with NVDA and latest Windows 10 1803


> Oh and isn't it time NVDA installed Win 10 essentials automagically if Win
> 10 is detected?� New users shouldn't certainly have to go hunting for
> addons
> for their screen reader.
>
> All the best
>
> Steve
>
> -----Original Message-----
> From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Steve Nutt
> Sent: 16 May 2018 15:43
> To: nvda@nvda.groups.io
> Subject: Re: [nvda] Problems with NVDA and latest Windows 10 1803
>
> Hi,
>
> I just downloaded Win 10 essentials stable today, but it doesn't seem to
> make much difference.
>
> I must play a bit more.
>
> All the best
>
> Steve
>
> -----Original Message-----
> From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian's Mail
> list account via Groups.Io
> Sent: 16 May 2018 13:17
> To: nvda@nvda.groups.io
> Subject: Re: [nvda] Problems with NVDA and latest Windows 10 1803
>
> I expect Joseph will be along soon to ask about the� version of win 10
> essentials you have, but have you tried the pre release master snap?
> If that fails too then somebody in the development team needs to try to
> isolate what makes some machines work and others not.
> Brian
>
> bglists@...
> Sent via blueyonder.
> Please address personal E-mail to:-
> briang1@..., putting 'Brian Gaff'
> in the display name field.
> ----- Original Message -----
> From: "Steve Nutt" <steve@...>
> To: <nvda@nvda.groups.io>
> Sent: Wednesday, May 16, 2018 12:31 PM
> Subject: Re: [nvda] Problems with NVDA and latest Windows 10 1803
>
>
>> Hi Jacob,
>>
>>
>>
>> I have three machines here, all on 1803.� None of them work at all
>> well with NVDA in Windows 10, in fact, File Explorer is pretty much
>> unusable, as is Outlook.
>>
>>
>>
>> At this point, I'm glad I have JAWS as well.� But I don't know why
>> NVDA is so broken with 1803, more so than JAWS.
>>
>>
>>
>> All the best
>>
>>
>> Steve
>>
>> From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Jacob
>> Kruger
>> Sent: 16 May 2018 09:10
>> To: nvda@nvda.groups.io
>> Subject: Re: [nvda] Problems with NVDA and latest Windows 10 1803
>>
>>
>>
>> Steve, this sounds almost like an iteration of what I was mentioning -
>> it seems to fluctuate/vary quite a bit on/off on my one windows 10
>> 1803 machine, which is a lenovo laptop, whereas on my slightly lower
>> hardware specification desktop machine, that does however have a solid
>> state operating system drive in it, it actually seems to react a bit
>> more consistently, in terms of reading out list items, like in file
>> explorer, to me, and, this is with both of them running windows 10
>> 1803 pro 64 bit, and, currently both running NVDA master snapshot.
>>
>>
>>
>> Stay well
>>
>>
>>
>> Jacob Kruger
>> Blind Biker
>> Skype: BlindZA
>> "Resistance is futile...but, acceptance is versatile..."
>>
>> On 5/16/2018 10:03 AM, Steve Nutt wrote:
>>
>> Hi,
>>
>>
>>
>> I recently reported that Outlook message lists were not reading for me.
>>
>>
>>
>> It is in fact worse than that, lists in general don't seem to be reading.
>> For example, File Explorer in Windows 10 is completely silent for me now.
>>
>>
>>
>> JAWS is reading lists quite happily.
>>
>>
>>
>> Any thoughts?
>>
>>
>>
>> Thanks.
>>
>>
>>
>> All the best
>>
>>
>>
>> Steve
>>
>>
>>
>> --
>>
>> Computer Room Services
>>
>> 77 Exeter Close
>>
>> Stevenage
>>
>> Hertfordshire
>>
>> SG1 4PW
>>
>> Tel: +44(0)1438-742286
>>
>> Mob: +44(0)7956-334938
>>
>> Fax: +44(0)1438-759589
>>
>> Email:� <mailto:steve@...> steve@...
>>
>> Web:� <http://www.comproom.co.uk/> http://www.comproom.co.uk
>>
>>
>>
>>
>>
>>
>>
>>
>
>
>
>
>
>
>
>
>
>
>
>
>
>

Hi,


I wish to disagree. I recently tried to use NVDA with Access 2016 as it was part of a college course. NVDA is unable to read any of the fields in the table view so I cannot know which column I am in; NVDA could not read sort column to choose A for ascending or D for descending.I could not choose which criterior I wanted to choose. The only way I could achieve this was to have my tutor tell me what I needed to do.


If I could afford to use JAWS, I would have been able to do these procedures on my own. So when will NVDA be able to cope with MS Access 2016 or later?�

Join nvda@nvda.groups.io to automatically receive all group messages.