1. nvda@nvda.groups.io
  2. Messages
   Date   
Re: How to activate clickable elements?

Arlene
 

, Using NVDA, How does one rout the mouse just as you would with Jaws?  0-0With Jaws you rout the mouse using insert zero with the num lock off. How does one do this with NVDA? I hope I’m making sense.

 

Sent from Mail for Windows 10

 

From: Gene
Sent: March 24, 2019 9:27 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] How to activate clickable elements?

 

It's the same.  Press enter on the clickable item.  If that doesn't work, you can try routing and clicking the mouse, just as you do with a link.

 

Gene

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

Sent: Sunday, March 24, 2019 7:15 PM

Subject: [nvda] How to activate clickable elements?

 

Hello guys,
Just yesterday, on another list I am in, there was a person asking how to deal with clickable elements on a page.
Well, main difference between us is that the person wanted to know how to do it with JAWS and I'm using NVDA, of course.
I gave a reply saying that I was hoping the way of dealing with these elements would be the same both using JAWS and NVDA, then I would be waiting for answers.
Trouble is, no answer at all thus far. Nor about JAWS nor NVDA.
So there we are. How to deal with these elements using our favorite screen reader ever? :)

Thanks in advance guys

Cheers,
Marcio

AKA Starboy


Follow or add me on Facebook

 
Re: How to activate clickable elements?

Gene
 

It's the same.  Press enter on the clickable item.  If that doesn't work, you can try routing and clicking the mouse, just as you do with a link.
 
Gene

----- Original Message -----
Sent: Sunday, March 24, 2019 7:15 PM
Subject: [nvda] How to activate clickable elements?

Hello guys,
Just yesterday, on another list I am in, there was a person asking how to deal with clickable elements on a page.
Well, main difference between us is that the person wanted to know how to do it with JAWS and I'm using NVDA, of course.
I gave a reply saying that I was hoping the way of dealing with these elements would be the same both using JAWS and NVDA, then I would be waiting for answers.
Trouble is, no answer at all thus far. Nor about JAWS nor NVDA.
So there we are. How to deal with these elements using our favorite screen reader ever? :)

Thanks in advance guys

Cheers,
Marcio AKA Starboy
Follow or add me on Facebook

Re: How to activate clickable elements?

Quentin Christensen
 

Hi Marcio,

If something is designated as clickable, it can be for various reasons.  In some cases, it is otherwise a standard button or link, and can be activated just like any other button or link.  In some cases, it is a piece of text that the author wants to behave like a button or link, and you might be able to activate it with enter or space.  In some cases you can interact with it in other ways - for instance a badly programmed element might be looking for the mouse and be difficult to access with the keyboard.  In some cases, the object may not be able to be activated at all, it just says it is clickable.

In short, try interacting with it as you would the type of element it seems like it should be.

Regards

Quentin.

On Mon, Mar 25, 2019 at 11:18 AM marcio via Groups.Io <marcinhorj21=yahoo.com.br@groups.io> wrote:
Hello guys,
Just yesterday, on another list I am in, there was a person asking how to deal with clickable elements on a page.
Well, main difference between us is that the person wanted to know how to do it with JAWS and I'm using NVDA, of course.
I gave a reply saying that I was hoping the way of dealing with these elements would be the same both using JAWS and NVDA, then I would be waiting for answers.
Trouble is, no answer at all thus far. Nor about JAWS nor NVDA.
So there we are. How to deal with these elements using our favorite screen reader ever? :)

Thanks in advance guys

Cheers,
Marcio AKA Starboy
Follow or add me on Facebook



--
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
 

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/

Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 
Re: Mouse Navigation

Quentin Christensen
 

Hi Greg,

Object navigation in NVDA isn't quite the same as moving the mouse.  If you do want to control the mouse, you might consider the golden cursor addon from https://addons.nvda-project.org/index.en.html

Basically, the main time you would want to use either the mouse or object navigation, is when you can't get to a particular control using regular navigation keys.

