Date   

"Can NVDA speak the number of items in a list?

Ann Byrne
 

Using eudora, my email program of preference, JAWS reads the number of messages in the inbox, and which message I am on. So 5/15, for example. Is there a setting I can tweak so that NVDA will do this?

Thanks.

Ann


Re: access gmail settings

 

Once you're logged in to your Gmail account, use NVDA's search function (NVDA Key+Ctrl+F) and enter "Settings" as your search string.  The first thing it finds is the Settings button, which is collapsed and places focus on it.  When you activate the button it brings up a dropdown list/menu and "Settings" is one of the entries.  That's the entry you should activate to get to all the settings you can tweak for Gmail, and there are a lot of those.
--
Brian

I worry a lot. . . I worry that no matter how cynical you become it's never enough to keep up.

         ~ Trudy, in Jane Wagner's "Search for Signs of Intelligent Life in the Universe"

    



Re: Windows 10: A try build for NVDA users, featuring some enhancements to support Windows 10 Anniversary Update and other fixes

 

Hi,

This is an alternate branch. Some things are there in next snapshots (incubating as we speak), while I’m waiting for others to be included in the next snapshot. This try build serves as a field test to gather real world data and to let you know what’s going on in various development labs.

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Christopher Bartlett
Sent: Sunday, June 5, 2016 7:28 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10: A try build for NVDA users, featuring some enhancements to support Windows 10 Anniversary Update and other fixes

 

I'm on the fast ring for Win 10 and snapshot builds for NVDA.  Am I getting these features already, or is this an alternate branch?

Chris Bartlett

 

On Sun, Jun 5, 2016 at 5:42 AM, Joseph Lee <joseph.lee22590@...> wrote:

Hi everyone,

 

As a Windows Insider and a code contributor to NVDA, I believe you should not be left in the dark as to what’s going on in Windows 10 development. To shed light on what to expect in Anniversary Update and to show that screen reader developers do care about users and that we’re preparing for this update, I’d like to present an NVDA try build that you can use in latest Insider builds and on production systems.

 

About Anniversary Update: Windows 10 Anniversary Update (codenamed Redstone) is a feature upgrade for Windows 10 scheduled to come out sometime in July (summer for some, winter for others). This upgrade includes updated Narrator, a workspace for pen-based input called Windows Ink, more proactive Cortana, redesigned Start menu, Settings and others, new Edge improvements and under the hood improvements. For other screen readers, the most significant change is UI Automation control changes, slightly better UIA and others.

 

What’s possible with the try build: The NVDA try build includes following features and fixes (some of them will require that you install this build):

 

·         UAC: Microsoft has changed the design of User Account Control (UAC) screen in recent Insider builds. Unfortunately, due to use of modern technology, UAC may not be read by NVDA. This try build includes a fix so NVDA will now announce UAC prompts (you need to install the try build to take advantage of this).

·         Login prompts: Current versions of NVDA does not read Windows 10 logoin prompts. This try build fixes this (same requirement as above).

·         Password box and touchscreens: the issue of not being able to activate password edit field in Windows 10 via touchscreen has been fixed (requires the build be installed on a touchscreen computer).

·         Search results announcement: Due to host of changes made in Microsoft Edge, current stable versions of NVDA will not read Start search suggestions in recent Insider builds. This has been fixed.

·         Browse mode in Microsoft Edge: Same as above.

 

Technical: in case of the last two items, this is due to the fact that Microsoft has changed one of the UIA properties in Microsoft Edge, thus breaking third-party screen readers that supposedly supported Edge features such as browse mode.

 

Known issues:

 

·         Invalid entry announcement: In recent Insider builds, NVDA will announce “invalid entry” when it encounters universal apps and controls powered by it. Microsoft and NV Access are working on a fix.

·         UIA failing: In some cases, UIA may fail after using NVDA for a while. This results in various problems, including search suggestions not being announced, failing to announce toast notifications and so on. The fix is to restart NVDA, and this problem has been reported to both NV Access and Microsoft numerous times.

 

The try build can be downloaded from this direct link:

https://ci.appveyor.com/api/buildjobs/cvyyut95te36d0n3/artifacts/output/nvda_snapshot_try-redstone-13350,cc06c8f4.exe

 

If you have comments:

 

·         If you are on various NVDA mailing lists, please do comment there.

·         You can also send a message to me via email at joseph.lee22590@..., via Twitter at @joslee, or look for josephsl on Facebook.

 

Thank you.

Cheers,

Joseph




--

Christopher Bartlett


Re: Itunes update

Ingrid-Merethe Berget <iberget1@...>
 

Thank you Chris,

I downloaded the addon and got it to work. Being blind, I never have used a mouse before and it proves to be quite challenging and different to navigating with just the keyboard. For now I will make it work, still hoping for a more permanent fix of the problem though :)

Thank you so much for your help, so happy I found this mailing list!

Ingrid-Merethe


Den 04.06.2016 22:18, skrev Chris Shook:

