Date   

Re: NVDA documentation

David Mellor
 

NVDA+2 (main keyboard) toggles speaking of typed characters?
I'm not sure what you had in mind there Gene.
David



From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Gene
Sent: 09 September 2021 13:25
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA documentation

Is scrolling through all the objects the same thing as using NVDA key 2 on the main  keyboard? 
 
Gene
-----Original Message-----
Sent: Thursday, September 09, 2021 3:20 AM
Subject: Re: [nvda] NVDA documentation
 

Hi Quentin ,

I'm not too concerned with arguing the case for default key strokes being setup.

So long as it goes into the manual then people can set the keys up if they wish.

I think these functions can be very useful though. When using object navigation to find elements that we know are on the screen somewhere but may not have a clear sense of the object hierarchy it can be a lot easier if time consuming to just scroll through all of the objects.

I have certainly used this on occasion.

I've assigned them to 3 and 9, prev and next respectively.

Very best wishes,

David

 


Re: not constantly maintained addon and compatibility issue

William
 

Well, do you mean rename the .addon file to .zip,

unzip it,

use text editor to open the .ini file

edit the line last tested version to thelatest nvda version

then zip the folder back to  a .zip file and rename to a .addon file?


Fawaz Abdul rahman 於 9/9/2021 17:10 寫道:

Hi,
if it is just a matter of the flag, then you can edit the manifest.ini file yourself and it should work properly.
However, if you are not sure how to do it or what to do, send the addons you have issues with, and someone may be able to help you.
good luck.


On Thu, Sep 9, 2021 at 8:41 AM William <xsuper.sillyx@...> wrote:
Hello, especially for nvda developers and addon developers,


Thanks to lots of addon that enhanced my productivity.

The current situation is that, some of the addon that I am using is not
supporting the latest nvda 2021.1 and are forced to be blocked by nvda.

To my understanding, some of these addons are not really "having
compatibility issue", it is only not updated the addon file to state
that the addon is supporting the latest nvda, am i right?


Can we have a mechanism to make these addons being maintained, even

if the developer ignored it or forget to update it?


Thanks,

William








Re: NVDA documentation

Gene
 

Is scrolling through all the objects the same thing as using NVDA key 2 on the main  keyboard? 
 
Gene

-----Original Message-----
Sent: Thursday, September 09, 2021 3:20 AM
Subject: Re: [nvda] NVDA documentation
 

Hi Quentin ,

I'm not too concerned with arguing the case for default key strokes being setup.

So long as it goes into the manual then people can set the keys up if they wish.

I think these functions can be very useful though. When using object navigation to find elements that we know are on the screen somewhere but may not have a clear sense of the object hierarchy it can be a lot easier if time consuming to just scroll through all of the objects.

I have certainly used this on occasion.

I've assigned them to 3 and 9, prev and next respectively.

Very best wishes,

David

 


NVDA development course

James AUSTIN
 

Hi gentle people

Hope everyone is well.

Back in 2019 I believe, a subgroup was created to discuss NVDA development. Would anyone by any chance please be willing to share in link to this information if it is available somewhere on the web as I am unable to find it.

Thank you

Kind regards

James


Re: not constantly maintained addon and compatibility issue

Fawaz Abdul rahman
 

Hi,
if it is just a matter of the flag, then you can edit the manifest.ini file yourself and it should work properly.
However, if you are not sure how to do it or what to do, send the addons you have issues with, and someone may be able to help you.
good luck.


On Thu, Sep 9, 2021 at 8:41 AM William <xsuper.sillyx@...> wrote:
Hello, especially for nvda developers and addon developers,


Thanks to lots of addon that enhanced my productivity.

The current situation is that, some of the addon that I am using is not
supporting the latest nvda 2021.1 and are forced to be blocked by nvda.

To my understanding, some of these addons are not really "having
compatibility issue", it is only not updated the addon file to state
that the addon is supporting the latest nvda, am i right?


Can we have a mechanism to make these addons being maintained, even

if the developer ignored it or forget to update it?


Thanks,

William








Re: NVDA documentation

David Mellor
 