Sometimes this is because the control was never designed to be interacted with - for instance, the "winver" dialog which tells you about the version of Windows you are using.  At other times, it is because a program developer hasn't made their program accessible and hasn't included a keystroke or way to get to a particular control with the keyboard.

Ideally most users shouldn't need to use those kinds of workarounds very often, but they can be useful if you find yourself in a situation where you need to get to something there isn't a standard keystroke for.

While all the keys for using Object navigation and the review cursor are in the User Guide: https://www.nvaccess.org/files/nvda/documentation/userGuide.html#NavigatingWithNVDA

The User Guide is handy to refresh yourself on a particular keystroke that you already know (eg if you are familiar with object navigation but forgot the exact keys to move the system focus to the current review object).

To learn how to use the review cursor and object navigation, I would recommend the "Basic Training for NVDA" which, while not free, is very reasonably priced in the NV Access shop: https://www.nvaccess.org/shop/ (and available in a selection of formats).

Where object navigation moves between the objects that make up a window, golden cursor lets you move the mouse itself, so you can move to the object to the right, regardless of where it is in the tree of objects.  You can find the keystrokes for that on its addon page that I linked to up the top of this message.

Kind regards

Quentin.

On Mon, Mar 25, 2019 at 7:52 AM Greg Rhodes <gkrhodes@...> wrote:

I spend most of my computer time browsing with Microsoft Edge and working on documents and spreadsheets in MS Word and Excel 2016. I’m running the latest version of Windows 10. I need to use a screen reader for almost all of my work these days (magnification is no longer real useful for me).

 

Given my above uses, can someone give me a couple of examples of where mouse navigation (using the numpad) would be used? I’m trying to figure out if there would be any benefit in my learning mouse navigation commands. Thanks. Thanks.

 

Greg

 



--
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
 

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@...> 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@...> 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@...
>>
>> On 3/21/19, Abbie Taylor <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@...
>>> Order my new memoir at http://www.abbiejohnsontaylor.com/memoir.htm
>>>
>>> --
>>> Abbie Johnson Taylor, Author
>>> http://www.abbiejohnsontaylor.com
>>> http://abbiescorner.wordpress.com
>>> abbietaylor945@...
>>>
>>>
>>>
>>
>>
>
>
>
>


--
Subscribe to a WordPress for Newbies Mailing List by sending a message to:
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 & www.mysitesbeenhacked.com





--
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 and NVDA

Aravind R
 

make sure the purchased book are screen reader supported. then NVDA
reads the book once you press enter on that book. all screen reading
command will work. cut, copy, paste keys are disabled to prevent us
copying and sharing.

On 3/25/19, Mary Otten <maryotten@...> wrote:
Hi don,
Could you be a little bit more specific? I Mean, are you having a problem?
Do you have the app installed? You have a Kindle library. You can download
books to the Kindle for PC app once you have it installed. You open the app,
and you can tap around and see the list of books that you have and arrow
down to the one you want to read. So I’m not too sure what problem you’re
having.
Mary
On Mar 24, 2019, at 4:30 PM, Don H <lmddh50@...> wrote:

How do you read books using the Kindle for PC if you want to use NVDA to
do the reading?








--
--
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: Kindle for pc and NVDA

Mary Otten
 

Hi don,
Could you be a little bit more specific? I Mean, are you having a problem? Do you have the app installed? You have a Kindle library. You can download books to the Kindle for PC app once you have it installed. You open the app, and you can tap around and see the list of books that you have and arrow down to the one you want to read. So I’m not too sure what problem you’re having.
Mary

On Mar 24, 2019, at 4:30 PM, Don H <lmddh50@...> wrote:

How do you read books using the Kindle for PC if you want to use NVDA to do the reading?
How to activate clickable elements?

Marcio
 