Ingrid,
I am unaware if this is an iTunes or NVDA issue. I do have something that may help. You could try downloading the following addon for NVDA.
http://addons.nvda-project.org/addons/goldenCursor.en.html
It may help. It is supposed to allow you to move the mouse using the keyboard.
Chris


access gmail settings

mattias
 

on the pc

when you go to gmail.com and loging in

how to access gmail settings


Re: Meet NVDA 2016.2, bringing spelling error beep, grammar error detection and more to your work, home and everything in between #NVAccess #release

Life My Way
 

you need to go into your nvda folder and do your context menu key and un check the particual check box and apply to all files and folder because sometimes this gets it into a read only method.

On 6/5/2016 11:07 AM, Rui Fontes wrote:
It will not allow save any changes, or only Voice setting changes?

Rui


-----Mensagem Original-----
De: Jolene Cardenas
Data: domingo, 5 de junho de 2016 03:21
Para: nvda@nvda.groups.io
Assunto: Re: [nvda] Meet NVDA 2016.2, bringing spelling error beep, grammar
error detection and more to your work, home and everything in between
#NVAccess #release

Hello,

I had just downloaded and installed this version of NVDA a few days
ago and noticed that it still wouldn't let me save my current
configuration settings.

I'm aware that some of you have shared helpful tips on how I could do
this in the previous version, but I admit I had waited until this new
version came out before doing anything, and it still wouldn't let me
save the configurations.

Is there something else I could do besides something drastic like
uninstalling this current version of NVDA from my Windows 10-based
Asus laptop, deleting the Profile folder from my Users folder, and
then reinstalling it again?

Since I don't have a backup laptop or device of any kind to use in
case something goes wrong, I'm afraid of doing anything drastic.
Please help.

Thank you very much, and have a good day.

aloha,

Jolene.






Re: Meet NVDA 2016.2, bringing spelling error beep, grammar error detection and more to your work, home and everything in between #NVAccess #release

Rui Fontes
 

It will not allow save any changes, or only Voice setting changes?

Rui


-----Mensagem Original-----
De: Jolene Cardenas
Data: domingo, 5 de junho de 2016 03:21
Para: nvda@nvda.groups.io
Assunto: Re: [nvda] Meet NVDA 2016.2, bringing spelling error beep, grammar
error detection and more to your work, home and everything in between
#NVAccess #release

Hello,

I had just downloaded and installed this version of NVDA a few days
ago and noticed that it still wouldn't let me save my current
configuration settings.

I'm aware that some of you have shared helpful tips on how I could do
this in the previous version, but I admit I had waited until this new
version came out before doing anything, and it still wouldn't let me
save the configurations.

Is there something else I could do besides something drastic like
uninstalling this current version of NVDA from my Windows 10-based
Asus laptop, deleting the Profile folder from my Users folder, and
then reinstalling it again?

Since I don't have a backup laptop or device of any kind to use in
case something goes wrong, I'm afraid of doing anything drastic.
Please help.

Thank you very much, and have a good day.

aloha,

Jolene.


Re: windows ten insider builds

Antony Stone
 

Well, according to http://www.howtogeek.com/224826/

"To stop getting insider builds, you can simply visit the “Advanced options”
page in the Windows Update settings again and click “Stop Insider builds.”
You’ll be thanked for participating and your computer will reboot. You don’t
actually have to leave the insider program with your Microsoft account."

Hope that helps,


Antony.

On Sunday 05 June 2016 at 16:31:37, Rayette Rucker wrote:

Is there an accessible way to opt out of Insider builds for windows 10.
I want to update my computer but don't want the insider builds anymore.
--
"In fact I wanted to be John Cleese and it took me some time to realise that
the job was already taken."

- Douglas Adams

Please reply to the list;
please *don't* CC me.


Re: Windows 10: A try build for NVDA users, featuring some enhancements to support Windows 10 Anniversary Update and other fixes

Brian's Mail list account <bglists@...>
 


It seems to me that the nvda snapshot page might need a bit of a rethink.
 At the moment it has cutting edge the next braanch
Master the stable branch, and
a release candidate branch, which is not the same as the release candidates posted elsewhere which are like full releases. Maybe the rc branch should become the rc downloads, and a new branch for special try builds should be added.
 At the moment having bits all over the place must be confusing.
 Brian

bglists@... 
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.

----- Original Message -----
Sent: Sunday, June 05, 2016 3:27 PM
Subject: Re: [nvda] Windows 10: A try build for NVDA users, featuring some enhancements to support Windows 10 Anniversary Update and other fixes

I'm on the fast ring for Win 10 and snapshot builds for NVDA.  Am I getting these features already, or is this an alternate branch?

Chris Bartlett


On Sun, Jun 5, 2016 at 5:42 AM, Joseph Lee <joseph.lee22590@...> wrote:

Hi everyone,

 

As a Windows Insider and a code contributor to NVDA, I believe you should not be left in the dark as to what’s going on in Windows 10 development. To shed light on what to expect in Anniversary Update and to show that screen reader developers do care about users and that we’re preparing for this update, I’d like to present an NVDA try build that you can use in latest Insider builds and on production systems.

 

