Date   

Re: 2019.1 appears to be out

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

Funnily enough I did not get it that way, I did a manual check as I know it can, and often does, update some hours sometimes into the operation of it, and as we were on rc1, I tend to force the issue to stop it if its there. Not sure what logic governs the system of updating but it seems to be pretty random.
Brian

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

----- Original Message -----
From: "Brian Vogel" <@britechguy>
To: <nvda@nvda.groups.io>
Sent: Monday, March 25, 2019 9:40 PM
Subject: Re: [nvda] 2019.1 appears to be out


And, with myself being number 3 (on this topic) I full well expect that everyone will be offered 2019.1 when they fire up NVDA over the next several days.
--

Brian *-* Windows 10 Home, 64-Bit, Version 1809, Build 17763

*The Internet is so big, so powerful and pointless that for some people it is a complete substitute for life.* *
* ~ Andrew Brown (1938-1994)**


Re: playing you tube with NVDA

 

Since I believe this question is well suited to this topic:
Guys, how we would access the comments' section on a YouTube video?
Quite a while ago, someone came up with a workaround for that, which initially worked like a charm. However, it's not working anymore.
So, is there a reliable way of doing just it?

Cheers,
Marcio AKA Starboy
Follow or add me on Facebook

Em 25/03/2019 20:08, Kerryn Gunness via Groups.Io disse:

HI all
are there commands for playing  you tube videos using NVDA on windows?
like to pause, fast forward, rewine etc?
thanks






Question about reading an entire line with NVDA

 

Hey guys, I'm here again :)
This time the question is about... well you saw it on the subject I suppose :)
So, the thing is: I found out that pressing CTRL along with the down arrow, NVDA will read the entire line from a text, regardless if that line is broken for some reason.
However, while I just found it out, I also found out that apparently, this  option isn't described on the NVDA's keystrokes refference.
So my question: is it actually something expected, that pressing CTRL+down arrow NVDA will read the entire line? If so, why isn't it described as an option?
Or, well, what would I be missing? Can anyone point me on the right direction? :)

Cheers,
Marcio AKA Starboy
Follow or add me on Facebook


Re: Profiles and a suggestion

 

Yes, I'm sure, actually I just tested it before posting :)
Besides don't having the option to turn on NVDA's sleep mode, one also can't turn NVDA's silent speech mode.
One thing I forgot to mention, since I wrote that email just before falling asleep, is that it doesn't mean one can't use these options.
What happens, actually, is that when one uses these options, they affect all the other windows NVDA happen to see, rather than the one for that profile.

Cheers,
Marcio AKA Starboy
Follow or add me on Facebook

Em 25/03/2019 11:28, Brian's Mail list account via Groups.Io disse:

Are you sure about that. I have some self voicing programs where I use an add on to turn off nvda when a range of exe files are detected as in focus. I'm sure it goes back a long way, even before the official add on loading system when you could just write a bit of python and shove it in  the global add on folder.
It still seems to be working. The only oddity is that if they have a bit of code that uses resources from normal windows which requires the dialogue to load a file, for example, the nvda comes in and some of the self voicing use another method to speak as well so it can get a bit  confusing!
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "marcio via Groups.Io" <marcinhorj21@...>
To: <nvda@nvda.groups.io>
Sent: Monday, March 25, 2019 10:00 AM
Subject: [nvda] Profiles and a suggestion


Hi guys,
Well I was just now playing a bit with NVDA profiles to test an add-on
called Profile Switcher, which by the way has proved to be quite useful.
However my question isn't about this add-on otherwise I'd have posted it
on the appropriated list :)
So let's go.
I noticed that when it comes to profile, one can personalize settings
for a specific window, that's the whole point of it I'd guess.
However, there isn't an option to, according with a profile, turn
on/off NVDA's sleep mode.
Why isn't there such option? Isn't it possible, would it cause problems
or something like that?
Well anyway here is my suggestion. It would be nice if we could just set
up a profile to whenever we go to a certain window NVDA automatically
could go into sleep mode.

Cheers,
Marcio
AKA /Starboy/


Follow or add me on Facebook <https://facebook.com/firirinfonfon>












Re: NVDA and icons in the system tray

Kwork
 

Gene, as you know, I fully agree with you on this, and I've never ever understood why this has never been a part of core NVDA as I've always found it less buggy to use the systray add-on than the Windows methods, and other screenreaders have recognized this long ago.

Travis

On 3/26/2019 12:35 AM, Gene wrote:
And if the problem is a bug in the system tray, then its time, after years of scattered but persistent such reports, for the system tray dialog to finally be added to NVDA both because of this and because it has been standard in screen-readers since Windows 98 and is so standard and universal that it is expected.
 
Gene
----- Original Message -----
Sent: Monday, March 25, 2019 9:03 PM
Subject: Re: [nvda] NVDA and icons in the system tray

I've seen this problem too. Doesn't matter what screen reader or which
PC I use.  The system tray in Windows is a bit buggy me thinks.


Bob


On 2019-03-23 12:52 p.m., Gene wrote:
> I have seen this problem that occurs no matter how you try to activate one of the icons.
>
> Gene
> ----- Original Message -----
>
> From: Sarah k Alawami
> Sent: Saturday, March 23, 2019 1:49 PM
> To: nvda@nvda.groups.io
> Subject: Re: [nvda] NVDA and icons in the system tray
>
>
> What happens if you hit enter or hit shift f10? Both shoudl do what you want to do.
>
> Take care
>
> On 23 Mar 2019, at 11:23, Kostadin Kolev wrote:
>
>    Hello all,
>
>    NVDA seams to have problems activating some icons in the system tray, for example the one for OneDrive. At first I thought that it was not a NVDA specific issue but a global screen reader / accessibility one, but after testing with Narrator as well, it turns out that at least the problem with OneDrive's system tray icon is specific to NVDA (Narrator is not affected).
>
>    To reproduce the issue, I press Windows+B to go to the system tray. I use up/down arrow keys to move the focus to the OneDrive's icon (OneDrive must be running). Then I press the space key to simulate a single left click with the mouse. All those are Windows and not NVDA commands. With Narrator, this works as expected and the pop-up window for OneDrive appears. With NVDA however, nothing happens. A person which cannot see the screen would wonder why it is so - what is different. I have some vision left and can see what's going on. For some reason, when pressing Windows+B and the system focus gets moved to the system tray area, NVDA also moves the mouse cursor there and for some reason, that causes the failure of the execution of the command with the spacebar to simulate a single left mouse click. With Narrator and with no screen reader running, the mouse cursor does not get moved to the system tray when the system focus gets moved there and the command gets executed correctly and the OneDrive pop-up window appears as it should.
>
>    So, does anyone (specially the NVDA developers) know why NVDA moves the mouse cursor to the system tray area when the system focus gets moved there? Because apparently this causes problems with some icons in the system tray. And now that I think of it, I wouldn't be surprised if the appearance of the problematic so called "Network Flyout" pop-up window under Windows 7 is caused by this behavior as well.
>
>    P.S.: I'm not asking for help/assistance with workarounds to activate such "problematic" icons in the system tray - I know how to handle them, including with the "SysTrayList" add-on for NVDA. This is not the purpose of this message. I'm asking why NVDA is causing the explained above behavior of the mouse when pressing Windows+B.
>
>    Thanks much in advance!
>
>
>    ______
>    Best wishes,
>    Kostadin Kolev
>
>
>
>
>




Re: NVDA and icons in the system tray

Gene
 

And if the problem is a bug in the system tray, then its time, after years of scattered but persistent such reports, for the system tray dialog to finally be added to NVDA both because of this and because it has been standard in screen-readers since Windows 98 and is so standard and universal that it is expected.
 
Gene

----- Original Message -----
Sent: Monday, March 25, 2019 9:03 PM
Subject: Re: [nvda] NVDA and icons in the system tray

I've seen this problem too. Doesn't matter what screen reader or which
PC I use.  The system tray in Windows is a bit buggy me thinks.


Bob


On 2019-03-23 12:52 p.m., Gene wrote:
> I have seen this problem that occurs no matter how you try to activate one of the icons.
>
> Gene
> ----- Original Message -----
>
> From: Sarah k Alawami
> Sent: Saturday, March 23, 2019 1:49 PM
> To: nvda@nvda.groups.io
> Subject: Re: [nvda] NVDA and icons in the system tray
>
>
> What happens if you hit enter or hit shift f10? Both shoudl do what you want to do.
>
> Take care
>
> On 23 Mar 2019, at 11:23, Kostadin Kolev wrote:
>
>    Hello all,
>
>    NVDA seams to have problems activating some icons in the system tray, for example the one for OneDrive. At first I thought that it was not a NVDA specific issue but a global screen reader / accessibility one, but after testing with Narrator as well, it turns out that at least the problem with OneDrive's system tray icon is specific to NVDA (Narrator is not affected).
>
>    To reproduce the issue, I press Windows+B to go to the system tray. I use up/down arrow keys to move the focus to the OneDrive's icon (OneDrive must be running). Then I press the space key to simulate a single left click with the mouse. All those are Windows and not NVDA commands. With Narrator, this works as expected and the pop-up window for OneDrive appears. With NVDA however, nothing happens. A person which cannot see the screen would wonder why it is so - what is different. I have some vision left and can see what's going on. For some reason, when pressing Windows+B and the system focus gets moved to the system tray area, NVDA also moves the mouse cursor there and for some reason, that causes the failure of the execution of the command with the spacebar to simulate a single left mouse click. With Narrator and with no screen reader running, the mouse cursor does not get moved to the system tray when the system focus gets moved there and the command gets executed correctly and the OneDrive pop-up window appears as it should.
>
>    So, does anyone (specially the NVDA developers) know why NVDA moves the mouse cursor to the system tray area when the system focus gets moved there? Because apparently this causes problems with some icons in the system tray. And now that I think of it, I wouldn't be surprised if the appearance of the problematic so called "Network Flyout" pop-up window under Windows 7 is caused by this behavior as well.
>
>    P.S.: I'm not asking for help/assistance with workarounds to activate such "problematic" icons in the system tray - I know how to handle them, including with the "SysTrayList" add-on for NVDA. This is not the purpose of this message. I'm asking why NVDA is causing the explained above behavior of the mouse when pressing Windows+B.
>
>    Thanks much in advance!
>
>
>    ______
>    Best wishes,
>    Kostadin Kolev
>
>
>
>
>




Re: playing you tube with NVDA

Alina
 

Thanks for these. There are some I didn't know about.

