Comment 1 by jteh on 2013-05-06 23:41
Please be more specific. Is this a web application? Are you talking about browse mode quick navigation keys? Do you want to disable browse mode altogether? What do you mean by "screen issues"?

Comment 2 by tulip1387 on 2013-05-08 13:46
Hello,

Yes this is a web application where we use an onscreen keyboard. The browse mode quick navigation keys are causing the screen to attempt to shift upwards throwing the layout off. This happens whenever you press the "b" key, but we have fixed this issue. We have also noticed that we are receiving an error :

error executing event: caret on <NVDAObjects.Dynamic_EditableTextWithoutAutoSelectDetectionMSHTMLIAccessible object at 0x05997110> with extra args of {}

Could you please provide some light on what is causing this error?

Comment 3 by briang1 on 2013-05-08 16:10
So, what form do the active areas take here? Are you just clicking links or buttons?
What is the purpose of having an on screen keyboard, as I assume what is being typed on it also displays here, would it not be best just to provide an editable text area for blind use with a normal keyboard?

many commands and redirects of keys pressed are just going to be a nightmare. Maybe it needs to be in a pass through mode or something. If its using some sort of quick access system, this will happen differently in the main two browsers in any case.
I'd imagine if you could point the devs at a test site or explain more what you are attempting and why, it might aid in an answer being forthcoming.

Comment 4 by fatma.mehanna on 2014-01-21 12:55
Hi all,
I want this feature to be emplimented because in face book and twitter, there are some quick navigation keys they provide to let the users access some features in the page.

so, sometimes, we want to disable browse mode keys to access these features rather than pressing pass next through each time we want to use a shortcut of those.
i think it will be better if we have a script to toggle browse mode keys on and off.
specially, facebook main page is now working fine with google chrome, moreover, twitter clients sometimes are always broken and we are being forced to use the web site.
Thanks.

Comment 5 by jteh on 2014-01-21 14:08
You disable browse mode keys by switching to focus mode with NVDA+space.

Comment 6 by jteh on 2014-02-28 03:02
Closing as worksforme as per comment:5.
Changes:
Added labels: worksforme
State: closed

Comment 7 by ateu on 2014-07-26 11:05
Hi,

I've received some requests from the Portuguese list concerning this problem.
Some application, like Twitter and other, use quick navigation keys, and sometimes, this keys can cause conflict between NVDA keys and the keys used by the aplication. Therefore, this would be a good idea to disable quick navigation keys.

Comment 8 by jteh on 2014-07-27 23:27
See comment:5. You simply disable browse mode by switching to focus mode.

Comment 9 by mdcurran on 2015-06-09 23:32
We have decided to add the ability for single letter quick navigation to be toggled on and off separate from just completely switching to focus mode.

Comment 10 by Michael Curran <mick@... on 2015-06-09 23:33
In [b3c8514]:

Merge branch 'toggleSingleLetterNav' into next. Incubates #3203

Changes:
Added labels: incubating
State: reopened

Comment 12 by Michael Curran <mick@... on 2015-06-15 03:43
In [1d9596f]:

Merge branch 'toggleSingleLetterNav' into next. Fixes #5151. Incubates #3203.

Comment 13 by James Teh <jamie@... on 2015-07-10 05:26
In [b7be7c2]:

In browse mode, you can now toggle single letter navigation on and off by pressing NVDA+shift+space. When off, single letter keys are passed to the application, which is useful for some web applications such as Gmail, Twitter and Facebook.

Fixes #3203.

Changes:
Removed labels: incubating, worksforme
State: closed

Comment 14 by jteh on 2015-07-10 05:29
Changes:
Milestone changed from None to 2015.3