Date   
Issue Downloading Image Describer

Bhavya shah
 

Dear all,

When I click on the Stable Version link on the add-on page for Image
Describer, instead of being displayed a file download dialog on
Firefox as I am for any other downloadable files, I get the following
message:
"This XML file does not appear to have any style information
associated with it. The document tree is shown below.
<Error>
<Code>UserProjectAccountProblem</Code>
<Message>User project billing account not in good standing.</Message>
<Details>
The billing account for the owning project is disabled in state closed
</Details>
</Error>"

I have only attempted to download a few add-ons in the past hour from
the NVDA community add-ons portal, and among those, this issue has
been unique to Image Describer.

I would truly appreciate any assistance with this.

Thanks.

--
Best Regards
Bhavya Shah

Blogger at Hiking Across Horizons: https://bhavyashah125.wordpress.com/
E-mail Address: bhavya.shah125@...
LinkedIn: https://www.linkedin.com/in/bhavyashah125/

Re: Issue With Tony's enhancements Add-on

 

Hi,
Does this happen with NVDA 2020.1? If not, this might be something to report to Tony after making sure it is his add-on that's causing this issue.
Cheers,
Joseph

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Bhavya shah
Sent: Friday, June 19, 2020 1:06 PM
To: nvda-addons <nvda-addons@nvda-addons.groups.io>
Subject: [nvda-addons] Issue With Tony's enhancements Add-on

Dear all,

I am not sure what the best means of sharing a bug report for an add-on is, i.e. whether reporting it publicly is appropriate, or if one should reach out to the add-on author personally. For now, I will be defaulting to the former.

After installing the latest stable version of Tony's enhancements, with NVDA 2020.2 Beta 1, and on a Windows 8.1 system, I am facing the following issue:
* Open the Volume Mixer in Windows.
* Tab to the Volume for NVDA Application slider.
* Attempt to increase or decrease it using the arrow keys or Page Up and Page Down.
Expected Result: Value of slider will change.
Actual Result: The value changes for an instant but immediately reverts to the original value, netting out to no change at all.
Note: Pressing the add-on's keystrokes of NVDA+Ctrl+Page Up/Page Down work fine.

It would be useful if other users of this great add-on could check if they can replicate this issue on their systems and report their results to the list. Comments and diagnoses from add-on developers would be greatly appreciated.

Thanks.

--
Best Regards
Bhavya Shah

Blogger at Hiking Across Horizons: https://bhavyashah125.wordpress.com/
E-mail Address: bhavya.shah125@...
LinkedIn: https://www.linkedin.com/in/bhavyashah125/

Issue With Tony's enhancements Add-on

Bhavya shah
 

Dear all,

I am not sure what the best means of sharing a bug report for an
add-on is, i.e. whether reporting it publicly is appropriate, or if
one should reach out to the add-on author personally. For now, I will
be defaulting to the former.

After installing the latest stable version of Tony's enhancements,
with NVDA 2020.2 Beta 1, and on a Windows 8.1 system, I am facing the
following issue:
* Open the Volume Mixer in Windows.
* Tab to the Volume for NVDA Application slider.
* Attempt to increase or decrease it using the arrow keys or Page Up
and Page Down.
Expected Result: Value of slider will change.
Actual Result: The value changes for an instant but immediately
reverts to the original value, netting out to no change at all.
Note: Pressing the add-on's keystrokes of NVDA+Ctrl+Page Up/Page Down work fine.

It would be useful if other users of this great add-on could check if
they can replicate this issue on their systems and report their
results to the list. Comments and diagnoses from add-on developers
would be greatly appreciated.

Thanks.

--
Best Regards
Bhavya Shah

Blogger at Hiking Across Horizons: https://bhavyashah125.wordpress.com/
E-mail Address: bhavya.shah125@...
LinkedIn: https://www.linkedin.com/in/bhavyashah125/

Re: Addon Compatibility Phrasing

 

Hi,
This information comes from add-on authors who have final authority on their add-ons. Not all add-ons listed on community add-ons site exhibits this phrasing - mine does include compatibility range statement. For Phonetic Punctuation, the best person to clarify compatibility status is Tony.
Cheers,
Joseph

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Bhavya shah
Sent: Friday, June 19, 2020 12:47 PM
To: nvda-addons@nvda-addons.groups.io
Subject: [nvda-addons] Addon Compatibility Phrasing

Dear NVDA Add-ons community,

