Date   

Re: NVDA Beta 4 error tone when opening outlook

 

Steve,

           For future reference, the posting of full NVDA logs or log segments on-group is strongly discouraged, because so very few are able to interpret these at all.  If an individual developer such as Joseph Lee or Quentin Christensen happen to request a log or log segment, please send that to them privately.  You can do that using the Reply to Sender link at the end of a message that the person you want to communicate with privately has sent to the group.
--

Brian - Windows 10 Pro, 64-Bit, Version 20H2, Build 19042  

The depths of denial one can be pushed to by outside forces of disapproval can make you not even recognize yourself to yourself.

       ~ Brian Vogel

 


Re: NVDA User Guide doesn't open in default browser

 

On Fri, Jan 29, 2021 at 12:42 AM, Louise Pfau wrote:
I haven't subscribed to the chat subgroup, because I get a lot of E-mail from the various groups I'm on.
-
This is not an encouragement (though I would encourage it) for you to join the Chat Subgroup, but for you to learn and use the tools that Groups.io gives you to control the traffic you actually get in your inbox for any/all of the groups you're subscribed to.

Groups.io allows the end user an exquisite level of control over what they do and do not receive as a subscriber to any group.  I wrote this tutorial so that people would have an easy reference guide as to how to control what they get:  Controlling the Messages You Receive via E-Mail from Groups.io (docx)

As Gene has noted, you can use the nomail option for any group and get nothing in your inbox, but can still check out that group on the Groups.io web interface.  You can also set up topic preview (detailed in the tutorial) where you get the first message in any new topic, but unless you choose to follow it, you will not receive any additional messages for that topic.  This can and does cut down on incoming traffic from a group immensely. 
--

Brian - Windows 10 Pro, 64-Bit, Version 20H2, Build 19042  

The depths of denial one can be pushed to by outside forces of disapproval can make you not even recognize yourself to yourself.

       ~ Brian Vogel

 


Re: SECURITY FEATURES

 

The myth, and it is a myth, that proprietary (closed-source) software is somehow "safer" has been disproven by many security experts.  There is a complete misunderstanding of what open-source even means.  Open-source software is available for anyone to view the source code, which makes it less susceptible to "sneaking something in" than closed-source software is (though I'll admit that virtually all proprietary software makers have good code security practices, as do any major open-source shops).  You cannot view proprietary source code, so you have no way of knowing what's actually in there.  The recent hack of Solar Winds was an excellent example that proprietary software, and ubiquitous proprietary software, can be hacked,

Open-source also does not mean that anyone on the street can literally waltz in and start editing the code for a project and have those changes send out into the world by that project.  The code used by NVDA, for instance, is managed using GitHub (which is now owned by Microsoft, but started out life as an open-source project itself), and goes through the same sort of rigorous tracking of what individual developers are pulling code, updating it, returning it for testing and, ultimately, distribution, as any commercially available software does.  The sad thing is that even many IT professionals do not realize that much of the software that they actually use is open-source software, and Microsoft includes quite a bit of open-source content in Windows.  From the Wikipedia page on GitHub:  From 2012 Microsoft became a significant user of GitHub, using it to host open-source projects and development tools such as .NET CoreChakra CoreMSBuildPowerShellPowerToysVisual Studio CodeWindows CalculatorWindows Terminal and the bulk of its product documentation (now to be found on Microsoft Docs).[31][32]

I also find your second initial question ironic.  That's not a jab at you, but at the widely held misconception that proprietary software, which one cannot examine the source code for or have your own security people analyze it if you were to so choose, is better at guaranteeing privacy/security than open-source software is.  You can't see or know what proprietary software is doing, therefore it's inherently less secure.  It depends entirely on trust and the desire of its maker to keep its reputation and market position (presuming we're talking a product like JAWS, which is very well established).  When competitors such as NVDA (and, now, Narrator) do appear on the scene they would have zero chance of making inroads if they were cavalier about exposing private data to the world.  Those who want to can actually examine the code for NVDA to see how it works.  The same cannot be said for proprietary software.
--

Brian - Windows 10 Pro, 64-Bit, Version 20H2, Build 19042  

The depths of denial one can be pushed to by outside forces of disapproval can make you not even recognize yourself to yourself.

       ~ Brian Vogel

 


Re: NVDA User Guide doesn't open in default browser

Gene
 

The chat list has some discussion but it isn't a lot of mail. Also, you can go nomail on the chat list and switch to receiving mail when you pose a question.