Hi Quentin ,

I'm not too concerned with arguing the case for default key strokes being setup.

So long as it goes into the manual then people can set the keys up if they wish.

I think these functions can be very useful though. When using object navigation to find elements that we know are on the screen somewhere but may not have a clear sense of the object hierarchy it can be a lot easier if time consuming to just scroll through all of the objects.

I have certainly used this on occasion.

I've assigned them to 3 and 9, prev and next respectively.

Very best wishes,

David

 


Re: not constantly maintained addon and compatibility issue

Jujube
 

Hi, I sympathize and agree it's a frustration, but I think what you're describing isn't something that can be fixed in a day and it's not something that's going to be perfect. A lot of the incompatibility issues are a result of the Python programming language constantly being updated so NVDA has to keep up with that. If an addon developer stops working on an addon, the only solution is to find another developer willing to work on it and that isn't always an easy task. I know this isn't very helpful news but hopefully this explains why the addons world isn't perfect..


On Wed, Sep 8, 2021 at 10:41 PM William <xsuper.sillyx@...> wrote:
Hello, especially for nvda developers and addon developers,


Thanks to lots of addon that enhanced my productivity.

The current situation is that, some of the addon that I am using is not
supporting the latest nvda 2021.1 and are forced to be blocked by nvda.

To my understanding, some of these addons are not really "having
compatibility issue", it is only not updated the addon file to state
that the addon is supporting the latest nvda, am i right?


Can we have a mechanism to make these addons being maintained, even

if the developer ignored it or forget to update it?


Thanks,

William








not constantly maintained addon and compatibility issue

William
 

Hello, especially for nvda developers and addon developers,


Thanks to lots of addon that enhanced my productivity.

The current situation is that, some of the addon that I am using is not supporting the latest nvda 2021.1 and are forced to be blocked by nvda.

To my understanding, some of these addons are not really "having compatibility issue", it is only not updated the addon file to state that the addon is supporting the latest nvda, am i right?


Can we have a mechanism to make these addons being maintained, even

if the developer ignored it or forget to update it?


Thanks,

William


Google Drive for Desktop Accessibility?

John Sanfilippo
 

Hi, I was a Backup and Sync user and, as is life's nature, things changed. That's ok, but the new system appears to be no more accessible than the old.

Is there any NVDA magic to get things working together? The stand keyboard nav does not appear to work, nor do siple screen review commands. Or, they wrk sporadically.

John


--
- JS o m -


Re: NVDA documentation

Quentin Christensen
 

Just to recap where we're at here:

1) In the Input Gestures dialog, under "Object Navigation" are two gestures, "Moves to the next object in a flattened view of the object navigation hierarchy", and "Moves to the previous...".  These are assigned flick right and flick left (respectively) in touch screen object mode.

2) There are no default keyboard keystrokes assigned to these gestures.  By opening the Input Gestures dialog and moving to those two options, you can assign keystrokes to these.

3) In the User Guide, under Object Navigation, flick right and left are listed as gestures for next and previous object with flick up and flick down listed as move into and out of the containing object.  The "flattened view" commands are not mentioned: https://www.nvaccess.org/files/nvda/documentation/userGuide.html#ObjectNavigation

So, for now, if you want to assign a keystroke to move by object in a flattened view, see point 1 above.  If you strongly feel there should be default gestures already and would like to put forward a good argument for that, please create an issue: https://github.com/nvaccess/nvda/issues

And meanwhile I will follow up the discrepancy between what is in the user guide and what the gestures are (point 3).

Kind regards

Quentin.


On Thu, Sep 9, 2021 at 5:59 AM Rui Fontes <rui.fontes@...> wrote:

In this specific case, it was Jaws copying NVDA! lol!


Regards,


Rui Fontes


Às 20:56 de 08/09/2021, Jonathan COHN via groups.io escreveu:
So this works the same way essentially as JAWS's touch cursor if I am reading your description correctly. JAWS does have an "advanced touch" cursor mode that treats up/down/left/right almost identically to how NVDA does object navigation.
Thanks, this is quite useful to know.
Jonathan C. Cohn 