About Anniversary Update: Windows 10 Anniversary Update (codenamed Redstone) is a feature upgrade for Windows 10 scheduled to come out sometime in July (summer for some, winter for others). This upgrade includes updated Narrator, a workspace for pen-based input called Windows Ink, more proactive Cortana, redesigned Start menu, Settings and others, new Edge improvements and under the hood improvements. For other screen readers, the most significant change is UI Automation control changes, slightly better UIA and others.

 

What’s possible with the try build: The NVDA try build includes following features and fixes (some of them will require that you install this build):

 

·         UAC: Microsoft has changed the design of User Account Control (UAC) screen in recent Insider builds. Unfortunately, due to use of modern technology, UAC may not be read by NVDA. This try build includes a fix so NVDA will now announce UAC prompts (you need to install the try build to take advantage of this).

·         Login prompts: Current versions of NVDA does not read Windows 10 logoin prompts. This try build fixes this (same requirement as above).

·         Password box and touchscreens: the issue of not being able to activate password edit field in Windows 10 via touchscreen has been fixed (requires the build be installed on a touchscreen computer).

·         Search results announcement: Due to host of changes made in Microsoft Edge, current stable versions of NVDA will not read Start search suggestions in recent Insider builds. This has been fixed.

·         Browse mode in Microsoft Edge: Same as above.

 

Technical: in case of the last two items, this is due to the fact that Microsoft has changed one of the UIA properties in Microsoft Edge, thus breaking third-party screen readers that supposedly supported Edge features such as browse mode.

 

Known issues:

 

·         Invalid entry announcement: In recent Insider builds, NVDA will announce “invalid entry” when it encounters universal apps and controls powered by it. Microsoft and NV Access are working on a fix.

·         UIA failing: In some cases, UIA may fail after using NVDA for a while. This results in various problems, including search suggestions not being announced, failing to announce toast notifications and so on. The fix is to restart NVDA, and this problem has been reported to both NV Access and Microsoft numerous times.

 

The try build can be downloaded from this direct link:

https://ci.appveyor.com/api/buildjobs/cvyyut95te36d0n3/artifacts/output/nvda_snapshot_try-redstone-13350,cc06c8f4.exe

 

If you have comments:

 

·         If you are on various NVDA mailing lists, please do comment there.

·         You can also send a message to me via email at joseph.lee22590@..., via Twitter at @joslee, or look for josephsl on Facebook.

 

Thank you.

Cheers,

Joseph




--
Christopher Bartlett


Re: Windows 10: A try build for NVDA users, featuring some enhancements to support Windows 10 Anniversary Update and other fixes

Brian's Mail list account <bglists@...>
 

Well, not transferred it over yet, but thus far its not screwed things up on xp as a portable install.
Brian always doing silly stuff!
 

bglists@... 
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: Joseph Lee
Sent: Sunday, June 05, 2016 10:42 AM
Subject: [nvda] Windows 10: A try build for NVDA users, featuring some enhancements to support Windows 10 Anniversary Update and other fixes

Hi everyone,

 

As a Windows Insider and a code contributor to NVDA, I believe you should not be left in the dark as to what’s going on in Windows 10 development. To shed light on what to expect in Anniversary Update and to show that screen reader developers do care about users and that we’re preparing for this update, I’d like to present an NVDA try build that you can use in latest Insider builds and on production systems.

 

About Anniversary Update: Windows 10 Anniversary Update (codenamed Redstone) is a feature upgrade for Windows 10 scheduled to come out sometime in July (summer for some, winter for others). This upgrade includes updated Narrator, a workspace for pen-based input called Windows Ink, more proactive Cortana, redesigned Start menu, Settings and others, new Edge improvements and under the hood improvements. For other screen readers, the most significant change is UI Automation control changes, slightly better UIA and others.

 

What’s possible with the try build: The NVDA try build includes following features and fixes (some of them will require that you install this build):

 

·         UAC: Microsoft has changed the design of User Account Control (UAC) screen in recent Insider builds. Unfortunately, due to use of modern technology, UAC may not be read by NVDA. This try build includes a fix so NVDA will now announce UAC prompts (you need to install the try build to take advantage of this).

·         Login prompts: Current versions of NVDA does not read Windows 10 logoin prompts. This try build fixes this (same requirement as above).

·         Password box and touchscreens: the issue of not being able to activate password edit field in Windows 10 via touchscreen has been fixed (requires the build be installed on a touchscreen computer).

·         Search results announcement: Due to host of changes made in Microsoft Edge, current stable versions of NVDA will not read Start search suggestions in recent Insider builds. This has been fixed.

·         Browse mode in Microsoft Edge: Same as above.

 

Technical: in case of the last two items, this is due to the fact that Microsoft has changed one of the UIA properties in Microsoft Edge, thus breaking third-party screen readers that supposedly supported Edge features such as browse mode.

 

Known issues:

 