It may be that your settings indicate that Edge is the default browser, but something is wrong and it actually isn't. Try making another browser the default, then making Edge the default again. In situations where the default setting was lost, or never was properly made, doing this often corrects the situation.

Gene

-----Original Message-----
From: Louise Pfau
Sent: Thursday, January 28, 2021 11:42 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA User Guide doesn't open in default browser

Hi. I checked settings, and Edge is my default browser. I could navigate to the address bar in Windows Explorer, but it wasn't read as an editable control. I opened the NVDA user guide from the "Help" menu, "Start" menu, and the documentation folder in "Program Files" as described. I just tried to open a different web-based manual from the one that I mentioned in the original post, and it also opened in another browser. It doesn't look like this is unique to the NVDA user guide, as I first thought. I haven't subscribed to the chat subgroup, because I get a lot of E-mail from the various groups I'm on.

Thanks,

Louise


Re: NVDA User Guide doesn't open in default browser

Chris Mullins
 

Hi

Your default browser will be launched for http and https type links but I suspect the User Guide consists of a bunch of html files, so you have to check the Apps settings and you will probably find Edge is assigned to html.

 

Cheers

Chris

 

From: Chris via groups.io
Sent: 28 January 2021 23:10
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA User Guide doesn't open in default browser

 

I would check to see if edge is still your default browser, things can change without you realizing

 

Thats the only thing it could be

 

From: Louise Pfau
Sent: 28 January 2021 22:39
To: nvda@nvda.groups.io
Subject: [nvda] NVDA User Guide doesn't open in default browser

 

Hi.  I opened the NVDA User Guide to reference something, and I noticed that it didn't open in Microsoft Edge, which is set as my default browser.  Is the specific shortcut to the User Guide set to open in another browser?  I tried to open another web-based manual for comparison, and it opened in Edge.

Thanks,

Louise

 

 


SECURITY FEATURES

heaven.lists92@...
 

Dear List

 

Could one of the developers please contact me regarding the following queries:

 

  1. JAWS fanatics often reference the fact that JAWS has a closed source, paid licence, as the main reason for its increased security, especially in the workplace.  As NVDA is open source, many companies are scared to use it, since they are afraid of the security risks involved with opensource licences.  How do NVDA developers make sure that the source code for NVDA is secured so that hackers cannot attach trojans or viruses, etc to it.
  2. How do the developers make sure that information, such as personally identifiable information used in call centres and health institutions, is not at risk when using NVDA?

The reasons why I am asking these questions are as follows:

 

  1. I love using NVDA on my home computer and would really encourage anyone to use it with all the features it offers without a yearly over-priced subscription.
  2. I need to recommend screen reading software to some companies in South Africa who are scared of the risks involved in installing open source software.
  3. NVDA has so many more languages that it supports with braille and speech, while JAWS is quite limited. Furthermore, NVDA is simpler to use than JAWS and I would love to see it being implemented in more companies since it is free and legal, preventing companies from resorting to illegal software.

Thank you for your help

 

Heaven


Re: NVDA Beta 4 error tone when opening outlook

Steve Nutt
 

Hi Joseph,

 

OK, I just opened NVDA, then opened Outlook, got the error tone, and here’s the output from the log:-

 

INFO - __main__ (08:53:59.059) - MainThread (9824):

Starting NVDA version 2020.4beta4

INFO - core.main (08:53:59.832) - MainThread (9824):

Config dir: C:\Users\steve\AppData\Roaming\nvda

INFO - config.ConfigManager._loadConfig (08:53:59.832) - MainThread (9824):

Loading config: C:\Users\steve\AppData\Roaming\nvda\nvda.ini

INFO - core.main (08:53:59.931) - MainThread (9824):

Using Windows version 10.0.19042 workstation

INFO - core.main (08:53:59.931) - MainThread (9824):

Using Python version 3.7.9 (tags/v3.7.9:13c94747c7, Aug 17 2020, 18:01:55) [MSC v.1900 32 bit (Intel)]

INFO - core.main (08:53:59.931) - MainThread (9824):

Using comtypes version 1.1.7

INFO - core.main (08:53:59.931) - MainThread (9824):

Using configobj version 5.1.0 with validate version 1.0.1

INFO - synthDriverHandler.setSynth (08:54:00.389) - MainThread (9824):

Loaded synthDriver vocalizer

