Does anyone know when the atguys code factory nvda addon will be
updated to work with the upcoming versions of NVDA?

Thanks Rowan, I've shared this with the team, will advise what we find out.

On Mon, Jul 5, 2021 at 7:50 PM Rowen Cary <manchen_0528@...> wrote:

Hi, I suspect there is a major error in RC2. ctypes throws many errors. Many add-ons that are compatible in rc1 are completely unavailable in rc2. The above problem also occurred when updating from alpha-23249 to alpha-23278.

In addition, after updating to alpha23278, there will be an error dialog box prompting "Error registering focus winEvent hook".

There are many cdll.LoadLibrary errors in the log, But I don't have time to open an Issue now, hoping to attract the attention of others. Thanks.

--

Quentin Christensen
Training and Support Manager

Web: www.nvaccess.org 

Training: https://www.nvaccess.org/shop/

Certification: https://certification.nvaccess.org/

User group: https://nvda.groups.io/g/nvda

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

What does it mean when it says that the release candidate breaks support for add-ons

Can I put the release candidate and then add all my add-ons back on again

Or can I not add any add-ons at all

On 5 Jul 2021, at 3:30 pm, Quentin Christensen <quentin@...> wrote:



Hi everyone,

NVDA 2021.1 Release Candidate 2 (RC2) is now available for download & testing. We encourage all users to download this RC & provide feedback. Unless any critical bugs are found, this will be identical to the final 2021.1 release. New features & download at https://www.nvaccess.org/post/nvda-2021-1rc2/

--

Quentin Christensen
Training and Support Manager

Web: www.nvaccess.org 

Training: https://www.nvaccess.org/shop/

Certification: https://certification.nvaccess.org/

User group: https://nvda.groups.io/g/nvda

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

Pasting the status from the addons Manager for remote support

Remote Support; Status: Incompatible; Version: 2.3; Author: Tyler Spivey <tspivey@...>, Christopher Toth <q@...>

On 7/4/2021 7:21 PM, Jacob Kruger wrote:

I myself gave the remote add-on a quick test on Friday afternoon, running under 2021.1 RC1, and, it worked fine?

Jacob Kruger
Blind Biker
Skype: BlindZA
"...resistance is futile...but, acceptance is versatile..."

On 2021-07-04 01:13 PM, Robert Mendoza wrote:

Hi,

I just tested the NVDA version 2021.1rc1today.
one quick question for you guys. Does the remote support add ons will be no longer supported once the stable is release?

I myself gave the remote add-on a quick test on Friday afternoon, running under 2021.1 RC1, and, it worked fine?

Jacob Kruger
Blind Biker
Skype: BlindZA
"...resistance is futile...but, acceptance is versatile..."

On 2021-07-04 01:13 PM, Robert Mendoza wrote:

Hi,

I just tested the NVDA version 2021.1rc1today.
one quick question for you guys. Does the remote support add ons will be no longer supported once the stable is release?

It would be nice if OCR could be taught to recognize these
checkboxes/radio buttons as such & also their state. Doesn't seem like
that should be all that hard w/AI & all that now.

On 7/4/21, Gene <gsasner@...> wrote:

You disagreed with me. I responded and that’s how the discussion began. I
do ;pay attention and respond to what people say. You said this in your
initial disagreement:
“I'm sorry, but I have to disagree. While I agree it can be annoying to
find one's favorite browser does not "play well" with a given site, or that
one's favorite screen reader does not, that does not mean a site is
inaccessible.”

As I said, there is a difference between accessible and usable. And you
never defined accessible. You criticized my definition as being abstract.
Without a generally accepted and defined definition of accessibility, there
would be no standards for determining when a site is or isn’t accessible
which would pose all sorts of problems.

All I said was that the problem should be called to the attention of the
bank even if a work around is found. I said nothing about people needing or
not needing to use other browsers or screen-readers. I didn’t say everyone
who encounters any site they need to use a work around to access should
complain to the site. Nor am I saying that a site has to work properly with
every possible combination of programs. But a site like this, a banking
site, should be generally accessible.

Gene
-----Original Message-----
From: Brian Vogel
Sent: Sunday, July 04, 2021 7:22 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] cannot check boxes.

