Date   

Re: problem with update

P. Otter
 

thanks for it!
it works!
cheers
paul otter


Op 8-12-2018 om 09:57 schreef Adriani Botez:

Hello,

sometimes it could be a server problem or an internet connection problem. You can try to download the last Beta version here:
https://www.nvaccess.org/files/nvda/snapshots/

You can navigate by headings (pressing h in browse mode) and download the last Beta which is 2018.4 Beta 4.

Best
Adriani

-----Ursprüngliche Nachricht-----
Von: nvda@nvda.groups.io <nvda@nvda.groups.io> Im Auftrag von P. Otter
Gesendet: Samstag, 8. Dezember 2018 09:45
An: nvda@nvda.groups.io
Betreff: [nvda] problem with update

hello all,
I've something, rather strange!
today I receive a new update from the beta of nvda.
I say yes to download it.
usual after the download the installer begins to ask me to install the update.
but not now.
I hear the error sound and nothing happens.
so the update can not be started to install.
what can that be?
are there other people who have the same problem with the newest beta update?
thanks in advance
paul otter








Re: problem with update

Adriani Botez
 

Hello,

sometimes it could be a server problem or an internet connection problem. You can try to download the last Beta version here:
https://www.nvaccess.org/files/nvda/snapshots/

You can navigate by headings (pressing h in browse mode) and download the last Beta which is 2018.4 Beta 4.

Best
Adriani

-----Ursprüngliche Nachricht-----
Von: nvda@nvda.groups.io <nvda@nvda.groups.io> Im Auftrag von P. Otter
Gesendet: Samstag, 8. Dezember 2018 09:45
An: nvda@nvda.groups.io
Betreff: [nvda] problem with update

hello all,
I've something, rather strange!
today I receive a new update from the beta of nvda.
I say yes to download it.
usual after the download the installer begins to ask me to install the update.
but not now.
I hear the error sound and nothing happens.
so the update can not be started to install.
what can that be?
are there other people who have the same problem with the newest beta update?
thanks in advance
paul otter


problem with update

P. Otter
 

hello all,
I've something, rather strange!
today I receive a new update from the beta of nvda.
I say yes to download it.
usual after the download the installer begins to ask me to install the update.
but not now.
I hear the error sound and nothing happens.
so the update can not be started to install.
what can that be?
are there other people who have the same problem with the newest beta update?
thanks in advance
paul otter


Re: Important notice: a note or two about future compatibilityof add-ons on community add-ons website and elsewhere

David Moore
 

Hi Joseph!

I just installed Alpha snapshot 16401, latest, and I had to check a lot of add-ons, because of the incompatible flags on most of my add-ons!

I hope all the add-ons can be made compatible with Python 3.

Thanks for your great explanation, Joseph!

 

                                                                                                                                                                                                                Sent from Mail for Windows 10

 

From: Tyler Spivey
Sent: Saturday, December 8, 2018 1:49 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Important notice: a note or two about future compatibilityof add-ons on community add-ons website and elsewhere

 

So far, the user experience for this is really bad. I had to manually

tweak 40+ addons three times during two updates.

I hope I don't have to deal with this every time I update my snapshot.

 

On 12/7/2018 10:45 PM, Devin Prater wrote:

> Thanks so much for all this information. I hope that the author of

> Braille Extender updates that add-on, as it is one of the most useful

> admins to me.

>

>> On Dec 7, 2018, at 11:50 PM, Joseph Lee <joseph.lee22590@...

>> <mailto:joseph.lee22590@...>> wrote:

>> 

>> Hi,

>> Yes, I and another NVDA developer wrote messages concerning this to

>> add-on authors.

>> By the way, one more thing: I’ll release patches for most of the

>> add-ons I’m maintaining (resource Monitor and StationPlaylist, for

>> instance) around Christmas to extend last tested NVDA version flag to

>> 2019.3. The only exception will be Unicode Braille Input, which is no

>> longer maintained by me.

>> Cheers,

>> Joseph

>>  

>> *From:* nvda@nvda.groups.io

>> <mailto:nvda@nvda.groups.io><nvda@nvda.groups.io

>> <mailto:nvda@nvda.groups.io>> *On Behalf Of *David Goldfield

>> *Sent:* Friday, December 7, 2018 9:44 PM

>> *To:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>

>> *Subject:* Re: [nvda] Important notice: a note or two about future

>> compatibility of add-ons on community add-ons website and elsewhere

>>  

>> 

>> Joseph,

>> 

>> Thank you for alerting us to this situation. I am somewhat concerned

>> as I do use some third-party add-ons not hosted on the community

>> add-ons page but which are well-known and legal. I'm wondering if the

>> developers of these add-ons have been informed about this change?

>> Specifically, I use the Code Factory Eloquence and Vocalizer add-on,

>> Acapela voices, Dictation Bridge and NVDA Remote. I also hope that

>> Clipspeak and Clip Contents Designer will be updated but I realize

>> these are not your apps.

>> 

>> Thank you again.

>> 

>>  

>> 

>> David Goldfield, Assistive Technology

>> Specialist WWW.David-Goldfield.Com <http://www.david-goldfield.com/>

>> On 12/8/2018 12:30 AM, Joseph Lee wrote:

>> 

>>     Dear NVDA community,

>>      

>>     This is Joseph Lee, one of the code contributors to NVDA screen

>>     reader project and a reviewer of community add-ons. I would like

>>     to take this time to update you on what’s been happening in

>>     regards to future compatibility of add-ons hosted on various

>>     websites, as well as rationale for compatibility notices you’re

>>     seeing from recent NVDA development releases (chiefly on alpha

>>     channel).

>>      

>>     As of December 6, 2018, NVDA 2019.1 alpha snapshots (build 16382

>>     onwards) will prompt you to check compatibility of various add-ons

>>     when you’re installing snapshots. This is because NVDA will now

>>     check if any of your add-ons are compatible with it by looking at

>>     two new manifest keys. These add-on manifest keys will tell NVDA

>>     if a given add-on is compatible with latest NVDA release, as well

>>     as providing a minimum compatible NVDA version if specified. After

>>     installing that alpha build and beyond, if NVDA detects one or

>>     more add-ons are not compatible, it will present a dialog at start

>>     up asking you to check which add-ons you still wish to use despite

>>     them being flagged as incompatible. This will be noticeable if you

>>     are using a third-party speech synthesizer or braille display by

>>     default and somehow these are not loading. Also, when trying to

>>     install new add-ons, if NVDA sees the add-on is incompatible,

>>     it’ll prompt a warning about it.

>>      

>>     Prior to this change, you can install add-ons on any NVDA release

>>     (including upcoming 2018.4), and it was up to add-ons to use