Thanks again.

On Tue, 26 Mar 2019 at 02:28, Andre Fisher <andrefisher729@...> wrote:
Here are the shortcuts:

Action

Shortcut

Toggle play/pause the video

k or Spacebar

Go back 5 seconds

Left arrow

Go back 10 seconds

Go forward 5 seconds  

Right arrow

Go forward 10 seconds

l

Skip to a particular section of the video (e.g., 5 goes to the video midpoint)

Numbers 1-9 (not the keypad numbers)

Restart video

0 (not the keypad number)

Go to Full Screen mode

f

Exit Full Screen mode  

Escape

Go to beginning of video

Home

Go to end of video

End

Increase volume 5%

Up arrow

Decrease volume 5%

Down arrow        

Increase speed

Shift+> (may not work in all browsers) or Shift+(period)

Decrease speed

Shift+< (may not work in all browsers)  or Shift+(comma)     

Move forward 1 frame when video is paused

. (period)

Move backward 1 frame when video is paused

, (comma)

Mute/unmute video

m

Turn captions on/off

c

Cycle through options for caption background color

b   

Move to the previous video in a playlist       

Shift+p

Move to the next video in a playlist       

Shift+n

 



--

For God so loved the world, that he gave his only begotten Son, that whosoever believeth in him should not perish, but have eternal life.

John 3:16



Re: Kindle for PC

Aravind R
 

On 3/26/19, Quentin Christensen <quentin@...> wrote:
At one point, Amazon brought out an "accessible version" of the Kindle app,
which was separate from the regular download. When they brought out
version 1.19, it was early 2017 and around the time we released NVDA 2017.1
which brought accessibility to the "standard" kindle for PC app.
Essentially, any version of Kindle since then should be accessible.

Re the website for books, I must admit, I don't read many kindle books
myself so haven't played with it much, but if there is a problem, do raise
it. If it's with the website, it's likely an issue for Amazon, but of
course it is worth us being aware of it as well.

Quentin.

On Mon, Mar 25, 2019 at 8:45 PM hurrikennyandopo ... <
hurrikennyandopo@...> wrote:

Hi Brian


Just looking at the site for a accessible version of kindle for pc. funny
thing was on the accessibility page for it it is a very old version and
when downloaded apart from the menus was in not accessible.

I think it was like version 1.4 and 1.9 now and above is recommended.


I did read up you needed a later version of which i got but not from them
as i could not find it any where on there amazon website it seems like
you
go in circles.


the version i got now is accessible but if some one knows more of a
direct
link i will add that into the tutorial.




Would any one have a direct link to the latest version of it on there
website to download instead of searching for it off the net.

This is for the amazon website.


Just putting to together a tutorial on the basic's of using it once i
figure it out.

Or could you call it notes.


I see there are users on the list using it. I might have to sus out how
to
download other free books to or does some one on the list know how? and
what hoops i might have to jump through.

Or tips i can add into it.




Gene nz



On 25/03/2019 10:28 PM, Brian's Mail list account via Groups.Io wrote:

Was there not an issue with the web site for Kindle books, a link that
did
not show up properly?
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Quentin Christensen"
<quentin@...> <quentin@...>
To: <nvda@nvda.groups.io> <nvda@nvda.groups.io>
Sent: Monday, March 25, 2019 2:20 AM
Subject: Re: [nvda] Kindle for PC


Hi Don,

NVDA first got support for Kindle for PC (version 1.19 at the time) in
NVDA
2017.1, and it has improved since then.

We do have a few notes on using Kindle for PC in the NVDA user guide:
https://www.nvaccess.org/files/nvda/documentation/userGuide.html#Kindle

If you do have any specific questions or run into any problems, please do
let us know. Note that as per the first line in that section I linked
to,
this functionality is only available in Kindle books designated with
"Screen Reader: Supported" which you can check on the details page for
the
book.

Kind regards

Quentin.

On Mon, Mar 25, 2019 at 7:49 AM Don H <lmddh50@...>
<lmddh50@...> wrote:

Does NVDA work well with Kindle for PC for reading Kindel books?

Thanks







--
Quentin Christensen
Training and Support Manager

Official NVDA Training modules and expert certification now available:
http://www.nvaccess.org/shop/

www.nvaccess.org
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess








--
[image: Image NVDA certified expert]
Check out my website for NVDA tutorials and other blindness related
material at http://www.accessibilitycentral.net

Regardless of where you are in New Zealand if you are near one of the
APNK
sites you can use a copy of the NVDA screen reader on one of their
computers. To find out which location (or locations) are nearest to you
please visit
http://www.aotearoapeoplesnetwork.org/content/partner-libraries (Aotearoa
People's Network Kaharoa). To find out which software is installed on the
APNK network please visit the following link
http://www.aotearoapeoplesnetwork.info/faq/software
To find out how to use NVDA on APNK computers please visit the following
link http://www.aotearoapeoplesnetwork.info/faq/nvda

To find out which software is available on the Christchurch City Library
network, and how to start the NVDA screen reader, please go to the
following links. Software available
https://my.christchurchcitylibraries.com/faq/computers/#faq_5884 How to
start the NVDA screen reader on Christchurch City Library computers
https://my.christchurchcitylibraries.com/faqs/what-screen-reader-software-is-available/

To find an NVDA certified expert near you, please visit the following
link
https://certification.nvaccess.org/. The certification page contains the
official list of NVDA certified individuals from around the world, who
have
sat and successfully passed the NVDA expert exam.



--
Quentin Christensen
Training and Support Manager

Official NVDA Training modules and expert certification now available:
http://www.nvaccess.org/shop/

www.nvaccess.org
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess




--
--
nothing is difficult unless you make it appear so.

r. aravind,

Assistant manager
Department of sales
bank of baroda specialised mortgage store, Chennai.
mobile no: +91 9940369593,
email id : aravind_069@..., aravind.andhrabank@....
aravind.rajendran@....


Re: Off topic

Jaffar Sidek
 

Hi.  There are tons of free SFZ files you can find on the internet.  Just google for them.  I particularly like sforzando which is used by many blind musicians who use Reaper and Sonar.  You can even modify SFZ files to your liking because they are basically text files installed along side a wave file. Here is a link from where you can get more information.

https://www.plogue.com/downloads.html#sforzand

o

Cheers!


On 3/26/2019 8:12 AM, Ame wrote:

Hi!  I use QWS which I dearly love.  I have a casio keyboard and I’d like to expand the number of instruments I can use.  Is there a way to get hold of other instruments?  Not just casio ones?

 

Thanks

 

Ame


Re: How to Select a Link While n Browse Mode

bestuiexperience
 

Sorry to revive this thread so late. I now have  a new link problem  (but am unable to share the link because it is under development). I am clicking on a link that actually uses JavaScript. It has an href of "javascript:void()", and has a click() event (which is also triggered by pressing the enter key) which executes a JavaScript function. The first time, the enter key is pressed the function works correctly, but the second time, focus just flies randomly to another part of the page. If I change the link to a button everything works fine, but for various reasons I want to keep it as a link. Is this an NVDA bug? Any workaround? I do not have this issue in JAWS. 


On Wed, Feb 27, 2019 at 11:02 AM Brian Vogel <britechguy@...> wrote:
On Tue, Feb 26, 2019 at 04:32 AM, Brian's Mail list account wrote:
I'd be interested in what the page is and if the link is actually in focus
This is one of the things I keep begging people to include when questions like this come up.  They are almost impossible to answer in the abstract because there are so many potential scenarios that can cause misbehavior.

Unless this is occurring somewhere like an online banking page, where one must be logged in to get to it, and involves private information, please, please, please include the URL of the page in question, and the identification for the problematic link on that page.  That's the way any of us here can examine things to get an answer that's both fast, and accurate.
 
--

Brian - Windows 10 Home, 64-Bit, Version 1809, Build 17763  

A great deal of intelligence can be invested in ignorance when the need for illusion is deep.

          ~ Saul Bellow, To Jerusalem and Back

 

 


NVDA 2019.1 available

Quentin Christensen
 

Hi everyone,

Apologies for the slight delay in the announcement, and I see several of you have already posted about it, but yes, NV Access is pleased to announce that version 2019.1 of NVDA, the free screen reader for Microsoft Windows, has now been released.

Highlights of this release include performance improvements when accessing both Microsoft word and Excel, stability and security improvements such as support for add-ons with version compatibility information, and many other bug fixes.

In the release announcement at https://www.nvaccess.org/post/nvda-2019-1-now-available/ there is also important information about add-on compatibility.  Note that although the framework for having add-ons report versions compatibility is there, and we encourage all add-on developers to update their add-ons to include this if they haven't already - This version of NVDA will however still allow installing and loading of add-ons that do not yet contain Minimum and Last Tested NVDA version information at all, but upgrading to future versions of NVDA (E.g. 2019.2) may automatically cause these older add-ons to be disabled.

Kind regards

Quentin.

--
Quentin Christensen
Training and Support Manager

Official NVDA Training modules and expert certification now available: http://www.nvaccess.org/shop/

Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 


Re: Sending Logs

Quentin Christensen
 

It doesn't, but I was just suggesting running without add-ons at least would rule out that line of inquiry :)


On Mon, Mar 25, 2019 at 10:05 PM Rui Fontes <rui.fontes@...> wrote:
No.

And, the log does not mention any error due to addons...

Rui Fontes