On Sun, Jul 4, 2021 at 08:03 PM, Gene wrote:

I’m saying that, in a case like this, where a major site is not usable by
a widely used screen-reader and browser or class of browsers, that site is
not accessible.
-
And I have said nothing that contradicts that in regard to this specific
site from the outset.

For the love of heaven, Gene, please read, and respond to, what I have
actually written, with the entire context of an ongoing conversation being
used as the framework. I don't make additions to a topic like this that are
each meant to stand, independently, of all others.

My very first response was to take this up with customer support since the
only change had been to the website. The screen reader and browser were the
same as have been used with their site's prior iteration.

My second was advising the offering of the specific institution in question,
as it's really impossible to know whether anyone else may have found an
accessibility method that you (the generic you) didn't, somehow.

Talking about issues like this in the abstract is as close to a complete
waste of time as one can get. I could say, I can't access the subscription
management page for my local newspaper, and it would be entirely useless to
discuss unless I could give the exact URL, or say something like it's a
Gannett paper and uses their subscription system (as there are hundreds of
papers owned and run under the Gannett name and software).

I understand the abstract concepts regarding accessibility. They're just of
little use when discussing a specific situation and whether anyone may, or
may not, have discovered a workaround. Talking about issues with
accessibility without specifics makes trying to find a solution akin to
trying to nail jello to a tree.

--

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

I do not understand why some seek to separate a person from their actions.
The self is composed of an individual’s thoughts, actions, and expression,
which are contained in and actuated by the body. What you do and say is the
clearest indicator of who you are.

~ Brian Vogel

You disagreed with me. I responded and that’s how the discussion began. I
do ;pay attention and respond to what people say. You said this in your
initial disagreement:
“I'm sorry, but I have to disagree. While I agree it can be annoying to
find one's favorite browser does not "play well" with a given site, or that
one's favorite screen reader does not, that does not mean a site is
inaccessible.”

As I said, there is a difference between accessible and usable. And you
never defined accessible. You criticized my definition as being abstract.
Without a generally accepted and defined definition of accessibility, there
would be no standards for determining when a site is or isn’t accessible
which would pose all sorts of problems.

All I said was that the problem should be called to the attention of the
bank even if a work around is found. I said nothing about people needing or
not needing to use other browsers or screen-readers. I didn’t say everyone
who encounters any site they need to use a work around to access should
complain to the site. Nor am I saying that a site has to work properly with
every possible combination of programs. But a site like this, a banking
site, should be generally accessible.

Gene
-----Original Message-----
From: Brian Vogel
Sent: Sunday, July 04, 2021 7:22 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] cannot check boxes.

On Sun, Jul 4, 2021 at 08:03 PM, Gene wrote:

I’m saying that, in a case like this, where a major site is not usable by
a widely used screen-reader and browser or class of browsers, that site is
not accessible.
-
And I have said nothing that contradicts that in regard to this specific
site from the outset.

For the love of heaven, Gene, please read, and respond to, what I have
actually written, with the entire context of an ongoing conversation being
used as the framework. I don't make additions to a topic like this that are
each meant to stand, independently, of all others.

My very first response was to take this up with customer support since the
only change had been to the website. The screen reader and browser were the
same as have been used with their site's prior iteration.

My second was advising the offering of the specific institution in question,
as it's really impossible to know whether anyone else may have found an
accessibility method that you (the generic you) didn't, somehow.

Talking about issues like this in the abstract is as close to a complete
waste of time as one can get. I could say, I can't access the subscription
management page for my local newspaper, and it would be entirely useless to
discuss unless I could give the exact URL, or say something like it's a
Gannett paper and uses their subscription system (as there are hundreds of
papers owned and run under the Gannett name and software).

I understand the abstract concepts regarding accessibility. They're just of
little use when discussing a specific situation and whether anyone may, or
may not, have discovered a workaround. Talking about issues with
accessibility without specifics makes trying to find a solution akin to
trying to nail jello to a tree.

--

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

I do not understand why some seek to separate a person from their actions.
The self is composed of an individual’s thoughts, actions, and expression,
which are contained in and actuated by the body. What you do and say is the
clearest indicator of who you are.

~ Brian Vogel