INFO - core.main (08:54:00.389) - MainThread (9824):

Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5 with six version 1.12.0

INFO - brailleInput.initialize (08:54:00.392) - MainThread (9824):

Braille input initialized

INFO - braille.initialize (08:54:00.392) - MainThread (9824):

Using liblouis version 3.16.1

INFO - braille.initialize (08:54:00.396) - MainThread (9824):

Using pySerial version 3.4

INFO - braille.BrailleHandler.setDisplayByName (08:54:00.402) - MainThread (9824):

Loaded braille display driver noBraille, current display has 0 cells.

INFO - core.main (08:54:00.586) - MainThread (9824):

Java Access Bridge support initialized

INFO - _UIAHandler.UIAHandler.MTAThreadFunc (08:54:00.601) - _UIAHandler.UIAHandler.MTAThread (17252):

UIAutomation: IUIAutomation6

INFO - core.main (08:54:00.814) - MainThread (9824):

NVDA initialized

ERROR - RPC process 19132 (nvda_slave.exe) (08:54:13.582) - Dummy-5 (8232):

__main__.main:

slave error

Traceback (most recent call last):

  File "nvda_slave.pyw", line 117, in main

  File "comHelper.pyc", line 22, in _lresultFromGetActiveObject

  File "comtypes\client\__init__.pyc", line 180, in GetActiveObject

  File "comtypes\__init__.pyc", line 1245, in GetActiveObject

  File "_ctypes/callproc.c", line 935, in GetResult

OSError: [WinError -2147221021] Operation unavailable

INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (08:54:18.910) - MainThread (9824):

Developer info for navigator object:

name: 'From Computer Room Services, Subject Your Computer Room Services Collection, Received Fri 29/01/2021 08:51, Size 14 KB,'

role: ROLE_LISTITEM

roleText: None

states: STATE_FOCUSABLE, STATE_SELECTABLE, STATE_FOCUSED, STATE_READONLY, STATE_SELECTED

isFocusable: True

hasFocus: True

Python object: <appModules.outlook.UIAGridRow object at 0x05DE4CF0>