The suggestion I am about to make originates from an observation I made when going through the Phonetic Punctuation add-on page at https://addons.nvda-project.org/addons/phoneticPunctuation.en.html.
One of the lines mentioned here is "• NVDA compatibility: 2019.3."
* Prima faci, it seems like NVDA version 2019.3 is the only version for which this add-on is designed. That is the direct implication of this phrasing. However, my intuition says that this is unlikely to be true.
* Perhaps this add-on is compatible with NVDA version 2019.3 and later or NVDA version 2019.3 and earlier. If it is either of these, then it is imperative that "and earlier" or "and later" be specified.

I have not browsed the pages of enough add-ons to yet to comment on whether this is a general problem, or if it is specific to this one add-on. Furthermore, if my intuition is incorrect and Phonetic Punctuation, in fact, works only with NVDA version 2019.3, then what I am pointing out is a non-issue. However, if that is not the case, I sincerely request add-on community members to consider using clearer phrasing to indicate compatibility on the NVDA community add-ons portal.

Thanks.

--
Best Regards
Bhavya Shah

Blogger at Hiking Across Horizons: https://bhavyashah125.wordpress.com/
E-mail Address: bhavya.shah125@...
LinkedIn: https://www.linkedin.com/in/bhavyashah125/

Addon Compatibility Phrasing

Bhavya shah
 

Dear NVDA Add-ons community,

The suggestion I am about to make originates from an observation I
made when going through the Phonetic Punctuation add-on page at
https://addons.nvda-project.org/addons/phoneticPunctuation.en.html.
One of the lines mentioned here is "• NVDA compatibility: 2019.3."
* Prima faci, it seems like NVDA version 2019.3 is the only version
for which this add-on is designed. That is the direct implication of
this phrasing. However, my intuition says that this is unlikely to be
true.
* Perhaps this add-on is compatible with NVDA version 2019.3 and later
or NVDA version 2019.3 and earlier. If it is either of these, then it
is imperative that "and earlier" or "and later" be specified.

I have not browsed the pages of enough add-ons to yet to comment on
whether this is a general problem, or if it is specific to this one
add-on. Furthermore, if my intuition is incorrect and Phonetic
Punctuation, in fact, works only with NVDA version 2019.3, then what I
am pointing out is a non-issue. However, if that is not the case, I
sincerely request add-on community members to consider using clearer
phrasing to indicate compatibility on the NVDA community add-ons
portal.

Thanks.

--
Best Regards
Bhavya Shah

Blogger at Hiking Across Horizons: https://bhavyashah125.wordpress.com/
E-mail Address: bhavya.shah125@...
LinkedIn: https://www.linkedin.com/in/bhavyashah125/

Add-on Updater 20.06.2 coming this weekend, last version to support NVDA 2019.3 and a notice on legacy add-ons to be shown #addonrelease

 

Hi all,

 

Add-on Updater 20.06.2 is on its way, to be released either today or tomorrow (likely later today). This release includes two major changes:

 

  • Add-on Updater 20.06.2 is the last version to support NVDA 2019.3.1 or earlier. I should have done that as part of 20.06 but didn’t get a chance to do that (Add-on Updater supports latest stable NVDA release).
  • If you are still using Screen Curtain and/or Focus Highlight, after installing Add-on Updater 20.06.2, you’ll get a courtesy notice asking you to uninstall these add-ons. If you are using NVDA 2019.3 or later, these add-ons are no longer necessary as they are part of NVDA (as far as Add-on Updater and add-ons community sees them, they are legacy add-ons kept for older NVDA releases). This notice will be presented only once. If you are indeed using NVDA 2019.3 or later and wish to avoid this notice, please uninstall Screen Curtain and Focus Highlight. Also, to avoid confusion, automatic add-on update facility (not manual command) will be disabled until you restart NVDA.

 

Regarding the second item: whenever all features from an add-on is included in NVDA, a notice like this will show up in the future. This can only occur if the author of the would-be legacy add-on informs the community that the add-on is no longer needed. The notice itself will be sent out a few months after legacy declaration takes place, likely around the time the successor NVDA version is in circulation.

 

For example, suppose NVDA 2020.3 includes all features from Resource Monitor add-on (hypothetically speaking). If that ever happens (unlikely), I will declare it as a legacy add-on around the time NVDA 2020.3 stable version comes out. A few months later (around the time NVDA 2020.4 shows up), I’ll include a notice in Add-on Updater saying that Resource Monitor should be removed.

 

