Date   

Re: Forcing an NVDA Search rather than a built-in search function

 

Thanks for the replies.

Gene, I was thinking that it might be possible that if I was still sitting in the edit box where you enter the search criteria that I might be in focus mode, rather than browse, but even forcing a "jump out" such that I know and can see that I am not in a context were text entry is possible, and automatic switching to browse mode has to have occurred, I'm still getting odd behavior.

The keyboard I'm using is the one that's built-in to my laptop and the one I've always used and generally used.  Right now, after having hit the period on the last sentence and being in the compose box for this message hitting NVDA+CTRL+F, while in Chrome, brought up the built-in Chrome search not the NVDA search.

Then jumping over to my Gmail tab I could get things to behave much more normally if I made sure I was out of the search criteria edit box after the search completed.  I think I'm going to try a full shutdown and restart, as this is one of those "just to bizarre to explain" behavior situations, and those often go away after power cycling.
--
Brian

 He discloses the workings of a mind to which incoherence lends an illusion of profundity.

         ~ T. De Vere White

    



Re: Forcing an NVDA Search rather than a built-in search function

Andre Fisher
 

This sounds like the user is still in focus mode when he invoked the
command. Note that focus mode can be on even if you are outside of an
edit box. In fact, the standard gmail site defaults to focus mode on
the first visit. As a button is a form field, if you were not placed
in focus mode automatically (see user guide), and you tab to a button,
you are still in focus mode until you toggle to browse mode.

On 1/11/17, Jacob Kruger <jacob@blindza.co.za> wrote:
Just worked fine for me using latest chrome, and, NVDA key + ctrl + F,
so, not sure what's happening.


Stay well


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

On 2017-01-11 23:10, Brian Vogel wrote:

OK, I'm getting similar "wacky" behavior out of JAWS 18 on the Gmail
inbox page as well. The first time I tried triggering a JAWS search
it said this feature is available only in a virtual document, such as
a web page. I have no idea what it thinks the Gmail inbox web page
is. When I tried it again it came up to search, but things I can see
on the page, including the "Select all conversations that match this
view" link come up with NADA.

I know I used the screen reader search function when writing up
instructions telling people how to get to certain "landmarks" on the
page without having to resort to brute force tabbing, which I despise
as a general technique because it's both a huge time waster and can be
really frustrating.