Python class mro: (<class 'appModules.outlook.UIAGridRow'>, <class 'NVDAObjects.behaviors.RowWithFakeNavigation'>, <class 'NVDAObjects.UIA.UIA'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'documentBase.TextContainerObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <class 'garbageHandler.TrackedObject'>, <class 'object'>)

description: ''

location: RectLTWH(left=259, top=200, width=1182, height=24)

value: None

appModule: <'outlook' (appName 'outlook', process ID 14396) at address 748d790>

appModule.productName: 'Microsoft Outlook'

appModule.productVersion: '16.0.13530.20440'

TextInfo: <class 'NVDAObjects.NVDAObjectTextInfo'>

windowHandle: 77859248

windowClassName: 'OutlookGrid'

windowControlID: 4704

windowStyle: 1442840576

extendedWindowStyle: 0

windowThreadID: 15116

windowText: 'Table View'

displayText: ''

UIAElement: <POINTER(IUIAutomationElement) ptr=0x7b8c978 at 7482530>

UIA automationID:

UIA frameworkID:

UIA runtimeID: (42, 77859248, 4, -314)

UIA providerDescription: [pid:14396,providerId:0x0 Main(parent link):Unidentified Provider (unmanaged:OUTLOOK.EXE)]

UIA className: LeafRow

UIA patterns available: GridItemPattern, ScrollItemPattern, SelectionItemPattern, InvokePattern, ValuePattern, LegacyIAccessiblePattern

 

I hope this helps.

 

All the best


Steve

 

--

Computer Room Services

77 Exeter Close

Stevenage

Hertfordshire

SG1 4PW

T: +44(0)1438-742286

M: +44(0)7956-334938

F: +44(0)1438-759589

E: steve@...

W: https://www.comproom.co.uk

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Sent: 28 January 2021 18:20
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Beta 4 error tone when opening outlook

 

Hi all,

I can’t speak to NV Access, but personally whenever you hear an error tone from NvDA (alpha and beta snapshots), I advise opening log viewer (NVDA+F1) and look at lines above developer info statement as it will record the error and traceback information so we (developers) can diagnose the problem. This is more so if you hear error tones constantly (from anywhere).

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel
Sent: Thursday, January 28, 2021 10:17 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Beta 4 error tone when opening outlook

 

On Thu, Jan 28, 2021 at 01:07 PM, Gary Metzler wrote:

When using the beta this sound is normal.

-
Yes and no.  I agree with you, from a practical standpoint, that this tone generally doesn't indicate that anything's wrong that the end user would be concerned about unless there were an obvious bad behavior.  That being said, even in the beta it does indicate that an error condition of some sort has been encountered, and if your logging level happens to be set to debug you can look at the NVDA log to see what, exactly, it is that was not liked.
--

Brian - Windows 10 Pro, 64-Bit, Version 20H2, Build 19042  

The depths of denial one can be pushed to by outside forces of disapproval can make you not even recognize yourself to yourself.

       ~ Brian Vogel

 


Re: NVDA Beta 4 error tone when opening outlook

Steve Nutt
 

Hi Brian,

 

I will get the error and post it.  If I recall, it’s an operating system error.

 

I’m not sure it should be ignored.

 

All the best


Steve

 

--

Computer Room Services

77 Exeter Close

Stevenage

Hertfordshire

SG1 4PW

T: +44(0)1438-742286

M: +44(0)7956-334938

F: +44(0)1438-759589

E: steve@...

W: https://www.comproom.co.uk

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel
Sent: 28 January 2021 18:17
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Beta 4 error tone when opening outlook

 

On Thu, Jan 28, 2021 at 01:07 PM, Gary Metzler wrote:

When using the beta this sound is normal.

-
Yes and no.  I agree with you, from a practical standpoint, that this tone generally doesn't indicate that anything's wrong that the end user would be concerned about unless there were an obvious bad behavior.  That being said, even in the beta it does indicate that an error condition of some sort has been encountered, and if your logging level happens to be set to debug you can look at the NVDA log to see what, exactly, it is that was not liked.
--

Brian - Windows 10 Pro, 64-Bit, Version 20H2, Build 19042  

The depths of denial one can be pushed to by outside forces of disapproval can make you not even recognize yourself to yourself.

       ~ Brian Vogel

 


Re: NVDA User Guide doesn't open in default browser

Louise Pfau
 

Hi.  I checked settings, and Edge is my default browser.  I could navigate to the address bar in Windows Explorer, but it wasn't read as an editable control.  I opened the NVDA user guide from the "Help" menu, "Start" menu, and the documentation folder in "Program Files" as described.  I just tried to open a different web-based manual from the one that I mentioned in the original post, and it also opened in another browser.  It doesn't look like this is unique to the NVDA user guide, as I first thought.  I haven't subscribed to the chat subgroup, because I get a lot of E-mail from the various groups I'm on.

Thanks,

Louise


Re: NVDA User Guide doesn't open in default browser

Quentin Christensen
 

NVDA doesn't specify a browser to use, it launches the web page which opens in whatever your default browser for .html files is.  To check, you can launch the file manually.  Either:
- open the user guide from the help menu, select the address bar, paste into the address bar of File Explorer and press ENTER.
- Or if you have NVDA installed, go to: C:\Program Files (x86)\NVDA\documentation\en and press ENTER on any of the files.

You can check your default browser, by pressing the WINDOWS key, type "default apps" and press ENTER, then tab to "Web browser" .  if it's set to something other than what you want, press ENTER and select the desired browser from the list.

Kind regards

Quentin.

On Fri, Jan 29, 2021 at 10:10 AM Chris via groups.io <chrismedley=btinternet.com@groups.io> wrote:

I would check to see if edge is still your default browser, things can change without you realizing

 

Thats the only thing it could be

 

From: Louise Pfau
Sent: 28 January 2021 22:39
To: nvda@nvda.groups.io
Subject: [nvda] NVDA User Guide doesn't open in default browser

 

Hi.  I opened the NVDA User Guide to reference something, and I noticed that it didn't open in Microsoft Edge, which is set as my default browser.  Is the specific shortcut to the User Guide set to open in another browser?  I tried to open another web-based manual for comparison, and it opened in Edge.

Thanks,

Louise

 



--
Quentin Christensen
Training and Support Manager


Re: NVDA Beta 4 error tone when opening outlook

Quentin Christensen
 

Alpha and Beta builds play an error sound whenever an error is written to the log.  RC and stable builds will record exactly the same errors, but don't play a sound.  There are a number of situations where NVDA might record an error, however it then tries something else which works, and so most end users wouldn't notice anything amiss.

If you can reliably reproduce an error in that situation, as Joseph noted, you can find the exact errors in the log, do test if you can reproduce with add-ons disabled, and if so, it's still worth creating an issue on GitHub for: https://github.com/nvaccess/nvda/issues 

We'll prioritise issues which have an adverse reaction for users of course, but fixing such an error might still result in a smoother experience.

Kind regards

Quentin.

On Fri, Jan 29, 2021 at 5:19 AM Joseph Lee <joseph.lee22590@...> wrote:

Hi all,

I can’t speak to NV Access, but personally whenever you hear an error tone from NvDA (alpha and beta snapshots), I advise opening log viewer (NVDA+F1) and look at lines above developer info statement as it will record the error and traceback information so we (developers) can diagnose the problem. This is more so if you hear error tones constantly (from anywhere).

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel
Sent: Thursday, January 28, 2021 10:17 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Beta 4 error tone when opening outlook

 

On Thu, Jan 28, 2021 at 01:07 PM, Gary Metzler wrote:

When using the beta this sound is normal.

-
Yes and no.  I agree with you, from a practical standpoint, that this tone generally doesn't indicate that anything's wrong that the end user would be concerned about unless there were an obvious bad behavior.  That being said, even in the beta it does indicate that an error condition of some sort has been encountered, and if your logging level happens to be set to debug you can look at the NVDA log to see what, exactly, it is that was not liked.
--

Brian - Windows 10 Pro, 64-Bit, Version 20H2, Build 19042  

The depths of denial one can be pushed to by outside forces of disapproval can make you not even recognize yourself to yourself.

       ~ Brian Vogel

 



--
Quentin Christensen
Training and Support Manager


Re: NVDA User Guide doesn't open in default browser

Chris
 

I would check to see if edge is still your default browser, things can change without you realizing

 

Thats the only thing it could be

 

From: Louise Pfau
Sent: 28 January 2021 22:39
To: nvda@nvda.groups.io
Subject: [nvda] NVDA User Guide doesn't open in default browser

 

Hi.  I opened the NVDA User Guide to reference something, and I noticed that it didn't open in Microsoft Edge, which is set as my default browser.  Is the specific shortcut to the User Guide set to open in another browser?  I tried to open another web-based manual for comparison, and it opened in Edge.

Thanks,

Louise

 


NVDA User Guide doesn't open in default browser

Louise Pfau
 

Hi.  I opened the NVDA User Guide to reference something, and I noticed that it didn't open in Microsoft Edge, which is set as my default browser.  Is the specific shortcut to the User Guide set to open in another browser?  I tried to open another web-based manual for comparison, and it opened in Edge.

Thanks,

Louise


Re: message announced by NVDA

Jaffar Sidek <jaffar.sidek10@...>
 

Hi Joseph.   Yup I got your drift.  Thanks for the explanation.  Cheers!

On 29/1/2021 1:02 am, Joseph Lee wrote:

Hi,

The UIA issues I’m talking about can be caused either by the app in question or NVDA not knowing certain UIA properties fully. The former is the case with older Chromium Edge releases where UIA implementation from Edge is incomplete, the latter was the case when NVDA didn’t know about notification event for several weeks during Version 1709 era (October 2017-April 2018).

As for bringing Windows 10 App Essentials to NVDA, as I stated a few days ago, parts of it are available in NVDA now, and I plan to transfer more code from that add-on to NVDA. In fact, NVDA 2020.4 includes support for Windows 10 Calculator, which came directly from Windows 10 App Essentials. The next version of the add-on will include code that may become part of NVDA later, specifically initial support for updated emoji panel being tested by Windows Insiders on development channel (build 21300 series); it is too early to put that code into NVDA because the feature can change without notice, hence I’m letting folks give it a try by incorporating it into WinTenApps first.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Jaffar Sidek
Sent: Thursday, January 28, 2021 2:25 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] message announced by NVDA

 