On Sep 8, 2021, at 08:29, Joseph Lee <joseph.lee22590@...> wrote:

Hi,

Quentin is the one who looks after documentation these days, and I sometimes look at user guide.

The flattened view refers to moving to the next or previous object regardless of object navigation hierarchy. For example, you can move from an object to its child, then to the object's sibling, then to the object next to its parent and what not. This was implemented to support object navigation via touchscreen gestures where you can move among objects on the screen regardless of relationship.

Cheers,

Joseph




--
Quentin Christensen
Training and Support Manager


Re: Clipspeak addon

Rui Fontes
 

Hello!


The last version is 21.05 and it is available in the add-ons oficial page...

So, if you do not have the add-on to update automatically, go to add-ons manager, Get add-ons and download it from there...


Rui Fontes


Às 22:30 de 08/09/2021, Kevin Cussick via groups.io escreveu:

ruia, do You have an updated addon for your addon documentation? thanks in advance.

On 08/09/2021 20:31, Chris Mullins wrote:
Hi Rui

That’s perfect, many thanks

Cheers

Chris

Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows

*From: *Rui Fontes <mailto:rui.fontes@tiflotecnia.com>
*Sent: *08 September 2021 18:06
*To: *nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
*Subject: *Re: [nvda] Clipspeak addon

Here is a version that should work...

https://www.dropbox.com/s/1ahmqhqbjde3gdm/clipspeak2021.1_compatible_and_translations_possible.nvda-addon?dl=1 <https://www.dropbox.com/s/1ahmqhqbjde3gdm/clipspeak2021.1_compatible_and_translations_possible.nvda-addon?dl=1>

You can also use other add-ons to the same purpose...


Rui Fontes

Às 16:41 de 08/09/2021, Brian Vogel escreveu:

    There does not seem to be.  Even on GitHub, the original ClipSpeak
    <https://github.com/nvdaes/NVDAAddon-Clipspeak> code has remained
    unchanged since 2017.  I can't seem to find any easy way to contact
    the original developer, either.

    Since this project is open-source someone else could take it over if
    the original developer cannot be reached or has made the decision to
    cease development.
    --
    Brian - Windows 10, 64-Bit, Version 21H1, Build 19043

    Nothing in all the world is more dangerous than sincere ignorance
    and conscientious stupidity.

              ~Martin Luther King, Jr.




COM registration tool in NVDA 2021.2rc1

Jason White
 

I can report that the COM Registration Tool in NVDA 2021.2rc1 was able to solve a problem that the version of the tool in 2021.1 was unable to fix. The symptoms were as follows.

  • NVDA was unable to access either Chromium-based browsers or Mozilla Firefox. Turning on User Interface Automation for Chromium browsers didn’t help. Browser windows were reported as “pane” (Google Chrome) or “unknown” (firefox).
  • JAWS 2021 running on the same machine couldn’t access Firefox, but it could access Google Chrome and Microsoft Edge.
  • Microsoft Narrator could in fact access Chromium-based browsers as well.

I don’t know what change caused these issues. I may have uninstalled something at some point that deleted registry entries which it shouldn’t have changed.

Fortunately, all appears to be in order after having run COM Registration in 2021.2rc1.

The system is Windows 10 21h1 (64-bit), build 19043.1202. All of the browsers concerned are up to date.

I’m noting this here in case it helps someone who encounters similar issues.

 


Re: Clipspeak addon

Kevin Cussick
 

ruia, do You have an updated addon for your addon documentation? thanks in advance.