Cheers,

Joseph

Re: NVDA 2020.2 and Joseph Lee's add-ons: compatibility testing in progress, Windows 10 App Essentials dropping support for NVDA 2019.3 soon

Brian's Mail list account
 

I just wish they would leave it alone, personally...
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users

----- Original Message -----
From: "Martina Letochová" <letochova@...>
To: <nvda-addons@nvda-addons.groups.io>
Sent: Thursday, June 18, 2020 4:12 PM
Subject: Re: [nvda-addons] NVDA 2020.2 and Joseph Lee's add-ons: compatibility testing in progress, Windows 10 App Essentials dropping support for NVDA 2019.3 soon


New versioning system by half a year instead of year and month; so h1 the first half, h2 the second.
Martina


On 18/6/2020 16:48, Brian's Mail list account via groups.io wrote:
Hmm the leading question then is, what does the H signify?
Heritage grin?
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users
----- Original Message ----- From: "Joseph Lee" <@joslee>
To: <nvda-addons@nvda-addons.groups.io>
Sent: Wednesday, June 17, 2020 11:53 PM
Subject: [nvda-addons] NVDA 2020.2 and Joseph Lee's add-ons: compatibility testing in progress, Windows 10 App Essentials dropping support for NVDA 2019.3 soon


Hi all,



In case you missed it: NVDA 2020.2 beta 1 was released for testing. Now is
the time to make sure add-ons are ready for the upcoming release.



In regards to my add-ons:

* Compatibility: yes, although I'm doing tests to make sure my add-ons
are ready for 2020.2.
* Windows 10 App Essentials: another policy I invoke which wasn't done
for a while is dropping support for old NVDA releases - the add-on supports
current and immediate past releases. I skipped this for 2019.3 due to
massive changes between 2019.2.1 and 2019.3. Now that 2020.2 is going
through beta testing phase, support for 2019.3 will end soon - this won't
happen until at least two weeks after 2020.2 stable version is released.
Also, upcoming version 20.07 (July) will require Windows 10 Version 1909
(November 2019 Update) or later (that is, 1909, 2004, 20H2, 21H1 preview).



Cheers,

Joseph






Re: Resource Monitor: June 16th development snapshot posted

 

Hi,
Things can change, as NV Access learned a few years ago when trying to support grammar error announcement in Word that didn't work in XP. I expect something similar to happen with Windows 7, perhaps by 2023.
Cheers,
Joseph

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Brian's Mail list account via groups.io
Sent: Thursday, June 18, 2020 7:46 AM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] Resource Monitor: June 16th development snapshot posted

Hopefully that will be a long time judging by the number of hospitals I see still using it and one supposes paying Microsoft for updates to it.
I have no beef with 10, except it won't run software I depend on correctly.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users
----- Original Message -----
From: "Joseph Lee" <@joslee>
To: <nvda-addons@nvda-addons.groups.io>
Sent: Wednesday, June 17, 2020 6:53 PM
Subject: Re: [nvda-addons] Resource Monitor: June 16th development snapshot posted


Hi,

I plan to maintain support for Windows 7 until NVDA itself drops support for it.

Cheers,

Joseph

Re: NVDA 2020.2 and Joseph Lee's add-ons: compatibility testing in progress, Windows 10 App Essentials dropping support for NVDA 2019.3 soon

Martina Letochová
 

New versioning system by half a year instead of year and month; so h1 the first half, h2 the second.
Martina

On 18/6/2020 16:48, Brian's Mail list account via groups.io wrote:
Hmm the leading question then is, what does the H signify?
Heritage grin?
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users
----- Original Message ----- From: "Joseph Lee" <@joslee>
To: <nvda-addons@nvda-addons.groups.io>
Sent: Wednesday, June 17, 2020 11:53 PM
Subject: [nvda-addons] NVDA 2020.2 and Joseph Lee's add-ons: compatibility testing in progress, Windows 10 App Essentials dropping support for NVDA 2019.3 soon


Hi all,



In case you missed it: NVDA 2020.2 beta 1 was released for testing. Now is
the time to make sure add-ons are ready for the upcoming release.



In regards to my add-ons:

* Compatibility: yes, although I'm doing tests to make sure my add-ons
are ready for 2020.2.
* Windows 10 App Essentials: another policy I invoke which wasn't done
for a while is dropping support for old NVDA releases - the add-on supports
current and immediate past releases. I skipped this for 2019.3 due to
massive changes between 2019.2.1 and 2019.3. Now that 2020.2 is going
through beta testing phase, support for 2019.3 will end soon - this won't
happen until at least two weeks after 2020.2 stable version is released.
Also, upcoming version 20.07 (July) will require Windows 10 Version 1909
(November 2019 Update) or later (that is, 1909, 2004, 20H2, 21H1 preview).



Cheers,

Joseph





Re: NVDA 2020.2 and Joseph Lee's add-ons: compatibility testing in progress, Windows 10 App Essentials dropping support for NVDA 2019.3 soon

Brian's Mail list account
 

Hmm the leading question then is, what does the H signify?
Heritage grin?
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users

----- Original Message -----
From: "Joseph Lee" <@joslee>
To: <nvda-addons@nvda-addons.groups.io>
Sent: Wednesday, June 17, 2020 11:53 PM
Subject: [nvda-addons] NVDA 2020.2 and Joseph Lee's add-ons: compatibility testing in progress, Windows 10 App Essentials dropping support for NVDA 2019.3 soon


Hi all,



In case you missed it: NVDA 2020.2 beta 1 was released for testing. Now is
the time to make sure add-ons are ready for the upcoming release.



In regards to my add-ons:

* Compatibility: yes, although I'm doing tests to make sure my add-ons
are ready for 2020.2.
* Windows 10 App Essentials: another policy I invoke which wasn't done
for a while is dropping support for old NVDA releases - the add-on supports
current and immediate past releases. I skipped this for 2019.3 due to
massive changes between 2019.2.1 and 2019.3. Now that 2020.2 is going
through beta testing phase, support for 2019.3 will end soon - this won't
happen until at least two weeks after 2020.2 stable version is released.
Also, upcoming version 20.07 (July) will require Windows 10 Version 1909
(November 2019 Update) or later (that is, 1909, 2004, 20H2, 21H1 preview).



Cheers,

Joseph



Re: Resource Monitor: June 16th development snapshot posted

Brian's Mail list account
 

Hopefully that will be a long time judging by the number of hospitals I see still using it and one supposes paying Microsoft for updates to it.
I have no beef with 10, except it won't run software I depend on correctly.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users

----- Original Message -----
From: "Joseph Lee" <@joslee>
To: <nvda-addons@nvda-addons.groups.io>
Sent: Wednesday, June 17, 2020 6:53 PM
Subject: Re: [nvda-addons] Resource Monitor: June 16th development snapshot posted


Hi,

I plan to maintain support for Windows 7 until NVDA itself drops support for it.

Cheers,

Joseph

NVDA 2020.2 and Joseph Lee's add-ons: compatibility testing in progress, Windows 10 App Essentials dropping support for NVDA 2019.3 soon

 

Hi all,

 

In case you missed it: NVDA 2020.2 beta 1 was released for testing. Now is the time to make sure add-ons are ready for the upcoming release.

 

In regards to my add-ons:

  • Compatibility: yes, although I’m doing tests to make sure my add-ons are ready for 2020.2.
  • Windows 10 App Essentials: another policy I invoke which wasn’t done for a while is dropping support for old NVDA releases – the add-on supports current and immediate past releases. I skipped this for 2019.3 due to massive changes between 2019.2.1 and 2019.3. Now that 2020.2 is going through beta testing phase, support for 2019.3 will end soon – this won’t happen until at least two weeks after 2020.2 stable version is released. Also, upcoming version 20.07 (July) will require Windows 10 Version 1909 (November 2019 Update) or later (that is, 1909, 2004, 20H2, 21H1 preview).

 

Cheers,

Joseph

Re: Resource Monitor: June 16th development snapshot posted

 

Hi,

The next Windows 10 feature update will be similar to Version 1909 (November 2019 Update). However, it won't be named Version 20MM anymore - it'll be called 20H2. The development build released yesterday reflects this change when you press NVDA+Shift+Number row 6 on a computer running the upcoming feature update.

Cheers,

Joseph

Re: Resource Monitor: June 16th development snapshot posted

Akash Kakkar
 

What is the microsoft announcement?

On 6/17/20, Joseph Lee <@joslee> wrote:
Hi,

I plan to maintain support for Windows 7 until NVDA itself drops support for
it.

Cheers,

Joseph



Re: Resource Monitor: June 16th development snapshot posted

 

Hi,

I plan to maintain support for Windows 7 until NVDA itself drops support for it.