Às 01:58 de 25/03/2019, Quentin Christensen escreveu:
> I haven't seen Abbie's log, but just looking at Rui's - if you restart
> NVDA with add-ons disabled does it make a difference?
>
> On Sat, Mar 23, 2019 at 3:29 AM Jackie <abletec@...
> <mailto:abletec@...>> wrote:
>
>     Rui, that was pretty confusing. At first I thought this was Abbie's
>     log, because she was the thread starter. Made even more confusing by
>     the fact that she'd sent a log very much different from the 1 in this
>     thread. I haven't had my full coffee quota yet, thus the main reason
>     for the confusion, but I also think it would likely help if you
>     started your own thread to avoid my poor little pea brain from getting
>     all tangled up around itself in future. Maybe others get confused as
>     well, I dunno, but I know it took me a minute or 2 to figure out
>     precisely what was occurring.
>
>     Normally when I ask folks for logs--& I do so quite regularly--I ask
>     them to put their name & date in the subject, ie, Rui Fontes log for
>     2019/03/21 or similar. That way I'm very clear on what I'm looking
>     at--& it often helps me know better what I'm looking for. Just a
>     suggestion--& no--I'm not vying for Brian V's job at all--that's not
>     my intent here. Just a conversation between folks who've known 1
>     another for years, asking for help so as not to get all tangled up in
>     the confusion zone.
>
>     On 3/22/19, Rui Fontes <rui.fontes@...
>     <mailto:rui.fontes@...>> wrote:
>      > Here is my log:
>      > I was sending a message through Mozilla Thunderbird...
>      >
>      > INFO - __main__ (10:23:39.753):
>      > Starting NVDA
>      > INFO - core.main (10:23:39.907):
>      > Config dir: C:\Users\tiflo\AppData\Roaming\nvda
>      > INFO - config.ConfigManager._loadConfig (10:23:39.907):
>      > Loading config: C:\Users\tiflo\AppData\Roaming\nvda\nvda.ini
>      > INFO - core.main (10:23:40.003):
>      > Developer Scratchpad mode enabled
>      > DEBUG - core.main (10:23:40.125):
>      > setting language to pt_PT
>      > INFO - core.main (10:23:40.174):
>      > NVDA version 2019.1rc1
>      > INFO - core.main (10:23:40.174):
>      > Using Windows version 10.0.17763 workstation
>      > INFO - core.main (10:23:40.174):
>      > Using Python version 2.7.15 (v2.7.15:ca079a3ea3, Apr 30 2018,
>     16:22:17)
>      > [MSC v.1500 32 bit (Intel)]
>      > INFO - core.main (10:23:40.174):
>      > Using comtypes version 1.1.3
>      > INFO - core.main (10:23:40.174):
>      > Using configobj version 5.1.0 with validate version 1.0.1
>      > DEBUG - core.main (10:23:40.184):
>      > Initializing add-ons system
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.196):
>      > Listing add-ons from C:\Users\tiflo\AppData\Roaming\nvda\addons
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.196):
>      > Loading add-on from
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\addonUpdater
>      > DEBUG - addonHandler.Addon.__init__ (10:23:40.203):
>      > Using manifest translation from
>      >
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\addonUpdater\locale\pt_PT\manifest.ini
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.213):
>      > Found add-on addonUpdater - 19.03. Requires API: (2018, 4, 0).
>      > Last-tested API: (2019, 1, 0)
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.213):
>      > Loading add-on from
>      > C:\Users\tiflo\AppData\Roaming\nvda\addons\applicationsDictionary
>      > DEBUG - addonHandler.Addon.__init__ (10:23:40.232):
>      > Using manifest translation from
>      >
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\applicationsDictionary\locale\pt_PT\manifest.ini
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.246):
>      > Found add-on applicationsDictionary - 1.0-beta. Requires API:
>     (2017, 1,
>      > 0). Last-tested API: (2019, 1, 0)
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.246):
>      > Disabling add-on applicationsDictionary
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.246):
>      > Loading add-on from
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\brailleme
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.250):
>      > Found add-on brailleme - 0.5. Requires API: (2018, 2, 0). Last-tested
>      > API: (2019, 1, 0)
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.250):
>      > Loading add-on from
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\browsernav
>      > DEBUG - addonHandler.Addon.__init__ (10:23:40.260):
>      > Using manifest translation from
>      >
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\browsernav\locale\pt_PT\manifest.ini
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.270):
>      > Found add-on browsernav - 1.1. Requires API: (2018, 1, 0).
>     Last-tested
>      > API: (2019, 1, 0)
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.276):
>      > Loading add-on from
>      > C:\Users\tiflo\AppData\Roaming\nvda\addons\clipContentsDesigner
>      > DEBUG - addonHandler.Addon.__init__ (10:23:40.282):
>      > Using manifest translation from
>      >
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\clipContentsDesigner\locale\pt_PT\manifest.ini
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.282):
>      > Found add-on clipContentsDesigner - 8.8. Requires API: (2018, 2, 0).
>      > Last-tested API: (2019, 1, 0)
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.282):
>      > Loading add-on from C:\Users\tiflo\AppData\Roaming\nvda\addons\clock
>      > DEBUG - addonHandler.Addon.__init__ (10:23:40.292):
>      > Using manifest translation from
>      >
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\clock\locale\pt_PT\manifest.ini
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.302):
>      > Found add-on clock - 19.03. Requires API: (2014, 3, 0).
>     Last-tested API:
>      > (2019, 1, 0)
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.306):
>      > Loading add-on from
>      > C:\Users\tiflo\AppData\Roaming\nvda\addons\controlUsageAssistant
>      > DEBUG - addonHandler.Addon.__init__ (10:23:40.322):
>      > Using manifest translation from
>      >
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\controlUsageAssistant\locale\pt_PT\manifest.ini
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.335):
>      > Found add-on controlUsageAssistant - 2.4. Requires API: (2014, 3, 0).
>      > Last-tested API: (2019, 1, 0)
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.335):
>      > Disabling add-on controlUsageAssistant
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.335):
>      > Loading add-on from
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\DelightGames
>      > DEBUG - addonHandler.Addon.__init__ (10:23:40.351):
>      > Using manifest translation from
>      >
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\DelightGames\locale\pt_PT\manifest.ini
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.361):
>      > Found add-on DelightGames - 1.0-dev. Requires API: (2018, 3, 0).
>      > Last-tested API: (2019, 1, 0)
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.361):
>      > Disabling add-on DelightGames
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.361):
>      > Loading add-on from
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\emoticons
>      > DEBUG - addonHandler.Addon.__init__ (10:23:40.381):
>      > Using manifest translation from
>      >
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\emoticons\locale\pt_PT\manifest.ini
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.385):
>      > Found add-on emoticons - 9.1. Requires API: (2018, 3, 0). Last-tested
>      > API: (2019, 1, 0)
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.385):
>      > Disabling add-on emoticons
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.391):
>      > Loading add-on from
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\goldenCursor
>      > DEBUG - addonHandler.Addon.__init__ (10:23:40.391):
>      > Using manifest translation from
>      >
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\goldenCursor\locale\pt_PT\manifest.ini
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.401):
>      > Found add-on goldenCursor - 3.4. Requires API: (2017, 3, 0).
>     Last-tested
>      > API: (2019, 1, 0)
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.401):
>      > Disabling add-on goldenCursor
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.421):
>      > Loading add-on from
>      > C:\Users\tiflo\AppData\Roaming\nvda\addons\ImageDescriber
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.430):
>      > Found add-on ImageDescriber - 1.2.1. Requires API: (2013, 1, 0).
>      > Last-tested API: (2019, 1, 0)
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.430):
>      > Loading add-on from
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\inputLock
>      > DEBUG - addonHandler.Addon.__init__ (10:23:40.440):
>      > Using manifest translation from
>      >
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\inputLock\locale\pt_PT\manifest.ini
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.451):
>      > Found add-on inputLock - 1.7. Requires API: (2017, 3, 0). Last-tested
>      > API: (2019, 1, 0)
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.451):
>      > Disabling add-on inputLock
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.451):
>      > Loading add-on from
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\Mozilla
>      > DEBUG - addonHandler.Addon.__init__ (10:23:40.460):
>      > Using manifest translation from
>      >
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\Mozilla\locale\pt_PT\manifest.ini
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.460):
>      > Found add-on Mozilla - 1.7. Requires API: (2018, 1, 0).
>     Last-tested API:
>      > (2019, 1, 0)
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.460):
>      > Loading add-on from
>      > C:\Users\tiflo\AppData\Roaming\nvda\addons\NVDAExtensionGlobalPlugin
>      > DEBUG - addonHandler.Addon.__init__ (10:23:40.476):
>      > Using manifest translation from
>      >
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\NVDAExtensionGlobalPlugin\locale\pt\manifest.ini
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.496):
>      > Found add-on NVDAExtensionGlobalPlugin - 7.3.1dev10. Requires API:
>      > (2018, 2, 0). Last-tested API: (2019, 1, 0)
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.496):
>      > Loading add-on from
>      > C:\Users\tiflo\AppData\Roaming\nvda\addons\outlookExtended
>      > DEBUG - addonHandler.Addon.__init__ (10:23:40.506):
>      > Using manifest translation from
>      >
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\outlookExtended\locale\pt_PT\manifest.ini
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.522):
>      > Found add-on outlookExtended - 1.1. Requires API: (2018, 3, 0).
>      > Last-tested API: (2019, 1, 0)
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.522):
>      > Loading add-on from
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\partialLines
>      > DEBUG - addonHandler.Addon.__init__ (10:23:40.532):
>      > Using manifest translation from
>      >
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\partialLines\locale\pt\manifest.ini
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.546):
>      > Found add-on partialLines - 0.1. Requires API: (2017, 4, 0).
>     Last-tested
>      > API: (2019, 1, 0)
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.546):
>      > Loading add-on from
>      > C:\Users\tiflo\AppData\Roaming\nvda\addons\poeditMadeEasy
>      > DEBUG - addonHandler.Addon.__init__ (10:23:40.556):
>      > Using manifest translation from
>      >
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\poeditMadeEasy\locale\en\manifest.ini
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.562):
>      > Found add-on poeditMadeEasy - 3.2. Requires API: (2017, 4, 0).
>      > Last-tested API: (2019, 1, 0)
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.562):
>      > Loading add-on from
>      > C:\Users\tiflo\AppData\Roaming\nvda\addons\profilesSwitcher
>      > DEBUG - addonHandler.Addon.__init__ (10:23:40.572):
>      > Using manifest translation from
>      >
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\profilesSwitcher\locale\pt_PT\manifest.ini
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.591):
>      > Found add-on profilesSwitcher - 1.1. Requires API: (2018, 3, 0).
>      > Last-tested API: (2018, 4, 1)
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.591):
>      > Loading add-on from
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\QTranslate
>      > DEBUG - addonHandler.Addon.__init__ (10:23:40.614):
>      > Using manifest translation from
>      >
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\QTranslate\locale\pt_PT\manifest.ini
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.631):
>      > Found add-on QTranslate - 1.0-dev. Requires API: (2018, 3, 0).
>      > Last-tested API: (2019, 1, 0)
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.631):
>      > Loading add-on from C:\Users\tiflo\AppData\Roaming\nvda\addons\remote
>      > DEBUG - addonHandler.Addon.__init__ (10:23:40.647):
>      > Using manifest translation from
>      >
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\remote\locale\pt\manifest.ini
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.651):
>      > Found add-on remote - 2.2. Requires API: (2017, 4, 0).
>     Last-tested API:
>      > (2019, 1, 0)
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.651):
>      > Loading add-on from
>      > C:\Users\tiflo\AppData\Roaming\nvda\addons\sayProductNameAndVersion
>      > DEBUG - addonHandler.Addon.__init__ (10:23:40.661):
>      > Using manifest translation from
>      >
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\sayProductNameAndVersion\locale\pt_PT\manifest.ini
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.677):
>      > Found add-on sayProductNameAndVersion - 1.0.2012060901. Requires API:
>      > (2013, 1, 0). Last-tested API: (2019, 1, 0)
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.680):
>      > Loading add-on from
>      > C:\Users\tiflo\AppData\Roaming\nvda\addons\screenCurtain
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.690):
>      > Found add-on screenCurtain - 20190114. Requires API: (2018, 2, 0).
>      > Last-tested API: (2019, 1, 0)
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.690):
>      > Disabling add-on screenCurtain
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.690):
>      > Loading add-on from
>      > C:\Users\tiflo\AppData\Roaming\nvda\addons\screenRapping
>      > DEBUG - addonHandler.Addon.__init__ (10:23:40.706):
>      > Using manifest translation from
>      >
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\screenRapping\locale\pt\manifest.ini
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.732):
>      > Found add-on screenRapping - 1.4. Requires API: (2017, 3, 0).
>      > Last-tested API: (2019, 1, 0)
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.732):
>      > Loading add-on from
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\SentenceNav
>      > DEBUG - addonHandler.Addon.__init__ (10:23:40.746):
>      > Using manifest translation from
>      >
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\SentenceNav\locale\pt_PT\manifest.ini
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.762):
>      > Found add-on SentenceNav - 2.5. Requires API: (2018, 1, 0).
>     Last-tested
>      > API: (2019, 1, 0)
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.765):
>      > Loading add-on from C:\Users\tiflo\AppData\Roaming\nvda\addons\skype
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.766):
>      > Found add-on skype - 2018.03.1. Requires API: (0, 0, 0). Last-tested
>      > API: (0, 0, 0)
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.766):
>      > Disabling add-on skype
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.772):
>      > Loading add-on from
>      > C:\Users\tiflo\AppData\Roaming\nvda\addons\textInformation
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.785):
>      > Found add-on textInformation - 1.0. Requires API: (2014, 3, 0).
>      > Last-tested API: (2019, 1, 0)
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.786):
>      > Loading add-on from
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\textnav
>      > DEBUG - addonHandler.Addon.__init__ (10:23:40.796):
>      > Using manifest translation from
>      >
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\textnav\locale\pt_PT\manifest.ini
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.806):
>      > Found add-on textnav - 1.2. Requires API: (2018, 1, 0).
>     Last-tested API:
>      > (2019, 1, 0)
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.806):
>      > Loading add-on from
>      > C:\Users\tiflo\AppData\Roaming\nvda\addons\toolbarsExplorer
>      > DEBUG - addonHandler.Addon.__init__ (10:23:40.816):
>      > Using manifest translation from
>      >
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\toolbarsExplorer\locale\pt_PT\manifest.ini
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.826):
>      > Found add-on toolbarsExplorer - 1.1. Requires API: (2017, 3, 0).
>      > Last-tested API: (2019, 1, 0)
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.826):
>      > Loading add-on from
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\translate
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.842):
>      > Found add-on translate - 2019.03.3. Requires API: (2018, 3, 0).
>      > Last-tested API: (2018, 4, 0)
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.842):
>      > Loading add-on from
>      > C:\Users\tiflo\AppData\Roaming\nvda\addons\vocalizer-driver
>      > DEBUG - addonHandler.Addon.__init__ (10:23:40.855):
>      > Using manifest translation from
>      >
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\vocalizer-driver\locale\pt_PT\manifest.ini
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.858):
>      > Found add-on vocalizer-driver - 2.0.3. Requires API: (2017, 4, 0).
>      > Last-tested API: (2019, 1, 0)
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.861):
>      > Loading add-on from
>      >
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\vocalizer-expressive-voice-catarina
>      >
>      > Plus
>      > DEBUG - addonHandler.Addon.__init__ (10:23:40.871):
>      > Using manifest translation from
>      >
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\vocalizer-expressive-voice-catarina
>      >
>      > Plus\locale\pt\manifest.ini
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.878):
>      > Found add-on vocalizer-expressive-voice-catarina Plus - 1.1.1.
>     Requires
>      > API: (2013, 2, 0). Last-tested API: (2099, 4, 0)
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.878):
>      > Loading add-on from
>      >
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\vocalizer-expressive-voice-english
>      >
>      > Compact
>      > DEBUG - addonHandler.Addon.__init__ (10:23:40.898):
>      > Using manifest translation from
>      >
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\vocalizer-expressive-voice-english
>      >
>      > Compact\locale\pt\manifest.ini
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.918):
>      > Found add-on vocalizer-expressive-voice-english Compact - 1.1.1.
>      > Requires API: (2013, 2, 0). Last-tested API: (2099, 4, 0)
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.918):
>      > Loading add-on from
>      >
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\vocalizer-expressive-voice-kyoko
>      >
>      > Plus
>      > DEBUG - addonHandler.Addon.__init__ (10:23:40.931):
>      > Using manifest translation from
>      >
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\vocalizer-expressive-voice-kyoko
>      >
>      > Plus\locale\pt\manifest.ini
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.951):
>      > Found add-on vocalizer-expressive-voice-kyoko Plus - 1.1.1. Requires
>      > API: (2013, 2, 0). Last-tested API: (2099, 4, 0)
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.951):
>      > Loading add-on from
>      >
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\vocalizer-expressive-voice-portugueseAndSpanish
>      >
>      > Compact Voices
>      > DEBUG - addonHandler.Addon.__init__ (10:23:40.971):
>      > Using manifest translation from
>      >
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\vocalizer-expressive-voice-portugueseAndSpanish
>      >
>      > Compact Voices\locale\pt\manifest.ini
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.990):
>      > Found add-on vocalizer-expressive-voice-portugueseAndSpanish Compact
>      > Voices - 1.1.1. Requires API: (2013, 2, 0). Last-tested API:
>     (2099, 4, 0)
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.990):
>      > Loading add-on from
>      > C:\Users\tiflo\AppData\Roaming\nvda\addons\vocalizer-voice-joana
>      > DEBUG - addonHandler.Addon.__init__ (10:23:41.002):
>      > Using manifest translation from
>      >
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\vocalizer-voice-joana\locale\pt\manifest.ini
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:41.009):
>      > Found add-on vocalizer-voice-joana - 5.5. Requires API: (2013, 2, 0).
>      > Last-tested API: (2099, 4, 0)
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:41.009):
>      > Loading add-on from
>      >
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\vocalizer_expressive_driver
>      > DEBUG - addonHandler.Addon.__init__ (10:23:41.022):
>      > Using manifest translation from
>      >
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\locale\pt_PT\manifest.ini
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:41.081):
>      > Found add-on vocalizer_expressive_driver - 3.0.14. Requires API:
>     (2013,
>      > 2, 0). Last-tested API: (2019, 1, 0)
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:41.081):
>      > Loading add-on from
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\Weather Plus
>      > DEBUG - addonHandler.Addon.__init__ (10:23:41.121):
>      > Using manifest translation from
>      > C:\Users\tiflo\AppData\Roaming\nvda\addons\Weather
>      > Plus\locale\pt_PT\manifest.ini
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:41.141):
>      > Found add-on Weather Plus - 5.0_13.03.2019. Requires API: (2017,
>     3, 0).
>      > Last-tested API: (2019, 1, 0)
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:41.141):
>      > Loading add-on from
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\wintenApps
>      > DEBUG - addonHandler.Addon.__init__ (10:23:41.157):
>      > Using manifest translation from
>      >
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\wintenApps\locale\pt_PT\manifest.ini
>      > DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:41.161):
>      > Found add-on wintenApps - 19.03.2. Requires API: (2018, 3, 0).
>      > Last-tested API: (2019, 1, 0)
>      > DEBUGWARNING - touchHandler.touchSupported (10:23:41.325):
>      > No touch devices found
>      > DEBUG - core.main (10:23:41.424):
>      > Initializing appModule Handler
>      > DEBUG - addonHandler.Addon.addToPackagePath (10:23:41.424):
>      > Addon Mozilla added to appModules package path
>      > DEBUG - addonHandler.Addon.addToPackagePath (10:23:41.424):
>      > Addon outlookExtended added to appModules package path
>      > DEBUG - addonHandler.Addon.addToPackagePath (10:23:41.438):
>      > Addon poeditMadeEasy added to appModules package path
>      > DEBUG - addonHandler.Addon.addToPackagePath (10:23:41.438):
>      > Addon QTranslate added to appModules package path
>      > DEBUG - addonHandler.Addon.addToPackagePath (10:23:41.438):
>      > Addon wintenApps added to appModules package path
>      > DEBUG - core.main (10:23:41.438):
>      > Initializing NVDAHelper
>      > DEBUG - core.main (10:23:41.512):
>      > Speech Dictionary processing
>      > DEBUG - speechDictHandler.SpeechDict.load (10:23:41.512):
>      > Loading speech dictionary
>      > 'C:\Users\tiflo\AppData\Roaming\nvda\speechDicts\default.dic'...
>      > DEBUG - speechDictHandler.SpeechDict.load (10:23:41.539):
>      > 3 loaded records.
>      > DEBUG - speechDictHandler.SpeechDict.load (10:23:41.539):
>      > Loading speech dictionary 'builtin.dic'...
>      > DEBUG - speechDictHandler.SpeechDict.load (10:23:41.539):
>      > 3 loaded records.
>      > DEBUG - core.main (10:23:41.539):
>      > Initializing speech
>      > DEBUG - addonHandler.Addon.addToPackagePath (10:23:41.539):
>      > Addon vocalizer-driver added to synthDrivers package path
>      > DEBUG - addonHandler.Addon.addToPackagePath (10:23:41.539):
>      > Addon vocalizer_expressive_driver added to synthDrivers package path
>      > INFO - core.main (10:23:41.900):
>      > Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5
>      > DEBUG - core.main (10:23:41.900):
>      > Initializing braille input
>      > INFO - brailleInput.initialize (10:23:41.900):
>      > Braille input initialized
>      > DEBUG - core.main (10:23:41.900):
>      > Initializing braille
>      > DEBUG - addonHandler.Addon.addToPackagePath (10:23:41.900):
>      > Addon brailleme added to brailleDisplayDrivers package path
>      > INFO - braille.initialize (10:23:41.914):
>      > Using liblouis version 3.8.0
>      > INFO - braille.BrailleHandler.setDisplayByName (10:23:41.914):
>      > Loaded braille display driver noBraille, current display has 0 cells.
>      > DEBUG - core.main (10:23:41.914):
>      > Initializing displayModel
>      > DEBUG - core.main (10:23:41.914):
>      > Initializing GUI
>      > DEBUG - core.main (10:23:42.013):
>      > initializing Java Access Bridge support
>      > WARNING - core.main (10:23:42.013):
>      > Java Access Bridge not available
>      > DEBUG - core.main (10:23:42.013):
>      > Initializing winConsole support
>      > DEBUG - core.main (10:23:42.013):
>      > Initializing UIA support
>      > INFO - _UIAHandler.UIAHandler.MTAThreadFunc (10:23:42.026):
>      > UIAutomation: IUIAutomation6
>      > DEBUG - core.main (10:23:42.200):
>      > Initializing IAccessible support
>      > DEBUG - core.main (10:23:42.200):
>      > Initializing input core
>      > DEBUG - core.main (10:23:42.214):
>      > Initializing keyboard handler
>      > DEBUG - core.main (10:23:42.214):
>      > initializing mouse handler
>      > DEBUG - core.main (10:23:42.334):
>      > Initializing touchHandler
>      > DEBUGWARNING - touchHandler.touchSupported (10:23:42.334):
>      > No touch devices found
>      > DEBUG - core.main (10:23:42.334):
>      > Initializing global plugin handler
>      > DEBUG - addonHandler.Addon.addToPackagePath (10:23:42.334):
>      > Addon addonUpdater added to globalPlugins package path
>      > DEBUG - addonHandler.Addon.addToPackagePath (10:23:42.334):
>      > Addon browsernav added to globalPlugins package path
>      > DEBUG - addonHandler.Addon.addToPackagePath (10:23:42.334):
>      > Addon clipContentsDesigner added to globalPlugins package path
>      > DEBUG - addonHandler.Addon.addToPackagePath (10:23:42.334):
>      > Addon clock added to globalPlugins package path
>      > DEBUG - addonHandler.Addon.addToPackagePath (10:23:42.342):
>      > Addon ImageDescriber added to globalPlugins package path
>      > DEBUG - addonHandler.Addon.addToPackagePath (10:23:42.342):
>      > Addon NVDAExtensionGlobalPlugin added to globalPlugins package path
>      > DEBUG - addonHandler.Addon.addToPackagePath (10:23:42.342):
>      > Addon partialLines added to globalPlugins package path
>      > DEBUG - addonHandler.Addon.addToPackagePath (10:23:42.344):
>      > Addon profilesSwitcher added to globalPlugins package path
>      > DEBUG - addonHandler.Addon.addToPackagePath (10:23:42.344):
>      > Addon remote added to globalPlugins package path
>      > DEBUG - addonHandler.Addon.addToPackagePath (10:23:42.344):
>      > Addon sayProductNameAndVersion added to globalPlugins package path
>      > DEBUG - addonHandler.Addon.addToPackagePath (10:23:42.344):
>      > Addon screenRapping added to globalPlugins package path
>      > DEBUG - addonHandler.Addon.addToPackagePath (10:23:42.344):
>      > Addon SentenceNav added to globalPlugins package path
>      > DEBUG - addonHandler.Addon.addToPackagePath (10:23:42.344):
>      > Addon textInformation added to globalPlugins package path
>      > DEBUG - addonHandler.Addon.addToPackagePath (10:23:42.344):
>      > Addon textnav added to globalPlugins package path
>      > DEBUG - addonHandler.Addon.addToPackagePath (10:23:42.344):
>      > Addon toolbarsExplorer added to globalPlugins package path
>      > DEBUG - addonHandler.Addon.addToPackagePath (10:23:42.344):
>      > Addon translate added to globalPlugins package path
>      > DEBUG - addonHandler.Addon.addToPackagePath (10:23:42.344):
>      > Addon vocalizer-driver added to globalPlugins package path
>      > DEBUG - addonHandler.Addon.addToPackagePath (10:23:42.351):
>      > Addon vocalizer_expressive_driver added to globalPlugins package path
>      > DEBUG - addonHandler.Addon.addToPackagePath (10:23:42.351):
>      > Addon Weather Plus added to globalPlugins package path
>      > DEBUG - addonHandler.Addon.addToPackagePath (10:23:42.351):
>      > Addon wintenApps added to globalPlugins package path
>      > DEBUG - external:globalPlugins.wintenObjs.GlobalPlugin.__init__
>      > (10:23:42.394):
>      > W10: adding additional events
>      > DEBUG - external:globalPlugins.wintenObjs.GlobalPlugin.__init__
>      > (10:23:42.404):
>      > W10: added event ID 20036, assigned to UIA_activeTextPositionChanged
>      > DEBUG - external:globalPlugins.wintenObjs.GlobalPlugin.__init__
>      > (10:23:42.404):
>      > W10: added event ID 20026, assigned to UIA_dragStart
>      > DEBUG - external:globalPlugins.wintenObjs.GlobalPlugin.__init__
>      > (10:23:42.414):
>      > W10: added event ID 20027, assigned to UIA_dragCancel
>      > DEBUG - external:globalPlugins.wintenObjs.GlobalPlugin.__init__
>      > (10:23:42.414):
>      > W10: added event ID 20028, assigned to UIA_dragComplete
>      > INFO - brailleDisplayDrivers.handyTech.BrailleDisplayDriver.__init__
>      > (10:23:42.473):
>      > Found Basic Braille 20 connected via serial (COM4)
>      > DEBUG - braille.BrailleHandler.setDisplayByName (10:23:42.473):
>      > Switching braille display from noBraille to handyTech
>      > INFO - braille.BrailleHandler.setDisplayByName (10:23:42.473):
>      > Loaded braille display driver handyTech, current display has 20
>     cells.
>      > DEBUG - addonHandler.Addon.__init__ (10:23:42.875):
>      > Using manifest translation from
>      > C:\Users\tiflo\AppData\Roaming\nvda\addons\Weather
>      > Plus\locale\pt_PT\manifest.ini
>      > DEBUG - NVDAObjects.NVDAObject._get_placeholder (10:23:42.888):
>      > Potential unimplemented child class: <NVDAObjects.window.Desktop
>     object
>      > at 0x0490DD70>
>      > IO - braille.BrailleBuffer.update (10:23:42.894):
>      > Braille regions text: [u'Ambiente de trabalho jan']
>      > IO - braille.BrailleHandler.update (10:23:42.894):
>      > Braille window dots: 17 134 12 24 15 1345 2345 15 - 145 15 - 2345
>     1235 1
>      > 12 1 123 125 135
>      > DEBUGWARNING - Python warning (10:23:43.838):
>      >
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\synthDrivers\vocalizer_expressive\_config.py:11:
>      >
>      > DeprecationWarning: Importing validate directly is deprecated. Please
>      > use configobj.validate instead
>      > DEBUG -
>      > external:synthDrivers.vocalizer_expressive.storage._loadLicenseData
>      > (10:23:44.243):
>      > Loading license data from
>      > C:\Users\tiflo\AppData\Roaming\vocalizer-for-nvda\activation.dat
>      > DEBUGWARNING - Python warning (10:23:44.796):
>      >
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\globalPlugins\vocalizer_expressive_globalPlugin\__init__.py:246:
>      >
>      > wxPyDeprecationWarning: Call to deprecated item. Use Append instead.
>      > DEBUGWARNING - Python warning (10:23:44.796):
>      > C:\Program Files (x86)\NVDA\library.zip\wx\core.py:2337:
>      > DeprecationWarning: Menu.Append() is deprecated
>      > DEBUGWARNING - Python warning (10:23:44.796):
>      >
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\globalPlugins\vocalizer_expressive_globalPlugin\__init__.py:267:
>      >
>      > wxPyDeprecationWarning: Call to deprecated item. Use Insert instead.
>      > DEBUG -
>      >
>     external:globalPlugins.vocalizer_expressive_globalPlugin.LicenseRenewer.__init__
>      >
>      > (10:23:44.796):
>      > License renewal starting in 0
>      > DEBUG - addonHandler.Addon.__init__ (10:23:44.898):
>      > Using manifest translation from
>      >
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\vocalizer-driver\locale\pt_PT\manifest.ini
>      > DEBUGWARNING - Python warning (10:23:45.549):
>      >
>     C:\Users\tiflo\AppData\Roaming\nvda\addons\vocalizer-driver\globalPlugins\vocalizer_globalPlugin\__init__.py:119:
>      >
>      > wxPyDeprecationWarning: Call to deprecated item. Use Insert instead.
>      > INFO - external:globalPlugins.translate.GlobalPlugin.__init__
>      > (10:23:45.963):
>      > Translate module initialized, translating to pt_PT
>      > ERROR - external:globalPlugins.translate.GlobalPlugin.loadLocalCache
>      > (10:23:46.036):
>      > Cannot read or decode data from
>      > C:\Users\tiflo\AppData\Roaming\nvda\translation-cache: No JSON object
>      > could be decoded
>      > INFO -
>      >
>     external:globalPlugins.NVDAExtensionGlobalPlugin.GlobalPlugin.__init__
>      > (10:23:50.631):
>      > Loaded NVDAExtensionGlobalPlugin version 7.3.1dev10
>      > IO - braille.BrailleBuffer.update (10:23:53.036):
>      > Braille regions text: [u'NVDA iniciado']
>      > IO - braille.BrailleHandler.update (10:23:53.036):
>      > Braille window dots: 13457 12367 1457 17 - 24 1345 24 14 24 1 145 135
>      > DEBUG - core.main (10:23:53.036):
>      > Initializing core pump
>      > DEBUG - core.main (10:23:53.036):
>      > Initializing watchdog
>      > DEBUG - core.main (10:23:53.040):
>      > initializing updateCheck
>      > INFO - core.main (10:23:53.051):
>      > NVDA initialized
>      > DEBUG - core.main (10:23:53.051):
>      > entering wx application main loop
>      > DEBUG -
>      >
>     external:globalPlugins.vocalizer_expressive_globalPlugin.LicenseRenewer._renew
>      >
>      > (10:23:53.325):
>      > Renewal data not available, checking later.
>      > DEBUGWARNING -
>      >
>     external:globalPlugins.NVDAExtensionGlobalPlugin.utils.keyboard.getKeyboardKeysIniFilePath
>      >
>      > (10:23:53.661):
>      > keyboard.ini file loaded from locale\pt folder
>      >
>      >
>      > IO -
>      >
>     external:globalPlugins.NVDAExtensionGlobalPlugin.commandKeysSelectiveAnnouncement.MyInputManager.executeGesture
>      >
>      > (10:47:20.013):
>      > Input: kb(desktop):downArrow
>      > DEBUG - editableText.EditableText._hasCaretMoved (10:47:20.059):
>      > Caret move detected using bookmarks. Elapsed: 0 ms
>      > IO - speech.speak (10:47:20.148):
>      > Speaking [u'Rui Fontes']
>      > IO -
>      >
>     external:globalPlugins.NVDAExtensionGlobalPlugin.commandKeysSelectiveAnnouncement.MyInputManager.executeGesture
>      >
>      > (10:47:21.190):
>      > Input: kb(desktop):downArrow
>      > DEBUG - editableText.EditableText._hasCaretMoved (10:47:21.250):
>      > Caret move detected using bookmarks. Elapsed: 10 ms
>      > IO -
>      >
>     external:globalPlugins.NVDAExtensionGlobalPlugin.commandKeysSelectiveAnnouncement.MyInputManager.executeGesture
>      >
>      > (10:47:22.065):
>      > Input: kb(desktop):downArrow
>      > IO -
>      >
>     external:globalPlugins.NVDAExtensionGlobalPlugin.commandKeysSelectiveAnnouncement.MyInputManager.executeGesture
>      >
>      > (10:47:22.621):
>      > Input: kb(desktop):downArrow
>      > IO -
>      >
>     external:globalPlugins.NVDAExtensionGlobalPlugin.commandKeysSelectiveAnnouncement.MyInputManager.executeGesture
>      >
>      > (10:47:23.033):
>      > Input: kb(desktop):downArrow
>      > IO -
>      >
>     external:globalPlugins.NVDAExtensionGlobalPlugin.commandKeysSelectiveAnnouncement.MyInputManager.executeGesture
>      >
>      > (10:47:24.210):
>      > Input: kb(desktop):control+enter
>      > IO -
>      >
>     external:globalPlugins.NVDAExtensionGlobalPlugin.commandKeysSelectiveAnnouncement.MyInputManager.executeGesture
>      >
>      > (10:47:29.437):
>      > Input: kb(desktop):control+enter
>      > DEBUGWARNING - watchdog._watcher (10:47:31.296):
>      > Trying to recover from freeze, core stack:
>      >    File "nvda.pyw", line 233, in <module>
>      >    File "core.pyo", line 519, in main
>      >    File "wx\core.pyo", line 2134, in MainLoop
>      >    File "gui\__init__.pyo", line 1003, in Notify
>      >    File "core.pyo", line 490, in run
>      >    File "queueHandler.pyo", line 86, in pumpAll
>      >    File "queueHandler.pyo", line 53, in flushQueue
>      >    File "scriptHandler.pyo", line 145, in _queueScriptCallback
>      >    File "scriptHandler.pyo", line 187, in executeScript
>      >    File "editableText.pyo", line 185, in script_caret_moveByLine
>      >    File
>      >
>     "C:\Users\tiflo\AppData\Roaming\nvda\addons\NVDAExtensionGlobalPlugin\globalPlugins\NVDAExtensionGlobalPlugin\clipboardCommandAnnouncement\__init__.py",
>      >
>      > line 210, in _caretMovementScriptHelper
>      >    File "editableText.pyo", line 144, in _caretMovementScriptHelper
>      >    File "editableText.pyo", line 130, in _caretScriptPostMovedHelper
>      >    File "speech.pyo", line 781, in speakTextInfo
>      >    File "NVDAObjects\IAccessible\ia2TextMozilla.pyo", line 341, in
>      > getTextWithFields
>      >    File "NVDAObjects\IAccessible\ia2TextMozilla.pyo", line 295,
>     in _getText
>      >    File "NVDAObjects\IAccessible\ia2TextMozilla.pyo", line 251, in
>      > _iterRecursiveText
>      >    File "NVDAObjects\IAccessible\ia2TextMozilla.pyo", line 251, in
>      > _iterRecursiveText
>      >    File "NVDAObjects\IAccessible\ia2TextMozilla.pyo", line 251, in
>      > _iterRecursiveText
>      >    File "NVDAObjects\IAccessible\ia2TextMozilla.pyo", line 251, in
>      > _iterRecursiveText
>      >    File "NVDAObjects\IAccessible\ia2TextMozilla.pyo", line 251, in
>      > _iterRecursiveText
>      >    File "NVDAObjects\IAccessible\ia2TextMozilla.pyo", line 251, in
>      > _iterRecursiveText
>      >    File "NVDAObjects\IAccessible\ia2TextMozilla.pyo", line 241, in
>      > _iterRecursiveText
>      >    File "compoundDocuments.pyo", line 135, in
>     _getControlFieldForObject
>      >    File "baseObject.pyo", line 47, in __get__
>      >    File "baseObject.pyo", line 147, in _getPropertyViaCache
>      >    File "NVDAObjects\IAccessible\mozilla.pyo", line 71, in
>     _get_states
>      >    File "baseObject.pyo", line 47, in __get__
>      >    File "baseObject.pyo", line 147, in _getPropertyViaCache
>      >    File "NVDAObjects\IAccessible\ia2Web.pyo", line 57, in _get_states
>      >    File "baseObject.pyo", line 47, in __get__
>      >    File "baseObject.pyo", line 147, in _getPropertyViaCache
>      >    File "NVDAObjects\IAccessible\__init__.pyo", line 854, in
>     _get_states
>      >    File "baseObject.pyo", line 47, in __get__
>      >    File "baseObject.pyo", line 147, in _getPropertyViaCache
>      >    File "NVDAObjects\IAccessible\__init__.pyo", line 1072, in
>      > _get_IA2Attributes
>      >    File "IAccessibleHandler.pyo", line 1059, in splitIA2Attribs
>      >
>      > And it repeats untill:
>      >
>      > WARNING - watchdog._watcher (10:52:33.105):
>      > Core frozen in stack:
>      >    File "nvda.pyw", line 233, in <module>
>      >    File "core.pyo", line 519, in main
>      >    File "wx\core.pyo", line 2134, in MainLoop
>      >    File "gui\__init__.pyo", line 1003, in Notify
>      >    File "core.pyo", line 490, in run
>      >    File "queueHandler.pyo", line 86, in pumpAll
>      >    File "queueHandler.pyo", line 53, in flushQueue
>      >    File "scriptHandler.pyo", line 145, in _queueScriptCallback
>      >    File "scriptHandler.pyo", line 187, in executeScript
>      >    File "editableText.pyo", line 185, in script_caret_moveByLine
>      >    File
>      >
>     "C:\Users\tiflo\AppData\Roaming\nvda\addons\NVDAExtensionGlobalPlugin\globalPlugins\NVDAExtensionGlobalPlugin\clipboardCommandAnnouncement\__init__.py",
>      >
>      > line 210, in _caretMovementScriptHelper
>      >    File "editableText.pyo", line 144, in _caretMovementScriptHelper
>      >    File "editableText.pyo", line 130, in _caretScriptPostMovedHelper
>      >    File "speech.pyo", line 781, in speakTextInfo
>      >    File "NVDAObjects\IAccessible\ia2TextMozilla.pyo", line 341, in
>      > getTextWithFields
>      >    File "NVDAObjects\IAccessible\ia2TextMozilla.pyo", line 295,
>     in _getText
>      >    File "NVDAObjects\IAccessible\ia2TextMozilla.pyo", line 251, in
>      > _iterRecursiveText
>      >    File "NVDAObjects\IAccessible\ia2TextMozilla.pyo", line 251, in
>      > _iterRecursiveText
>      >    File "NVDAObjects\IAccessible\ia2TextMozilla.pyo", line 251, in
>      > _iterRecursiveText
>      >    File "NVDAObjects\IAccessible\ia2TextMozilla.pyo", line 251, in
>      > _iterRecursiveText
>      >    File "NVDAObjects\IAccessible\ia2TextMozilla.pyo", line 251, in
>      > _iterRecursiveText
>      >    File "NVDAObjects\IAccessible\ia2TextMozilla.pyo", line 251, in
>      > _iterRecursiveText
>      >    File "NVDAObjects\IAccessible\ia2TextMozilla.pyo", line 241, in
>      > _iterRecursiveText
>      >    File "compoundDocuments.pyo", line 135, in
>     _getControlFieldForObject
>      >    File "baseObject.pyo", line 47, in __get__
>      >    File "baseObject.pyo", line 147, in _getPropertyViaCache
>      >    File "NVDAObjects\IAccessible\mozilla.pyo", line 71, in
>     _get_states
>      >    File "baseObject.pyo", line 47, in __get__
>      >    File "baseObject.pyo", line 147, in _getPropertyViaCache
>      >    File "NVDAObjects\IAccessible\ia2Web.pyo", line 57, in _get_states
>      >    File "baseObject.pyo", line 47, in __get__
>      >    File "baseObject.pyo", line 147, in _getPropertyViaCache
>      >    File "NVDAObjects\IAccessible\__init__.pyo", line 854, in
>     _get_states
>      >    File "baseObject.pyo", line 47, in __get__
>      >    File "baseObject.pyo", line 147, in _getPropertyViaCache
>      >    File "NVDAObjects\IAccessible\__init__.pyo", line 1072, in
>      > _get_IA2Attributes
>      >    File "IAccessibleHandler.pyo", line 1059, in splitIA2Attribs
>      >
>      >
>      > Rui Fontes
>      >
>      >
>      > Às 02:29 de 22/03/2019, zahra escreveu:
>      >> hi.
>      >> send it hear, (but copy peist the content), because if i am correct,
>      >> you cant send attachment hear.
>      >> or send it to
>      >> info@... <mailto:info@...>
>      >>
>      >> On 3/21/19, Abbie Taylor <abbietaylor945@...
>     <mailto:abbietaylor945@...>> wrote:
>      >>> For quite some time, I've  been having the same intermittent
>     issues as
>      >>> Rosemary and others with NVDA losing speech. For me, it happens
>     most of
>      >>> the
>      >>> time when I'm in Word but occasionally occurs in Outlook and
>     Firefox.
>      >>> This
>      >>> morning after installing the latest add-on update, I had to
>     restart my
>      >>> computer twice before it would work properly. I figured out how to
>      >>> access
>      >>> the log through the NVDA tools menu. Where can I send it? Thank
>     you.
>      >>>
>      >>> Abbie Johnson Taylor, Author https://abbiescorner.wordpress.com
>      >>> http://www.abbiejohnsontaylor.com
>      >>> abbietaylor945@... <mailto:abbietaylor945@...>
>      >>> Order my new memoir at http://www.abbiejohnsontaylor.com/memoir.htm
>      >>>
>      >>> --
>      >>> Abbie Johnson Taylor, Author
>      >>> http://www.abbiejohnsontaylor.com
>      >>> http://abbiescorner.wordpress.com
>      >>> abbietaylor945@... <mailto:abbietaylor945@...>
>      >>>
>      >>>
>      >>>
>      >>
>      >>
>      >
>      >
>      >
>      >
>
>
>     --
>     Subscribe to a WordPress for Newbies Mailing List by sending a
>     message to:
>     wp4newbs-request@...
>     <mailto:wp4newbs-request@...> with 'subscribe' in the
>     Subject field OR by
>     visiting the list page at http://www.freelists.org/list/wp4newbs
>     & check out my sites at www.brighter-vision.com
>     <http://www.brighter-vision.com> & www.mysitesbeenhacked.com
>     <http://www.mysitesbeenhacked.com>
>
>
>
>
>
> --
> Quentin Christensen
> Training and Support Manager
>
> Official NVDA Training modules and expert certification now available:
> http://www.nvaccess.org/shop/
>
> www.nvaccess.org <http://www.nvaccess.org/>
> Facebook: http://www.facebook.com/NVAccess
> Twitter: @NVAccess
>





