Date   

Re: Custom screen access

Christian Comaschi
 

Thanks for the explanation, but unfortunately I’m working on a steno application that can be thought more as a driver than as a normal application. In fact, its main goal is to translate steno keyboards key combinations to normal key presses and send them to other apps, e.g. text editing apps.
So I don’t have to make its windows accessible, they already are, but I have to do what I wrote in my previous mail, read the text and caret position of the most common applications in a screen-reader like manner.
I could explain more in detail why I have to do that but it would take pages!

Il giorno 21 giu 2020, alle ore 20:47, Travis Siegel <tsiegel@...> ha scritto:

In general, if you have the source code for an application, (and with opensource, you do), there's no need to fiddle with screen reader built-in functions at all, just rewrite the actual application to use standard windows api calls, (instead of custom functionality) such as gui elements, buttons, and the like. This will automatically translate to better functionality in screen readers, because they're already built to watch the regular apis for information. I.E.
If the app is written in java, instead of drawing your text onto a canvas, like so many apps do, simply use a standard text control instead, it may take more work to make it look the way you want (which is why some folks use the graphical canvas), but it will automatically become more accessible without you having to do anything at all. in regards to the screen readers. Other languages have similar functionality issues. In general, using a nongraphical method to get the text to the screen, properly labeling graphical elements, and using standard windows controls instead of creating your own from scratch will make the applications completely accessible, with very few tweaks being necessary to complete any accessibility issues that may remain.
In general, the more custom gui elements you use, the less accessible your application becomes. Obviously, there's ways to get around this, but few (If any) developers know enough about accessibility out of the box to make those required modifications to custom elements so they work with screen readers. I don't know specifically what you're trying to fix, I've never heard of the application you're trying to fix, neither do I know what language it's written in, but most of the time, making an application more accessible doesn't require writing scripts or screen reader modules, simply make the application use standard windows controls at the source level, and most of those things will solve themselves.

On Sun, 21 Jun 2020, Christian Comaschi wrote:

Hello,
I'm asking a question that might be a little off topic because I'm not planning to develop anything for NVDA at the moment; but I'm working on an accessibility project and I'd like to know more about screen readers internals, and I think that someone here can help me find the info I need.
I'm writing custom code to improve the accessibility of an open source application (Plover), because common screen reader scripts and app modules alone don't allow me to bring it to the needed accessiblity requirements.
The problem is that at some point I need to read text from editable controls of any application in a "screen reader"-like manner, so I would like to know how screen readers can get the caret position and read the text of an editable control and the different approach of JAWS and NVDA.
I'm asking you the details of this functionality because I am trying to figure out if it could be a viable solution to read text from the screen in a "screen-reader like" manner with an approach that is valid for almost every application, or if it'stoo complex because it would require re-inventing a screen driver from scratch or re-inventing scripts for common application. In this latter case, I would consider a less stand-alone approach and make the application work in tandem with JAWS or NVDA.

After some analysis I have come to a conclusion and I would like to know if it's righgt:
- NVDA has no generic way to "read" the text given a screen position, but there are scripts for the most common applications that provide this information to the main module using the most proper technique for the single application (Win32 API, MSAA, UIA or other means);
- JAWS seems to have generic functions such as "SayLine", "SayRow" or "SaySentence" that work for most of the applications because of its video intercept driver.

As a first try, I wrote some small scripts to use just UIA to read the text and caret position inside Notepad or Winword, but it didn't work; I also tried to use the inspect tool from Microsoft, meant to analyze the windows of any application to get accessibility info, but even that tool wasn't able to get the caret position inside the edit windows.
Am I missing something or is it really that complex?
Thanks in advance
Best,
Christian











Re: Custom screen access

Travis Siegel
 