Cheers,

Joseph

Re: Resource Monitor: June 16th development snapshot posted

Brian's Mail list account
 

So what about windows 7 users, I'm assuming that version will be always retained or the resource monitor will be compatible with both versions of windows.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users

----- Original Message -----
From: "Joseph Lee" <@joslee>
To: <nvda-addons@nvda-addons.groups.io>
Sent: Wednesday, June 17, 2020 8:09 AM
Subject: Re: [nvda-addons] Resource Monitor: June 16th development snapshot posted


Hi,

It won't show up on add-ons website prominently as this is a development branch release. You need to manually switch to dev channel by going to NVDA menu/Preferences/Settings/Add-on Updater and selecting Resource Monitor from "prefer development releases" list.

I expect to release another dev branch snapshto next week. Together, these builds (and a mystery change) will show up as part of Resource Monitor 20.07.

Cheers,

Joseph

Re: Resource Monitor: June 16th development snapshot posted

 

Hi,

It won't show up on add-ons website prominently as this is a development branch release. You need to manually switch to dev channel by going to NVDA menu/Preferences/Settings/Add-on Updater and selecting Resource Monitor from "prefer development releases" list.

I expect to release another dev branch snapshto next week. Together, these builds (and a mystery change) will show up as part of Resource Monitor 20.07.

Cheers,

Joseph

Re: Resource Monitor: June 16th development snapshot posted

 

its not on the website.
how to download

On 6/17/20, Joseph Lee <@joslee> wrote:
Hi all,



I'm still in vacation, but I'm releasing a development build of Resource
Monitor add-on today in response to announcements from Microsoft:

Resource Monitor June 16th development build is now available. This build
is
meant for Windows Insiders using upcoming Version 20H2 builds.

Cheers,

Joseph




--
search for me on facebook, google+, orkut..
@austin
follow me on twitter.
austinmpinto
contact me on skype.
austin.pinto3

Resource Monitor: June 16th development snapshot posted

 

Hi all,

 

I’m still in vacation, but I’m releasing a development build of Resource Monitor add-on today in response to announcements from Microsoft:

Resource Monitor June 16th development build is now available. This build is meant for Windows Insiders using upcoming Version 20H2 builds.

Cheers,

Joseph

Re: Developer toolkit reaches a new level

Jim Homme
 

Hi Andy,

If you do a browser extension for Chrome, I would put it in the Chrome Store and sell it. Same with Firefox. Same with Edge, if Microsoft has an extension store. Maybe with the new standards where web extension code is being standardized, you will luck out and only have to write the code once.

 

Thanks.

 

Jim H

 

 

From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Andy B. via groups.io
Sent: Thursday, June 11, 2020 10:11 PM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] Developer toolkit reaches a new level

 

Hi,

 

Thanks for the support. I will have to try some simple tests in Chrome. On the desktop environment side of things, I might have figured out how to avoid the NVDA add-on idea completely, and go with a pure python implementation of DTK. As a result, there would be browser extension implementations and a python implementation of DTK. Would this be worth paying for?

 

 

Sent from Mail for Windows 10

 

From: James Scholes
Sent: Thursday, June 11, 2020 6:37 PM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] Developer toolkit reaches a new level

 

As far as I know, the only way to access a true representation of the

DOM and accessibility tree (if web extensions have direct access to

that) is to run your code inside the browser.  I believe you've already

realised this yourself through a lot of trial and error, trying to

obtain the mark-up of an element from within NVDA.  It just doesn't work.

 

So, my vote is that any accessibility-focused tools which need DOM

access must run in the browser.  If you want to expose an interface via

an NVDA add-on, your browser extension can share information with a

native process and vice-versa.  But equally, if the UI was good, I would

use an entirely in-browser version of DTK.

 

Regards,

 

James Scholes

 

On 11/06/2020 at 1:56 pm, Andy B. wrote:

> Is this even worth putting into an NVDA add-on then? Why not have the

> add-on for desktop environments and a browser extension for web content?

> The only question then, is the layout of the browser extension’s output.

>

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

> Windows 10

>

> *From: *James Scholes <mailto:james@...>

> *Sent: *Thursday, June 11, 2020 12:23 PM

> *To: *nvda-addons@nvda-addons.groups.io

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

> *Subject: *Re: [nvda-addons] Developer toolkit reaches a new level

>

> That explains how it parses the content, but not where it gets it from.

>