Hi Joseph.  Correct me if I am wrong, but what you seem to be saying is that while WxWidgets uses MSAA as it's accessibility go to, NVDA itself relies on both the native Windows dialog and UIA to function properly, particularly with the more newly built apps.  If my assumption is correct, then your win10 issentials AddOn is bridging the gap so as to cause less of a conflict with access issues?  Would it then be better to embed Win10 issentials into NVDA itself?  Cheers!

On 28/1/2021 1:36 pm, Joseph Lee wrote:

Hi,

I think there’s another aspect to account for: it isn’t NVDA that has control over how messages are presented/announced: it is really wxWidgets that controls this. Part of the reason why NVDA’s user interface is accessible is because it isn’t NVDA that instructs Windows that its own message boxes are dialogs; rather, it is wxWidgets that reveals MSAA information to Windows about controls. Therefore, NVDA can announce its own dialog content simply because it is retrieving whatever accessibility API information Windows says about controls.

Speaking of GUI toolkits and NVDA: I’m researching how NVDA will work under more recent wxPython releases (currently NVDA is powered by wxPython 4.0.3 based on wxWidgets 3.0.5). More recent wxPython releases such as 4.1.1 are powered by wxWidgets development code, and tests show most NVDA controls and scenarios will work apart from a weird bug where you can’t perform NVDA commands while NVDA menu is opened and a huge lag when message boxes are open. So far, wxWidgets will use MSAA to reveal information about controls to Windows, and in extension, to NVDA. As opposed to this, QT offers an option to use UIA to communicate control information to Windows and NVDA, and anyone who have experimented with Windows 10 apps may have come across all sorts of UIA issues with apps such as Settings and Mail (these are powered by all sorts of GUI toolkits which uses UIA to talk about controls; UIA issues is another reason why I release Windows 10 App Essentials development builds on a weekly basis).

