Date   

Re: RE Using NVDA To Create a Digital Signature

Pranav Lal
 

Hi David,

We are dealing with 2 ways to sign documents.
1. A digital signature.
In this case, the author would use a digital certificate to sign the document. Ideally, this certificate should be one issued by a government authority. A self-signed digital signature may not do. You will need to check the laws. This is accessible because you will be able to read if the document is signed or not and can verify the validity of the certificate. Alternatively, authors could buy certificates from certification authorities and have them signed that way. I do not know if they would be valid for signing contracts but this is how the current security infrastructure of the Internet works. You could also use a digital signature and sign the document the same way as the authors do. This is the most accessible approach.
2. Inserting the image of a signature into a document
You could also ask authors to insert an image of the signature into the word document. This too is called a digital signature which is what makes things confusing. There is no easy way for you to verify this. I could say that you could perhaps extract the image from each contract and run it through the vOICe for windows at http://www.seeingwithsound.com. This would give you the shape of the signature but then you may not have anything to compare it with. Best get sighted assistance. If you can't then you could get very fancy and write an image comparison program. However, once again, you would need reference data.
If you go with the scanned documents approach, keep the e-mail from the author where he has sent the signed copy. I think this may be valid in a court of law but once again, please check with a lawyer.
As for you, you could draw your signature on paper, scan it and insert it as an image into the word document. Your authors would do things the same way.
Pranav


Re: NVDA and speech of toggle keys.

Quentin Christensen
 

Hi Andy,

At this stage there isn't.  It seems to be one of those issues where everyone has their own, slightly different, idea of exactly how it should work.

Kind regards

Quentin.

On Tue, May 30, 2017 at 10:00 AM, andy.tidwell <andy.tidwell@...> wrote:
Hello Quentin, what I was wondering is if there is a way to toggle the speech on the arrow keys on the numpad and the other arrow keys while allowing speech of the tab and function keys because when I went in to the sittings
and checked to   toggle keys it enabled speech on all toggle keys including all arrow keys and I would like to know if there is a way some how to turn off speech on the arrow keys only.
 
From: Quentin Christensen
Sent: Monday, May 29, 2017 7:31 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA and speech of toggle keys.
 
I think this is an issue related to the conversation?
 
 
Regards
 
Quentin.
 
On Tue, May 30, 2017 at 5:53 AM, Rui Fontes <rui.fontes@...> wrote:
NV Access team and Joseph, this is another thing we have to think...

We have discussed this issue some time ago in devellopers list, and, I think, we have arrived to an almost agreement that this type of keys should be voiced by NVDA, but not arrows...

Regards,

Rui Fontes


-----Mensagem Original----- De: andy.tidwell
Data: 29 de maio de 2017 19:46
Para: nvda@nvda.groups.io
Assunto: [nvda] NVDA and speech of toggle keys.


Hello everyone I have a question about speech on the toggle keys. I went in to the NVDA menu and enabled speech on toggle keys because I
wanted to hear when I pressed the tab and escape and function keys but now I also hear speech when I press the arrow keys, is there any way I
can stop speech on the arrow keys and still have NVDA announce the other keys? any help will be appreciated.Jesus dyed for us, why can't we live for him?







 
--
Quentin Christensen
Training and Support Manager

Basic Training for NVDA & Microsoft Word with NVDA E-Books now available: http://www.nvaccess.org/shop/

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

Jesus dyed for us, why can't we live for him?




--
Quentin Christensen
Training and Support Manager

Basic Training for NVDA & Microsoft Word with NVDA E-Books now available: http://www.nvaccess.org/shop/

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


Re: NVDA 2017.2 official release announcement

Quentin Christensen
 

Hi Ben,

Good questions.  Re Burmese, the translation was done by native speakers in Myanmar.

Re Aria-current.  I can't find any statistics on how commonly it is used yet, however having it working means that as and when you do come across a web page which uses it, you should find that NVDA is able to handle it correctly, so that's a good thing!

Kind regards

Quentin.

On Tue, May 30, 2017 at 9:36 AM, Ben J. Bloomgren <bbloomgren@...> wrote:
OK, here goes my geeky self.

Burmese is one of those difficult languages from Southeast Asia. How well has anyone heard it working.? I think my night is eighty-sixed. I can't wait to also look at edge more. How well used is the aria current attribute?

Thanks,

Ben

On May 29, 2017, at 16:26, Quentin Christensen <quentin@...> wrote:

Hi everyone,

NVDA 2017.2 is officially available.


Version 2017.2 of the free NVDA screen Reader from NV Access is now available for download. Highlights of this release include full support for audio ducking in the Windows 10 Creators Update; fixes for several selection issues in browse mode, including problems with select all; significant improvements in Microsoft Edge support; and improvements on the web such as indication of elements marked as current (using aria-current).

NVDA is used by 10s of thousands of blind and vision impaired people spanning more than 120 countries, enabling them to socialise, get an education and participate in the workforce regardless of their location, language or economic situation. However, NV Access needs your help to continue this important work. Please consider making a donation when downloading.

To download NVDA, please visit our Download page.

The full what's new is below, which I know if of interest to many:

2017.2

Highlights of this release include full support for audio ducking in the Windows 10 Creators Update; fixes for several selection issues in browse mode, including problems with select all; significant improvements in Microsoft Edge support; and improvements on the web such as indication of elements marked as current (using aria-current).