In general, if you have the source code for an application, (and with opensource, you do), there's no need to fiddle with screen reader built-in functions at all, just rewrite the actual application to use standard windows api calls, (instead of custom functionality) such as gui elements, buttons, and the like. This will automatically translate to better functionality in screen readers, because they're already built to watch the regular apis for information. I.E.
If the app is written in java, instead of drawing your text onto a canvas, like so many apps do, simply use a standard text control instead, it may take more work to make it look the way you want (which is why some folks use the graphical canvas), but it will automatically become more accessible without you having to do anything at all. in regards to the screen readers. Other languages have similar functionality issues. In general, using a nongraphical method to get the text to the screen, properly labeling graphical elements, and using standard windows controls instead of creating your own from scratch will make the applications completely accessible, with very few tweaks being necessary to complete any accessibility issues that may remain.
In general, the more custom gui elements you use, the less accessible your application becomes. Obviously, there's ways to get around this, but few (If any) developers know enough about accessibility out of the box to make those required modifications to custom elements so they work with screen readers. I don't know specifically what you're trying to fix, I've never heard of the application you're trying to fix, neither do I know what language it's written in, but most of the time, making an application more accessible doesn't require writing scripts or screen reader modules, simply make the application use standard windows controls at the source level, and most of those things will solve themselves.

On Sun, 21 Jun 2020, Christian Comaschi wrote:

Hello,
I'm asking a question that might be a little off topic because I'm not planning to develop anything for NVDA at the moment; but I'm working on an accessibility project and I'd like to know more about screen readers internals, and I think that someone here can help me find the info I need.
I'm writing custom code to improve the accessibility of an open source application (Plover), because common screen reader scripts and app modules alone don't allow me to bring it to the needed accessiblity requirements.
The problem is that at some point I need to read text from editable controls of any application in a "screen reader"-like manner, so I would like to know how screen readers can get the caret position and read the text of an editable control and the different approach of JAWS and NVDA.
I'm asking you the details of this functionality because I am trying to figure out if it could be a viable solution to read text from the screen in a "screen-reader like" manner with an approach that is valid for almost every application, or if it'stoo complex because it would require re-inventing a screen driver from scratch or re-inventing scripts for common application. In this latter case, I would consider a less stand-alone approach and make the application work in tandem with JAWS or NVDA.

After some analysis I have come to a conclusion and I would like to know if it's righgt:
- NVDA has no generic way to "read" the text given a screen position, but there are scripts for the most common applications that provide this information to the main module using the most proper technique for the single application (Win32 API, MSAA, UIA or other means);
- JAWS seems to have generic functions such as "SayLine", "SayRow" or "SaySentence" that work for most of the applications because of its video intercept driver.

As a first try, I wrote some small scripts to use just UIA to read the text and caret position inside Notepad or Winword, but it didn't work; I also tried to use the inspect tool from Microsoft, meant to analyze the windows of any application to get accessibility info, but even that tool wasn't able to get the caret position inside the edit windows.
Am I missing something or is it really that complex?
Thanks in advance
Best,
Christian










Custom screen access

Christian Comaschi
 

Hello,
I'm asking a question that might be a little off topic because I'm not planning to develop anything for NVDA at the moment; but I'm working on an accessibility project and I'd like to know more about screen readers internals, and I think that someone here can help me find the info I need.
I'm writing custom code to improve the accessibility of an open source application (Plover), because common screen reader scripts and app modules alone don't allow me to bring it to the needed accessiblity requirements.
The problem is that at some point I need to read text from editable controls of any application in a "screen reader"-like manner, so I would like to know how screen readers can get the caret position and read the text of an editable control and the different approach of JAWS and NVDA.
I'm asking you the details of this functionality because I am trying to figure out if it could be a viable solution to read text from the screen in a "screen-reader like" manner with an approach that is valid for almost every application, or if it'stoo complex because it would require re-inventing a screen driver from scratch or re-inventing scripts for common application. In this latter case, I would consider a less stand-alone approach and make the application work in tandem with JAWS or NVDA.

After some analysis I have come to a conclusion and I would like to know if it's righgt:
- NVDA has no generic way to "read" the text given a screen position, but there are scripts for the most common applications that provide this information to the main module using the most proper technique for the single application (Win32 API, MSAA, UIA or other means);
- JAWS seems to have generic functions such as "SayLine", "SayRow" or "SaySentence" that work for most of the applications because of its video intercept driver.

As a first try, I wrote some small scripts to use just UIA to read the text and caret position inside Notepad or Winword, but it didn't work; I also tried to use the inspect tool from Microsoft, meant to analyze the windows of any application to get accessibility info, but even that tool wasn't able to get the caret position inside the edit windows.
Am I missing something or is it really that complex?
Thanks in advance
Best,
Christian