--
Quentin Christensen
Training and Support Manager

Official NVDA Training modules and expert certification now available: http://www.nvaccess.org/shop/

Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 


Re: Kindle for PC

Quentin Christensen
 

At one point, Amazon brought out an "accessible version" of the Kindle app, which was separate from the regular download.  When they brought out version 1.19, it was early 2017 and around the time we released NVDA 2017.1 which brought accessibility to the "standard" kindle for PC app.  Essentially, any version of Kindle since then should be accessible.

Re the website for books, I must admit, I don't read many kindle books myself so haven't played with it much, but if there is a problem, do raise it.  If it's with the website, it's likely an issue for Amazon, but of course it is worth us being aware of it as well.

Quentin.

On Mon, Mar 25, 2019 at 8:45 PM hurrikennyandopo ... <hurrikennyandopo@...> wrote:

Hi Brian


Just looking at the site for a accessible version of kindle for pc. funny thing was on the accessibility page for it it is a very old version and when downloaded apart from the menus was in not accessible.

I think it was like version 1.4 and 1.9 now and above is recommended.


I did read up you needed a later version of which i got but not from them as i could not find it any where on there amazon website it seems like you go in circles.


the version i got now is accessible but if some one knows more of a direct link i will add that into the tutorial.




Would any one have a direct link to the latest version of it on there website to download instead of searching for it off the net.