Hello guys,
Just yesterday, on another list I am in, there was a person asking how to deal with clickable elements on a page.
Well, main difference between us is that the person wanted to know how to do it with JAWS and I'm using NVDA, of course.
I gave a reply saying that I was hoping the way of dealing with these elements would be the same both using JAWS and NVDA, then I would be waiting for answers.
Trouble is, no answer at all thus far. Nor about JAWS nor NVDA.
So there we are. How to deal with these elements using our favorite screen reader ever? :)

Thanks in advance guys

Cheers,
Marcio AKA Starboy
Follow or add me on Facebook

Kindle for pc and NVDA

Don H
 

How do you read books using the Kindle for PC if you want to use NVDA to do the reading?
Re: NVDA and icons in the system tray

Shaun Everiss
 

I can confirm that onedrive just doesn't want to click but then I have had icons I have had to click with the mouse like the intel driver update so who knows.

On 25/03/2019 11:14 AM, Kevin Cussick via Groups.Io wrote:
Nothing works.

On 24/03/2019 10:03, Brian's Mail list account via Groups.Io wrote:
What about the context menu?
Does that work, if it does then it means the mouse is there and its highlighted and just needs that  extra command.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Kevin Cussick via Groups.Io" <the.big.white.shepherd@...>
To: <nvda@nvda.groups.io>
Sent: Saturday, March 23, 2019 10:26 PM
Subject: Re: [nvda] NVDA and icons in the system tray


Yes,   but it does nothing on the one drive system icon.

On 23/03/2019 18:58, Rui Fontes wrote:
Because of that the Systray addon was develloped...
Many times it is possible through the icons list activate that not cooperative buttons...

Rui Fontes


Às 18:52 de 23/03/2019, Gene escreveu:
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 <mailto:marrie12@...>
*Sent:* Saturday, March 23, 2019 1:49 PM
*To:* nvda@nvda.groups.io <mailto: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

Kevin Cussick
 

Nothing works.

On 24/03/2019 10:03, Brian's Mail list account via Groups.Io wrote:
What about the context menu?
Does that work, if it does then it means the mouse is there and its highlighted and just needs that  extra command.
Brian
bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Kevin Cussick via Groups.Io" <the.big.white.shepherd@...>
To: <nvda@nvda.groups.io>
Sent: Saturday, March 23, 2019 10:26 PM
Subject: Re: [nvda] NVDA and icons in the system tray

Yes,   but it does nothing on the one drive system icon.

On 23/03/2019 18:58, Rui Fontes wrote:
Because of that the Systray addon was develloped...
Many times it is possible through the icons list activate that not cooperative buttons...

Rui Fontes


Às 18:52 de 23/03/2019, Gene escreveu:
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 <mailto:marrie12@...>
*Sent:* Saturday, March 23, 2019 1:49 PM
*To:* nvda@nvda.groups.io <mailto: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

Kevin Cussick
 

Hi, it stopped working for me at some point when windows got upgraded. I remember this but meant to ask and just carried on with the system tray not working. anyway most icons work just not one drive. I have just done a clean install of windows as the insider slow build just did not install. I upgraded the machine to a 1 TB SSD and it is flying will try the system icon later now that I have installed windows from scratch.

On 24/03/2019 05:00, Ron Canazzi wrote:
Hi Kevin,
I tried it again with the same specs and it works just fine on my system. I wonder if there is a setting in Windows 10 that is different for both of us.  Darned if I could figure out where to start looking for it.
On 3/23/2019 6:28 PM, Kevin Cussick via Groups.Io wrote:
this does not work for me,   using windows10 home 64 bit and latest alpha nvda and yes I have tried this with the stable build.

On 23/03/2019 19:30, Ron Canazzi wrote:
Hi Kostadian,


I am using Windows 10 latest update with NVDA 2018.4 latest stable release and I am able to access my One Drive icon with no problem. There is an add on that simulates the JAWS equivalent with the NVDA + F11 keystroke, but even without the add on, if you do the following, you get the interface displayed.