Problems during translation

Rui Fontes
 

Hello!


Translating NVDA 2020.2 I found the following problems:


1 - In changes.t2t I have found this:

- Removed "top" and "bottom" messages when moving the review cursor to the first or last line of the current navigator object. (#9551)
- Removed "left" and "right" messages when moving the refiew cursor to the first or last character of the line for the current navigator object. (#9551)

but my NVDA 2020.2 Beta1 still announce those messages...


2 - Also in changes.t2t, found this:

- NVDA no longer freezes when you open the context menu for 1Password in the system notification area. (#11017)

- The tool-tips of the icons in the system tray are no longer reported upon keyboard navigation if their text is equal to the name of the icons, to avoid a double announcing. (#6656)


Should we use "system notification area" or "system tray"?


For me, we should use the first...


3 - In NVDA/Preferences/Settings, Advanced the itens in the Enabled logging categories list, are not translatable...



Rui Fontes

NVDA portuguese team


Re: Sending keystrokes

Karl-Otto Rosenqvist
 

Absolutely, that could be one solution. My thought here would be if one could catch the key down event, announce the function key and if the key up event comes from the same function key alone, i e no key down event for the adjecent function key immediately after you could count it as a press of that function key. One could experiment with the timing.

The problem here is that I don’t have the necessary hardware and I’d like to test some kind of working solution before spending all that money.


Regards

Karl-Otto
MAWINGU
0701-75 98 56
https://mawingu.se
Orgnr: 750804-3937

20 juni 2020 kl. 00:13 skrev Bill Dengler <codeofdusk@...>:

I’ve actually thought about an alternative solution for this: how about writing a global plug-in that intersects the function keys, and on first press announces them, then on second press sends them through? this would make the Touch Bar at least partially accessible, as well as machines with capacitive media keys…

Bill
On Jun 19, 2020, at 18:07, Karl-Otto Rosenqvist <Karl-otto@...> wrote:

Hi!
I wonder if anyone could point me in the right driection. I’d like to create a global plugin that converts some keystrokes to others. How can I send new key events from the Python code? It’s easy to bind the gestures to functions but how the heck do I generate a key press?

The goal is to use it on a MacBook Pro with Touch Bar running Windows. The MacBooks with Touch Bar lacs the physical function keys and your only option is to use the touch screen where the function keys are drawn.

I want to test using Ctrl + Win + 1 for F1, Ctrl + Win + 2 for F2 and so on.

The MacBook Pros have a very bright screen which I benefit from and I’d like to test this and see if it’s a good enough solution or not before I buy one, they are quite expensive...


Kind regards

Karl-Otto
MAWINGU
0701-75 98 56
https://mawingu.se
Orgnr: 750804-3937



Re: Sending keystrokes

Bill Dengler
 

I’ve actually thought about an alternative solution for this: how about writing a global plug-in that intersects the function keys, and on first press announces them, then on second press sends them through? this would make the Touch Bar at least partially accessible, as well as machines with capacitive media keys…

Bill

On Jun 19, 2020, at 18:07, Karl-Otto Rosenqvist <Karl-otto@...> wrote:

Hi!
I wonder if anyone could point me in the right driection. I’d like to create a global plugin that converts some keystrokes to others. How can I send new key events from the Python code? It’s easy to bind the gestures to functions but how the heck do I generate a key press?

The goal is to use it on a MacBook Pro with Touch Bar running Windows. The MacBooks with Touch Bar lacs the physical function keys and your only option is to use the touch screen where the function keys are drawn.

I want to test using Ctrl + Win + 1 for F1, Ctrl + Win + 2 for F2 and so on.

The MacBook Pros have a very bright screen which I benefit from and I’d like to test this and see if it’s a good enough solution or not before I buy one, they are quite expensive...


Kind regards

Karl-Otto
MAWINGU
0701-75 98 56
https://mawingu.se
Orgnr: 750804-3937


Sending keystrokes

Karl-Otto Rosenqvist
 

Hi!
I wonder if anyone could point me in the right driection. I’d like to create a global plugin that converts some keystrokes to others. How can I send new key events from the Python code? It’s easy to bind the gestures to functions but how the heck do I generate a key press?

The goal is to use it on a MacBook Pro with Touch Bar running Windows. The MacBooks with Touch Bar lacs the physical function keys and your only option is to use the touch screen where the function keys are drawn.

I want to test using Ctrl + Win + 1 for F1, Ctrl + Win + 2 for F2 and so on.

The MacBook Pros have a very bright screen which I benefit from and I’d like to test this and see if it’s a good enough solution or not before I buy one, they are quite expensive...


Kind regards

Karl-Otto
MAWINGU
0701-75 98 56
https://mawingu.se
Orgnr: 750804-3937


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: Process to make an NVDA app-specific addon for a web-based application

Brian's Mail list account
 

More to the point though, one has to ask why, if this is a web application, is it so inaccessible that it would need an add on. Without more detail on the actual problem most are just guessing here.
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: "Luke Davis" <luke@...>
To: <nvda-devel@groups.io>
Sent: Wednesday, June 17, 2020 9:49 PM
Subject: Re: [nvda-devel] Process to make an NVDA app-specific addon for a web-based application


I like Nolea's elegant solution for this problem.

Another, quicker and dirtier solution, would probably be to make your add-on a globalPlugin, and have it activated and deactivated by key combination.

You may be able to code something using profiles, to detect that it only runs in the right context.

Luke

On Wed, 17 Jun 2020, Julie Stoltz wrote:

Thank you for the information. Your suggestion is actually in the works already. Our developers are creating a new implementation that will not be browser
dependent. Unfortunately, that is about a year away, and we have a client that needs accessibility much sooner than that, so I was hoping to create a
solution for the interim.


Re: Process to make an NVDA app-specific addon for a web-based application

Julie Stoltz <jstoltz@...>
 

Thank you Julien. After a quick skim, your app looks like it addresses a lot of the things we will need. I can already tell you I'll be spending my weekend reading through it closely and playing with it. Many, many thanks for sharing.

-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Noelia Ruiz via groups.io
Sent: Thursday, June 18, 2020 1:40 AM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] Process to make an NVDA app-specific addon for a web-based application

Thanks a lot Julien. I'm very interested in your add-on.
placeMarkers works in browse mode documents. It saves and searches bookmarks and strings of text in files whose names deppend on the following code, in case you are curious or maybe useful.
I will clone and explore your add-on, of course.
Piece of code of placeMarkers:

obj=api.getForegroundObject()
file = obj.name
obj = api.getFocusObject()
try:
obj = obj.treeInterceptor.rootNVDAObject
childID = obj.IAccessibleChildID
iAObj = obj.IAccessibleObject
accValue = iAObj.accValue(childID)
nameToAdd = " - %s" % accValue.split("#")[0].split("/")[-1].split("\\")[-1]
except:
nameToAdd = ""
file = file.rsplit(" - ", 1)[0]
file = file.split("\\")[-1]
file += nameToAdd
file = standardFileName(file)
folderPath = os.path.join(PLACE_MARKERS_PATH, folder)
maxLenFileName = 232-len(folderPath)
if maxLenFileName <= 0:
return ""
file = file[:maxLenFileName]
file = file+ext
path = os.path.join(folderPath, file)
return path


2020-06-18 7:21 GMT+02:00, Julien Cochuyt <j.cochuyt@...>:
Hi,

I am a French IT professional specialized in accessibility and core
NVDA contributor.
As Joseph pointed out, there is no native support in NVDA for the use
case you describe.
However, some add-ons can come in handy.

My company - with support of the french employment agency and the
governmental central IT agency - is developing WebAccess, an add-on
for NVDA that allows to easily implement alternative behaviors based
on URL matching and DOM elements selection.
It handles, through simple form-filling, definition of new shortcuts,
automatic announcement of content or restructuring of pages with basic
transformations to create regions, titles, and the like.
It also serves as a framework to implement new specific behaviors
through code.
Centered around WebModules - our web app equivalent of NVDA's
AppModules - it currently supports Internet Explorer 11, Mozilla
Firefox and Google Chrome. Support of Microsoft Edge is still a work in progress.

For the past five years, we're successfully using it to develop
add-ons targeting business web applications, for the sake of visually
impaired workers productivity.
Still under active development, it is already used by our network of
fellow professionals but not yet quite ready for use by the general public.
We're aiming at a general public launch near the end of 2020, most
likely during NVDA Con.

GitHub repo: https://github.com/accessolutions/WebAccessForNVDA


As Noelia pointed out, another alternative worth considering is the
PlaceMarkers add-on, though I'm less aware of its current feature-scope.


Best regards,

Julien Cochuyt
Accessolutions

Le mer. 17 juin 2020 à 19:58, Julie Stoltz <jstoltz@...> a écrit :

Hi all,

I am very new to this group and the NVDA application, and I apologize
if I have missed anything critical in the steps to address this.



I searched the archives and development guide and did not find an
answer to my question.



Our company provides a web-based app to our clients. I have been
looking into NVDA and I see that it can be used to create
application-specific behavior. However, such addons are named for the
executable file that opens the application. In our case, our
application is opened with a web address in an Internet Explorer 11
browser.



Can NVDA work with domain-specific web applications? If so, how
should the addon be named? Are there any config settings I could use
to create an alias (I believe this is how JAWS addresses this issue)?



I know I can create an addon for IE itself, but that option would
likely interfere with other sites or applications run through IE, so
I don’t want to go that route unless absolutely necessary.



Any guidance at all is greatly appreciated.





Julie Stoltz

Technical Communications Specialist

Cycom Data Systems, Inc.

www.cycominc.com

888-292-6688







Re: Process to make an NVDA app-specific addon for a web-based application

Noelia Ruiz
 

Thanks a lot Julien. I'm very interested in your add-on.
placeMarkers works in browse mode documents. It saves and searches
bookmarks and strings of text in files whose names deppend on the
following code, in case you are curious or maybe useful.
I will clone and explore your add-on, of course.
Piece of code of placeMarkers:

obj=api.getForegroundObject()
file = obj.name
obj = api.getFocusObject()
try:
obj = obj.treeInterceptor.rootNVDAObject
childID = obj.IAccessibleChildID
iAObj = obj.IAccessibleObject
accValue = iAObj.accValue(childID)
nameToAdd = " - %s" % accValue.split("#")[0].split("/")[-1].split("\\")[-1]
except:
nameToAdd = ""
file = file.rsplit(" - ", 1)[0]
file = file.split("\\")[-1]
file += nameToAdd
file = standardFileName(file)
folderPath = os.path.join(PLACE_MARKERS_PATH, folder)
maxLenFileName = 232-len(folderPath)
if maxLenFileName <= 0:
return ""
file = file[:maxLenFileName]
file = file+ext
path = os.path.join(folderPath, file)
return path


2020-06-18 7:21 GMT+02:00, Julien Cochuyt <j.cochuyt@...>:

Hi,

I am a French IT professional specialized in accessibility and core NVDA
contributor.
As Joseph pointed out, there is no native support in NVDA for the use case
you describe.
However, some add-ons can come in handy.

My company - with support of the french employment agency and the
governmental central IT agency - is developing WebAccess, an add-on for
NVDA that allows to easily implement alternative behaviors based on URL
matching and DOM elements selection.
It handles, through simple form-filling, definition of new shortcuts,
automatic announcement of content or restructuring of pages with basic
transformations to create regions, titles, and the like.
It also serves as a framework to implement new specific behaviors
through code.
Centered around WebModules - our web app equivalent of NVDA's AppModules -
it currently supports Internet Explorer 11, Mozilla Firefox and Google
Chrome. Support of Microsoft Edge is still a work in progress.

For the past five years, we're successfully using it to develop add-ons
targeting business web applications, for the sake of visually impaired
workers productivity.
Still under active development, it is already used by our network of fellow
professionals but not yet quite ready for use by the general public.
We're aiming at a general public launch near the end of 2020, most likely
during NVDA Con.

GitHub repo: https://github.com/accessolutions/WebAccessForNVDA


As Noelia pointed out, another alternative worth considering is the
PlaceMarkers add-on, though I'm less aware of its current feature-scope.


Best regards,

Julien Cochuyt
Accessolutions

Le mer. 17 juin 2020 à 19:58, Julie Stoltz <jstoltz@...> a écrit :

Hi all,

I am very new to this group and the NVDA application, and I apologize if
I
have missed anything critical in the steps to address this.



I searched the archives and development guide and did not find an answer
to my question.



Our company provides a web-based app to our clients. I have been looking
into NVDA and I see that it can be used to create application-specific
behavior. However, such addons are named for the executable file that
opens
the application. In our case, our application is opened with a web
address
in an Internet Explorer 11 browser.



Can NVDA work with domain-specific web applications? If so, how should
the
addon be named? Are there any config settings I could use to create an
alias (I believe this is how JAWS addresses this issue)?



I know I can create an addon for IE itself, but that option would likely
interfere with other sites or applications run through IE, so I don’t
want
to go that route unless absolutely necessary.



Any guidance at all is greatly appreciated.





Julie Stoltz

Technical Communications Specialist

Cycom Data Systems, Inc.

www.cycominc.com

888-292-6688







Re: Process to make an NVDA app-specific addon for a web-based application

Julien Cochuyt
 

Hi,

I am a French IT professional specialized in accessibility and core NVDA contributor.
As Joseph pointed out, there is no native support in NVDA for the use case you describe.
However, some add-ons can come in handy.

My company - with support of the french employment agency and the governmental central IT agency - is developing WebAccess, an add-on for NVDA that allows to easily implement alternative behaviors based on URL matching and DOM elements selection.
It handles, through simple form-filling, definition of new shortcuts, automatic announcement of content or restructuring of pages with basic transformations to create regions, titles, and the like.
It also serves as a framework to implement new specific behaviors through code.
Centered around WebModules - our web app equivalent of NVDA's AppModules - it currently supports Internet Explorer 11, Mozilla Firefox and Google Chrome. Support of Microsoft Edge is still a work in progress.

For the past five years, we're successfully using it to develop add-ons targeting business web applications, for the sake of visually impaired workers productivity.
Still under active development, it is already used by our network of fellow professionals but not yet quite ready for use by the general public.
We're aiming at a general public launch near the end of 2020, most likely during NVDA Con.



As Noelia pointed out, another alternative worth considering is the PlaceMarkers add-on, though I'm less aware of its current feature-scope.


Best regards,

Julien Cochuyt
Accessolutions

Le mer. 17 juin 2020 à 19:58, Julie Stoltz <jstoltz@...> a écrit :

Hi all,

I am very new to this group and the NVDA application, and I apologize if I have missed anything critical in the steps to address this.

 

I searched the archives and development guide and did not find an answer to my question.

 

Our company provides a web-based app to our clients. I have been looking into NVDA and I see that it can be used to create application-specific behavior. However, such addons are named for the executable file that opens the application. In our case, our application is opened with a web address in an Internet Explorer 11 browser.

 

Can NVDA work with domain-specific web applications? If so, how should the addon be named? Are there any config settings I could use to create an alias (I believe this is how JAWS addresses this issue)?

 

I know I can create an addon for IE itself, but that option would likely interfere with other sites or applications run through IE, so I don’t want to go that route unless absolutely necessary.

 

Any guidance at all is greatly appreciated.

 

 

Julie Stoltz

Technical Communications Specialist

Cycom Data Systems, Inc.

www.cycominc.com

888-292-6688

 


Re: Process to make an NVDA app-specific addon for a web-based application

 

Hi,
It might be possible using foreground and gain/lose focus events, but be
aware that you need to think about possibilities such as a website having
the same name and/or content as your app but hosted somewhere else.
Cheers,
Joseph

-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Julie Stoltz
Sent: Wednesday, June 17, 2020 2:13 PM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] Process to make an NVDA app-specific addon for a
web-based application

Thank you Nolea for the example. It will likely help me a great deal.

Thank you Luke for the suggestions. I was wondering if I could simply create
an addon for IE, but have it verify the URL before it does anything. But
your idea to make it a globalPlugin the user can turn on/off is very
promising. I wonder if I did it this way if I could get it to turn itself on
and off as the user moves between apps or browser tabs, so that it
effectively activates and deactivates itself?

-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Luke Davis
via groups.io
Sent: Wednesday, June 17, 2020 4:50 PM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] Process to make an NVDA app-specific addon for a
web-based application

I like Nolea's elegant solution for this problem.

Another, quicker and dirtier solution, would probably be to make your add-on
a globalPlugin, and have it activated and deactivated by key combination.

You may be able to code something using profiles, to detect that it only
runs in the right context.

Luke

On Wed, 17 Jun 2020, Julie Stoltz wrote:

Thank you for the information. Your suggestion is actually in the
works already. Our developers are creating a new implementation that
will not be browser dependent. Unfortunately, that is about a year away,
and we have a client that needs accessibility much sooner than that, so I
was hoping to create a solution for the interim.


Re: Process to make an NVDA app-specific addon for a web-based application

Julie Stoltz <jstoltz@...>
 

Thank you Nolea for the example. It will likely help me a great deal.

Thank you Luke for the suggestions. I was wondering if I could simply create an addon for IE, but have it verify the URL before it does anything. But your idea to make it a globalPlugin the user can turn on/off is very promising. I wonder if I did it this way if I could get it to turn itself on and off as the user moves between apps or browser tabs, so that it effectively activates and deactivates itself?

-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Luke Davis via groups.io
Sent: Wednesday, June 17, 2020 4:50 PM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] Process to make an NVDA app-specific addon for a web-based application