> If your add-on downloads a copy of the web page and only uses

>

> stylesheets or inline styles, that's not a true representation of the

>

> DOM for a huge percentage of websites which rely on JavaScript.  It

>

> won't work at all with SPAs, or websites which require a login.  And as

>

> the web moves more towards web components and other dynamic techniques,

>

> it will become increasingly less useful.

>

> Now, if you were to write a web extension for the browser which could

>

> communicate a true representation of DOM elements to your add-on via

>

> IPC, that would be worth paying for.

>

> Regards,

>

> James Scholes

>

> On 11/06/2020 at 11:19 am, Andy B. wrote:

>

>  > It uses the bs4 and tinycss libraries found in the pip repository.

>

>  >

>

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

>

>  > Windows 10

>

>  >

>

>  > *From: *James Scholes <mailto:james@...>

>

>  > *Sent: *Thursday, June 11, 2020 10:57 AM

>

>  > *To: *nvda-addons@nvda-addons.groups.io

>

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

>

>  > *Subject: *Re: [nvda-addons] Developer toolkit reaches a new level

>

>  >

>

>  > Before offering any sort of paid material, be that the add-on itself or

>

>  >

>

>  > supporting content, it would be good to know how the add-on is obtaining

>

>  >

>

>  > the mark-up and styling information.  Is it taken directly from the

>

>  >

>

>  > browser's DOM?

>

>  >

>

>  > Regards,

>

>  >

>

>  > James Scholes

>

>  >

>

>  > On 10/06/2020 at 9:10 pm, Andy B. wrote:

>

>  >

>

>  >  > Hi,

>

>  >

>

>  >  >

>

>  >

>

>  >  > I am writing today to let you know that Developer toolkit, an NVDA

>

>  >

>

>  >  > add-on which assists with the user interface design experience for

>

>  >

>

>  >  > blind/visually impaired developers, has reached a major milestone

> in its

>

>  >

>

>  >  > development. For the first time in its history, users can gain

> access to

>

>  >

>

>  >  > the css and html of the focused object while developer toolkit mode is

>

>  >

>

>  >  > turned on.

>

>  >

>

>  >  >

>

>  >

>

>  >  > Once implemented, you can do the following:

>

>  >

>

>  >  >

>

>  >

>

>  >  >   * See positioning of the focused object. For example, absolute,

>

>  >

>

>  >  >     relative, and float.

>

>  >

>

>  >  >   * Determine the margins for each object.

>

>  >

>

>  >  >   * Find out how much padding each object contains.

>

>  >

>

>  >  >   * Find out the borders of an object if one is present.

>

>  >

>

>  >  >   * Find font/formatting information provided directly from the css.

>

>  >

>

>  >  >   * Determine if text or objects in a parent object are

>

>  >

>

>  >  >     vertical/horizontally aligned.

>

>  >

>

>  >  >   * Find the z-index of the focused object.

>

>  >

>

>  >  >   * Find out anything the style rule has defined for the focused

> object.

>

>  >

>

>  >  >   * Obtain the html source for the focused object.

>

>  >

>

>  >  >   * Explore and get suggestions on common color schemes such as

>

>  >

>

>  >  >     complementary, monochrome, analogous, triad, square, etc.

>

>  >

>

>  >  >   * Anything that having the css/html source will allow.

>

>  >

>

>  >  >

>

>  >

>

>  >  > Since this opens many more opportunities, it also demands more

> time and

>

>  >

>

>  >  > work. I would like to know how interested people are in obtaining

> a paid

>

>  >

>

>  >  > version once it is complete. The options are as follows:

>

>  >

>

>  >  >

>

>  >

>

>  >  >   * Offer a free NVDA add-on that does everything, and sell how-to

>

>  >

>

>  >  >     guides, training, and books.

>

>  >

>

>  >  >   * Offer a free edition and paid edition of the add-on, and sell

> how-to

>

>  >

>

>  >  >     guides, training, and books.

>

>  >

>

>  >  >

>

>  >

>

>  >  > Send your preferences and any concerns to ajborka@...

>

>  >

>

>  >  > <mailto:ajborka@...> as to not lock up the lists with unrelated

>

>  >

>

>  >  > content. Thanks for your time and consideration.

>

>  >

>

>  >  >

>

>  >

>

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

>

>  >

>

>  >  > Windows 10

>

>  >

>

>  >  >

>

>  >

>

>  >  >

>

>  >

>

>  >

>

>