1.  Press Windows + B to move to the system tray.

2.  Move to the open drive icon.

3.  Route your mouse cursor to the application cursor with NVDA + numpad slash.

4.  initiate a right click with numpad star and a menu opens.


If you have the add on it's much simpler.

Press NVDA + F11, use first letter navigation to move to the open drive icon and tab to the right click item and press enter.




On 3/23/2019 2:23 PM, 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: Kindle for PC

Mary Otten
 

Yes, it does work well with Kindle for PC.

On Mar 24, 2019, at 1:49 PM, Don H <lmddh50@...> wrote:

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

Thanks
Mouse Navigation

Greg Rhodes <gkrhodes@...>
 

I spend most of my computer time browsing with Microsoft Edge and working on documents and spreadsheets in MS Word and Excel 2016. I’m running the latest version of Windows 10. I need to use a screen reader for almost all of my work these days (magnification is no longer real useful for me).

 

Given my above uses, can someone give me a couple of examples of where mouse navigation (using the numpad) would be used? I’m trying to figure out if there would be any benefit in my learning mouse navigation commands. Thanks. Thanks.

 

Greg

 
Kindle for PC

Don H
 

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

Thanks
Re: NVDA with Chrome

Gene
 

If you use add-ons, try running NVDA with no add-ons running and see if Chrome runs.
 
If you don't know how to run NVDA with no add-ons running, you do so in the shut down dialog of NVDA, ask here.
 
Gene

----- Original Message -----
Sent: Sunday, March 24, 2019 2:54 PM
Subject: [nvda] Nbda with chrome

I use Windows 10 1809, latest nvda and chrome. Most of time nvda hangs when I use chrome. I faced this problem in previous version of chrome as well. How to fix it?
Re: My Log from Yesterday

Gene
 

In Chrome, try going to the address bar, control l, and experiment typing parts of names of sites that are in book marks.  Wait a moment, and start down arrowing.
 
When I want to find The New York Times from bookmarks, I just type times.  You can experiment with words from book marks that are likely to be only in the book mark you want to find.  You can type more of a name, of course.  the more you type, the more likely you will be to find it if there are other results that might be shown with less words. 
 
This method also finds things in history so you may see either as a result.
 
Gene

----- Original Message -----
Sent: Sunday, March 24, 2019 11:25 AM
To: NVDA
Subject: Re: [nvda] My Log from Yesterday

I’m using an earlier version of Firefox I installed several years ago when the latest version was not accessible. I’m happy with Chrome except for the way it handles bookmarks, but I’ve found ways to work around that. If I decide to go back to Firefox, I’ll un-install it and try the latest version. Thank you, Brian.

 

 

 

Abbie Johnson Taylor, Author https://abbiescorner.wordpress.com

http://www.abbiejohnsontaylor.com

abbietaylor945@...

 

 

 


--
Abbie Johnson Taylor, Author
http://www.abbiejohnsontaylor.com
http://abbiescorner.wordpress.com
abbietaylor945@...

NVDA with Chrome

farhan israk
 

I use Windows 10 1809, latest nvda and chrome. Most of time nvda hangs when I use chrome. I faced this problem in previous version of chrome as well. How to fix it?
Re: My Log from Yesterday

Abbie Taylor
 

I’m using an earlier version of Firefox I installed several years ago when the latest version was not accessible. I’m happy with Chrome except for the way it handles bookmarks, but I’ve found ways to work around that. If I decide to go back to Firefox, I’ll un-install it and try the latest version. Thank you, Brian.

 

 

 

Abbie Johnson Taylor, Author https://abbiescorner.wordpress.com

http://www.abbiejohnsontaylor.com

abbietaylor945@...

 

 

 


--
Abbie Johnson Taylor, Author
http://www.abbiejohnsontaylor.com
http://abbiescorner.wordpress.com
abbietaylor945@...
44121 - 44140 of 103095