I like Nolea's elegant solution for this problem.

Another, quicker and dirtier solution, would probably be to make your add-on a globalPlugin, and have it activated and deactivated by key combination.

You may be able to code something using profiles, to detect that it only runs in the right context.

Luke

On Wed, 17 Jun 2020, Julie Stoltz wrote:

Thank you for the information. Your suggestion is actually in the
works already. Our developers are creating a new implementation that
will not be browser dependent. Unfortunately, that is about a year away, and we have a client that needs accessibility much sooner than that, so I was hoping to create a solution for the interim.


Re: Process to make an NVDA app-specific addon for a web-based application

Luke Davis
 

I like Nolea's elegant solution for this problem.

Another, quicker and dirtier solution, would probably be to make your add-on a globalPlugin, and have it activated and deactivated by key combination.

You may be able to code something using profiles, to detect that it only runs in the right context.

Luke

On Wed, 17 Jun 2020, Julie Stoltz wrote:

Thank you for the information. Your suggestion is actually in the works already. Our developers are creating a new implementation that will not be browser
dependent. Unfortunately, that is about a year away, and we have a client that needs accessibility much sooner than that, so I was hoping to create a
solution for the interim.


Re: Process to make an NVDA app-specific addon for a web-based application

Julie Stoltz <jstoltz@...>
 