This is for the amazon website.


Just putting to together a tutorial on the basic's of using it once i figure it out.

Or could you call it notes.


I see there are users on the list using it. I might have to sus out how to download other free books to or does some one on the list know how? and what hoops i might have to jump through.

Or tips i can add into it.




Gene nz



On 25/03/2019 10:28 PM, Brian's Mail list account via Groups.Io wrote:
Was there not an issue with the web site for Kindle books, a link that did not show up properly?
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Quentin Christensen" <quentin@...>
To: <nvda@nvda.groups.io>
Sent: Monday, March 25, 2019 2:20 AM
Subject: Re: [nvda] Kindle for PC


Hi Don,

NVDA first got support for Kindle for PC (version 1.19 at the time) in NVDA
2017.1, and it has improved since then.

We do have a few notes on using Kindle for PC in the NVDA user guide:
https://www.nvaccess.org/files/nvda/documentation/userGuide.html#Kindle

If you do have any specific questions or run into any problems, please do
let us know.  Note that as per the first line in that section I linked to,
this functionality is only available in Kindle books designated with
"Screen Reader: Supported" which you can check on the details page for the
book.

Kind regards

Quentin.

On Mon, Mar 25, 2019 at 7:49 AM Don H <lmddh50@...> wrote:

Does NVDA work well with Kindle for PC for reading Kindel books?