·         Invalid entry announcement: In recent Insider builds, NVDA will announce “invalid entry” when it encounters universal apps and controls powered by it. Microsoft and NV Access are working on a fix.

·         UIA failing: In some cases, UIA may fail after using NVDA for a while. This results in various problems, including search suggestions not being announced, failing to announce toast notifications and so on. The fix is to restart NVDA, and this problem has been reported to both NV Access and Microsoft numerous times.

 

The try build can be downloaded from this direct link:

https://ci.appveyor.com/api/buildjobs/cvyyut95te36d0n3/artifacts/output/nvda_snapshot_try-redstone-13350,cc06c8f4.exe

 

If you have comments:

 

·         If you are on various NVDA mailing lists, please do comment there.

·         You can also send a message to me via email at joseph.lee22590@..., via Twitter at @joslee, or look for josephsl on Facebook.

 

Thank you.

Cheers,

Joseph


windows ten insider builds

Rayette Kay Rucker <rayette.rucker23@...>
 

Is there an accessible way to opt out of Insider builds for windows 10. I want to update my computer but don't want the insider builds anymore.


Re: Windows 10: A try build for NVDA users, featuring some enhancements to support Windows 10 Anniversary Update and other fixes

Christopher Bartlett
 

I'm on the fast ring for Win 10 and snapshot builds for NVDA.  Am I getting these features already, or is this an alternate branch?

Chris Bartlett


On Sun, Jun 5, 2016 at 5:42 AM, Joseph Lee <joseph.lee22590@...> wrote:

Hi everyone,

 

As a Windows Insider and a code contributor to NVDA, I believe you should not be left in the dark as to what’s going on in Windows 10 development. To shed light on what to expect in Anniversary Update and to show that screen reader developers do care about users and that we’re preparing for this update, I’d like to present an NVDA try build that you can use in latest Insider builds and on production systems.

 

About Anniversary Update: Windows 10 Anniversary Update (codenamed Redstone) is a feature upgrade for Windows 10 scheduled to come out sometime in July (summer for some, winter for others). This upgrade includes updated Narrator, a workspace for pen-based input called Windows Ink, more proactive Cortana, redesigned Start menu, Settings and others, new Edge improvements and under the hood improvements. For other screen readers, the most significant change is UI Automation control changes, slightly better UIA and others.

 

What’s possible with the try build: The NVDA try build includes following features and fixes (some of them will require that you install this build):

 

·         UAC: Microsoft has changed the design of User Account Control (UAC) screen in recent Insider builds. Unfortunately, due to use of modern technology, UAC may not be read by NVDA. This try build includes a fix so NVDA will now announce UAC prompts (you need to install the try build to take advantage of this).

·         Login prompts: Current versions of NVDA does not read Windows 10 logoin prompts. This try build fixes this (same requirement as above).

·         Password box and touchscreens: the issue of not being able to activate password edit field in Windows 10 via touchscreen has been fixed (requires the build be installed on a touchscreen computer).

·         Search results announcement: Due to host of changes made in Microsoft Edge, current stable versions of NVDA will not read Start search suggestions in recent Insider builds. This has been fixed.

·         Browse mode in Microsoft Edge: Same as above.

 

Technical: in case of the last two items, this is due to the fact that Microsoft has changed one of the UIA properties in Microsoft Edge, thus breaking third-party screen readers that supposedly supported Edge features such as browse mode.

 

Known issues:

 

·         Invalid entry announcement: In recent Insider builds, NVDA will announce “invalid entry” when it encounters universal apps and controls powered by it. Microsoft and NV Access are working on a fix.

·         UIA failing: In some cases, UIA may fail after using NVDA for a while. This results in various problems, including search suggestions not being announced, failing to announce toast notifications and so on. The fix is to restart NVDA, and this problem has been reported to both NV Access and Microsoft numerous times.

 

The try build can be downloaded from this direct link:

https://ci.appveyor.com/api/buildjobs/cvyyut95te36d0n3/artifacts/output/nvda_snapshot_try-redstone-13350,cc06c8f4.exe

 

If you have comments:

 

·         If you are on various NVDA mailing lists, please do comment there.

·         You can also send a message to me via email at joseph.lee22590@..., via Twitter at @joslee, or look for josephsl on Facebook.

 

Thank you.

Cheers,

Joseph




--
Christopher Bartlett


Re: Question About Portable Installation of NVDA

Gene
 

Try using Narrator and see if a message comes up that you need to respond to to allow it to run.  It could be UAC or something else.
 
Gene

----- Original Message -----
Sent: Saturday, June 04, 2016 3:59 PM
Subject: [nvda] Question About Portable Installation of NVDA

Hi Group,


Well, I got my new old back up computer--a Windows 7 with 4 GB RAM and a
duel core processor.