@Joseph

Thank you for the information. Your suggestion is actually in the works already. Our developers are creating a new implementation that will not be browser dependent. Unfortunately, that is about a year away, and we have a client that needs accessibility much sooner than that, so I was hoping to create a solution for the interim.

 

From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Joseph Lee via groups.io
Sent: Wednesday, June 17, 2020 2:15 PM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] Process to make an NVDA app-specific addon for a web-based application

 

Hi,

At the moment there is no way of creating domain specific add-ons. I think a better approach might be looking into making your app usable with browsers other than (or in addition to) Internet Explorer, as IE is under maintenance mode at the moment.

Cheers,

Joseph

 

From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Julie Stoltz
Sent: Wednesday, June 17, 2020 10:35 AM
To: nvda-devel@groups.io
Subject: [nvda-devel] Process to make an NVDA app-specific addon for a web-based application

 

Hi all,

I am very new to this group and the NVDA application, and I apologize if I have missed anything critical in the steps to address this.

 

I searched the archives and development guide and did not find an answer to my question.

 

Our company provides a web-based app to our clients. I have been looking into NVDA and I see that it can be used to create application-specific behavior. However, such addons are named for the executable file that opens the application. In our case, our application is opened with a web address in an Internet Explorer 11 browser.

 

Can NVDA work with domain-specific web applications? If so, how should the addon be named? Are there any config settings I could use to create an alias (I believe this is how JAWS addresses this issue)?

 