Thanks







-- 
Quentin Christensen
Training and Support Manager

Official NVDA Training modules and expert certification now available:
http://www.nvaccess.org/shop/

www.nvaccess.org
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess








--
Image NVDA
        certified expert
Check out my website for NVDA tutorials and other blindness related material at http://www.accessibilitycentral.net
 
Regardless of where you are in New Zealand if you are near one of the APNK sites you can use a copy of the NVDA screen reader on one of their computers. To find out which location (or locations) are nearest to you please visit http://www.aotearoapeoplesnetwork.org/content/partner-libraries (Aotearoa People's Network Kaharoa).
To find out which software is installed on the APNK network please visit the following link http://www.aotearoapeoplesnetwork.info/faq/software To find out how to use NVDA on APNK computers please visit the following link http://www.aotearoapeoplesnetwork.info/faq/nvda
 

To find out which software is available on the Christchurch City Library network, and how to start the NVDA screen reader, please go to the following links. Software available  https://my.christchurchcitylibraries.com/faq/computers/#faq_5884  How to start the NVDA screen reader on Christchurch City Library computers  https://my.christchurchcitylibraries.com/faqs/what-screen-reader-software-is-available/
 
To find an NVDA certified expert near you, please visit the following link https://certification.nvaccess.org/. The certification page contains the official list of NVDA certified individuals from around the world, who have sat and successfully passed the NVDA expert exam.