Hope this helps.

Cheers,

JOseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of bering.p
Sent: Wednesday, January 27, 2021 9:24 PM
To: nvda@nvda.groups.io
Subject: [nvda] message announced by NVDA

 

Thank you Joseph for your reply.
I am satisfied with the general behavior of NVDA regarding the announcement of the object description.
But I think in the case of a message issued by NVDA using gui.messageBox and which
presents only a dialog box with a text and one or two buttons, the text must be announced whatever the state of the option.
obviously, this is a point of view and I am perhaps the only one to deactivate the announcement of the description of the objects for the "normal configuratio" profiln.
Best regards
Paul.



Paul.

Le 28/01/2021 04:36, Joseph Lee a écrit :

Hi,

An object’s description is typically retrieved through accessibility API’s, although screen readers can customize certain behavior. This is the approach used by NVDA: NvDA defines dialog text as a dialog’s description. As you’ve observed, if report object descriptions is off, NVDA will not announce description text for controls such as dialog text.

As for defining messages NVDA should announce all the time, in theory, it might be possible. In practice though, think about the following:

  1. Different people have different ways to define what “essential” messages are. Some would say dialog text should be announced all the time, while others may say NVDA should announce clipboard operations including in places where you can’t copy or paste things.
  2. Screen readers do not possess hundreds of magnifying glasses; that is, screen readers cannot announce everything on the screen.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of bering.p
Sent: Wednesday, January 27, 2021 7:10 PM
To: nvda courrier <nvda@nvda.groups.io>
Subject: [nvda] message announced by NVDA

 

Hi.
I am surprised that this question is not answered .
So I return in my box with it.
Best regards.
Paul.

Le 23/01/2021 09:56, bering.p a écrit :

Hi to all.
I am sharing with you an observation I made concerning the announcement of messages by NVDA and which may be the subject of a PR.

When the option "Report object descriptions" is disabled, NVDA does not speak the text in dialog boxes.
This is annoying when it comes to a message informing the user or questioning him.
For example:
- following a manual search for update request.
- when an add-on uses "gui.messageBox" to query the user.

In this case, it is necessary to read the contents of the dialog box using "NVDA + b".

I think that any message emitted by NVDA should be announced regardless of the state of activation of the option.
What do you think ?
And if you agree, please do the PR.
best regards.
Paul.

 

 


is there an addon for signal?

Ibrahim Abedrabbo
 

Hi folks,

I am gradually transitioning from WhatsApp messenger to signal messenger. I installed the signal desktop client and it seems to be fine except  in reading group messages. Does anyone know if there is an NVDA add on for signal?

Cheers,

 

Ibrahim


Re: unigram accessibility

Lino Morales
 

Your better off using de Shark da doot da doot with Doug Lee's scripts buddy.

On 1/28/2021 12:41 AM, Governor staten wrote:
Hello list. I Downloaded an add-on for Unigram. It doesn't seem to do much. Is there more than one add-on out there? It could be that the program has changed and the add-on no longer works. Any help with this would be most appreciated.





Re: Focus Blue 4th generation problem?

Chantelle Buys
 

Thanks.

I'm also thinking that it's a display problem but, how to fix it?

Is there no way to reset a display to factory default?