I know I can create an addon for IE itself, but that option would likely interfere with other sites or applications run through IE, so I don’t want to go that route unless absolutely necessary.

 

Any guidance at all is greatly appreciated.

 

 

Julie Stoltz

Technical Communications Specialist

Cycom Data Systems, Inc.

www.cycominc.com

888-292-6688

 


Re: Process to make an NVDA app-specific addon for a web-based application

 

Hi,

At the moment there is no way of creating domain specific add-ons. I think a better approach might be looking into making your app usable with browsers other than (or in addition to) Internet Explorer, as IE is under maintenance mode at the moment.

Cheers,

Joseph

 

From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Julie Stoltz
Sent: Wednesday, June 17, 2020 10:35 AM
To: nvda-devel@groups.io
Subject: [nvda-devel] Process to make an NVDA app-specific addon for a web-based application

 

Hi all,

I am very new to this group and the NVDA application, and I apologize if I have missed anything critical in the steps to address this.

 

I searched the archives and development guide and did not find an answer to my question.

 

Our company provides a web-based app to our clients. I have been looking into NVDA and I see that it can be used to create application-specific behavior. However, such addons are named for the executable file that opens the application. In our case, our application is opened with a web address in an Internet Explorer 11 browser.

 

Can NVDA work with domain-specific web applications? If so, how should the addon be named? Are there any config settings I could use to create an alias (I believe this is how JAWS addresses this issue)?

 