I do not have speech on it. This was semi-deliberate.  That is to say,
the seller wasn't familiar with that type of thing.  I got the system
set up and it boots into Windows; no problem.  I thought I'd be cool and
advanced and create a portable version of NVDA to gain audible access to
the system.  I created it from the 2016.2 installer no problem.  I
placed it on a USB drive and created a shortcut so that when I heard the
Windows sound on the new system for USB active, I could just press the
corresponding first letter to navigate to the shortcut and press enter. 
It worked fine on my new main system.  I tried this on the new old
system and for some reason, It doesn't work.  When I highlight the
shortcut that i created which begins with an exclamation point, and
press enter, nothing happens.  What could I be doing wrong?



--
They Ask Me If I'm Happy; I say Yes.
They ask: "How Happy are You?"
I Say: "I'm as happy as a stow away chimpanzee on a banana boat!"




Re: iTunes 12.4.1 update.

Matt Turner
 

Hi, I've done one awhile back.
I haven't updated it, because i don't use iTunes anymore.
If i recall, it's still up on Jean's sites

On 6/5/2016 4:27 AM, Cearbhall O'Meadhra wrote:
Hi,

I have downloaded the latest iTunes. Is there a good tutorial for using it
with NVDA?


All the best,

Cearbhall

m +353 (0)833323487 Ph: _353 (0)1-2864623 e: cearbhall.omeadhra@...



----------------------------------------------------------------------------
-----
I use the free version of Spam Reader to get rid of spam. The Professional
version doesn't have this disclaimer in outgoing emails.
Try Spam Reader (http://www.spam-reader.com) for free now!
-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Chris
Sent: Saturday, June 4, 2016 11:13 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] iTunes 12.4.1 update.

Many thanks , I can confirm it has improved using nvda


-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Clare
Page
Sent: 04 June 2016 10:00
To: nvda@nvda.groups.io
Subject: Re: [nvda] iTunes 12.4.1 update.

Hi!
In answer to your question, yes, I've updated iTunes to 12.4.1, that's the
correct version number, and it has definitely improved. I haven't tested
everything, but I can report that scrolling up and down lists works like it
used to, with NVDA reading whatever item you land on if you arrow down a
list, use the Page Up and Page Down or Home and End keys, or do first letter
navigation in the list. It also seems to me that iTunes opens and runs
faster than it used to on my Windows 7 laptop, but maybe I'm just lucky with
that.
Glad to see Apple bringing out an improved version so quickly!
Bye for now!
From Clare

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Matt
Turner
Sent: vendredi 3 juin 2016 15:37
To: nvda@nvda.groups.io
Subject: [nvda] iTunes 4.0.1 update.

Anyone tried the updated version of iTunes?

If so, does everything work again?












Re: espeak issue fixed

Sharni-Lee Ward
 

Brian, try listening to the Linda voice. I use Linda, as up until this
update, she was the only female voice I could stand, and I'm so used to
her that I can't handle any other voice for long periods, even with this
issue. Listen to words like "updated" and "message" and "notice" for the
problem I'm having. I use the default English voice and my inflection's
at 100%, if that helps any.


I confess I was so desperate to get rid of the problem that I didn't
think before acting. I'm still extremely wary of doing this again, but
if a more concrete solution is provided, I'll test it out on a portable
copy as has been recommended.

On 5/06/2016 5:53 PM, Brian's Mail list account wrote:
Well, often its a very good idea before any kind of fiddling like this
to create a portable version from it as it is in a folder you can get
to easily. That way, you can in fact get back quite easily I find.
This Espeak issue is weird as nobody I know who uses it here has any
issues. If this is just perhaps in one language other than UK English
this would I imagine point to an eror in the data.
As for why it screwed up, many reasons for this one. It only needs one
file to not copy or there to be other errors, and the engine will just
give up. Often another synth will work though.
I guess its a bit like gambling. Only gamble if you can afford to lose
your money/data in this case.

Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Shaun Everiss" <@smeveriss>
To: <nvda@nvda.groups.io>
Sent: Sunday, June 05, 2016 6:46 AM
Subject: Re: [nvda] espeak issue fixed


Hmmm?
Well I did do this and this has fixed my nvda I am not sure why yours
didn't fix.



On 5/06/2016 12:44 a.m., Sharni-Lee Ward wrote:
...


I just did this and succeeded in screwing up my copy of NVDA. I
copied in the "Espeak Data" folder as was suggested, and suddenly
everything NVDA was saying was incomprehensible to me. I tried to
undo what I'd done. All I ended up with was silence. Horrible,
horrible, unbroken silence. With sighted help, I did a system
restore, which accomplished nothing, then had to resort to using a
portable copy of NVDA which I hadn't updated since 2015.2,
uninstalling NVDA from my computer, reinstalling it from the
portable copy and updating it back to 2016.2. I've probably lost a
few dictionary entries and I'm right back where I started, but I
infinitely prefer speech with a few squished syllables to no NVDA at
all. Did I mention after I tried undo NVDA wouldn't even start,
probably because it's default synth had been stuffed around with? Oh
yeah, it did that.


I am never, ever messing with my screen readers data files again.