--
Quentin Christensen
Training and Support Manager

Official NVDA Training modules and expert certification now available: http://www.nvaccess.org/shop/

Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 


Re: NVDA and icons in the system tray

Robert Logue
 

I've seen this problem too. Doesn't matter what screen reader or which PC I use.  The system tray in Windows is a bit buggy me thinks.


Bob

On 2019-03-23 12:52 p.m., Gene wrote:
I have seen this problem that occurs no matter how you try to activate one of the icons.

Gene
----- Original Message -----

From: Sarah k Alawami
Sent: Saturday, March 23, 2019 1:49 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA and icons in the system tray


What happens if you hit enter or hit shift f10? Both shoudl do what you want to do.

Take care

On 23 Mar 2019, at 11:23, Kostadin Kolev wrote:

Hello all,

NVDA seams to have problems activating some icons in the system tray, for example the one for OneDrive. At first I thought that it was not a NVDA specific issue but a global screen reader / accessibility one, but after testing with Narrator as well, it turns out that at least the problem with OneDrive's system tray icon is specific to NVDA (Narrator is not affected).

To reproduce the issue, I press Windows+B to go to the system tray. I use up/down arrow keys to move the focus to the OneDrive's icon (OneDrive must be running). Then I press the space key to simulate a single left click with the mouse. All those are Windows and not NVDA commands. With Narrator, this works as expected and the pop-up window for OneDrive appears. With NVDA however, nothing happens. A person which cannot see the screen would wonder why it is so - what is different. I have some vision left and can see what's going on. For some reason, when pressing Windows+B and the system focus gets moved to the system tray area, NVDA also moves the mouse cursor there and for some reason, that causes the failure of the execution of the command with the spacebar to simulate a single left mouse click. With Narrator and with no screen reader running, the mouse cursor does not get moved to the system tray when the system focus gets moved there and the command gets executed correctly and the OneDrive pop-up window appears as it should.

So, does anyone (specially the NVDA developers) know why NVDA moves the mouse cursor to the system tray area when the system focus gets moved there? Because apparently this causes problems with some icons in the system tray. And now that I think of it, I wouldn't be surprised if the appearance of the problematic so called "Network Flyout" pop-up window under Windows 7 is caused by this behavior as well.

P.S.: I'm not asking for help/assistance with workarounds to activate such "problematic" icons in the system tray - I know how to handle them, including with the "SysTrayList" add-on for NVDA. This is not the purpose of this message. I'm asking why NVDA is causing the explained above behavior of the mouse when pressing Windows+B.

Thanks much in advance!


______
Best wishes,
Kostadin Kolev




Re: playing you tube with NVDA

Sarah k Alawami
 

It worked here. Thanks for the shortcuts.

On 25 Mar 2019, at 16:57, Brice Mijares wrote:

didn't work for me as well.

On 3/25/2019 4:52 PM, Kerryn Gunness via Groups.Io wrote:


hey andre
this link is not working

----- Original Message -----
*From:* Andre Fisher <mailto:andrefisher729@...>
*To:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
*Sent:* Monday, March 25, 2019 7:17 PM
*Subject:* Re: [nvda] playing you tube with NVDA

Visit this link for the keyboard shortcuts:

https://sites.googlecom/a/umich.edu/u-m-google-170816/accessibility/google-keyboard-shortcuts---youtube



Re: Translating NVDA into Te Reo Māori option

Rui Fontes
 

The problem is:
Translate for mahori is only good if a synth with that language is available...
If not, you will have mahori text read by a english voice, by instance... and I do not make a slightly idea how it will sound...

Rui Fontes



Às 00:29 de 26/03/2019, hurrikennyandopo ... escreveu:

Hi
I would have to ask him. I know there used to be a synth for there language maybe he would know. Is it better for him to have a synth for there language instead of translating the user manual etc into there language? It is new to me and probably him as well.
Even the steps he would have to take.
I did find the wicki page on translating and sent that back to him while i find out more information from both sides.
They might even be able to get funding to cover translating nvda and or the synth. I will know more when he gets back to me.
Gene nz
On 26/03/2019 1:03 PM, Rui Fontes wrote:
And it worth the effort do not having a mahori synth?

Rui Fontes


Às 23:39 de 25/03/2019, hurrikennyandopo ... escreveu:
hi guys


I know there are translators on this list and i have been asked about having a Te Reo Māori option  in NVDA.



I only speak English but i have been contacted by a person who speaks the above language  and can translate it into there language.


I am wondering how much is involved? I am guessing the whole user manual would have to be translated along with maybe quick reference and whats new?


What program would they have to use? Is there a easy way to do it? How would i start and also we would be new to try and do this for NVDA.


The above language is recognized in our country along side of english and sign language.


We are not programmers so it would be a matter of starting from scratch doing this.


I just hope it does not scare us off translating it into there language.


I am wondering also  if it was just the user manual etc or the synth? as well. They might be able to get funding to do this?


any help would be great.


Gene nz