I know I can create an addon for IE itself, but that option would likely interfere with other sites or applications run through IE, so I don’t want to go that route unless absolutely necessary.

 

Any guidance at all is greatly appreciated.

 

 

Julie Stoltz

Technical Communications Specialist

Cycom Data Systems, Inc.

www.cycominc.com

888-292-6688

 


Re: Process to make an NVDA app-specific addon for a web-based application

Noelia Ruiz
 

Hello, here are core developers of NVDA and they are experts in code.
I'm just an author and maintainer of some add-ons in collaboration
with community. I created placeMarkers add-on, in collaboration with
Chris and other contributors. You may be interested in looking at the
source code of this add-on, since it works in browse mode (in webpages
and other apps using it), and bookmarks and specific strings of text
to be searched are saved in files (in this case pickle and txt), to be
used in browse mode deppending on the title and other properties of
the website, so that they can work in different browsers:

https://github.com/nvdaes/placemarkers

Kind regards

2020-06-17 19:34 GMT+02:00, Julie Stoltz <jstoltz@...>:

Hi all,
I am very new to this group and the NVDA application, and I apologize if I
have missed anything critical in the steps to address this.

I searched the archives and development guide and did not find an answer to
my question.

Our company provides a web-based app to our clients. I have been looking
into NVDA and I see that it can be used to create application-specific
behavior. However, such addons are named for the executable file that opens
the application. In our case, our application is opened with a web address
in an Internet Explorer 11 browser.