On 4/06/2016 7:21 PM, Shaun Everiss wrote:
Hi all.
Ok here is a solution to the espeak issue.
This will go on the skype group as well
https://www.dropbox.com/s/7e35z5au9bc05vh/espeak.7z?dl=1
Anyway, testing looks as if its the espeakdata itself either the
phonem or the actual synth data.
What I did.
While I was not able to find previous releases of 2016-2015 in
compiled form I was able to find via sourceforge 2014.4 and this had
espeak in it.
I coppied over the espeakdata folder over itself in nvda program
folder.
While this will have to be done for just about every coppy it does
mean that while espeak will remain the new ng with the voice as it
is, the squished crap is at least back to normal.
I have not tried to override the espeak dll but the link has 2
folders synthdrivers which has the old espeak state from 2014.4 and
the new ng dataset.
Anyway, it looks like its the data files rather than the driver itself.
So if we can figure out what the hell is going on with this, then it
may be easier to fix than we first thought.
Now I didn't replace the driver because although it has some harsh
elements I wanted to see what this would do.
Its fixed it such that the mangled squished elements are gone.
This file will remain up until at least we can fix it.
Aniother way is to download the latest old espeak sapi and run it I
have yet to see compiled ng binaries for windows sapi, etc so till
we see that and as long as sourceforge keeps the depricated espeak
project up we will be ok.
To the devs and such trying to solve this especially if you have
access to the espeak list which I have no desire to handle and since
this may happen on multiple platforms it seems to be the database
itself or something in the database causing the trouble currently
faced.
I am unsure about what part of the database is naff though, this
will require some other beepstard to troubleshoot.
I'd like to but I have never fiddled with this and pluss I am not
that interested.
For all users though this is one way out of the current issue for now.
The buty of this is as long as we replace the data we can still use
the latest engine.
I will keep other units the same however as it is not needed that we
fiddle with our units like this but at least for my own personal it
will work.







Re: espeak issue fixed

Sharni-Lee Ward
 

Brian, try listening to the Linda voice. I use Linda, as up until this
update, she was the only female voice I could stand, and I'm so used to
her that I can't handle any other voice for long periods, even with this
issue. Listen to words like "updated" and "message" and "notice" for the
problem I'm having. I use the default English voice and my inflection's
at 100%, if that helps any.


I confess I was so desperate to get rid of the problem that I didn't
think before acting. I'm still extremely wary of doing this again, but
if a more concrete solution is provided, I'll test it out on a portable
copy as has been recommended.

On 5/06/2016 5:53 PM, Brian's Mail list account wrote:
Well, often its a very good idea before any kind of fiddling like this
to create a portable version from it as it is in a folder you can get
to easily. That way, you can in fact get back quite easily I find.
This Espeak issue is weird as nobody I know who uses it here has any
issues. If this is just perhaps in one language other than UK English
this would I imagine point to an eror in the data.
As for why it screwed up, many reasons for this one. It only needs one
file to not copy or there to be other errors, and the engine will just
give up. Often another synth will work though.
I guess its a bit like gambling. Only gamble if you can afford to lose
your money/data in this case.

Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Shaun Everiss" <@smeveriss>
To: <nvda@nvda.groups.io>
Sent: Sunday, June 05, 2016 6:46 AM
Subject: Re: [nvda] espeak issue fixed


Hmmm?
Well I did do this and this has fixed my nvda I am not sure why yours
didn't fix.



On 5/06/2016 12:44 a.m., Sharni-Lee Ward wrote:
...


I just did this and succeeded in screwing up my copy of NVDA. I
copied in the "Espeak Data" folder as was suggested, and suddenly
everything NVDA was saying was incomprehensible to me. I tried to
undo what I'd done. All I ended up with was silence. Horrible,
horrible, unbroken silence. With sighted help, I did a system
restore, which accomplished nothing, then had to resort to using a
portable copy of NVDA which I hadn't updated since 2015.2,
uninstalling NVDA from my computer, reinstalling it from the
portable copy and updating it back to 2016.2. I've probably lost a
few dictionary entries and I'm right back where I started, but I
infinitely prefer speech with a few squished syllables to no NVDA at
all. Did I mention after I tried undo NVDA wouldn't even start,
probably because it's default synth had been stuffed around with? Oh
yeah, it did that.


I am never, ever messing with my screen readers data files again.