What on earth have I forgotten or am I missing here? By the way, I'm
using the latest NVDA and JAWS under Win10 Home 64-bit, build 14393.576
--
*/Brian/*

*//**/He discloses the workings of a mind to which incoherence
/**/lends an illusion of profundity./*

*/~ T. De Vere White/*



Re: Forcing an NVDA Search rather than a built-in search function

Jacob Kruger
 

Just worked fine for me using latest chrome, and, NVDA key + ctrl + F, so, not sure what's happening.


Stay well


Jacob Kruger
Blind Biker
Skype: BlindZA
"Resistance is futile, but, acceptance is versatile..."
On 2017-01-11 23:10, Brian Vogel wrote:

OK, I'm getting similar "wacky" behavior out of JAWS 18 on the Gmail inbox page as well.  The first time I tried triggering a JAWS search it said this feature is available only in a virtual document, such as a web page.  I have no idea what it thinks the Gmail inbox web page is.  When I tried it again it came up to search, but things I can see on the page, including the "Select all conversations that match this view" link come up with NADA.

I know I used the screen reader search function when writing up instructions telling people how to get to certain "landmarks" on the page without having to resort to brute force tabbing, which I despise as a general technique because it's both a huge time waster and can be really frustrating.

What on earth have I forgotten or am I missing here?  By the way, I'm using the latest NVDA and JAWS under Win10 Home 64-bit, build 14393.576
--
Brian

 He discloses the workings of a mind to which incoherence lends an illusion of profundity.

         ~ T. De Vere White

    




Re: Forcing an NVDA Search rather than a built-in search function

Gene
 

I don't know if others will have any suggestions but assuming you are in browse mode, whatever is causing the problem isn't general to other users. You never have to be on any structure to use search. 
As longt as you are in the web page and in browse mode, search should work wherever you are. 
 
I doubt this is related to the problem but what kind of keyboard are you using?
Gene 

----- Original Message -----
Gene
----- Original Message -----
Sent: Wednesday, January 11, 2017 3:01 PM
Subject: [nvda] Forcing an NVDA Search rather than a built-in search function

Hello All,

           I have got to be doing something wrong, but I'll be darned if I know what it might be, because sometimes using INS+CTRL+F (where INS is the NVDA Key) will cause the NVDA search dialog to pop up and other times it just brings up the native search function of the web browser I'm using at the moment.

           At first I thought it might be because I was in an edit box and I needed focus to be on a control object of some kind, but even if I tab to what NVDA announces as a button on the Gmail inbox page, in this specific case, I am unable to use single letter navigation to the next button nor to get INS+CTRL+F to bring up the NVDA search.  I'm getting the Firefox or Chrome browser search function, respectively, far more often than I am getting the NVDA search function.

           Is there some trick I can use, or something I need to be certain of, before invoking the NVDA search function to be sure I'll get the NVDA search function?  I need to test this some more with JAWS and Window Eyes, but I don't recall this same behavior occurring in those contexts.  I'll report back on whether I get the same behavior or not, because if I do I must be making the same mistake and if I don't I really have no idea what's up here.
--
Brian

 He discloses the workings of a mind to which incoherence lends an illusion of profundity.

         ~ T. De Vere White

    



Re: Forcing an NVDA Search rather than a built-in search function

 

OK, I'm getting similar "wacky" behavior out of JAWS 18 on the Gmail inbox page as well.  The first time I tried triggering a JAWS search it said this feature is available only in a virtual document, such as a web page.  I have no idea what it thinks the Gmail inbox web page is.  When I tried it again it came up to search, but things I can see on the page, including the "Select all conversations that match this view" link come up with NADA.

I know I used the screen reader search function when writing up instructions telling people how to get to certain "landmarks" on the page without having to resort to brute force tabbing, which I despise as a general technique because it's both a huge time waster and can be really frustrating.

What on earth have I forgotten or am I missing here?  By the way, I'm using the latest NVDA and JAWS under Win10 Home 64-bit, build 14393.576
--
Brian

 He discloses the workings of a mind to which incoherence lends an illusion of profundity.

         ~ T. De Vere White

    



Forcing an NVDA Search rather than a built-in search function

 

Hello All,

           I have got to be doing something wrong, but I'll be darned if I know what it might be, because sometimes using INS+CTRL+F (where INS is the NVDA Key) will cause the NVDA search dialog to pop up and other times it just brings up the native search function of the web browser I'm using at the moment.

           At first I thought it might be because I was in an edit box and I needed focus to be on a control object of some kind, but even if I tab to what NVDA announces as a button on the Gmail inbox page, in this specific case, I am unable to use single letter navigation to the next button nor to get INS+CTRL+F to bring up the NVDA search.  I'm getting the Firefox or Chrome browser search function, respectively, far more often than I am getting the NVDA search function.

           Is there some trick I can use, or something I need to be certain of, before invoking the NVDA search function to be sure I'll get the NVDA search function?  I need to test this some more with JAWS and Window Eyes, but I don't recall this same behavior occurring in those contexts.  I'll report back on whether I get the same behavior or not, because if I do I must be making the same mistake and if I don't I really have no idea what's up here.
--
Brian

 He discloses the workings of a mind to which incoherence lends an illusion of profundity.

         ~ T. De Vere White

    



having problem to use one of Baum braille displays by NVDA

داریوش جوادی
 

hi, I am Dariush Javadi. I have a Baum braille display (Frank
Audio-Data bk2-40). I want to use it by NVDA, but NVDA doesn’t
support it. It's an old version of Baum braille displays and work by
Jaws properly. Also it support windows 32 bit and lower. help me
pleas. Thanks a lot.


Re: who knows this problem?

Jacob
 

By default Windowù is set to restart on a critical error. I always turn this function off. I have a problem with some scanner software make the PC restart but when I turn this function off it runs anyway. Since I'm running a danish version of Windows I don't know exactly the name of the menu where you can turn it off. Try something like system setting, advanced setting and then setting for restart and recovery. Uncheck the automatically restart box. It'll at least make it possible for you to have a chance to read the error message.

OZ0TE Jacob

On 11. jan. 2017 at 19.43 P. Otter <pam.otter@...> wrote:

hello all, i have a 20 cels braille display, the hims syncbraille.
it works fine, all what i want it is nice displayed but there is only one problem, when i want to restart nvda, there comes a big error, i cann't see what the problem is, because the computer will reboot imidiately  this happens only whit that display, i allso have a 14 cels hims smart beetle, there are no problems when i'm restarting nvda.
what can that be?
cheers
paul otter
 


who knows this problem?

P. Otter
 

hello all, i have a 20 cels braille display, the hims syncbraille.
it works fine, all what i want it is nice displayed but there is only one problem, when i want to restart nvda, there comes a big error, i cann't see what the problem is, because the computer will reboot imidiately  this happens only whit that display, i allso have a 14 cels hims smart beetle, there are no problems when i'm restarting nvda.
what can that be?
cheers
paul otter
 


Re: NVDA problem with hashtag symbol

Life My Way
 

do you have a list of all the codes to make things work like this?

On 1/11/2017 3:33 AM, Paolo Leva wrote:

The Acapela TTS allows usage of special codes to get the TTS to laugh, cry, cough and so on. To get the desired sound you need to type for instance #LAUGH01#, #CRY01#, #COUGH01# and so on.

However NVDA seems to always process the # symbol even when you select to let it pass through to the TTS, so there seems to be no way to let these sounds work when using the Acapela TTS with NVDA, as NVDA always read like "pound sign laugh 0 1 pound sign"

I do not know whether this issue can be solved by configuration or needs some fix into the code, is anyone able to shed some light on it?

Thanks in advance!



Bug in danish contracted Braille

Jacob
 

I notice exactly the same problem both in NVDA and JAWS. Therefore I think it's related to LibLouis.

No matter if it's 6 og 8 dot I get some strange codes. For example in Windows Exprore data and time i shown like this:
file.txt /x200e 2017 /x200e 01 /x200e 11 /x200e 12:25.
If i turn off contraction it's shown normal with out the /x200e codes. I also see it often on websites and in Skype and nearly every any application. I try several displays and PC's running Win 7 and 10. What's the best way to report this bug?

OZ0TE Jacob


Re: For StationPlaylist Studio users: Add-on 17.01 posted

Joe Paton
 

Thanks joseph.
And a good new year to you.

JP

On Fri, 30 Dec 2016 09:01:00 -0800
"Joseph Lee" <joseph.lee22590@gmail.com> wrote:

Hi all.



For those using SPL Studio for broadcasting: add-on 17.01 is now available.
You can grab it via add-on update (SPL Assistant, Control+Shift+U).
Alternatively, visit the following page:

https://github.com/josephsl/stationPlaylist/releases/tag/17.01



This minor stable version provides enhancements and fixes for Cart Explorer,
as well as slight performance improvements when switching to Studio from
anywhere.


Re: NVDA and MalWare Bytes

 

For those who'd like the direct link to Gene's tutorial page for Malwarebytes 3.0, it is:

                         http://accessibilitycentral.net/How%20to%20navigate%20Malwarebytes%20Anti-Malware%20with%20NVDA.html

It took me a while to find it.

I've never used the premium version, just the home free version, and am still on 2.2.1.   My main purpose for having Malwarebytes, and having clients install it, is as an "in case of emergency" tool.  I run scans every once in a while, but I've never had a detection for real malware on any of my machines.  The most it's tagged is tracking cookies and PUPs (Potentially Unwanted Programs) - some of which were unwanted, others not.
--
Brian

 He discloses the workings of a mind to which incoherence lends an illusion of profundity.

         ~ T. De Vere White

    



Re: Adobe Reading by Page

 

Kelby,

         What you're describing is probably the interaction between several things you can set using the accessibility wizard in Adobe Reader (regardless of version).  If this is a large file you're dealing with (which, by default, would be 50 pages or more) it could very likely be the problem.

          I would use ALT+E,Y,S to run the accessibility setup wizard.  That key sequence is for Reader DC but I also don't think it has changed in a very long time.  If it is different then open the Edit menu, look for accessibility, and choose the setup wizard from the submenu.

          On the first dialog page, you may wish to activate the radio button to set only the accessibility settings options for screen readesr rather than using the default that walks you through screen reader and magnification accessibility settings.

           On the second dialog page you should leave the "Infer reading order from document (recommended)" radio button selected, and this is the default, or select it if it's been set to one of the other two settings,

            On the third dialog page activate the  "Read the entire document at once" radio button for large files.

            On the fourth, and final dialog page, you may wish to check the checkbox for "Reopen documents to the last viewed page" if you frequently deal with large documents and would rather that they "pick up where you last stopped" when you open them later.  Some people love this feature while others despise it with a burning passion.
--
Brian

 He discloses the workings of a mind to which incoherence lends an illusion of profundity.

         ~ T. De Vere White

    



Re: Adobe Reading by Page

Domingos de Oliveira <domingos20000@...>
 

You have to activarte in the accessibility options, that the whole
document is tagged at once and not only the actual page. I use the
reader in German, so I can't tell you where to find this option in the
englisch version.

2017-01-11 14:22 GMT+01:00, Greg Wocher <gwocher@gwocher.com>:

Hello,
Adobe Reader is not the only accessible PDF reader. It may be the only
accessible free one but there is one that costs $30. It is called QRead and
works well with NVDA.

Regards,
Greg Wocher

On Jan 11, 2017, at 5:14 AM, Walmir Schultz via Groups.Io
<wsautodidata=yahoo.com.br@groups.io> wrote:

I have the same problem. Changing the options in the Accessibility Wizard
don't solve the issue.

Unfortunately Adobe Reader is the only accessible PDF reader that works
wit NVDA.


Em 10/01/2017 12:27, kelby carlson escreveu:
All,

I'm having issues with NVDA and Adober Reader. In some PDF files where
I have to scroll down by page, when I get to the bottom of a page
before I can press ctrl-page down I get cycled back to the top of the
page. This is pretty annoying and I really haven't figured out how to
optimize NVDA with Adobe in general. Would appreciate pointers.






--
Domingos de Oliveira
- Online-Redakteur

Karthäuserstraße 13
53129 Bonn
Telefon: 017632245129
Web: www.oliveira-online.net
www.netz-barrierefrei.de
Mail: domingos20000@googlemail.com
USt-ID: DE273231108


Re: NVDA with Firefox Unable to manipulate Silver Light's controls

Brian's Mail list account <bglists@...>
 

Do they use Silverlight?
Are you sure? I'd tend to take Silverlight off and see if it falls back to use html 5 or flash instead.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Gerardo Corripio" <gera1027@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Wednesday, January 11, 2017 5:31 AM
Subject: [nvda] NVDA with Firefox Unable to manipulate Silver Light's controls


Hi guys
Any tips/tricks how with NVDA's latest and Firefox to work the playing of a video with Netflicks, that would allow me to change the language so as to be aboable to access the DVS track? I space or Enter where it says Language submenu, but nothing works to get into the options! The video either plays or pauses" I'm getting very very frustrated! Thanks for any info you guys might have, or if there's an audio tutorial demoing how to manipulate the Silver Light controls that would be awesome.

--
Enviado desde mi lap
Gerardo J Corripio Flores Psicólogo, Terapéuta Reiki
Saludos desde Tampico, Tamaulipas México



Re: Adobe Reading by Page

Greg Wocher
 

Hello,
Adobe Reader is not the only accessible PDF reader. It may be the only accessible free one but there is one that costs $30. It is called QRead and works well with NVDA.

Regards,
Greg Wocher

On Jan 11, 2017, at 5:14 AM, Walmir Schultz via Groups.Io <wsautodidata=yahoo.com.br@groups.io> wrote:

I have the same problem. Changing the options in the Accessibility Wizard don't solve the issue.

Unfortunately Adobe Reader is the only accessible PDF reader that works wit NVDA.


Em 10/01/2017 12:27, kelby carlson escreveu:
All,

I'm having issues with NVDA and Adober Reader. In some PDF files where
I have to scroll down by page, when I get to the bottom of a page
before I can press ctrl-page down I get cycled back to the top of the
page. This is pretty annoying and I really haven't figured out how to
optimize NVDA with Adobe in general. Would appreciate pointers.




Re: NVDA problem with hashtag symbol

ChrisLeo
 

See also the *builtin.dic* voice dictionary in the installed folder of NVDA.
This regexpt probabily it interferes with the string of the Acapela tags:

#Break words that have numbers at the end
Pattern: ((?:(?=\D)\w)+)(\d+)
Replacement: \1 \2

This means that e.g., the string "#LAUGH01#" changes in "#LAUGH 01#".
There is a space before the digits 01.





Chris.

ChrisLeo, 11/01/2017 11:15:

You set so?
Symbol: #
replacement: #
Level: Some
Preserve: always.

In the replacement edit write the symbol instead of the name.

Cheers,


Chris.

Paolo Leva, 11/01/2017 10:33:
The Acapela TTS allows usage of special codes to get the TTS to laugh,
cry, cough and so on. To get the desired sound you need to type for
instance #LAUGH01#, #CRY01#, #COUGH01# and so on.

However NVDA seems to always process the # symbol even when you select
to let it pass through to the TTS, so there seems to be no way to let
these sounds work when using the Acapela TTS with NVDA, as NVDA always
read like "pound sign laugh 0 1 pound sign"

I do not know whether this issue can be solved by configuration or
needs some fix into the code, is anyone able to shed some light on it?

Thanks in advance!


Re: NVDA problem with hashtag symbol

ChrisLeo
 

You set so?
Symbol: #
replacement: #
Level: Some
Preserve: always.

In the replacement edit write the symbol instead of the name.

Cheers,


Chris.

Paolo Leva, 11/01/2017 10:33:

The Acapela TTS allows usage of special codes to get the TTS to laugh, cry, cough and so on. To get the desired sound you need to type for instance #LAUGH01#, #CRY01#, #COUGH01# and so on.

However NVDA seems to always process the # symbol even when you select to let it pass through to the TTS, so there seems to be no way to let these sounds work when using the Acapela TTS with NVDA, as NVDA always read like "pound sign laugh 0 1 pound sign"

I do not know whether this issue can be solved by configuration or needs some fix into the code, is anyone able to shed some light on it?

Thanks in advance!


Re: Adobe Reading by Page

Walmir Schultz <wsautodidata@...>
 

I have the same problem. Changing the options in the Accessibility Wizard don't solve the issue.

Unfortunately Adobe Reader is the only accessible PDF reader that works wit NVDA.


Em 10/01/2017 12:27, kelby carlson escreveu:

All,

I'm having issues with NVDA and Adober Reader. In some PDF files where
I have to scroll down by page, when I get to the bottom of a page
before I can press ctrl-page down I get cycled back to the top of the
page. This is pretty annoying and I really haven't figured out how to
optimize NVDA with Adobe in general. Would appreciate pointers.