>>     features provided by a given NVDA release. This meant really old

>>     add-ons could be installed, and if not optimized for recent NVDA

>>     releases, the add-on would not work as intended, and in some

>>     cases, fail to run outright. Some add-ons do have specific NVDA

>>     version requirements, but not all add-ons take advantage of this

>>     recommendation.

>>      

>>     There are several reasons for the change as described above:

>>      

>> 

>>      1. Python 3 transition: as some of you (I think, at this point,

>>         more people) may know, NV Access and several developers

>>         (including I) are researching possible roadblocks to Python 3

>>         transition, and I’m maintaining an actual Python 3 version of

>>         NVDA for testing purposes. Given massive differences between

>>         Python 2 and 3, it was felt to place add-on compatibility

>>         checks in place so you won’t install add-ons written in Python

>>         2 on a Python 3 version of NVDA. This is one of the reasons

>>         for adding minimum NVDA version checks for add-ons if

>>         appropriate. As of today (December 8, 2018), at least three

>>         add-ons are Python 3 ready (thus will require newer NVDA

>>         versions in the future), and I expect that number to grow

>>         significantly in the next few months; the three compatible

>>         add-ons are Resource Monitor, SystrayList, and Windows 10 App

>>         Essentials, with StationPlaylist Studio to be added to this

>>         list in January 2019. 

>>      2. Various internal work planned for the future: these include

>>         projects such as speech refactor (changing internals behind

>>         NVDA’s speech functionality) and such that will cause some

>>         add-ons to fail to work as advertised. 

>> 

>>      

>>     The new compatibility flags are:

>>      

>> 

>>       * minimumNVDAVersion: specifies minimum version of NVDA the

>>         add-on is compatible with. 

>>       * lastTestedNVDAVersion: latest compatible NVDA version for the

>>         add-on. 

>> 

>>      

>>     These manifest keys are optional for now; in 2019, they will

>>     become mandatory for ALL add-ons. I would go so far as say that

>>     they are MANDATORY from now on, especially if you need to test

>>     your add-ons in alpha snapshots and intend to produce a Python 3

>>     version of your add-ons.

>>      

>>     As of December 8, 2018, only several add-ons hosted on community