On 08/09/2021 20:31, Chris Mullins wrote:
Hi Rui
That’s perfect, many thanks
Cheers
Chris
Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows
*From: *Rui Fontes <mailto:rui.fontes@tiflotecnia.com>
*Sent: *08 September 2021 18:06
*To: *nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
*Subject: *Re: [nvda] Clipspeak addon
Here is a version that should work...
https://www.dropbox.com/s/1ahmqhqbjde3gdm/clipspeak2021.1_compatible_and_translations_possible.nvda-addon?dl=1 <https://www.dropbox.com/s/1ahmqhqbjde3gdm/clipspeak2021.1_compatible_and_translations_possible.nvda-addon?dl=1>
You can also use other add-ons to the same purpose...
Rui Fontes
Às 16:41 de 08/09/2021, Brian Vogel escreveu:
There does not seem to be.  Even on GitHub, the original ClipSpeak
<https://github.com/nvdaes/NVDAAddon-Clipspeak> code has remained
unchanged since 2017.  I can't seem to find any easy way to contact
the original developer, either.
Since this project is open-source someone else could take it over if
the original developer cannot be reached or has made the decision to
cease development.
--
Brian - Windows 10, 64-Bit, Version 21H1, Build 19043
Nothing in all the world is more dangerous than sincere ignorance
and conscientious stupidity.
         ~Martin Luther King, Jr.


Clock add-on: being modernized as we speak

 

Hello NVDA users,

In the midst of studying for graduate coursework, I’m delighted to announce that Clock add-on (developed by Hrvoje Katic) is undergoing massive facelift. I’m sure many of you were wondering about lack of news about this add-on, but fear not – a group of NVDA add-on developers are updating the add-on to make it work on newer NVDA releases.

Part of the reason why there has been no news on Clock add-on was the difficulty in finding new maintainers. The add-ons community recently got in touch with Hrvoje (original author) about the status of the Clock add-on with NvDA 2021.1. In response, Hrvoje informed us that he cannot maintain the add-on on a timely manner and asked the community to keep it updated. After a community-led discussion, it was agreed that I (Joseph Lee) will perform a massive “surgery” of this add-on i.e. I’m modernizing it on behalf of the community as it was felt that I was the best person to do it (a huge thank you to Abdel and others for keeping the add-on updated for a while).

The whole point of this massive surgery is to teach Clock add-on to use newer NVDA features. The last major change was made last year (2020) as part of upgrading to Python 3. Since then many things happened, and it was found that there are features in newer NVDA releases that the add-on can use. The most noticeable change is better integration with NVDA’s multi-page settings interface, as well as defining scripts easier.

At the same time, it was pointed out that the add-on uses a mixture of Python 2 and 3 code. Python 2 is end of life as of 2020, and since NVDA 2019.3’s release more add-ons have migrated to Python 3. Therefore, it was decided that this would be the golden opportunity to move Clock add-on to full Python 3 once and for all.

But perhaps the biggest reason for this surgery is to clean up the add-on code. I think the biggest reason why the add-ons community asked me to perform this facelift was recent experiences with modernizing add-on code. I believe that one way to make add-on development easier is to align the source code more closely with that of NVDA screen reader itself. With this mindset, I have performed code cleanup and modernization on a number of add-ons, and add-ons that were maintained by me recently had their code cleaned up.

So in summary, the following changes are planned or coming with a future version of Clock add-on (tentatively scheduled for late September):

  • NVDA 2019.3 or later is required. As I pointed out earlier, this is so that the Clock add-on can take advantage of Python 3 and newer NVDA features.
  • Possible changes to the user interface messages: there are areas (particularly add-on settings) that could see some refinements to interface messages. Although not for certain, I expect some changes will be made to interface messages.
  • Many internal changes to align add-on source code closer to that of NVDA screen reader. This mostly affects future add-on maintainers.

 

As for how long I will maintain Clock add-on, it depends; I think maybe several months before I pass the add-on back to the community for further maintenance as my primary job with this add-on is the grand modernization surgery. So, as users, you can rest assured that I and members of the add-ons community are working hard to release a version of Clock add-on that is optimized for NVDA 2019.3 and later (and also compatible with 2021.1 and later).

Thank you.

Cheers,

Joseph


Re: NVDA documentation

Rui Fontes
 

In this specific case, it was Jaws copying NVDA! lol!


Regards,


Rui Fontes


Às 20:56 de 08/09/2021, Jonathan COHN via groups.io escreveu:

So this works the same way essentially as JAWS's touch cursor if I am reading your description correctly. JAWS does have an "advanced touch" cursor mode that treats up/down/left/right almost identically to how NVDA does object navigation.
Thanks, this is quite useful to know.
Jonathan C. Cohn 