Can NVDA work with domain-specific web applications? If so, how should the
addon be named? Are there any config settings I could use to create an alias
(I believe this is how JAWS addresses this issue)?

I know I can create an addon for IE itself, but that option would likely
interfere with other sites or applications run through IE, so I don't want
to go that route unless absolutely necessary.

Any guidance at all is greatly appreciated.


Julie Stoltz
Technical Communications Specialist
Cycom Data Systems, Inc.
www.cycominc.com<http://www.cycominc.com/>
888-292-6688





Process to make an NVDA app-specific addon for a web-based application

Julie Stoltz <jstoltz@...>
 

Hi all,

I am very new to this group and the NVDA application, and I apologize if I have missed anything critical in the steps to address this.

 

I searched the archives and development guide and did not find an answer to my question.

 

Our company provides a web-based app to our clients. I have been looking into NVDA and I see that it can be used to create application-specific behavior. However, such addons are named for the executable file that opens the application. In our case, our application is opened with a web address in an Internet Explorer 11 browser.

 

Can NVDA work with domain-specific web applications? If so, how should the addon be named? Are there any config settings I could use to create an alias (I believe this is how JAWS addresses this issue)?

 

I know I can create an addon for IE itself, but that option would likely interfere with other sites or applications run through IE, so I don’t want to go that route unless absolutely necessary.

 

Any guidance at all is greatly appreciated.

 

 

Julie Stoltz

Technical Communications Specialist

Cycom Data Systems, Inc.

www.cycominc.com

888-292-6688

 


new version of Nvda

Brian's Mail list account
 

2020.2 beta 1 is out


Is there anything in particular which we windows 7 folk need to check?
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