On 4/06/2016 7:21 PM, Shaun Everiss wrote:
Hi all.
Ok here is a solution to the espeak issue.
This will go on the skype group as well
https://www.dropbox.com/s/7e35z5au9bc05vh/espeak.7z?dl=1
Anyway, testing looks as if its the espeakdata itself either the
phonem or the actual synth data.
What I did.
While I was not able to find previous releases of 2016-2015 in
compiled form I was able to find via sourceforge 2014.4 and this had
espeak in it.
I coppied over the espeakdata folder over itself in nvda program
folder.
While this will have to be done for just about every coppy it does
mean that while espeak will remain the new ng with the voice as it
is, the squished crap is at least back to normal.
I have not tried to override the espeak dll but the link has 2
folders synthdrivers which has the old espeak state from 2014.4 and
the new ng dataset.
Anyway, it looks like its the data files rather than the driver itself.
So if we can figure out what the hell is going on with this, then it
may be easier to fix than we first thought.
Now I didn't replace the driver because although it has some harsh
elements I wanted to see what this would do.
Its fixed it such that the mangled squished elements are gone.
This file will remain up until at least we can fix it.
Aniother way is to download the latest old espeak sapi and run it I
have yet to see compiled ng binaries for windows sapi, etc so till
we see that and as long as sourceforge keeps the depricated espeak
project up we will be ok.
To the devs and such trying to solve this especially if you have
access to the espeak list which I have no desire to handle and since
this may happen on multiple platforms it seems to be the database
itself or something in the database causing the trouble currently
faced.
I am unsure about what part of the database is naff though, this
will require some other beepstard to troubleshoot.
I'd like to but I have never fiddled with this and pluss I am not
that interested.
For all users though this is one way out of the current issue for now.
The buty of this is as long as we replace the data we can still use
the latest engine.
I will keep other units the same however as it is not needed that we
fiddle with our units like this but at least for my own personal it
will work.







Windows 10: A try build for NVDA users, featuring some enhancements to support Windows 10 Anniversary Update and other fixes

 

Hi everyone,

 

As a Windows Insider and a code contributor to NVDA, I believe you should not be left in the dark as to what’s going on in Windows 10 development. To shed light on what to expect in Anniversary Update and to show that screen reader developers do care about users and that we’re preparing for this update, I’d like to present an NVDA try build that you can use in latest Insider builds and on production systems.

 

About Anniversary Update: Windows 10 Anniversary Update (codenamed Redstone) is a feature upgrade for Windows 10 scheduled to come out sometime in July (summer for some, winter for others). This upgrade includes updated Narrator, a workspace for pen-based input called Windows Ink, more proactive Cortana, redesigned Start menu, Settings and others, new Edge improvements and under the hood improvements. For other screen readers, the most significant change is UI Automation control changes, slightly better UIA and others.

 

What’s possible with the try build: The NVDA try build includes following features and fixes (some of them will require that you install this build):

 

·         UAC: Microsoft has changed the design of User Account Control (UAC) screen in recent Insider builds. Unfortunately, due to use of modern technology, UAC may not be read by NVDA. This try build includes a fix so NVDA will now announce UAC prompts (you need to install the try build to take advantage of this).

·         Login prompts: Current versions of NVDA does not read Windows 10 logoin prompts. This try build fixes this (same requirement as above).

·         Password box and touchscreens: the issue of not being able to activate password edit field in Windows 10 via touchscreen has been fixed (requires the build be installed on a touchscreen computer).

·         Search results announcement: Due to host of changes made in Microsoft Edge, current stable versions of NVDA will not read Start search suggestions in recent Insider builds. This has been fixed.

·         Browse mode in Microsoft Edge: Same as above.

 

Technical: in case of the last two items, this is due to the fact that Microsoft has changed one of the UIA properties in Microsoft Edge, thus breaking third-party screen readers that supposedly supported Edge features such as browse mode.

 

Known issues:

 

·         Invalid entry announcement: In recent Insider builds, NVDA will announce “invalid entry” when it encounters universal apps and controls powered by it. Microsoft and NV Access are working on a fix.

·         UIA failing: In some cases, UIA may fail after using NVDA for a while. This results in various problems, including search suggestions not being announced, failing to announce toast notifications and so on. The fix is to restart NVDA, and this problem has been reported to both NV Access and Microsoft numerous times.

 

The try build can be downloaded from this direct link:

https://ci.appveyor.com/api/buildjobs/cvyyut95te36d0n3/artifacts/output/nvda_snapshot_try-redstone-13350,cc06c8f4.exe

 

If you have comments:

 

·         If you are on various NVDA mailing lists, please do comment there.

·         You can also send a message to me via email at joseph.lee22590@..., via Twitter at @joslee, or look for josephsl on Facebook.

 

Thank you.

Cheers,

Joseph