>>     add-ons website (addons.nvda-project.org

>>     <http://addons.nvda-project.org/>) are truly future-proof

>>     (compatibility flags are present). The good news is that add-on

>>     authors do understand the impact this change will have on their

>>     add-ons and some have begun updating their add-ons to add

>>     compatibility flags; others plan to add changes once 2019.1 enters

>>     beta testing phase (based on past conversations), while the

>>     community lost contact with authors of some add-ons (some of which

>>     are popular) and their add-ons will be flagged as incompatible

>>     unless updates are released.

>>      

>>     The following add-ons are NVDA 2019.1 compatible and thus won’t

>>     cause NVDA to flag them as incompatible:

>>      

>> 

>>       * Add-on Updater 

>>       * Easy Table Navigator 

>>       * Enhanced Touch Gestures 

>>       * Focus Highlight 

>>       * Golden Cursor 

>>       * GoldWave 

>>       * ObjPad 

>>       * Object Location Tones 

>>       * Resource Monitor 

>>       * StationPlaylist Studio 

>>       * SystrayList 

>>       * Unicode Braille Input 

>>       * Virtual Review 

>>       * Windows 10 App Essentials 

>>       * And possibly more. 

>> 

>>      

>>     For add-ons not listed:

>>      

>> 

>>       * For users: please contact authors of add-ons you’re using and

>>         ask for their thoughts and plans for add-on compatibility

>>         flags and other future work (see below for words about my

>>         add-ons). 

>>       * For developers: please think about the impact of this change

>>         and update your add-ons. I don’t expect all add-ons to be made

>>         compatible by the time 2019.1 stable version (or release

>>         candidate) is released, but at least for popular ones, please

>>         have your add-ons made compatible by the time 2019.1 beta 1

>>         shows up. Also, I advise setting last tested version to 2019.2

>>         so you can have plenty of time modernizing add-ons. 

>> 

>>      

>>     Notes for users of my add-ons or add-ons that’ll be reviewed by me:

>>      

>> 

>>       * For users: I expect all my add-ons (at least ones currently

>>         under active support) to be made Python 3 ready no later than

>>         March 2019. As far as last tested version flag is concerned,

>>         I’ll try my best to target later NVDA releases (for example,

>>         if using an add-on in NVDA 2019.1, the compatibility flag will

>>         indicate support for at least NvDA 2019.3) so you won’t have

>>         to worry about compatibility flag problems for a long time;

>>         compatibility flags (at least last tested version flag) will

>>         be updated once or twice a year. 

>>       * For add-ons to be reviewed: I will look for compatibility

>>         flags (as part of user experience portion of basic review)

>>         starting from February 2019; other add-on reviewers may or may

>>         not look for these flags. 

>>       * For Add-on Updater users: I will start enforcing add-on

>>         compatibility flags from version 19.03; that is, Add-on

>>         Updater will refuse to install add-on updates if they do not

>>         specify at least last tested version flag to align with NVDA

>>         2019.1 behavior. 

>> 

>>      

>>     Thank you.

>>     Cheers,

>>     Joseph

>> 

>

>

 

 

 

 


Re: Important notice: a note or two about future compatibility of add-ons on community add-ons website and elsewhere

Tyler Spivey
 

So far, the user experience for this is really bad. I had to manually
tweak 40+ addons three times during two updates.
I hope I don't have to deal with this every time I update my snapshot.

On 12/7/2018 10:45 PM, Devin Prater wrote:
Thanks so much for all this information. I hope that the author of
Braille Extender updates that add-on, as it is one of the most useful
admins to me.

On Dec 7, 2018, at 11:50 PM, Joseph Lee <joseph.lee22590@gmail.com
<mailto:joseph.lee22590@gmail.com>> wrote:

Hi,
Yes, I and another NVDA developer wrote messages concerning this to
add-on authors.
By the way, one more thing: I’ll release patches for most of the
add-ons I’m maintaining (resource Monitor and StationPlaylist, for
instance) around Christmas to extend last tested NVDA version flag to
2019.3. The only exception will be Unicode Braille Input, which is no
longer maintained by me.
Cheers,
Joseph
 
*From:* nvda@nvda.groups.io
<mailto:nvda@nvda.groups.io><nvda@nvda.groups.io
<mailto:nvda@nvda.groups.io>> *On Behalf Of *David Goldfield
*Sent:* Friday, December 7, 2018 9:44 PM
*To:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
*Subject:* Re: [nvda] Important notice: a note or two about future
compatibility of add-ons on community add-ons website and elsewhere
 

Joseph,

Thank you for alerting us to this situation. I am somewhat concerned
as I do use some third-party add-ons not hosted on the community
add-ons page but which are well-known and legal. I'm wondering if the
developers of these add-ons have been informed about this change?
Specifically, I use the Code Factory Eloquence and Vocalizer add-on,
Acapela voices, Dictation Bridge and NVDA Remote. I also hope that
Clipspeak and Clip Contents Designer will be updated but I realize
these are not your apps.

Thank you again.

 

David Goldfield, Assistive Technology
Specialist WWW.David-Goldfield.Com <http://www.david-goldfield.com/>
On 12/8/2018 12:30 AM, Joseph Lee wrote:

Dear NVDA community,
 
This is Joseph Lee, one of the code contributors to NVDA screen
reader project and a reviewer of community add-ons. I would like
to take this time to update you on what’s been happening in
regards to future compatibility of add-ons hosted on various
websites, as well as rationale for compatibility notices you’re
seeing from recent NVDA development releases (chiefly on alpha
channel).
 
As of December 6, 2018, NVDA 2019.1 alpha snapshots (build 16382
onwards) will prompt you to check compatibility of various add-ons
when you’re installing snapshots. This is because NVDA will now
check if any of your add-ons are compatible with it by looking at
two new manifest keys. These add-on manifest keys will tell NVDA
if a given add-on is compatible with latest NVDA release, as well
as providing a minimum compatible NVDA version if specified. After
installing that alpha build and beyond, if NVDA detects one or
more add-ons are not compatible, it will present a dialog at start
up asking you to check which add-ons you still wish to use despite
them being flagged as incompatible. This will be noticeable if you
are using a third-party speech synthesizer or braille display by
default and somehow these are not loading. Also, when trying to
install new add-ons, if NVDA sees the add-on is incompatible,
it’ll prompt a warning about it.
 
Prior to this change, you can install add-ons on any NVDA release
(including upcoming 2018.4), and it was up to add-ons to use
features provided by a given NVDA release. This meant really old
add-ons could be installed, and if not optimized for recent NVDA
releases, the add-on would not work as intended, and in some
cases, fail to run outright. Some add-ons do have specific NVDA
version requirements, but not all add-ons take advantage of this
recommendation.
 
There are several reasons for the change as described above:
 

1. Python 3 transition: as some of you (I think, at this point,
more people) may know, NV Access and several developers
(including I) are researching possible roadblocks to Python 3
transition, and I’m maintaining an actual Python 3 version of
NVDA for testing purposes. Given massive differences between
Python 2 and 3, it was felt to place add-on compatibility
checks in place so you won’t install add-ons written in Python
2 on a Python 3 version of NVDA. This is one of the reasons
for adding minimum NVDA version checks for add-ons if
appropriate. As of today (December 8, 2018), at least three
add-ons are Python 3 ready (thus will require newer NVDA
versions in the future), and I expect that number to grow
significantly in the next few months; the three compatible
add-ons are Resource Monitor, SystrayList, and Windows 10 App
Essentials, with StationPlaylist Studio to be added to this
list in January 2019. 
2. Various internal work planned for the future: these include
projects such as speech refactor (changing internals behind
NVDA’s speech functionality) and such that will cause some
add-ons to fail to work as advertised. 

 
The new compatibility flags are:
 

* minimumNVDAVersion: specifies minimum version of NVDA the
add-on is compatible with. 
* lastTestedNVDAVersion: latest compatible NVDA version for the
add-on. 

 
These manifest keys are optional for now; in 2019, they will
become mandatory for ALL add-ons. I would go so far as say that
they are MANDATORY from now on, especially if you need to test
your add-ons in alpha snapshots and intend to produce a Python 3
version of your add-ons.
 
As of December 8, 2018, only several add-ons hosted on community
add-ons website (addons.nvda-project.org
<http://addons.nvda-project.org/>) are truly future-proof
(compatibility flags are present). The good news is that add-on
authors do understand the impact this change will have on their
add-ons and some have begun updating their add-ons to add
compatibility flags; others plan to add changes once 2019.1 enters
beta testing phase (based on past conversations), while the
community lost contact with authors of some add-ons (some of which
are popular) and their add-ons will be flagged as incompatible
unless updates are released.
 
The following add-ons are NVDA 2019.1 compatible and thus won’t
cause NVDA to flag them as incompatible:
 

* Add-on Updater 
* Easy Table Navigator 
* Enhanced Touch Gestures 
* Focus Highlight 
* Golden Cursor 
* GoldWave 
* ObjPad 
* Object Location Tones 
* Resource Monitor 
* StationPlaylist Studio 
* SystrayList 
* Unicode Braille Input 
* Virtual Review 
* Windows 10 App Essentials 
* And possibly more. 

 
For add-ons not listed:
 

* For users: please contact authors of add-ons you’re using and
ask for their thoughts and plans for add-on compatibility
flags and other future work (see below for words about my
add-ons). 
* For developers: please think about the impact of this change
and update your add-ons. I don’t expect all add-ons to be made
compatible by the time 2019.1 stable version (or release
candidate) is released, but at least for popular ones, please
have your add-ons made compatible by the time 2019.1 beta 1
shows up. Also, I advise setting last tested version to 2019.2
so you can have plenty of time modernizing add-ons. 

 
Notes for users of my add-ons or add-ons that’ll be reviewed by me:
 

* For users: I expect all my add-ons (at least ones currently
under active support) to be made Python 3 ready no later than
March 2019. As far as last tested version flag is concerned,
I’ll try my best to target later NVDA releases (for example,
if using an add-on in NVDA 2019.1, the compatibility flag will
indicate support for at least NvDA 2019.3) so you won’t have
to worry about compatibility flag problems for a long time;
compatibility flags (at least last tested version flag) will
be updated once or twice a year. 
* For add-ons to be reviewed: I will look for compatibility
flags (as part of user experience portion of basic review)
starting from February 2019; other add-on reviewers may or may
not look for these flags. 
* For Add-on Updater users: I will start enforcing add-on
compatibility flags from version 19.03; that is, Add-on
Updater will refuse to install add-on updates if they do not
specify at least last tested version flag to align with NVDA
2019.1 behavior. 

 
Thank you.
Cheers,
Joseph


Re: Important notice: a note or two about future compatibility of add-ons on community add-ons website and elsewhere

Devin Prater
 

Thanks so much for all this information. I hope that the author of Braille Extender updates that add-on, as it is one of the most useful admins to me.

On Dec 7, 2018, at 11:50 PM, Joseph Lee <joseph.lee22590@...> wrote:

Hi,
Yes, I and another NVDA developer wrote messages concerning this to add-on authors.
By the way, one more thing: I’ll release patches for most of the add-ons I’m maintaining (resource Monitor and StationPlaylist, for instance) around Christmas to extend last tested NVDA version flag to 2019.3. The only exception will be Unicode Braille Input, which is no longer maintained by me.
Cheers,
Joseph
 
From: nvda@nvda.groups.io<nvda@nvda.groups.io> On Behalf Of David Goldfield
Sent: Friday, December 7, 2018 9:44 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Important notice: a note or two about future compatibility of add-ons on community add-ons website and elsewhere
 

Joseph,

Thank you for alerting us to this situation. I am somewhat concerned as I do use some third-party add-ons not hosted on the community add-ons page but which are well-known and legal. I'm wondering if the developers of these add-ons have been informed about this change? Specifically, I use the Code Factory Eloquence and Vocalizer add-on, Acapela voices, Dictation Bridge and NVDA Remote. I also hope that Clipspeak and Clip Contents Designer will be updated but I realize these are not your apps.

Thank you again.

 

David Goldfield, Assistive Technology Specialist WWW.David-Goldfield.Com
On 12/8/2018 12:30 AM, Joseph Lee wrote:
Dear NVDA community,
 
This is Joseph Lee, one of the code contributors to NVDA screen reader project and a reviewer of community add-ons. I would like to take this time to update you on what’s been happening in regards to future compatibility of add-ons hosted on various websites, as well as rationale for compatibility notices you’re seeing from recent NVDA development releases (chiefly on alpha channel).
 
As of December 6, 2018, NVDA 2019.1 alpha snapshots (build 16382 onwards) will prompt you to check compatibility of various add-ons when you’re installing snapshots. This is because NVDA will now check if any of your add-ons are compatible with it by looking at two new manifest keys. These add-on manifest keys will tell NVDA if a given add-on is compatible with latest NVDA release, as well as providing a minimum compatible NVDA version if specified. After installing that alpha build and beyond, if NVDA detects one or more add-ons are not compatible, it will present a dialog at start up asking you to check which add-ons you still wish to use despite them being flagged as incompatible. This will be noticeable if you are using a third-party speech synthesizer or braille display by default and somehow these are not loading. Also, when trying to install new add-ons, if NVDA sees the add-on is incompatible, it’ll prompt a warning about it.
 
Prior to this change, you can install add-ons on any NVDA release (including upcoming 2018.4), and it was up to add-ons to use features provided by a given NVDA release. This meant really old add-ons could be installed, and if not optimized for recent NVDA releases, the add-on would not work as intended, and in some cases, fail to run outright. Some add-ons do have specific NVDA version requirements, but not all add-ons take advantage of this recommendation.
 
There are several reasons for the change as described above:
 
  1. Python 3 transition: as some of you (I think, at this point, more people) may know, NV Access and several developers (including I) are researching possible roadblocks to Python 3 transition, and I’m maintaining an actual Python 3 version of NVDA for testing purposes. Given massive differences between Python 2 and 3, it was felt to place add-on compatibility checks in place so you won’t install add-ons written in Python 2 on a Python 3 version of NVDA. This is one of the reasons for adding minimum NVDA version checks for add-ons if appropriate. As of today (December 8, 2018), at least three add-ons are Python 3 ready (thus will require newer NVDA versions in the future), and I expect that number to grow significantly in the next few months; the three compatible add-ons are Resource Monitor, SystrayList, and Windows 10 App Essentials, with StationPlaylist Studio to be added to this list in January 2019. 
  2. Various internal work planned for the future: these include projects such as speech refactor (changing internals behind NVDA’s speech functionality) and such that will cause some add-ons to fail to work as advertised. 
 
The new compatibility flags are:
 
  • minimumNVDAVersion: specifies minimum version of NVDA the add-on is compatible with. 
  • lastTestedNVDAVersion: latest compatible NVDA version for the add-on. 
 
These manifest keys are optional for now; in 2019, they will become mandatory for ALL add-ons. I would go so far as say that they are MANDATORY from now on, especially if you need to test your add-ons in alpha snapshots and intend to produce a Python 3 version of your add-ons.
 
As of December 8, 2018, only several add-ons hosted on community add-ons website (addons.nvda-project.org) are truly future-proof (compatibility flags are present). The good news is that add-on authors do understand the impact this change will have on their add-ons and some have begun updating their add-ons to add compatibility flags; others plan to add changes once 2019.1 enters beta testing phase (based on past conversations), while the community lost contact with authors of some add-ons (some of which are popular) and their add-ons will be flagged as incompatible unless updates are released.
 
The following add-ons are NVDA 2019.1 compatible and thus won’t cause NVDA to flag them as incompatible:
 
  • Add-on Updater 
  • Easy Table Navigator 
  • Enhanced Touch Gestures 
  • Focus Highlight 
  • Golden Cursor 
  • GoldWave 
  • ObjPad 
  • Object Location Tones 
  • Resource Monitor 
  • StationPlaylist Studio 
  • SystrayList 
  • Unicode Braille Input 
  • Virtual Review 
  • Windows 10 App Essentials 
  • And possibly more. 
 
For add-ons not listed:
 
  • For users: please contact authors of add-ons you’re using and ask for their thoughts and plans for add-on compatibility flags and other future work (see below for words about my add-ons). 
  • For developers: please think about the impact of this change and update your add-ons. I don’t expect all add-ons to be made compatible by the time 2019.1 stable version (or release candidate) is released, but at least for popular ones, please have your add-ons made compatible by the time 2019.1 beta 1 shows up. Also, I advise setting last tested version to 2019.2 so you can have plenty of time modernizing add-ons. 
 
Notes for users of my add-ons or add-ons that’ll be reviewed by me:
 
  • For users: I expect all my add-ons (at least ones currently under active support) to be made Python 3 ready no later than March 2019. As far as last tested version flag is concerned, I’ll try my best to target later NVDA releases (for example, if using an add-on in NVDA 2019.1, the compatibility flag will indicate support for at least NvDA 2019.3) so you won’t have to worry about compatibility flag problems for a long time; compatibility flags (at least last tested version flag) will be updated once or twice a year. 
  • For add-ons to be reviewed: I will look for compatibility flags (as part of user experience portion of basic review) starting from February 2019; other add-on reviewers may or may not look for these flags. 
  • For Add-on Updater users: I will start enforcing add-on compatibility flags from version 19.03; that is, Add-on Updater will refuse to install add-on updates if they do not specify at least last tested version flag to align with NVDA 2019.1 behavior. 
 
Thank you.
Cheers,
Joseph



Re: Important notice: a note or two about future compatibility of add-ons on community add-ons website and elsewhere

 

Hi,

Yes, I and another NVDA developer wrote messages concerning this to add-on authors.

By the way, one more thing: I’ll release patches for most of the add-ons I’m maintaining (resource Monitor and StationPlaylist, for instance) around Christmas to extend last tested NVDA version flag to 2019.3. The only exception will be Unicode Braille Input, which is no longer maintained by me.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of David Goldfield
Sent: Friday, December 7, 2018 9:44 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Important notice: a note or two about future compatibility of add-ons on community add-ons website and elsewhere

 

Joseph,

Thank you for alerting us to this situation. I am somewhat concerned as I do use some third-party add-ons not hosted on the community add-ons page but which are well-known and legal. I'm wondering if the developers of these add-ons have been informed about this change? Specifically, I use the Code Factory Eloquence and Vocalizer add-on, Acapela voices, Dictation Bridge and NVDA Remote. I also hope that Clipspeak and Clip Contents Designer will be updated but I realize these are not your apps.

Thank you again.

 

David Goldfield, Assistive Technology Specialist WWW.David-Goldfield.Com

On 12/8/2018 12:30 AM, Joseph Lee wrote:

Dear NVDA community,

 

This is Joseph Lee, one of the code contributors to NVDA screen reader project and a reviewer of community add-ons. I would like to take this time to update you on what’s been happening in regards to future compatibility of add-ons hosted on various websites, as well as rationale for compatibility notices you’re seeing from recent NVDA development releases (chiefly on alpha channel).

 

As of December 6, 2018, NVDA 2019.1 alpha snapshots (build 16382 onwards) will prompt you to check compatibility of various add-ons when you’re installing snapshots. This is because NVDA will now check if any of your add-ons are compatible with it by looking at two new manifest keys. These add-on manifest keys will tell NVDA if a given add-on is compatible with latest NVDA release, as well as providing a minimum compatible NVDA version if specified. After installing that alpha build and beyond, if NVDA detects one or more add-ons are not compatible, it will present a dialog at start up asking you to check which add-ons you still wish to use despite them being flagged as incompatible. This will be noticeable if you are using a third-party speech synthesizer or braille display by default and somehow these are not loading. Also, when trying to install new add-ons, if NVDA sees the add-on is incompatible, it’ll prompt a warning about it.

 

Prior to this change, you can install add-ons on any NVDA release (including upcoming 2018.4), and it was up to add-ons to use features provided by a given NVDA release. This meant really old add-ons could be installed, and if not optimized for recent NVDA releases, the add-on would not work as intended, and in some cases, fail to run outright. Some add-ons do have specific NVDA version requirements, but not all add-ons take advantage of this recommendation.

 

There are several reasons for the change as described above:

 

  1. Python 3 transition: as some of you (I think, at this point, more people) may know, NV Access and several developers (including I) are researching possible roadblocks to Python 3 transition, and I’m maintaining an actual Python 3 version of NVDA for testing purposes. Given massive differences between Python 2 and 3, it was felt to place add-on compatibility checks in place so you won’t install add-ons written in Python 2 on a Python 3 version of NVDA. This is one of the reasons for adding minimum NVDA version checks for add-ons if appropriate. As of today (December 8, 2018), at least three add-ons are Python 3 ready (thus will require newer NVDA versions in the future), and I expect that number to grow significantly in the next few months; the three compatible add-ons are Resource Monitor, SystrayList, and Windows 10 App Essentials, with StationPlaylist Studio to be added to this list in January 2019.
  2. Various internal work planned for the future: these include projects such as speech refactor (changing internals behind NVDA’s speech functionality) and such that will cause some add-ons to fail to work as advertised.

 

The new compatibility flags are:

 

  • minimumNVDAVersion: specifies minimum version of NVDA the add-on is compatible with.
  • lastTestedNVDAVersion: latest compatible NVDA version for the add-on.

 

These manifest keys are optional for now; in 2019, they will become mandatory for ALL add-ons. I would go so far as say that they are MANDATORY from now on, especially if you need to test your add-ons in alpha snapshots and intend to produce a Python 3 version of your add-ons.

 

As of December 8, 2018, only several add-ons hosted on community add-ons website (addons.nvda-project.org) are truly future-proof (compatibility flags are present). The good news is that add-on authors do understand the impact this change will have on their add-ons and some have begun updating their add-ons to add compatibility flags; others plan to add changes once 2019.1 enters beta testing phase (based on past conversations), while the community lost contact with authors of some add-ons (some of which are popular) and their add-ons will be flagged as incompatible unless updates are released.

 

The following add-ons are NVDA 2019.1 compatible and thus won’t cause NVDA to flag them as incompatible:

 

  • Add-on Updater
  • Easy Table Navigator
  • Enhanced Touch Gestures
  • Focus Highlight
  • Golden Cursor
  • GoldWave
  • ObjPad
  • Object Location Tones
  • Resource Monitor
  • StationPlaylist Studio
  • SystrayList
  • Unicode Braille Input
  • Virtual Review
  • Windows 10 App Essentials
  • And possibly more.

 

For add-ons not listed:

 

  • For users: please contact authors of add-ons you’re using and ask for their thoughts and plans for add-on compatibility flags and other future work (see below for words about my add-ons).
  • For developers: please think about the impact of this change and update your add-ons. I don’t expect all add-ons to be made compatible by the time 2019.1 stable version (or release candidate) is released, but at least for popular ones, please have your add-ons made compatible by the time 2019.1 beta 1 shows up. Also, I advise setting last tested version to 2019.2 so you can have plenty of time modernizing add-ons.

 

Notes for users of my add-ons or add-ons that’ll be reviewed by me:

 

  • For users: I expect all my add-ons (at least ones currently under active support) to be made Python 3 ready no later than March 2019. As far as last tested version flag is concerned, I’ll try my best to target later NVDA releases (for example, if using an add-on in NVDA 2019.1, the compatibility flag will indicate support for at least NvDA 2019.3) so you won’t have to worry about compatibility flag problems for a long time; compatibility flags (at least last tested version flag) will be updated once or twice a year.
  • For add-ons to be reviewed: I will look for compatibility flags (as part of user experience portion of basic review) starting from February 2019; other add-on reviewers may or may not look for these flags.
  • For Add-on Updater users: I will start enforcing add-on compatibility flags from version 19.03; that is, Add-on Updater will refuse to install add-on updates if they do not specify at least last tested version flag to align with NVDA 2019.1 behavior.

 

Thank you.

Cheers,

Joseph


Re: Important notice: a note or two about future compatibility of add-ons on community add-ons website and elsewhere

David Goldfield
 

Joseph,

Thank you for alerting us to this situation. I am somewhat concerned as I do use some third-party add-ons not hosted on the community add-ons page but which are well-known and legal. I'm wondering if the developers of these add-ons have been informed about this change? Specifically, I use the Code Factory Eloquence and Vocalizer add-on, Acapela voices, Dictation Bridge and NVDA Remote. I also hope that Clipspeak and Clip Contents Designer will be updated but I realize these are not your apps.

Thank you again.


David Goldfield, Assistive Technology Specialist WWW.David-Goldfield.Com

On 12/8/2018 12:30 AM, Joseph Lee wrote:

Dear NVDA community,

 

This is Joseph Lee, one of the code contributors to NVDA screen reader project and a reviewer of community add-ons. I would like to take this time to update you on what’s been happening in regards to future compatibility of add-ons hosted on various websites, as well as rationale for compatibility notices you’re seeing from recent NVDA development releases (chiefly on alpha channel).

 

As of December 6, 2018, NVDA 2019.1 alpha snapshots (build 16382 onwards) will prompt you to check compatibility of various add-ons when you’re installing snapshots. This is because NVDA will now check if any of your add-ons are compatible with it by looking at two new manifest keys. These add-on manifest keys will tell NVDA if a given add-on is compatible with latest NVDA release, as well as providing a minimum compatible NVDA version if specified. After installing that alpha build and beyond, if NVDA detects one or more add-ons are not compatible, it will present a dialog at start up asking you to check which add-ons you still wish to use despite them being flagged as incompatible. This will be noticeable if you are using a third-party speech synthesizer or braille display by default and somehow these are not loading. Also, when trying to install new add-ons, if NVDA sees the add-on is incompatible, it’ll prompt a warning about it.

 

Prior to this change, you can install add-ons on any NVDA release (including upcoming 2018.4), and it was up to add-ons to use features provided by a given NVDA release. This meant really old add-ons could be installed, and if not optimized for recent NVDA releases, the add-on would not work as intended, and in some cases, fail to run outright. Some add-ons do have specific NVDA version requirements, but not all add-ons take advantage of this recommendation.

 

There are several reasons for the change as described above:

 

  1. Python 3 transition: as some of you (I think, at this point, more people) may know, NV Access and several developers (including I) are researching possible roadblocks to Python 3 transition, and I’m maintaining an actual Python 3 version of NVDA for testing purposes. Given massive differences between Python 2 and 3, it was felt to place add-on compatibility checks in place so you won’t install add-ons written in Python 2 on a Python 3 version of NVDA. This is one of the reasons for adding minimum NVDA version checks for add-ons if appropriate. As of today (December 8, 2018), at least three add-ons are Python 3 ready (thus will require newer NVDA versions in the future), and I expect that number to grow significantly in the next few months; the three compatible add-ons are Resource Monitor, SystrayList, and Windows 10 App Essentials, with StationPlaylist Studio to be added to this list in January 2019.
  2. Various internal work planned for the future: these include projects such as speech refactor (changing internals behind NVDA’s speech functionality) and such that will cause some add-ons to fail to work as advertised.

 

The new compatibility flags are:

 

  • minimumNVDAVersion: specifies minimum version of NVDA the add-on is compatible with.
  • lastTestedNVDAVersion: latest compatible NVDA version for the add-on.

 

These manifest keys are optional for now; in 2019, they will become mandatory for ALL add-ons. I would go so far as say that they are MANDATORY from now on, especially if you need to test your add-ons in alpha snapshots and intend to produce a Python 3 version of your add-ons.

 

As of December 8, 2018, only several add-ons hosted on community add-ons website (addons.nvda-project.org) are truly future-proof (compatibility flags are present). The good news is that add-on authors do understand the impact this change will have on their add-ons and some have begun updating their add-ons to add compatibility flags; others plan to add changes once 2019.1 enters beta testing phase (based on past conversations), while the community lost contact with authors of some add-ons (some of which are popular) and their add-ons will be flagged as incompatible unless updates are released.

 

The following add-ons are NVDA 2019.1 compatible and thus won’t cause NVDA to flag them as incompatible:

 

  • Add-on Updater
  • Easy Table Navigator
  • Enhanced Touch Gestures
  • Focus Highlight
  • Golden Cursor
  • GoldWave
  • ObjPad
  • Object Location Tones
  • Resource Monitor
  • StationPlaylist Studio
  • SystrayList
  • Unicode Braille Input
  • Virtual Review
  • Windows 10 App Essentials
  • And possibly more.

 

For add-ons not listed:

 

  • For users: please contact authors of add-ons you’re using and ask for their thoughts and plans for add-on compatibility flags and other future work (see below for words about my add-ons).
  • For developers: please think about the impact of this change and update your add-ons. I don’t expect all add-ons to be made compatible by the time 2019.1 stable version (or release candidate) is released, but at least for popular ones, please have your add-ons made compatible by the time 2019.1 beta 1 shows up. Also, I advise setting last tested version to 2019.2 so you can have plenty of time modernizing add-ons.

 

Notes for users of my add-ons or add-ons that’ll be reviewed by me:

 

  • For users: I expect all my add-ons (at least ones currently under active support) to be made Python 3 ready no later than March 2019. As far as last tested version flag is concerned, I’ll try my best to target later NVDA releases (for example, if using an add-on in NVDA 2019.1, the compatibility flag will indicate support for at least NvDA 2019.3) so you won’t have to worry about compatibility flag problems for a long time; compatibility flags (at least last tested version flag) will be updated once or twice a year.
  • For add-ons to be reviewed: I will look for compatibility flags (as part of user experience portion of basic review) starting from February 2019; other add-on reviewers may or may not look for these flags.
  • For Add-on Updater users: I will start enforcing add-on compatibility flags from version 19.03; that is, Add-on Updater will refuse to install add-on updates if they do not specify at least last tested version flag to align with NVDA 2019.1 behavior.

 

Thank you.

Cheers,

Joseph


Important notice: a note or two about future compatibility of add-ons on community add-ons website and elsewhere

 

Dear NVDA community,

 

This is Joseph Lee, one of the code contributors to NVDA screen reader project and a reviewer of community add-ons. I would like to take this time to update you on what’s been happening in regards to future compatibility of add-ons hosted on various websites, as well as rationale for compatibility notices you’re seeing from recent NVDA development releases (chiefly on alpha channel).

 

As of December 6, 2018, NVDA 2019.1 alpha snapshots (build 16382 onwards) will prompt you to check compatibility of various add-ons when you’re installing snapshots. This is because NVDA will now check if any of your add-ons are compatible with it by looking at two new manifest keys. These add-on manifest keys will tell NVDA if a given add-on is compatible with latest NVDA release, as well as providing a minimum compatible NVDA version if specified. After installing that alpha build and beyond, if NVDA detects one or more add-ons are not compatible, it will present a dialog at start up asking you to check which add-ons you still wish to use despite them being flagged as incompatible. This will be noticeable if you are using a third-party speech synthesizer or braille display by default and somehow these are not loading. Also, when trying to install new add-ons, if NVDA sees the add-on is incompatible, it’ll prompt a warning about it.

 

Prior to this change, you can install add-ons on any NVDA release (including upcoming 2018.4), and it was up to add-ons to use features provided by a given NVDA release. This meant really old add-ons could be installed, and if not optimized for recent NVDA releases, the add-on would not work as intended, and in some cases, fail to run outright. Some add-ons do have specific NVDA version requirements, but not all add-ons take advantage of this recommendation.

 

There are several reasons for the change as described above:

 

  1. Python 3 transition: as some of you (I think, at this point, more people) may know, NV Access and several developers (including I) are researching possible roadblocks to Python 3 transition, and I’m maintaining an actual Python 3 version of NVDA for testing purposes. Given massive differences between Python 2 and 3, it was felt to place add-on compatibility checks in place so you won’t install add-ons written in Python 2 on a Python 3 version of NVDA. This is one of the reasons for adding minimum NVDA version checks for add-ons if appropriate. As of today (December 8, 2018), at least three add-ons are Python 3 ready (thus will require newer NVDA versions in the future), and I expect that number to grow significantly in the next few months; the three compatible add-ons are Resource Monitor, SystrayList, and Windows 10 App Essentials, with StationPlaylist Studio to be added to this list in January 2019.
  2. Various internal work planned for the future: these include projects such as speech refactor (changing internals behind NVDA’s speech functionality) and such that will cause some add-ons to fail to work as advertised.

 

The new compatibility flags are:

 

  • minimumNVDAVersion: specifies minimum version of NVDA the add-on is compatible with.
  • lastTestedNVDAVersion: latest compatible NVDA version for the add-on.

 

These manifest keys are optional for now; in 2019, they will become mandatory for ALL add-ons. I would go so far as say that they are MANDATORY from now on, especially if you need to test your add-ons in alpha snapshots and intend to produce a Python 3 version of your add-ons.

 

As of December 8, 2018, only several add-ons hosted on community add-ons website (addons.nvda-project.org) are truly future-proof (compatibility flags are present). The good news is that add-on authors do understand the impact this change will have on their add-ons and some have begun updating their add-ons to add compatibility flags; others plan to add changes once 2019.1 enters beta testing phase (based on past conversations), while the community lost contact with authors of some add-ons (some of which are popular) and their add-ons will be flagged as incompatible unless updates are released.

 

The following add-ons are NVDA 2019.1 compatible and thus won’t cause NVDA to flag them as incompatible:

 

  • Add-on Updater
  • Easy Table Navigator
  • Enhanced Touch Gestures
  • Focus Highlight
  • Golden Cursor
  • GoldWave
  • ObjPad
  • Object Location Tones
  • Resource Monitor
  • StationPlaylist Studio
  • SystrayList
  • Unicode Braille Input
  • Virtual Review
  • Windows 10 App Essentials
  • And possibly more.

 

For add-ons not listed:

 

  • For users: please contact authors of add-ons you’re using and ask for their thoughts and plans for add-on compatibility flags and other future work (see below for words about my add-ons).
  • For developers: please think about the impact of this change and update your add-ons. I don’t expect all add-ons to be made compatible by the time 2019.1 stable version (or release candidate) is released, but at least for popular ones, please have your add-ons made compatible by the time 2019.1 beta 1 shows up. Also, I advise setting last tested version to 2019.2 so you can have plenty of time modernizing add-ons.

 

Notes for users of my add-ons or add-ons that’ll be reviewed by me:

 

  • For users: I expect all my add-ons (at least ones currently under active support) to be made Python 3 ready no later than March 2019. As far as last tested version flag is concerned, I’ll try my best to target later NVDA releases (for example, if using an add-on in NVDA 2019.1, the compatibility flag will indicate support for at least NvDA 2019.3) so you won’t have to worry about compatibility flag problems for a long time; compatibility flags (at least last tested version flag) will be updated once or twice a year.
  • For add-ons to be reviewed: I will look for compatibility flags (as part of user experience portion of basic review) starting from February 2019; other add-on reviewers may or may not look for these flags.
  • For Add-on Updater users: I will start enforcing add-on compatibility flags from version 19.03; that is, Add-on Updater will refuse to install add-on updates if they do not specify at least last tested version flag to align with NVDA 2019.1 behavior.

 

Thank you.

Cheers,

Joseph


Bug report and mouse

farhan israk
 

I use nvda 2018.3.2. how to send bug report to nbda developer along with log? I'm not getting log in temp folder. Where will I get it? How to use mouse with nvda?


Re: EM Client mail client

Rosemarie Chavarria
 

I haven't heard of it.

 

 

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Quentin Christensen
Sent: Friday, December 7, 2018 2:02 PM
To: nvda@nvda.groups.io
Subject: [nvda] EM Client mail client

 

Hi everyone,

 

I had an inquiry about using the EM Client - http://www.emclient.com/

 

Has anyone used this mail client and if so, is it accessible, and are there any tips for using it or setting it up etc?

 

Quentin.

 

--

Quentin Christensen
Training and Support Manager

 

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

 

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


Re: a problem focusing the mouse cursor on items

Gene
 

Are you in object review mode or screen review mode.  I have said before that object review mode should be automatically returned to when the window you are using a different mode in is left.  A lot of people have no idea that you need to be in object navigation mode for a lot of commands to work properly.  Unfortunately, my idea has not been implemented.  We'll see if your problem is another illustration of why it should be.
 
Also, have you changed the default setting that causes the object navigator to follow the cursor?  That could be the problem, too.  You are routing the mouse to the object navigator, not to the application cursor nor the browse mode virtual cursor. 
Gene

----- Original Message -----
From: Dan Beaver
Sent: Friday, December 07, 2018 4:30 PM
Subject: [nvda] a problem focusing the mouse cursor on items

Hi,


I have recently noticed that using the nvda+shift+m combo isn't working correctly.  If I do this on a webpage to click on an item that normally would be identified as a link it doesn't allow me to click on it.


If I do this and then issue nvda+[ to do a mouse click it tries to activate something on the desktop instead.  It seems like the mouse focus isn't being placed on the item that I was looking at in browse mode.


Any ideas on this one?


I am running the latest stable NVDA and Windows 10 home. I am having trouble figuring out

how to find the exact version of Windows 10 home though.  I found this using the Chrome browser.


Thanks.



--

Dan Beaver (KC4DOY)


Re: a problem focusing the mouse cursor on items

Adriani Botez
 

Hi,

 

which browser are you using? In Firefox an Crome this will work much better in NVDA 2018.4.

 

Best

Adriani

 

 

 

Von: nvda@nvda.groups.io <nvda@nvda.groups.io> Im Auftrag von Dan Beaver
Gesendet: Freitag, 7. Dezember 2018 23:31
An: nvda@nvda.groups.io
Betreff: [nvda] a problem focusing the mouse cursor on items

 

Hi,

 

I have recently noticed that using the nvda+shift+m combo isn't working correctly.  If I do this on a webpage to click on an item that normally would be identified as a link it doesn't allow me to click on it.

 

If I do this and then issue nvda+[ to do a mouse click it tries to activate something on the desktop instead.  It seems like the mouse focus isn't being placed on the item that I was looking at in browse mode.

 

Any ideas on this one?

 

I am running the latest stable NVDA and Windows 10 home. I am having trouble figuring out

how to find the exact version of Windows 10 home though.  I found this using the Chrome browser.

 

Thanks.

 

 

--

Dan Beaver (KC4DOY)


a problem focusing the mouse cursor on items

Dan Beaver
 

Hi,


I have recently noticed that using the nvda+shift+m combo isn't working correctly.  If I do this on a webpage to click on an item that normally would be identified as a link it doesn't allow me to click on it.


If I do this and then issue nvda+[ to do a mouse click it tries to activate something on the desktop instead.  It seems like the mouse focus isn't being placed on the item that I was looking at in browse mode.


Any ideas on this one?


I am running the latest stable NVDA and Windows 10 home. I am having trouble figuring out

how to find the exact version of Windows 10 home though.  I found this using the Chrome browser.


Thanks.



--

Dan Beaver (KC4DOY)


EM Client mail client

Quentin Christensen
 

Hi everyone,

I had an inquiry about using the EM Client - http://www.emclient.com/

Has anyone used this mail client and if so, is it accessible, and are there any tips for using it or setting it up etc?

Quentin.

--
Quentin Christensen
Training and Support Manager

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

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


Re: NVDA reading dialog boxes

Don H
 

Thanks that fixed it

On 12/7/2018 12:03 PM, Tyler Spivey wrote:
Sorry, let's try with slightly clearer instructions:
1. Activate the NVDA menu, Preferences, Settings.
2. Select Object Presentation from the list.
3. Tab until you hear Report object descriptions and check it.
4. Press enter.
On 12/7/2018 8:10 AM, Don H wrote:
Tried this and got nothing.
when hitting insert control o nothing happens alt v gives me a ding and
nothing else.

On 12/7/2018 7:58 AM, Tyler Spivey wrote:
NVDA+CTRL+o, alt+d to check Report object descriptions, enter. Try again.
On 12/7/2018 5:54 AM, Don H wrote:
Running latest beta of NVDA on a Win 10 1809 system.
while in the NVDA UI if I go to help then about NVDA does not read the
dialog box it only says OK.  If you open up the check for updates or
addon updates NVDA only says close where I thought it always said No
updates available in the past










Re: Microsofts blog on the edge and chrome merge

Devin Prater
 

Well, if you don’t like it because of how it shows websites, then just wait for it to switch to Chrome. If you don’t like it because of the alt+X menu, well, there’s still Google Chrome or Firefox. :) 

On Dec 7, 2018, at 11:40 AM, molly the blind tech lover <brainardmolly@...> wrote:

not to be rude but i dislike edge.


On Fri, Dec 7, 2018, 9:54 AM Robert Kingett <kingettr@... wrote:

I haven't seen this posted yet, so I wanted to share the below blog post from Microsoft themselves. Personally, this is great for developers! Less accessibility tinkering, in my opinion. Also, since chrome based stuff is open source, anybody can develop and code for accessibility. Microsoft even said they want to do this to make web accessibility better but no, Edge is not going away. Nowhere has anybody ever said edge is going away and if they did, they are wrong and can't read.

https://blogs.windows.com/windowsexperience/2018/12/06/microsoft-edge-making-the-web-better-through-more-open-source-collaboration/





Re: NVDA reading dialog boxes

Don H
 

I have also changed the speech syn and problem still exists.

On 12/7/2018 11:08 AM, Don H wrote:
I disabled all addons and it still doesn't read the dialog boxes that NVDA generates.
On 12/7/2018 11:07 AM, Joseph Lee wrote:
Hi,
Does restarting with add-ons disabled help? If NvDA reads dialogs after disabling add-ons, chances are that it might be an add-on that's interfering with some NVDA work.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Don H
Sent: Friday, December 7, 2018 9:04 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA reading dialog boxes

Reboot doesn't fix the issue.  Ironic that NVDA doesn't read the dialog boxes it generates.

On 12/7/2018 10:56 AM, Brian's Mail list account via Groups.Io wrote:
Try rebooting the machine. I've seen this too but no idea why it comes
and goes though I use windows 7. i I have a feeling its a windows issue.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Don H" <lmddh50@adams.net>
To: <nvda@nvda.groups.io>
Sent: Friday, December 07, 2018 1:54 PM
Subject: [nvda] NVDA reading dialog boxes


Running latest beta of NVDA on a Win 10 1809 system.
while in the NVDA UI if I go to help then about NVDA does not read
the dialog box it only says OK.  If you open up the check for updates
or addon updates NVDA only says close where I thought it always said
No updates available in the past















Re: NVDA reading dialog boxes

Don H
 

OK I did a complete uninstall of NVDA including removal of all left over folders then did a clean install of the latest non beta version of NVDA. Now dialogs read as they should. Something must have gotten corrupted during installs of the beta versions on top of the released version of NVDA


Re: NVDA reading dialog boxes

Tyler Spivey
 

Sorry, let's try with slightly clearer instructions:
1. Activate the NVDA menu, Preferences, Settings.
2. Select Object Presentation from the list.
3. Tab until you hear Report object descriptions and check it.
4. Press enter.

On 12/7/2018 8:10 AM, Don H wrote:
Tried this and got nothing.
when hitting insert control o nothing happens alt v gives me a ding and
nothing else.

On 12/7/2018 7:58 AM, Tyler Spivey wrote:
NVDA+CTRL+o, alt+d to check Report object descriptions, enter. Try again.
On 12/7/2018 5:54 AM, Don H wrote:
Running latest beta of NVDA on a Win 10 1809 system.
while in the NVDA UI if I go to help then about NVDA does not read the
dialog box it only says OK.  If you open up the check for updates or
addon updates NVDA only says close where I thought it always said No
updates available in the past