--
Image NVDA certified expert
Check out my website for NVDA tutorials and other blindness related material at http://www.accessibilitycentral.net

Regardless of where you are in New Zealand if you are near one of the APNK sites you can use a copy of the NVDA screen reader on one of their computers. To find out which location (or locations) are nearest to you please visit http://www.aotearoapeoplesnetwork.org/content/partner-libraries (Aotearoa People's Network Kaharoa). To find out which software is installed on the APNK network please visit the following linkhttp://www.aotearoapeoplesnetwork.info/faq/software To find out how to use NVDA on APNK computers please visit the following linkhttp://www.aotearoapeoplesnetwork.info/faq/nvda

To find out which software is available on the Christchurch City Library network, and how to start the NVDA screen reader, please go to the following links. Software available https://my.christchurchcitylibraries.com/faq/computers/#faq_5884How to start the NVDA screen reader on Christchurch City Library computers https://my.christchurchcitylibraries.com/faqs/what-screen-reader-software-is-available/

To find an NVDA certified expert near you, please visit the following link https://certification.nvaccess.org/. The certification page contains the official list of NVDA certified individuals from around the world, who have sat and successfully passed the NVDA expert exam.


--
Image NVDA certified expert
Check out my website for NVDA tutorials and other blindness related material at http://www.accessibilitycentral.net
Regardless of where you are in New Zealand if you are near one of the APNK sites you can use a copy of the NVDA screen reader on one of their computers. To find out which location (or locations) are nearest to you please visit http://www.aotearoapeoplesnetwork.org/content/partner-libraries (Aotearoa People's Network Kaharoa). To find out which software is installed on the APNK network please visit the following linkhttp://www.aotearoapeoplesnetwork.info/faq/software To find out how to use NVDA on APNK computers please visit the following linkhttp://www.aotearoapeoplesnetwork.info/faq/nvda
To find out which software is available on the Christchurch City Library network, and how to start the NVDA screen reader, please go to the following links. Software available https://my.christchurchcitylibraries.com/faq/computers/#faq_5884How to start the NVDA screen reader on Christchurch City Library computers https://my.christchurchcitylibraries.com/faqs/what-screen-reader-software-is-available/
To find an NVDA certified expert near you, please visit the following link https://certification.nvaccess.org/. The certification page contains the official list of NVDA certified individuals from around the world, who have sat and successfully passed the NVDA expert exam.


Re: playing you tube with NVDA

Kerryn Gunness
 


aww by the way, the commands which andre recommended, you need to turn on browse mode first, before using them
to do this press NVDA key and space bar
 
 

----- Original Message -----
From: Gene
Sent: Monday, March 25, 2019 8:35 PM
Subject: Re: [nvda] playing you tube with NVDA

Unless you want to go into forms mode, you need to have the NVDA setting on that allows commands to pass to the browser.  I don't know if the setting is on by default or just what it is called.  I don't use it in part because I use an old version of NVDA.  It does what I want and I don't need to update.  But others can discuss that setting.
 
you may have to move to the player.  If you start at the top of the page and type b until you get to a player command such as the play button or mute, any button in the player, then you can use the following commands and maybe others I don't know.
 
Space pauses and resumes play.  Right and left arrow moves you through the video.  You can press and hold those keys or press and release them.  but I'm not sure if press and hold works properly. 
 
The numbers 0 through 9 move you through the video.  I've never seen this part explained but it looks to me as though 1 through perhsps 4 moves you by single percents, 1 2, etc.  5 through 9 may move you to fifty, sixty, etc.  But you can experiment and maybe you can find information if you look.  But those numbers move you in jumps through the video.  0 moves you back to the beginning and starts play from the beginning.  If the file stops playing at the end and you want to hear it again, 0 will play it again.  the other numbers will do what I described earlier even if the file has stopped.  But of course, if you have up next enabled, it won't do it if it has already started to switch to the next viddeo it wants to play.
 
Gene 
----- Original Message -----
Sent: Monday, March 25, 2019 6:08 PM
Subject: [nvda] playing you tube with NVDA

HI all
are there commands for playing  you tube videos using NVDA on windows?
like to pause, fast forward, rewine etc?
thanks



Re: playing you tube with NVDA

Kerryn Gunness
 


nice andre
thank u
 

----- Original Message -----
Sent: Monday, March 25, 2019 8:28 PM
Subject: Re: [nvda] playing you tube with NVDA

Here are the shortcuts:

Action

Shortcut

Toggle play/pause the video

k or Spacebar

Go back 5 seconds

Left arrow

Go back 10 seconds

Go forward 5 seconds  

Right arrow

Go forward 10 seconds

l

Skip to a particular section of the video (e.g., 5 goes to the video midpoint)

Numbers 1-9 (not the keypad numbers)

Restart video

0 (not the keypad number)

Go to Full Screen mode

f

Exit Full Screen mode  

Escape

Go to beginning of video

Home

Go to end of video

End

Increase volume 5%

Up arrow

Decrease volume 5%

Down arrow        

Increase speed

Shift+> (may not work in all browsers) or Shift+(period)

Decrease speed

Shift+< (may not work in all browsers)  or Shift+(comma)     

Move forward 1 frame when video is paused

. (period)

Move backward 1 frame when video is paused

, (comma)

Mute/unmute video

m

Turn captions on/off

c

Cycle through options for caption background color

b   

Move to the previous video in a playlist       

Shift+p

Move to the next video in a playlist       

Shift+n

 


Re: playing you tube with NVDA

Gene
 

Unless you want to go into forms mode, you need to have the NVDA setting on that allows commands to pass to the browser.  I don't know if the setting is on by default or just what it is called.  I don't use it in part because I use an old version of NVDA.  It does what I want and I don't need to update.  But others can discuss that setting.
 
you may have to move to the player.  If you start at the top of the page and type b until you get to a player command such as the play button or mute, any button in the player, then you can use the following commands and maybe others I don't know.
 
Space pauses and resumes play.  Right and left arrow moves you through the video.  You can press and hold those keys or press and release them.  but I'm not sure if press and hold works properly. 
 
The numbers 0 through 9 move you through the video.  I've never seen this part explained but it looks to me as though 1 through perhsps 4 moves you by single percents, 1 2, etc.  5 through 9 may move you to fifty, sixty, etc.  But you can experiment and maybe you can find information if you look.  But those numbers move you in jumps through the video.  0 moves you back to the beginning and starts play from the beginning.  If the file stops playing at the end and you want to hear it again, 0 will play it again.  the other numbers will do what I described earlier even if the file has stopped.  But of course, if you have up next enabled, it won't do it if it has already started to switch to the next viddeo it wants to play.
 
Gene 

----- Original Message -----
Sent: Monday, March 25, 2019 6:08 PM
Subject: [nvda] playing you tube with NVDA

HI all
are there commands for playing  you tube videos using NVDA on windows?
like to pause, fast forward, rewine etc?
thanks



Re: Translating NVDA into Te Reo Māori option

hurrikennyandopo ...
 

Hi


I would have to ask him. I know there used to be a synth for there language maybe he would know. Is it better for him to have a synth for there language instead of translating the user manual etc into there language? It is new to me and probably him as well.

Even the steps he would have to take.


I did find the wicki page on translating and sent that back to him while i find out more information from both sides.


They might even be able to get funding to cover translating nvda and or the synth. I will know more when he gets back to me.



Gene nz


On 26/03/2019 1:03 PM, Rui Fontes wrote:
And it worth the effort do not having a mahori synth?

Rui Fontes


Às 23:39 de 25/03/2019, hurrikennyandopo ... escreveu:
hi guys


I know there are translators on this list and i have been asked about having a Te Reo Māori option  in NVDA.



I only speak English but i have been contacted by a person who speaks the above language  and can translate it into there language.


I am wondering how much is involved? I am guessing the whole user manual would have to be translated along with maybe quick reference and whats new?


What program would they have to use? Is there a easy way to do it? How would i start and also we would be new to try and do this for NVDA.


The above language is recognized in our country along side of english and sign language.


We are not programmers so it would be a matter of starting from scratch doing this.


I just hope it does not scare us off translating it into there language.


I am wondering also  if it was just the user manual etc or the synth? as well. They might be able to get funding to do this?


any help would be great.


Gene nz


-- 
Image NVDA certified expert
Check out my website for NVDA tutorials and other blindness related material at http://www.accessibilitycentral.net

Regardless of where you are in New Zealand if you are near one of the APNK sites you can use a copy of the NVDA screen reader on one of their computers. To find out which location (or locations) are nearest to you please visit http://www.aotearoapeoplesnetwork.org/content/partner-libraries (Aotearoa People's Network Kaharoa). To find out which software is installed on the APNK network please visit the following linkhttp://www.aotearoapeoplesnetwork.info/faq/software To find out how to use NVDA on APNK computers please visit the following linkhttp://www.aotearoapeoplesnetwork.info/faq/nvda

To find out which software is available on the Christchurch City Library network, and how to start the NVDA screen reader, please go to the following links. Software available https://my.christchurchcitylibraries.com/faq/computers/#faq_5884How to start the NVDA screen reader on Christchurch City Library computers https://my.christchurchcitylibraries.com/faqs/what-screen-reader-software-is-available/

To find an NVDA certified expert near you, please visit the following link https://certification.nvaccess.org/. The certification page contains the official list of NVDA certified individuals from around the world, who have sat and successfully passed the NVDA expert exam.





--
Check out my website for NVDA tutorials and other blindness related material at http://www.accessibilitycentral.net
 
Regardless of where you are in New Zealand if you are near one of the APNK sites you can use a copy of the NVDA screen reader on one of their computers. To find out which location (or locations) are nearest to you please visit http://www.aotearoapeoplesnetwork.org/content/partner-libraries (Aotearoa People's Network Kaharoa).
To find out which software is installed on the APNK network please visit the following link http://www.aotearoapeoplesnetwork.info/faq/software To find out how to use NVDA on APNK computers please visit the following link http://www.aotearoapeoplesnetwork.info/faq/nvda
 

To find out which software is available on the Christchurch City Library network, and how to start the NVDA screen reader, please go to the following links. Software available  https://my.christchurchcitylibraries.com/faq/computers/#faq_5884  How to start the NVDA screen reader on Christchurch City Library computers  https://my.christchurchcitylibraries.com/faqs/what-screen-reader-software-is-available/
 
To find an NVDA certified expert near you, please visit the following link https://certification.nvaccess.org/. The certification page contains the official list of NVDA certified individuals from around the world, who have sat and successfully passed the NVDA expert exam.