Notice some people struggling to find windows 10 com[ponents.

Brian's Mail list account BY <bglists@...>
 

Pinched from another list.
This might help you out.

Enabling GodMode is pretty simple. You simply create a new folder (can be created anywhere, but I suggest

putting it on the Windows 10 Desktop so it's easy to locate), and give the new folder an intricately

specific name.
1. Create a New Folder on the desktop.
2. Rename the folder to exactly this (copy and paste is best):
GodMode.{ED7BA470-8E54-465E-825C-99712043E01C}
Voila! Welcome to GodMode! Have fun with it.

Well, basically its a nice list of links to parts of windows searching sometimes misses, or in my case my typos probably miss..
Brrian
bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.


Re: iTunes 12.4.1 update.

Cearbhall O'Meadhra
 

Hi,

I have downloaded the latest iTunes. Is there a good tutorial for using it
with NVDA?


All the best,

Cearbhall

m +353 (0)833323487 Ph: _353 (0)1-2864623 e: cearbhall.omeadhra@...



----------------------------------------------------------------------------
-----
I use the free version of Spam Reader to get rid of spam. The Professional
version doesn't have this disclaimer in outgoing emails.
Try Spam Reader (http://www.spam-reader.com) for free now!

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Chris
Sent: Saturday, June 4, 2016 11:13 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] iTunes 12.4.1 update.

Many thanks , I can confirm it has improved using nvda



-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Clare
Page
Sent: 04 June 2016 10:00
To: nvda@nvda.groups.io
Subject: Re: [nvda] iTunes 12.4.1 update.

Hi!
In answer to your question, yes, I've updated iTunes to 12.4.1, that's the
correct version number, and it has definitely improved. I haven't tested
everything, but I can report that scrolling up and down lists works like it
used to, with NVDA reading whatever item you land on if you arrow down a
list, use the Page Up and Page Down or Home and End keys, or do first letter
navigation in the list. It also seems to me that iTunes opens and runs
faster than it used to on my Windows 7 laptop, but maybe I'm just lucky with
that.
Glad to see Apple bringing out an improved version so quickly!
Bye for now!
From Clare

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Matt
Turner
Sent: vendredi 3 juin 2016 15:37
To: nvda@nvda.groups.io
Subject: [nvda] iTunes 4.0.1 update.

Anyone tried the updated version of iTunes?

If so, does everything work again?


Re: espeak issue fixed

Brian's Mail list account BY <bglists@...>
 

Well, often its a very good idea before any kind of fiddling like this to create a portable version from it as it is in a folder you can get to easily. That way, you can in fact get back quite easily I find.
This Espeak issue is weird as nobody I know who uses it here has any issues. If this is just perhaps in one language other than UK English this would I imagine point to an eror in the data.
As for why it screwed up, many reasons for this one. It only needs one file to not copy or there to be other errors, and the engine will just give up. Often another synth will work though.
I guess its a bit like gambling. Only gamble if you can afford to lose your money/data in this case.

Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Shaun Everiss" <@smeveriss>
To: <nvda@nvda.groups.io>
Sent: Sunday, June 05, 2016 6:46 AM
Subject: Re: [nvda] espeak issue fixed


Hmmm?
Well I did do this and this has fixed my nvda I am not sure why yours didn't fix.



On 5/06/2016 12:44 a.m., Sharni-Lee Ward wrote:
...


I just did this and succeeded in screwing up my copy of NVDA. I copied in the "Espeak Data" folder as was suggested, and suddenly everything NVDA was saying was incomprehensible to me. I tried to undo what I'd done. All I ended up with was silence. Horrible, horrible, unbroken silence. With sighted help, I did a system restore, which accomplished nothing, then had to resort to using a portable copy of NVDA which I hadn't updated since 2015.2, uninstalling NVDA from my computer, reinstalling it from the portable copy and updating it back to 2016.2. I've probably lost a few dictionary entries and I'm right back where I started, but I infinitely prefer speech with a few squished syllables to no NVDA at all. Did I mention after I tried undo NVDA wouldn't even start, probably because it's default synth had been stuffed around with? Oh yeah, it did that.


I am never, ever messing with my screen readers data files again.

On 4/06/2016 7:21 PM, Shaun Everiss wrote:
Hi all.
Ok here is a solution to the espeak issue.
This will go on the skype group as well
https://www.dropbox.com/s/7e35z5au9bc05vh/espeak.7z?dl=1
Anyway, testing looks as if its the espeakdata itself either the phonem or the actual synth data.
What I did.
While I was not able to find previous releases of 2016-2015 in compiled form I was able to find via sourceforge 2014.4 and this had espeak in it.
I coppied over the espeakdata folder over itself in nvda program folder.
While this will have to be done for just about every coppy it does mean that while espeak will remain the new ng with the voice as it is, the squished crap is at least back to normal.
I have not tried to override the espeak dll but the link has 2 folders synthdrivers which has the old espeak state from 2014.4 and the new ng dataset.
Anyway, it looks like its the data files rather than the driver itself.
So if we can figure out what the hell is going on with this, then it may be easier to fix than we first thought.
Now I didn't replace the driver because although it has some harsh elements I wanted to see what this would do.
Its fixed it such that the mangled squished elements are gone.
This file will remain up until at least we can fix it.
Aniother way is to download the latest old espeak sapi and run it I have yet to see compiled ng binaries for windows sapi, etc so till we see that and as long as sourceforge keeps the depricated espeak project up we will be ok.
To the devs and such trying to solve this especially if you have access to the espeak list which I have no desire to handle and since this may happen on multiple platforms it seems to be the database itself or something in the database causing the trouble currently faced.
I am unsure about what part of the database is naff though, this will require some other beepstard to troubleshoot.
I'd like to but I have never fiddled with this and pluss I am not that interested.
For all users though this is one way out of the current issue for now.
The buty of this is as long as we replace the data we can still use the latest engine.
I will keep other units the same however as it is not needed that we fiddle with our units like this but at least for my own personal it will work.