Chantelle

On 1/28/21, Bob Cavanaugh <cavbob1993@gmail.com> wrote:
I'm going to take a wild guess on the problem of NVDA resetting your
settings to no braille. There's an option, I think off by default,
that reads "save configuration on exit." If this is unchecked, next
time NVDA starts, it will load the configuration it has saved. As for
your other problem, I have no idea but since you say the same thing
happens on your phone, I'd guess it's a braille display problem.

On 1/28/21, Chantelle Buys <cbuys6@gmail.com> wrote:
Afternoon everyone.

Just a quick question. I have a Focus Blue 40 cell display to try out
and have run into a strange problem.

Nvda resets the settings to no braille each time I restart the program
and for some or other reason, when you try to type lets say the
alphabet, it does the strangest thing. I would get the letters A/b
but, when I want to type c/d and so on, it would show other braille
symbols instead. I also realized that when I press dot1/4/7/8 after
pressing the power key to get to menu, the display won't do anything.

So, the same happens on android/IOS and since I don't know what's
going on here I just want to ask if any nvda user knows how to get the
braille keyboard to work the right way around and if somethings gone
wrong with the display?

Chantelle

--
Never give up, at any cost.









--
Never give up, at any cost.


Re: Focus Blue 4th generation problem?

Bob Cavanaugh <cavbob1993@...>
 

I'm going to take a wild guess on the problem of NVDA resetting your
settings to no braille. There's an option, I think off by default,
that reads "save configuration on exit." If this is unchecked, next
time NVDA starts, it will load the configuration it has saved. As for
your other problem, I have no idea but since you say the same thing
happens on your phone, I'd guess it's a braille display problem.

On 1/28/21, Chantelle Buys <cbuys6@gmail.com> wrote:
Afternoon everyone.

Just a quick question. I have a Focus Blue 40 cell display to try out
and have run into a strange problem.

Nvda resets the settings to no braille each time I restart the program
and for some or other reason, when you try to type lets say the
alphabet, it does the strangest thing. I would get the letters A/b
but, when I want to type c/d and so on, it would show other braille
symbols instead. I also realized that when I press dot1/4/7/8 after
pressing the power key to get to menu, the display won't do anything.

So, the same happens on android/IOS and since I don't know what's
going on here I just want to ask if any nvda user knows how to get the
braille keyboard to work the right way around and if somethings gone
wrong with the display?

Chantelle

--
Never give up, at any cost.






Re: NVDA Beta 4 error tone when opening outlook

 

Hi all,

I can’t speak to NV Access, but personally whenever you hear an error tone from NvDA (alpha and beta snapshots), I advise opening log viewer (NVDA+F1) and look at lines above developer info statement as it will record the error and traceback information so we (developers) can diagnose the problem. This is more so if you hear error tones constantly (from anywhere).

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel
Sent: Thursday, January 28, 2021 10:17 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Beta 4 error tone when opening outlook

 

On Thu, Jan 28, 2021 at 01:07 PM, Gary Metzler wrote:

When using the beta this sound is normal.

-
Yes and no.  I agree with you, from a practical standpoint, that this tone generally doesn't indicate that anything's wrong that the end user would be concerned about unless there were an obvious bad behavior.  That being said, even in the beta it does indicate that an error condition of some sort has been encountered, and if your logging level happens to be set to debug you can look at the NVDA log to see what, exactly, it is that was not liked.
--

Brian - Windows 10 Pro, 64-Bit, Version 20H2, Build 19042  

The depths of denial one can be pushed to by outside forces of disapproval can make you not even recognize yourself to yourself.

       ~ Brian Vogel

 


Re: NVDA Beta 4 error tone when opening outlook

 

On Thu, Jan 28, 2021 at 01:07 PM, Gary Metzler wrote:
When using the beta this sound is normal.
-
Yes and no.  I agree with you, from a practical standpoint, that this tone generally doesn't indicate that anything's wrong that the end user would be concerned about unless there were an obvious bad behavior.  That being said, even in the beta it does indicate that an error condition of some sort has been encountered, and if your logging level happens to be set to debug you can look at the NVDA log to see what, exactly, it is that was not liked.
--

Brian - Windows 10 Pro, 64-Bit, Version 20H2, Build 19042  

The depths of denial one can be pushed to by outside forces of disapproval can make you not even recognize yourself to yourself.

       ~ Brian Vogel

 

5501 - 5520 of 86669