New Features

  • Cell border information can now be reported in Microsoft Excel by using NVDA+f. (#3044)
  • In web browsers, NVDA now indicates when an element has been marked as current (specifically, using the aria-current attribute). (#6358)
  • Automatic language switching is now supported in Microsoft Edge. (#6852)
  • Added support for Windows Calculator on Windows 10 Enterprise LTSB (Long-Term Servicing Branch) and Server. (#6914)
  • Performing the read current line command three times quickly spells the line with character descriptions. (#6893)
  • New language: Burmese.
  • Unicode up and down arrows and fraction symbols are now spoken appropriately. (#3805)

Changes

  • When navigating with simple review in applications using UI Automation, more extraneous objects are now ignored, making navigation easier. (#6948#6950)

Bug Fixes

  • Web page menu items can now be activated while in browse mode. (#6735)
  • Pressing escape while the configuration profile "Confirm Deletion" dialog is active now dismisses the dialog. (#6851)
  • Fixed some crashes in Mozilla Firefox and other Gecko applications where the multi-process feature is enabled. (#6885)
  • Reporting of background color in screen review is now more accurate when text was drawn with a transparent background. (#6467)
  • Improved support for control descriptions provided on web pages in Internet Explorer 11 (specifically, support for aria-describedby within iframes and when multiple IDs are provided). (#5784)
  • In the Windows 10 Creators Update, NVDA's audio ducking again works as in previous Windows releases; i.e. Duck with speech and sounds, always duck and no ducking are all available. (#6933)
  • NVDA will no longer fail to navigate to or report certain (UIA) controls where a keyboard shortcut is not defined. (#6779)
  • Two empty spaces are no longer added in keyboard shortcut information for certain (UIA) controls. (#6790)
  • Certain combinations of keys on HIMS displays (e.g. space+dot4) no longer fail intermittently. (#3157)
  • Fixed an issue when opening a serial port on systems using certain languages other than English which caused connecting to braille displays to fail in some cases. (#6845)
  • Reduced the chance of the configuration file being corrupted when Windows shuts down. Configuration files are now written to a temporary file before replacing the actual configuration file. (#3165)
  • When performing the read current line command twice quickly to spell the line, the appropriate language is now used for the spelled characters. (#6726)
  • Navigating by line in Microsoft Edge is now up to three times faster in the Windows 10 Creators Update. (#6994)
  • NVDA no longer announces "Web Runtime grouping" when focusing Microsoft Edge documents in the Windows 10 Creators Update. (#6948)
  • All existing versions of SecureCRT are now supported. (#6302)
  • Adobe Acrobat Reader no longer crashes in certain PDF documents (specifically, those containing empty ActualText attributes). (#7021#7034)
  • In browse mode in Microsoft Edge, interactive tables (ARIA grids) are no longer skipped when navigating to tables with t and shift+t. (#6977)
  • In browse mode, pressing shift+home after selecting forward now unselects to the beginning of the line as expected. (#5746)
  • In browse mode, select all (control+a) no longer fails to select all text if the caret is not at the start of the text. (#6909)
  • Fixed some other rare selection problems in browse mode. (#7131)

Changes for Developers

  • Commandline arguments are now processed with Python's argparse module, rather than optparse. This allows certain options such as -r and -q to be handled exclusively. (#6865)
  • core.callLater now queues the callback to NVDA's main queue after the given delay, rather than waking the core and executing it directly. This stops possible freezes due to the core accidentally going to sleep after processing a callback, in the midle of a modal call such as the desplaying of a message box. (#6797)
  • The InputGesture.identifiers property has been changed so that it is no longer normalized. (#6945)
    • Subclasses no longer need to normalize identifiers before returning them from this property.
    • If you want normalized identifiers, there is now an InputGesture.normalizedIdentifiers property which normalizes the identifiers returned by the identifiers property .
  • The InputGesture.logIdentifier property is now deprecated. Callers should use InputGesture.identifiers[0] instead. (#6945)
  • Removed some deprecated code:
    • `speech.REASON_*` constants: `controlTypes.REASON_*` should be used instead. (#6846)
    • `i18nName` for synth settings: `displayName` and `displayNameWithAccelerator` should be used instead. (#6846#5185)
    • `config.validateConfig`. (#6846#667)
    • `config.save`: `config.conf.save` should be used instead. (#6846#667)
  • The list of completions in the autocomplete context menu of the Python Console no longer shows any object path leading up to the final symbol being completed. (#7023)
  • There is now a unit testing framework for NVDA. (#7026)
    • Unit tests and infrastructure are located in the tests/unit directory. See the docstring in the tests\unit\init.py file for details.
    • You can run tests using "scons tests". See the "Running Tests" section of readme.md for details.
    • If you are submitting a pull request for NVDA, you should first run the tests and ensure they pass.
Kind regards

Quentin.
--
Quentin Christensen
Training and Support Manager

Basic Training for NVDA & Microsoft Word with NVDA E-Books now available: http://www.nvaccess.org/shop/

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




--
Quentin Christensen
Training and Support Manager

Basic Training for NVDA & Microsoft Word with NVDA E-Books now available: http://www.nvaccess.org/shop/

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


NVDACon

Earle Zwicker
 

I really enjoyed attending my very first NVDACon. I unfortunately had to miss the Windows 10 and NVDA session. Does anyone know if that particular session is going to be put up in the archives?

Thanks.

Earle

Sent from my iPhone


Re: NVDA and speech of toggle keys.

andy.tidwell
 

Hello Quentin, what I was wondering is if there is a way to toggle the speech on the arrow keys on the numpad and the other arrow keys while allowing speech of the tab and function keys because when I went in to the sittings
and checked to   toggle keys it enabled speech on all toggle keys including all arrow keys and I would like to know if there is a way some how to turn off speech on the arrow keys only.
 

From: Quentin Christensen
Sent: Monday, May 29, 2017 7:31 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA and speech of toggle keys.
 
I think this is an issue related to the conversation?
 
 
Regards
 
Quentin.
 
On Tue, May 30, 2017 at 5:53 AM, Rui Fontes <rui.fontes@...> wrote:
NV Access team and Joseph, this is another thing we have to think...

We have discussed this issue some time ago in devellopers list, and, I think, we have arrived to an almost agreement that this type of keys should be voiced by NVDA, but not arrows...

Regards,

Rui Fontes


-----Mensagem Original----- De: andy.tidwell
Data: 29 de maio de 2017 19:46
Para: nvda@nvda.groups.io
Assunto: [nvda] NVDA and speech of toggle keys.


Hello everyone I have a question about speech on the toggle keys. I went in to the NVDA menu and enabled speech on toggle keys because I
wanted to hear when I pressed the tab and escape and function keys but now I also hear speech when I press the arrow keys, is there any way I
can stop speech on the arrow keys and still have NVDA announce the other keys? any help will be appreciated.Jesus dyed for us, why can't we live for him?







 
--
Quentin Christensen
Training and Support Manager

Basic Training for NVDA & Microsoft Word with NVDA E-Books now available: http://www.nvaccess.org/shop/

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

Jesus dyed for us, why can't we live for him?


Re: NVDA and speech of toggle keys.

Rui Fontes
 

Yes, related with this topic and to the topic of people changing from other screen readers to NVDA!

It is one of NVDA's most criticized failures!

Rui


Rui


-----Mensagem Original-----
De: Quentin Christensen
Data: 30 de maio de 2017 00:31
Para: nvda@nvda.groups.io
Assunto: Re: [nvda] NVDA and speech of toggle keys.


I think this is an issue related to the conversation?

https://github.com/nvaccess/nvda/issues/6553

Regards

Quentin.

On Tue, May 30, 2017 at 5:53 AM, Rui Fontes <rui.fontes@...> wrote:
NV Access team and Joseph, this is another thing we have to think...

We have discussed this issue some time ago in devellopers list, and, I think, we have arrived to an almost agreement that this type of keys should be voiced by NVDA, but not arrows...

Regards,

Rui Fontes


-----Mensagem Original----- De: andy.tidwell
Data: 29 de maio de 2017 19:46
Para: nvda@nvda.groups.io
Assunto: [nvda] NVDA and speech of toggle keys.


Hello everyone I have a question about speech on the toggle keys. I went in to the NVDA menu and enabled speech on toggle keys because I
wanted to hear when I pressed the tab and escape and function keys but now I also hear speech when I press the arrow keys, is there any way I
can stop speech on the arrow keys and still have NVDA announce the other keys? any help will be appreciated.Jesus dyed for us, why can't we live for him?










--

Quentin Christensen
Training and Support Manager


Basic Training for NVDA & Microsoft Word with NVDA E-Books now available: http://www.nvaccess.org/shop/


Ph +61 7 3149 3306
www.nvaccess.org
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess


Re: NVDA 2017.2 official release announcement

Ben J. Bloomgren
 

OK, here goes my geeky self.

Burmese is one of those difficult languages from Southeast Asia. How well has anyone heard it working.? I think my night is eighty-sixed. I can't wait to also look at edge more. How well used is the aria current attribute?

Thanks,

Ben

On May 29, 2017, at 16:26, Quentin Christensen <quentin@...> wrote:

Hi everyone,

NVDA 2017.2 is officially available.


Version 2017.2 of the free NVDA screen Reader from NV Access is now available for download. Highlights of this release include full support for audio ducking in the Windows 10 Creators Update; fixes for several selection issues in browse mode, including problems with select all; significant improvements in Microsoft Edge support; and improvements on the web such as indication of elements marked as current (using aria-current).

NVDA is used by 10s of thousands of blind and vision impaired people spanning more than 120 countries, enabling them to socialise, get an education and participate in the workforce regardless of their location, language or economic situation. However, NV Access needs your help to continue this important work. Please consider making a donation when downloading.

To download NVDA, please visit our Download page.

The full what's new is below, which I know if of interest to many:

2017.2

Highlights of this release include full support for audio ducking in the Windows 10 Creators Update; fixes for several selection issues in browse mode, including problems with select all; significant improvements in Microsoft Edge support; and improvements on the web such as indication of elements marked as current (using aria-current).

New Features

  • Cell border information can now be reported in Microsoft Excel by using NVDA+f. (#3044)
  • In web browsers, NVDA now indicates when an element has been marked as current (specifically, using the aria-current attribute). (#6358)
  • Automatic language switching is now supported in Microsoft Edge. (#6852)
  • Added support for Windows Calculator on Windows 10 Enterprise LTSB (Long-Term Servicing Branch) and Server. (#6914)
  • Performing the read current line command three times quickly spells the line with character descriptions. (#6893)
  • New language: Burmese.
  • Unicode up and down arrows and fraction symbols are now spoken appropriately. (#3805)

Changes

  • When navigating with simple review in applications using UI Automation, more extraneous objects are now ignored, making navigation easier. (#6948#6950)

Bug Fixes

  • Web page menu items can now be activated while in browse mode. (#6735)
  • Pressing escape while the configuration profile "Confirm Deletion" dialog is active now dismisses the dialog. (#6851)
  • Fixed some crashes in Mozilla Firefox and other Gecko applications where the multi-process feature is enabled. (#6885)
  • Reporting of background color in screen review is now more accurate when text was drawn with a transparent background. (#6467)
  • Improved support for control descriptions provided on web pages in Internet Explorer 11 (specifically, support for aria-describedby within iframes and when multiple IDs are provided). (#5784)
  • In the Windows 10 Creators Update, NVDA's audio ducking again works as in previous Windows releases; i.e. Duck with speech and sounds, always duck and no ducking are all available. (#6933)
  • NVDA will no longer fail to navigate to or report certain (UIA) controls where a keyboard shortcut is not defined. (#6779)
  • Two empty spaces are no longer added in keyboard shortcut information for certain (UIA) controls. (#6790)
  • Certain combinations of keys on HIMS displays (e.g. space+dot4) no longer fail intermittently. (#3157)
  • Fixed an issue when opening a serial port on systems using certain languages other than English which caused connecting to braille displays to fail in some cases. (#6845)
  • Reduced the chance of the configuration file being corrupted when Windows shuts down. Configuration files are now written to a temporary file before replacing the actual configuration file. (#3165)
  • When performing the read current line command twice quickly to spell the line, the appropriate language is now used for the spelled characters. (#6726)
  • Navigating by line in Microsoft Edge is now up to three times faster in the Windows 10 Creators Update. (#6994)
  • NVDA no longer announces "Web Runtime grouping" when focusing Microsoft Edge documents in the Windows 10 Creators Update. (#6948)
  • All existing versions of SecureCRT are now supported. (#6302)
  • Adobe Acrobat Reader no longer crashes in certain PDF documents (specifically, those containing empty ActualText attributes). (#7021#7034)
  • In browse mode in Microsoft Edge, interactive tables (ARIA grids) are no longer skipped when navigating to tables with t and shift+t. (#6977)
  • In browse mode, pressing shift+home after selecting forward now unselects to the beginning of the line as expected. (#5746)
  • In browse mode, select all (control+a) no longer fails to select all text if the caret is not at the start of the text. (#6909)
  • Fixed some other rare selection problems in browse mode. (#7131)

Changes for Developers

  • Commandline arguments are now processed with Python's argparse module, rather than optparse. This allows certain options such as -r and -q to be handled exclusively. (#6865)
  • core.callLater now queues the callback to NVDA's main queue after the given delay, rather than waking the core and executing it directly. This stops possible freezes due to the core accidentally going to sleep after processing a callback, in the midle of a modal call such as the desplaying of a message box. (#6797)
  • The InputGesture.identifiers property has been changed so that it is no longer normalized. (#6945)
    • Subclasses no longer need to normalize identifiers before returning them from this property.
    • If you want normalized identifiers, there is now an InputGesture.normalizedIdentifiers property which normalizes the identifiers returned by the identifiers property .
  • The InputGesture.logIdentifier property is now deprecated. Callers should use InputGesture.identifiers[0] instead. (#6945)
  • Removed some deprecated code:
    • `speech.REASON_*` constants: `controlTypes.REASON_*` should be used instead. (#6846)
    • `i18nName` for synth settings: `displayName` and `displayNameWithAccelerator` should be used instead. (#6846#5185)
    • `config.validateConfig`. (#6846#667)
    • `config.save`: `config.conf.save` should be used instead. (#6846#667)
  • The list of completions in the autocomplete context menu of the Python Console no longer shows any object path leading up to the final symbol being completed. (#7023)
  • There is now a unit testing framework for NVDA. (#7026)
    • Unit tests and infrastructure are located in the tests/unit directory. See the docstring in the tests\unit\init.py file for details.
    • You can run tests using "scons tests". See the "Running Tests" section of readme.md for details.
    • If you are submitting a pull request for NVDA, you should first run the tests and ensure they pass.
Kind regards

Quentin.
--
Quentin Christensen
Training and Support Manager

Basic Training for NVDA & Microsoft Word with NVDA E-Books now available: http://www.nvaccess.org/shop/

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


Re: NVDA and speech of toggle keys.

Quentin Christensen
 

I think this is an issue related to the conversation?


Regards

Quentin.

On Tue, May 30, 2017 at 5:53 AM, Rui Fontes <rui.fontes@...> wrote:
NV Access team and Joseph, this is another thing we have to think...

We have discussed this issue some time ago in devellopers list, and, I think, we have arrived to an almost agreement that this type of keys should be voiced by NVDA, but not arrows...

Regards,

Rui Fontes


-----Mensagem Original----- De: andy.tidwell
Data: 29 de maio de 2017 19:46
Para: nvda@nvda.groups.io
Assunto: [nvda] NVDA and speech of toggle keys.


Hello everyone I have a question about speech on the toggle keys. I went in to the NVDA menu and enabled speech on toggle keys because I
wanted to hear when I pressed the tab and escape and function keys but now I also hear speech when I press the arrow keys, is there any way I
can stop speech on the arrow keys and still have NVDA announce the other keys? any help will be appreciated.Jesus dyed for us, why can't we live for him?








--
Quentin Christensen
Training and Support Manager

Basic Training for NVDA & Microsoft Word with NVDA E-Books now available: http://www.nvaccess.org/shop/

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


NVDA 2017.2 official release announcement

Quentin Christensen
 

Hi everyone,

NVDA 2017.2 is officially available.


Version 2017.2 of the free NVDA screen Reader from NV Access is now available for download. Highlights of this release include full support for audio ducking in the Windows 10 Creators Update; fixes for several selection issues in browse mode, including problems with select all; significant improvements in Microsoft Edge support; and improvements on the web such as indication of elements marked as current (using aria-current).

NVDA is used by 10s of thousands of blind and vision impaired people spanning more than 120 countries, enabling them to socialise, get an education and participate in the workforce regardless of their location, language or economic situation. However, NV Access needs your help to continue this important work. Please consider making a donation when downloading.

To download NVDA, please visit our Download page.

The full what's new is below, which I know if of interest to many:

2017.2

Highlights of this release include full support for audio ducking in the Windows 10 Creators Update; fixes for several selection issues in browse mode, including problems with select all; significant improvements in Microsoft Edge support; and improvements on the web such as indication of elements marked as current (using aria-current).

New Features

  • Cell border information can now be reported in Microsoft Excel by using NVDA+f. (#3044)
  • In web browsers, NVDA now indicates when an element has been marked as current (specifically, using the aria-current attribute). (#6358)
  • Automatic language switching is now supported in Microsoft Edge. (#6852)
  • Added support for Windows Calculator on Windows 10 Enterprise LTSB (Long-Term Servicing Branch) and Server. (#6914)
  • Performing the read current line command three times quickly spells the line with character descriptions. (#6893)
  • New language: Burmese.
  • Unicode up and down arrows and fraction symbols are now spoken appropriately. (#3805)

Changes

  • When navigating with simple review in applications using UI Automation, more extraneous objects are now ignored, making navigation easier. (#6948#6950)

Bug Fixes

  • Web page menu items can now be activated while in browse mode. (#6735)
  • Pressing escape while the configuration profile "Confirm Deletion" dialog is active now dismisses the dialog. (#6851)
  • Fixed some crashes in Mozilla Firefox and other Gecko applications where the multi-process feature is enabled. (#6885)
  • Reporting of background color in screen review is now more accurate when text was drawn with a transparent background. (#6467)
  • Improved support for control descriptions provided on web pages in Internet Explorer 11 (specifically, support for aria-describedby within iframes and when multiple IDs are provided). (#5784)
  • In the Windows 10 Creators Update, NVDA's audio ducking again works as in previous Windows releases; i.e. Duck with speech and sounds, always duck and no ducking are all available. (#6933)
  • NVDA will no longer fail to navigate to or report certain (UIA) controls where a keyboard shortcut is not defined. (#6779)
  • Two empty spaces are no longer added in keyboard shortcut information for certain (UIA) controls. (#6790)
  • Certain combinations of keys on HIMS displays (e.g. space+dot4) no longer fail intermittently. (#3157)
  • Fixed an issue when opening a serial port on systems using certain languages other than English which caused connecting to braille displays to fail in some cases. (#6845)
  • Reduced the chance of the configuration file being corrupted when Windows shuts down. Configuration files are now written to a temporary file before replacing the actual configuration file. (#3165)
  • When performing the read current line command twice quickly to spell the line, the appropriate language is now used for the spelled characters. (#6726)
  • Navigating by line in Microsoft Edge is now up to three times faster in the Windows 10 Creators Update. (#6994)
  • NVDA no longer announces "Web Runtime grouping" when focusing Microsoft Edge documents in the Windows 10 Creators Update. (#6948)
  • All existing versions of SecureCRT are now supported. (#6302)
  • Adobe Acrobat Reader no longer crashes in certain PDF documents (specifically, those containing empty ActualText attributes). (#7021#7034)
  • In browse mode in Microsoft Edge, interactive tables (ARIA grids) are no longer skipped when navigating to tables with t and shift+t. (#6977)
  • In browse mode, pressing shift+home after selecting forward now unselects to the beginning of the line as expected. (#5746)
  • In browse mode, select all (control+a) no longer fails to select all text if the caret is not at the start of the text. (#6909)
  • Fixed some other rare selection problems in browse mode. (#7131)

Changes for Developers

  • Commandline arguments are now processed with Python's argparse module, rather than optparse. This allows certain options such as -r and -q to be handled exclusively. (#6865)
  • core.callLater now queues the callback to NVDA's main queue after the given delay, rather than waking the core and executing it directly. This stops possible freezes due to the core accidentally going to sleep after processing a callback, in the midle of a modal call such as the desplaying of a message box. (#6797)
  • The InputGesture.identifiers property has been changed so that it is no longer normalized. (#6945)
    • Subclasses no longer need to normalize identifiers before returning them from this property.
    • If you want normalized identifiers, there is now an InputGesture.normalizedIdentifiers property which normalizes the identifiers returned by the identifiers property .
  • The InputGesture.logIdentifier property is now deprecated. Callers should use InputGesture.identifiers[0] instead. (#6945)
  • Removed some deprecated code:
    • `speech.REASON_*` constants: `controlTypes.REASON_*` should be used instead. (#6846)
    • `i18nName` for synth settings: `displayName` and `displayNameWithAccelerator` should be used instead. (#6846#5185)
    • `config.validateConfig`. (#6846#667)
    • `config.save`: `config.conf.save` should be used instead. (#6846#667)
  • The list of completions in the autocomplete context menu of the Python Console no longer shows any object path leading up to the final symbol being completed. (#7023)
  • There is now a unit testing framework for NVDA. (#7026)
    • Unit tests and infrastructure are located in the tests/unit directory. See the docstring in the tests\unit\init.py file for details.
    • You can run tests using "scons tests". See the "Running Tests" section of readme.md for details.
    • If you are submitting a pull request for NVDA, you should first run the tests and ensure they pass.
Kind regards

Quentin.
--
Quentin Christensen
Training and Support Manager

Basic Training for NVDA & Microsoft Word with NVDA E-Books now available: http://www.nvaccess.org/shop/

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


Re: 2017.2

Quentin Christensen
 

Sorry folks, Mick and Jamie were working later than me last night, I had to go out to a prior engagement.  But yes, NVDA 2017.2 is officially out.  As Dennis guessed, no changes from the rc1 version that came out last week.  I'll send out a fresh message to the list in a minute.

Regards

Quentin.

On Tue, May 30, 2017 at 5:03 AM, Георги Ламбов <obichamlegiona@...> wrote:
   Hi!

I also updated to the latest NvdA-version from the help menu, reading your letter. By the way it happened no strange thing, so, I'm quiet. Yes, by the way I also waited for an official announcement but so is good too.

best wishes
Georgi
На 29.5.2017 г. в 18:39 ч., David Mehler написа:
Hello,

I didn't see any announcement about 2017.2 being out, but my machine
just updated to 2017.2. Is this correct? Can I get some clarification?

Thanks.
Dave.










--
Quentin Christensen
Training and Support Manager

Basic Training for NVDA & Microsoft Word with NVDA E-Books now available: http://www.nvaccess.org/shop/

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


Re: objPad addon suggestion

 

Hi,
In the past, I would have said "yes", but in order to instill a culture of thinking, I'd like to ask you to think carefully about the scope of the add-on. Is ObjPad purely a navigational add-on or does it do something else?
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Josh Kennedy
Sent: Monday, May 29, 2017 1:35 PM
To: nvda@nvda.groups.io
Subject: [nvda] objPad addon suggestion

I have a suggestion for objPad. Could you add a dialog box that will let you 1. monitor certain objects for changes and speak those changes. 2.
If certain objects appear you could silence those objects from speaking any changes and save them on an app by app basis. 3. if an object is unknown go into a dialog and change its roll or change the kind of object NVDA thinks that it is. 4. rename or re-label any object, give it your own name or label it based on its tooltip. 5. monitor parts of objects for changes, speak those changes when triggered by various things happening like a key press, color change, font change, text style change, so on. Assign different tts voices for different objects different pitches and rates of speech. example, all graphic objects may have a higher pitch or may speak slower or faster or use a different voice or different variant. settings could be saved and shared with other NVDA users. Also someday down the road, incorporate objPad into NVDA core itself so its a standard part of NVDA.


Re: fear mongering? Re: [nvda] New Blog Post: Will VFO Acquire NV Access?

 

Well I don't want nvda to be jawasified to be honest.

Unless ofcause it meant that jaws for home users was free and fs were not so stupid about licences, ie pro for running on oses with pro in them and no extra features.

On the other hand, if microsoft simply intigrated narator and nvda together and we could continue having nvda as a major part of windows and could continue to update it and continue the opensource model like chrome and chromium, etc does then I'd nave no issue with it..

While narator has a lot of issues meaning its still quite bad in some situations there is no doubt about it, it does have a few more tricks being intergrated into windows like that and we don't it would be a huge boost.

It does seem the next reader to probably go is the dolphin one since its only supporting ie and a few other things.

My issue is having everyone jawsified.

Jaws hasn't inovated to much either, true its the biggest but things can't stay stale like this.

What I like about nvda is even when its core doesn't move, there are more modules for it.

And the users also can develop for it so if there is a problem or a need you ask and at some point soon someone will do it.

On 30/05/2017 6:11 a.m., erik burggraaf wrote:
Just to follow up, I read the blog post, and it's not fearmongering. I wish I had been available for nvda con. I had surgery at the time and missed the festivities.

Based on the transcript provided in the blog post, my dream of NVDA becoming a core windows component is just that and can never happen.

I still don't understand, and the article fails to explain, why screen reader monopolies are bad. Apple has two very successful ones. Android doesn't preclude any one from developing a screen reader, but google's product is good enough now that it's put numerous screen access and accessibility suite tools out of business, and the biggest losers there unfortunately are the early adopters who largely paid and now have no viable product.

How would we feel if NVDA became the recognized gold standard and a combination of NVDA and built in tools for windows forced VFO out of the AT software market? I suspect most of us would feel better about a market controlled by NVAccess than we would about one controlled by VFO, but if we don't want an AT monopoly, who will compete with NVDA when governments stop funding AT for good? Will we still love the more established NVDA when the next upstart comes along, or will the new thing fade into obscurity leaving NVDA with what amounts to an unchallenged monopoly?

I haven't really observed negative effects of screen reader monopolies on other platforms, and personally I'd welcome a monopoly driven by NVDA in the windows space. I don't really see that happening either, but NVDA continues to meet the needs of consumers and it's easy to see the passion users and contributers have for it.

Best,

Erik


On May 29, 2017 1:41:55 PM "erik burggraaf" <erik@...> wrote:

Pardon folks,

Could it be that I have an overdeveloped sense of delete button? Have I
missed important announcements from nvda developers, blog posts, or
interviews intimating that ownership changes are in the offing at NV
Access? Have I missed similar from any company intimating they wish to buy
up interest in NV Access? Have there been development changes in the nvda
sycle that suggest new directions in control of the product? Please direct
me to those if they exist.

I haven't read Bavia. Does he have a roll in development of NVDA or
directing interest there-in? I suspect not. Well, Chris Hofsteader has
some things on the ball and others not. Despite what he has to say about
VFO's adjenda he clearly has one of his own and despite his experience in
the industry, his facts aren't always right. I ask you where Bavia is
coming from and whether his experience suggests he may have knowledge or
perspective beyond that of an end user?

Why are we talking about an acquisition of NVDA as if it's a thing that
could happen? No evidence have I observed to justify any such.

I was a proud window-eyes user for 10 years, and signs of it's impending
discontinuance had been available for any to see for years before the
acquisitions. Development slowed, then stopped. Spin off software from
new developers emerged to keep the company generating reviniew. Old hands
left not to be replaced. Dan and Doug are retired, presumably happily, and
never was there ever a thought in the hofsteader post that insiders at gw
micro were ready to move on at the time of the acquisitions. As far as I
know, nothing like this is looming on the horizon of NV access. Correct me
if I'm wrong.

Personally, I think that the end of windows as we know it will have a much
bigger impact on NVDA than the VFO group. Those people will milk access
for all they can get while the gettin is still somewhat good, but does any
one here believe the money in the AT market now is on par with what it was
5 and 10 years ago? In November of 2016, dollar volume of mobile device
sales globally exceeded dollar volume of personal computer sales for the
first time, while PC sales themselves have been steadily droping since 2011
and have not been bouncing back. Both major opperating systems in the pc
space have gone from completely paid to free or alternatively priced in an
attempt to revive interest in the personal computer, but corporations and
consumers are slowly pulling the bandaids off of their eyes. Accessibility
features of mobile devices are equal to or better than those built into
personal computers. Mobile devices can be had cheaper outright than pc's,
and better communication regulations are forcing carriers to share back
more of their prophets with users in the form of more user friendly
contracts, and more service delivery for less money. Canada isn't really
onboard unfortunately, but the rest of the western world seems to be doing
more to provide value for money over all. The two biggest mobile players,
IOS and android, have professional quality accessibility suites built in
and those tools are getting better.

To me, it makes more sense for microsoft to buy NVDA and make it a core
operating system feature in place of narrator than for VFO to acquire it
just to put it out of business. At least MS with full control over
development and system intergration would have the ability to make money
from the product, even if the income stream were nowhere near enough to pay
for development.

The real questions are, what will the next itteration of windows in a year
or two look like? and, How much longer will I want a personal computer?
Myself, I haven't owned a computer in nine months. The only thing I missed
about a pc was the ability to store large files, and I got a little box for
$150 to hook up to a drive tower last month. I need a bigger, better
phone, but the only time I'm prevented from doing anything I want on my
phone is when there's a badly designed website or inaccessible app. The
fact that I can litterally work anywhere, and have access to modern
computing will mean that I will never want a computer for day to day use
again, and you'll be there yourself in the next 1-3 years. How windows and
NVDA fit in modern computing remains to be seen as far as I'm concerned. I
don't see it disappearing over night, but I don't see it lasting forever
either. Yes, I still have an old dos machine, and yes, I do regret not
taking the old apple IIe I was offered back in 2005, but that doesn't mean
I use information the way I did in the 80's and 90's.

I'm a proud NVDA contributer and I plan to use nothing else on any windows
systems I may need in future, but I don't think NVDA will last forever, nor
do I think it necessarily should last forever, nor do I believe the people
working on NVDA will pull the rug out from under us with no warning, nor do
I believe speculation without information contributes meaningfully to the
community. Fire away if you think I'm wrong, but seriously, there's no
reason for panick or uncertainty that I can see.

Best,

Erik


On May 29, 2017 12:44:36 PM "Rosemarie Chavarria" <knitqueen2007@...>
wrote:

Hi,

I don't think V F O will acquire NV access. We need to keep NVDA open
source as it is now because so many people can't afford to pay for Jaws
plus the upgrades. I hope and pray that NVDA will stay as it is now.

Rosemarie



-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Bhavya shah
Sent: Sunday, May 28, 2017 9:03 PM
To: nvda@nvda.groups.io
Subject: [nvda] New Blog Post: Will VFO Acquire NV Access?

Dear all,
‘Will VFO Acquire NVDA?’ has been a highly debated topic in the blindness
community in recent times. Find out the answer to this inquiry with all the
cogent reasoning, justification and arguments you may desire as I explore
all the possibilities and probabilities in my new blog post.
‘Now, let me restate the question of the hour in a simplified form – will
the VFO-Group, owners of the Freedom Scientific made JAWS screen reader,
after phasing out its subsidiary AI Squared’s Window Eyes screen reader,
venture out (caught the pun?) to buy out NV Access and its free and open
source NVDA screen reader, and thereby establish an absolute monopoly as
far as Windows screen readers go?’
Post URL:
https://bhavyashah125.wordpress.com/2017/05/28/will-vfo-acquire-nv-access/
Blog Address: https://bhavyashah125.wordpress.com/

Feel free to drop your comments, follow the blog or share the post.
Thanks.

--
Best Regards
Bhavya Shah

Blogger at Hiking Across Horizons: https://bhavyashah125.wordpress.com/

Contacting Me
E-mail Address: bhavya.shah125@... Follow me on Twitter
@BhavyaShah125 or www.twitter.com/BhavyaShah125 Mobile Number: +91 7506221750












objPad addon suggestion

Josh Kennedy
 

I have a suggestion for objPad. Could you add a dialog box that will let you 1. monitor certain objects for changes and speak those changes. 2. If certain objects appear you could silence those objects from speaking any changes and save them on an app by app basis. 3. if an object is unknown go into a dialog and change its roll or change the kind of object NVDA thinks that it is. 4. rename or re-label any object, give it your own name or label it based on its tooltip. 5. monitor parts of objects for changes, speak those changes when triggered by various things happening like a key press, color change, font change, text style change, so on. Assign different tts voices for different objects different pitches and rates of speech. example, all graphic objects may have a higher pitch or may speak slower or faster or use a different voice or different variant. settings could be saved and shared with other NVDA users. Also someday down the road, incorporate objPad into NVDA core itself so its a standard part of NVDA.


Re: error on ms sites right now

 

Well I logged to msn today and its fixed so I must have hit a down moment or something.

On 29/05/2017 10:20 p.m., Marco Oros wrote:
What crazyness?
I have encountered this problem, but I think, that NVDA addons website had also problems with SSL.



Re: NVDA and speech of toggle keys.

Rui Fontes
 

NV Access team and Joseph, this is another thing we have to think...

We have discussed this issue some time ago in devellopers list, and, I think, we have arrived to an almost agreement that this type of keys should be voiced by NVDA, but not arrows...

Regards,

Rui Fontes


-----Mensagem Original-----
De: andy.tidwell
Data: 29 de maio de 2017 19:46
Para: nvda@nvda.groups.io
Assunto: [nvda] NVDA and speech of toggle keys.


Hello everyone I have a question about speech on the toggle keys. I went in to the NVDA menu and enabled speech on toggle keys because I
wanted to hear when I pressed the tab and escape and function keys but now I also hear speech when I press the arrow keys, is there any way I
can stop speech on the arrow keys and still have NVDA announce the other keys? any help will be appreciated.Jesus dyed for us, why can't we live for him?


Re: 2017.2

Георги Ламбов <obichamlegiona@...>
 

Hi!

I also updated to the latest NvdA-version from the help menu, reading your letter. By the way it happened no strange thing, so, I'm quiet. Yes, by the way I also waited for an official announcement but so is good too.

best wishes
Georgi
На 29.5.2017 г. в 18:39 ч., David Mehler написа:

Hello,

I didn't see any announcement about 2017.2 being out, but my machine
just updated to 2017.2. Is this correct? Can I get some clarification?

Thanks.
Dave.


NVDA and speech of toggle keys.

andy.tidwell
 

Hello everyone I have a question about speech on the toggle keys. I went in to the NVDA menu and enabled speech on toggle keys because I
wanted to hear when I pressed the tab and escape and function keys but now I also hear speech when I press the arrow keys, is there any way I
can stop speech on the arrow keys and still have NVDA announce the other keys? any help will be appreciated.Jesus dyed for us, why can't we live for him?


Re: fear mongering? Re: [nvda] New Blog Post: Will VFO Acquire NV Access?

 

If people would read the post, it makes it clear that NV access can't be bought off. LOL. so, babble babble babble, I guess.


Re: fear mongering? Re: [nvda] New Blog Post: Will VFO Acquire NV Access?

erik burggraaf <erik@...>
 

Just to follow up, I read the blog post, and it's not fearmongering. I wish I had been available for nvda con. I had surgery at the time and missed the festivities.

Based on the transcript provided in the blog post, my dream of NVDA becoming a core windows component is just that and can never happen.

I still don't understand, and the article fails to explain, why screen reader monopolies are bad. Apple has two very successful ones. Android doesn't preclude any one from developing a screen reader, but google's product is good enough now that it's put numerous screen access and accessibility suite tools out of business, and the biggest losers there unfortunately are the early adopters who largely paid and now have no viable product.

How would we feel if NVDA became the recognized gold standard and a combination of NVDA and built in tools for windows forced VFO out of the AT software market? I suspect most of us would feel better about a market controlled by NVAccess than we would about one controlled by VFO, but if we don't want an AT monopoly, who will compete with NVDA when governments stop funding AT for good? Will we still love the more established NVDA when the next upstart comes along, or will the new thing fade into obscurity leaving NVDA with what amounts to an unchallenged monopoly?

I haven't really observed negative effects of screen reader monopolies on other platforms, and personally I'd welcome a monopoly driven by NVDA in the windows space. I don't really see that happening either, but NVDA continues to meet the needs of consumers and it's easy to see the passion users and contributers have for it.

Best,

Erik

On May 29, 2017 1:41:55 PM "erik burggraaf" <erik@...> wrote:

Pardon folks,

Could it be that I have an overdeveloped sense of delete button? Have I
missed important announcements from nvda developers, blog posts, or
interviews intimating that ownership changes are in the offing at NV
Access? Have I missed similar from any company intimating they wish to buy
up interest in NV Access? Have there been development changes in the nvda
sycle that suggest new directions in control of the product? Please direct
me to those if they exist.

I haven't read Bavia. Does he have a roll in development of NVDA or
directing interest there-in? I suspect not. Well, Chris Hofsteader has
some things on the ball and others not. Despite what he has to say about
VFO's adjenda he clearly has one of his own and despite his experience in
the industry, his facts aren't always right. I ask you where Bavia is
coming from and whether his experience suggests he may have knowledge or
perspective beyond that of an end user?

Why are we talking about an acquisition of NVDA as if it's a thing that
could happen? No evidence have I observed to justify any such.

I was a proud window-eyes user for 10 years, and signs of it's impending
discontinuance had been available for any to see for years before the
acquisitions. Development slowed, then stopped. Spin off software from
new developers emerged to keep the company generating reviniew. Old hands
left not to be replaced. Dan and Doug are retired, presumably happily, and
never was there ever a thought in the hofsteader post that insiders at gw
micro were ready to move on at the time of the acquisitions. As far as I
know, nothing like this is looming on the horizon of NV access. Correct me
if I'm wrong.

Personally, I think that the end of windows as we know it will have a much
bigger impact on NVDA than the VFO group. Those people will milk access
for all they can get while the gettin is still somewhat good, but does any
one here believe the money in the AT market now is on par with what it was
5 and 10 years ago? In November of 2016, dollar volume of mobile device
sales globally exceeded dollar volume of personal computer sales for the
first time, while PC sales themselves have been steadily droping since 2011
and have not been bouncing back. Both major opperating systems in the pc
space have gone from completely paid to free or alternatively priced in an
attempt to revive interest in the personal computer, but corporations and
consumers are slowly pulling the bandaids off of their eyes. Accessibility
features of mobile devices are equal to or better than those built into
personal computers. Mobile devices can be had cheaper outright than pc's,
and better communication regulations are forcing carriers to share back
more of their prophets with users in the form of more user friendly
contracts, and more service delivery for less money. Canada isn't really
onboard unfortunately, but the rest of the western world seems to be doing
more to provide value for money over all. The two biggest mobile players,
IOS and android, have professional quality accessibility suites built in
and those tools are getting better.

To me, it makes more sense for microsoft to buy NVDA and make it a core
operating system feature in place of narrator than for VFO to acquire it
just to put it out of business. At least MS with full control over
development and system intergration would have the ability to make money
from the product, even if the income stream were nowhere near enough to pay
for development.

The real questions are, what will the next itteration of windows in a year
or two look like? and, How much longer will I want a personal computer?
Myself, I haven't owned a computer in nine months. The only thing I missed
about a pc was the ability to store large files, and I got a little box for
$150 to hook up to a drive tower last month. I need a bigger, better
phone, but the only time I'm prevented from doing anything I want on my
phone is when there's a badly designed website or inaccessible app. The
fact that I can litterally work anywhere, and have access to modern
computing will mean that I will never want a computer for day to day use
again, and you'll be there yourself in the next 1-3 years. How windows and
NVDA fit in modern computing remains to be seen as far as I'm concerned. I
don't see it disappearing over night, but I don't see it lasting forever
either. Yes, I still have an old dos machine, and yes, I do regret not
taking the old apple IIe I was offered back in 2005, but that doesn't mean
I use information the way I did in the 80's and 90's.

I'm a proud NVDA contributer and I plan to use nothing else on any windows
systems I may need in future, but I don't think NVDA will last forever, nor
do I think it necessarily should last forever, nor do I believe the people
working on NVDA will pull the rug out from under us with no warning, nor do
I believe speculation without information contributes meaningfully to the
community. Fire away if you think I'm wrong, but seriously, there's no
reason for panick or uncertainty that I can see.

Best,

Erik


On May 29, 2017 12:44:36 PM "Rosemarie Chavarria" <knitqueen2007@...>
wrote:

Hi,

I don't think V F O will acquire NV access. We need to keep NVDA open
source as it is now because so many people can't afford to pay for Jaws
plus the upgrades. I hope and pray that NVDA will stay as it is now.

Rosemarie



-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Bhavya shah
Sent: Sunday, May 28, 2017 9:03 PM
To: nvda@nvda.groups.io
Subject: [nvda] New Blog Post: Will VFO Acquire NV Access?

Dear all,
‘Will VFO Acquire NVDA?’ has been a highly debated topic in the blindness
community in recent times. Find out the answer to this inquiry with all the
cogent reasoning, justification and arguments you may desire as I explore
all the possibilities and probabilities in my new blog post.
‘Now, let me restate the question of the hour in a simplified form – will
the VFO-Group, owners of the Freedom Scientific made JAWS screen reader,
after phasing out its subsidiary AI Squared’s Window Eyes screen reader,
venture out (caught the pun?) to buy out NV Access and its free and open
source NVDA screen reader, and thereby establish an absolute monopoly as
far as Windows screen readers go?’
Post URL:
https://bhavyashah125.wordpress.com/2017/05/28/will-vfo-acquire-nv-access/
Blog Address: https://bhavyashah125.wordpress.com/

Feel free to drop your comments, follow the blog or share the post.
Thanks.

--
Best Regards
Bhavya Shah

Blogger at Hiking Across Horizons: https://bhavyashah125.wordpress.com/

Contacting Me
E-mail Address: bhavya.shah125@... Follow me on Twitter
@BhavyaShah125 or www.twitter.com/BhavyaShah125 Mobile Number: +91 7506221750








Re: Where does it go?

 

Hi,
When you download from an installed copy, the updater will be found in the temp directory.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Roger Stewart
Sent: Monday, May 29, 2017 10:49 AM
To: nvda@nvda.groups.io
Subject: [nvda] Where does it go?

I'm just wondering where the installer file for nvda goes if you update from the program itself instead of going to the website and downloading it? I can't find it anywhere accessible to me. Thought it would be in the downloads folder but it isn't. Does it just delete itself after the install is finished?


Roger