On Sep 8, 2021, at 08:29, Joseph Lee <joseph.lee22590@...> wrote:

Hi,

Quentin is the one who looks after documentation these days, and I sometimes look at user guide.

The flattened view refers to moving to the next or previous object regardless of object navigation hierarchy. For example, you can move from an object to its child, then to the object's sibling, then to the object next to its parent and what not. This was implemented to support object navigation via touchscreen gestures where you can move among objects on the screen regardless of relationship.

Cheers,

Joseph



Re: NVDA documentation

Jonathan COHN
 

So this works the same way essentially as JAWS's touch cursor if I am reading your description correctly. JAWS does have an "advanced touch" cursor mode that treats up/down/left/right almost identically to how NVDA does object navigation.
Thanks, this is quite useful to know.
Jonathan C. Cohn 

On Sep 8, 2021, at 08:29, Joseph Lee <joseph.lee22590@...> wrote:

Hi,

Quentin is the one who looks after documentation these days, and I sometimes look at user guide.

The flattened view refers to moving to the next or previous object regardless of object navigation hierarchy. For example, you can move from an object to its child, then to the object's sibling, then to the object next to its parent and what not. This was implemented to support object navigation via touchscreen gestures where you can move among objects on the screen regardless of relationship.

Cheers,

Joseph



Re: Clipspeak addon

Chris Mullins
 

Hi Rui

That’s perfect, many thanks

 

Cheers

Chris

 

Sent from Mail for Windows

 

From: Rui Fontes
Sent: 08 September 2021 18:06
To: nvda@nvda.groups.io
Subject: Re: [nvda] Clipspeak addon

 

Here is a version that should work...

https://www.dropbox.com/s/1ahmqhqbjde3gdm/clipspeak2021.1_compatible_and_translations_possible.nvda-addon?dl=1

 

You can also use other add-ons to the same purpose...


Rui Fontes

 

Às 16:41 de 08/09/2021, Brian Vogel escreveu:

There does not seem to be.  Even on GitHub, the original ClipSpeak code has remained unchanged since 2017.  I can't seem to find any easy way to contact the original developer, either.

Since this project is open-source someone else could take it over if the original developer cannot be reached or has made the decision to cease development.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

Nothing in all the world is more dangerous than sincere ignorance and conscientious stupidity.

         ~Martin Luther King, Jr.

 

 


Re: The use of Docusign and NVDA

ss sarfudeen
 

Dear members,

I haven't used this tool. Can you please throw some light on how to
use Docusign to sign documents?
Your inputs are highly appreciated.

With kind regards,

Sultana

On 9/8/21, Louise Pfau <lpfau@telus.net> wrote:
I have successfully signed documents with docusign using NVDA and Microsoft

Edge. I have not used the remote application or created documents.

Louise







Re: Clipspeak addon

Rui Fontes
 

Here is a version that should work...

https://www.dropbox.com/s/1ahmqhqbjde3gdm/clipspeak2021.1_compatible_and_translations_possible.nvda-addon?dl=1


You can also use other add-ons to the same purpose...


Rui Fontes


Às 16:41 de 08/09/2021, Brian Vogel escreveu:

There does not seem to be.  Even on GitHub, the original ClipSpeak code has remained unchanged since 2017.  I can't seem to find any easy way to contact the original developer, either.

Since this project is open-source someone else could take it over if the original developer cannot be reached or has made the decision to cease development.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

Nothing in all the world is more dangerous than sincere ignorance and conscientious stupidity.

         ~Martin Luther King, Jr.

 


Re: Clipspeak addon

 

There does not seem to be.  Even on GitHub, the original ClipSpeak code has remained unchanged since 2017.  I can't seem to find any easy way to contact the original developer, either.

Since this project is open-source someone else could take it over if the original developer cannot be reached or has made the decision to cease development.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

Nothing in all the world is more dangerous than sincere ignorance and conscientious stupidity.

         ~Martin Luther King, Jr.

 

401 - 800 of 87781