Date   

Re: Does anyone have any tips for clicking on links that won’t click with NVDA

Gene
 

Did you try object navigation? 
 
Gene

-----Original Message-----
Sent: Friday, August 06, 2021 11:41 AM
Subject: [nvda] Does anyone have any tips for clicking on links that won’t click with NVDA
 
I’m using A website calledCACs Enterprise by CGI it’s a billing and payment platform, one of the problems I’m having is that there is a link which is actually a hover over menu, so hovering over it with the mouse will open up a list of other options but NVDA sees it only as a link.
i’ve tried clicking it but I’ve had no luck, and pressing shift plus NVDA  plus M to move the mouse over it, NVDA will read out the options on the list but there is no way to get at them to click them.
Does anyone have any ideas or tips?


Does anyone have any tips for clicking on links that won’t click with NVDA

Khalid Anwar
 

I’m using A website calledCACs Enterprise by CGI it’s a billing and payment platform, one of the problems I’m having is that there is a link which is actually a hover over menu, so hovering over it with the mouse will open up a list of other options but NVDA sees it only as a link.
i’ve tried clicking it but I’ve had no luck, and pressing shift plus NVDA  plus M to move the mouse over it, NVDA will read out the options on the list but there is no way to get at them to click them.
Does anyone have any ideas or tips?


Re: Resource: Youtube Video From Thee Quinn: How to Use Microsoft Access With NVDA: Part 1

tim
 

You know its interesting just how far and how much its lost with JFW and its access with Microsoft office products have dropped.

When i beta tested office 4.3 with JFW 3 it was totally accessible.

However, that was under henter Joyce and he wanted Office to be the power for those that work.

Now you have to fight for the accessibility he tried to achieve.

Thanks to him I got A's for all my Microsoft classes witch got me in the beta program. Back then office was so easy everything worked..

On 8/6/2021 10:37 AM, Brian Vogel wrote:
While I'll agree that any method to use MS-Access with a screen reader that works is absolutely amazing, this is an instance where I think that "going the GUI route" is a way to make things far, far more difficult than they need be.

I cut my teeth with databases before the age of the GUI interface learning SQL, which is still very widely in use to this day and which is supported (or was, anyway) by MS-Access and a lot of other relational databases.

The amount of work to learn SQL to commit and manipulate databases is not herculean.  The ability to deal with it when you're a screen reader user, since SQL is just plain text code, and pretty directly understandable plain text code for most of the basic database wizardry, it's just so much easier to deal with overall.  And that even applies to report formatting and generation.  

It's worth having a look at SQL as a possible option.  You might be pleasantly surprised at what you find.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

Nothing in all the world is more dangerous than sincere ignorance and conscientious stupidity.

         ~Martin Luther King, Jr.

 


Adobe DC Pro crashes with NVDA

falkogiepmans@...
 

Hi all,

I have someone whose Adobe Reader DC Pro crashes when reading PDF files. He got the following setup:

Windows versie: 1909 (Enterprise)

Adobe Acrobat Pro DC versie: 2021.005.20048

NVDA 2021.1

When opening a PDF with Adobe Acrobat Pro NVDA starts loading. When that finishes we step trhough the document with down arrow but Adobe gives a crash report shortly after that. I will paste that below if there is a wizard that can read that.
The reason why I post it here is because this only occurs with NVDA. I get a "frozen in stack" error as in the nvda.log snippet below.

I have tried COM Registration fix tool and updated from 2020.4 to 2021.1 but those did not change the problem. Is there someone that might know what this is and how to potentionally fix this?

Kind regards,
Falko


NVDA LOG SNIPPET


ERROR - watchdog._watcher (13:43:17.729) - watchdog (7856):
Core frozen in stack!
INFO - watchdog._watcher (13:43:17.805) - watchdog (7856):
Listing stacks for Python threads:
Python stack for thread 12924 (Dummy-2):
  File "comtypes\_comobject.pyc", line 148, in call_without_this
  File "_UIAHandler.pyc", line 534, in IUIAutomationFocusChangedEventHandler_HandleFocusChangedEvent
  File "_UIAHandler.pyc", line 859, in isNativeUIAElement
  File "_UIAHandler.pyc", line 838, in getNearestWindowHandle
  File "comtypesMonkeyPatches.pyc", line 27, in __call__

Python stack for thread 2728 (watchdog.CancellableCallThread.execute(<_FuncPtr object at 0x0C12AC60>)):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "watchdog.pyc", line 332, in run
  File "threading.pyc", line 552, in wait
  File "threading.pyc", line 296, in wait

Python stack for thread 12388 (visionEnhancementProviders.NVDAHighlighter.NVDAHighlighter):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "threading.pyc", line 870, in run
  File "visionEnhancementProviders\NVDAHighlighter.pyc", line 454, in _run
  File "winUser.pyc", line 425, in getMessage

Python stack for thread 7856 (watchdog):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "threading.pyc", line 870, in run
  File "watchdog.pyc", line 141, in _watcher
  File "watchdog.pyc", line 62, in getFormattedStacksForAllThreads

Python stack for thread 19672 (touchHandler.TouchHandler):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "touchHandler.pyc", line 241, in run

Python stack for thread 2192 (winInputHook):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "threading.pyc", line 870, in run
  File "winInputHook.pyc", line 79, in hookThreadFunc

Python stack for thread 3776 (_UIAHandler.UIAHandler.MTAThread):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "threading.pyc", line 870, in run
  File "_UIAHandler.pyc", line 340, in MTAThreadFunc
  File "queue.pyc", line 170, in get
  File "threading.pyc", line 296, in wait

Python stack for thread 4296 (braille._BgThread):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "threading.pyc", line 870, in run
  File "braille.pyc", line 2199, in func

Python stack for thread 19644 (Thread-1):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "C:\Users\C40813\AppData\Roaming\nvda\addons\vocalizer-driver\synthDrivers\vocalizer\_vocalizer.py", line 32, in run
    func, args, kwargs = bgQueue.get()
  File "queue.pyc", line 170, in get
  File "threading.pyc", line 296, in wait

Python stack for thread 15012 (MainThread):
  File "nvda.pyw", line 359, in <module>
  File "core.pyc", line 750, in main
  File "wx\core.pyc", line 2237, in MainLoop
  File "gui\__init__.pyc", line 838, in Notify
  File "core.pyc", line 712, in run
  File "queueHandler.pyc", line 88, in pumpAll
  File "queueHandler.pyc", line 55, in flushQueue
  File "scriptHandler.pyc", line 162, in _queueScriptCallback
  File "keyboardHandler.pyc", line 516, in executeScript
  File "inputCore.pyc", line 202, in executeScript
  File "scriptHandler.pyc", line 208, in executeScript
  File "cursorManager.pyc", line 243, in script_moveByCharacter_forward
  File "cursorManager.pyc", line 165, in _caretMovementScriptHelper
  File "browseMode.pyc", line 1347, in _set_selection
  File "review.pyc", line 177, in handleCaretMove
  File "api.pyc", line 220, in setReviewPosition
  File "vision\visionHandler.pyc", line 314, in handleReviewMove
  File "extensionPoints\__init__.pyc", line 47, in notify
  File "extensionPoints\util.pyc", line 170, in callWithSupportedKwargs
  File "visionEnhancementProviders\NVDAHighlighter.pyc", line 484, in handleReviewMove
  File "visionEnhancementProviders\NVDAHighlighter.pyc", line 471, in updateContextRect
  File "vision\util.pyc", line 72, in getContextRect
  File "api.pyc", line 234, in getNavigatorObject
  File "baseObject.pyc", line 26, in __get__
  File "textInfos\offsets.pyc", line 483, in _get_NVDAObjectAtStart
  File "virtualBuffers\__init__.pyc", line 180, in _getNVDAObjectFromOffset
  File "virtualBuffers\__init__.pyc", line 155, in _getFieldIdentifierFromOffset

ERROR - watchdog._watcher (13:43:32.757) - watchdog (7856):
Core frozen in stack!
INFO - watchdog._watcher (13:43:32.767) - watchdog (7856):
Listing stacks for Python threads:
Python stack for thread 2728 (watchdog.CancellableCallThread.execute(<_FuncPtr object at 0x0C12AC60>)):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "watchdog.pyc", line 332, in run
  File "threading.pyc", line 552, in wait
  File "threading.pyc", line 296, in wait

Python stack for thread 12388 (visionEnhancementProviders.NVDAHighlighter.NVDAHighlighter):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "threading.pyc", line 870, in run
  File "visionEnhancementProviders\NVDAHighlighter.pyc", line 452, in _run
  File "winUser.pyc", line 425, in getMessage

Python stack for thread 7856 (watchdog):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "threading.pyc", line 870, in run
  File "watchdog.pyc", line 141, in _watcher
  File "watchdog.pyc", line 62, in getFormattedStacksForAllThreads

Python stack for thread 19672 (touchHandler.TouchHandler):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "touchHandler.pyc", line 241, in run

Python stack for thread 2192 (winInputHook):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "threading.pyc", line 870, in run
  File "winInputHook.pyc", line 79, in hookThreadFunc

Python stack for thread 3776 (_UIAHandler.UIAHandler.MTAThread):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "threading.pyc", line 870, in run
  File "_UIAHandler.pyc", line 340, in MTAThreadFunc
  File "queue.pyc", line 170, in get
  File "threading.pyc", line 296, in wait

Python stack for thread 4296 (braille._BgThread):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "threading.pyc", line 870, in run
  File "braille.pyc", line 2199, in func

Python stack for thread 19644 (Thread-1):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "C:\Users\C40813\AppData\Roaming\nvda\addons\vocalizer-driver\synthDrivers\vocalizer\_vocalizer.py", line 32, in run
    func, args, kwargs = bgQueue.get()
  File "queue.pyc", line 170, in get
  File "threading.pyc", line 296, in wait

Python stack for thread 15012 (MainThread):
  File "nvda.pyw", line 359, in <module>
  File "core.pyc", line 750, in main
  File "wx\core.pyc", line 2237, in MainLoop
  File "gui\__init__.pyc", line 838, in Notify
  File "core.pyc", line 712, in run
  File "queueHandler.pyc", line 88, in pumpAll
  File "queueHandler.pyc", line 55, in flushQueue
  File "scriptHandler.pyc", line 162, in _queueScriptCallback
  File "keyboardHandler.pyc", line 516, in executeScript
  File "inputCore.pyc", line 202, in executeScript
  File "scriptHandler.pyc", line 208, in executeScript
  File "cursorManager.pyc", line 243, in script_moveByCharacter_forward
  File "cursorManager.pyc", line 165, in _caretMovementScriptHelper
  File "browseMode.pyc", line 1347, in _set_selection
  File "review.pyc", line 177, in handleCaretMove
  File "api.pyc", line 220, in setReviewPosition
  File "vision\visionHandler.pyc", line 314, in handleReviewMove
  File "extensionPoints\__init__.pyc", line 47, in notify
  File "extensionPoints\util.pyc", line 170, in callWithSupportedKwargs
  File "visionEnhancementProviders\NVDAHighlighter.pyc", line 484, in handleReviewMove
  File "visionEnhancementProviders\NVDAHighlighter.pyc", line 471, in updateContextRect
  File "vision\util.pyc", line 72, in getContextRect
  File "api.pyc", line 234, in getNavigatorObject
  File "baseObject.pyc", line 26, in __get__
  File "textInfos\offsets.pyc", line 483, in _get_NVDAObjectAtStart
  File "virtualBuffers\__init__.pyc", line 180, in _getNVDAObjectFromOffset
  File "virtualBuffers\__init__.pyc", line 155, in _getFieldIdentifierFromOffset




END OF NVDA LOG SNIPPET







START OF ADOBE REPORT CRASH

<?xml version="1.0"?>

<!DOCTYPE AdobeCrashReport SYSTEM "AdobeCrashReporter.dtd">

<crashreport serviceVersion="4.7.0" clientVersion="4.7.0" applicationName="Adobe Acrobat" applicationVersion="21.005.20048" build="0" source="Windows-Client-WER" crashType="n/a">

<time year="2021" month="7" day="9" hour="13" minute="38" second="3" timeoffset="60" timezone="West-Europa (zomertijd)"/>

<user guid="f69f073f-3072-436b-b63d-1d674976076d"/>

<system platform="Windows 10 Enterprise" osversion="10.0" osbuild="18363" applicationlanguage="nl-nl" userlanguage="nl-NL" oslanguage="en-GB" ram="16194" machine="Intel(R) Core(TM) i5-8365U CPU @ 1.60GHz" model="Intel64 Family 6 Model 142 Stepping 12" cpuCount="8" cpuType="586" cpuFreq="1896 MHz" processorArchitecture="0"/>

<gpu>

<gpuinfo availability="Running/Full Power" adapterCompatibility="Intel Corporation" adapterRAM="1024 MB" caption="Intel(R) UHD Graphics 620" description="Intel(R) UHD Graphics 620" driverDate="20190925000000.000000-000" driverVersion="26.20.100.7262" videoModeDescription="2560 x 1440 x 4294967296 kleuren" pnpDeviceID="PCI&#92;VEN_8086&#38;DEV_3EA0&#38;SUBSYS_08E11028&#38;REV_02&#92;3&#38;11583659&#38;0&#38;10" installedDisplayDrivers="igd10iumd64.dll,igd12umd64.dll,igdumdim64.dll"/>

</gpu>

<crash exception="EXCEPTION_ACCESS_VIOLATION" exceptionCode="0xc0000005" instruction="0x0EE4146B">

<backtrace crashedThread="0">

<thread index="0">

<stackStatement index="0" address="0x000000000EE4146B" symbolname="ObsoleteProc"/>

<stackStatement index="1" address="0x000000000EE2C5F2" symbolname="ObsoleteProc"/>

<stackStatement index="2" address="0x00000000796405AA" symbolname="AIDE::PixelPartInfo::operator="/>

<stackStatement index="3" address="0x0000000078A7997F" symbolname="PlugInMain"/>

<stackStatement index="4" address="0x000000007752FC24" symbolname="NdrByteCountPointerUnmarshall"/>

<stackStatement index="5" address="0x00000000774F4D02" symbolname="NdrStubCall2"/>

<stackStatement index="6" address="0x0000000076349A6D" symbolname="CStdStubBuffer_Invoke"/>

<stackStatement index="7" address="0x0000000075FA5DB2" symbolname="OACleanup"/>

<stackStatement index="8" address="0x0000000076349878" symbolname="WindowsIsStringEmpty"/>

<stackStatement index="9" address="0x0000000076349413" symbolname="WindowsIsStringEmpty"/>

<stackStatement index="10" address="0x00000000762FB5F1" symbolname="CStdStubBuffer_AddRef"/>

<stackStatement index="11" address="0x000000007631B9C1" symbolname="RoGetApartmentIdentifier"/>

<stackStatement index="12" address="0x00000000762FC3E7" symbolname="CStdStubBuffer_AddRef"/>

<stackStatement index="13" address="0x00000000762FDAEB" symbolname="CStdStubBuffer_AddRef"/>

<stackStatement index="14" address="0x00000000762F93AA" symbolname="CoTaskMemFree"/>

<stackStatement index="15" address="0x0000000075A847AB" symbolname="AddClipboardFormatListener"/>

<stackStatement index="16" address="0x0000000075A652AC" symbolname="CallWindowProcW"/>

<stackStatement index="17" address="0x0000000075A643FE" symbolname="DispatchMessageW"/>

<stackStatement index="18" address="0x0000000075A641E0" symbolname="DispatchMessageW"/>

<stackStatement index="19" address="0x0000000078BB017E" symbolname="DllCanUnloadNow"/>

<stackStatement index="20" address="0x0000000078BAFEBE" symbolname="DllCanUnloadNow"/>

<stackStatement index="21" address="0x0000000078BAFD54" symbolname="DllCanUnloadNow"/>

<stackStatement index="22" address="0x0000000078B326C1" symbolname="AcroWinMainSandbox"/>

<stackStatement index="23" address="0x0000000078B32169" symbolname="AcroWinMainSandbox"/>

<stackStatement index="24" address="0x000000000015B6C1" symbolname="unknown"/>

<stackStatement index="25" address="0x000000000030BCCA" symbolname="IsSandboxedProcess"/>

<stackStatement index="26" address="0x0000000074EB6359" symbolname="BaseThreadInitThunk"/>

<stackStatement index="27" address="0x00000000776287A4" symbolname="RtlGetAppContainerNamedObjectPath"/>

<stackStatement index="28" address="0x0000000077628774" symbolname="RtlGetAppContainerNamedObjectPath"/>

</thread>

</backtrace>

<registerSet>

<register name="EAX" value="0x0000000000001446"/>

<register name="EBX" value="0x00000000050FEA00"/>

<register name="ECX" value="0x000000000000FFFF"/>

<register name="EDX" value="0x0000000010000000"/>

<register name="ESI" value="0x0000000000000001"/>

<register name="EDI" value="0x0000000000000000"/>

<register name="ESP" value="0x00000000050FE800"/>

<register name="EBP" value="0x00000000050FE808"/>

<register name="EIP" value="0x000000000EE4146B"/>

<register name="EFL" value="0x0000000000010217"/>

</registerSet>

 

<binaryImageSet>

<binaryImage start="0x0000000000150000" end="0x00000000004F6000" path="adobe\Acrobat.exe"/>

<binaryImage start="0x00000000775C0000" end="0x000000007775A000" path="ntdll.dll"/>

<binaryImage start="0x0000000074EA0000" end="0x0000000074F80000" path="kernel32.dll"/>

<binaryImage start="0x0000000075D00000" end="0x0000000075EFF000" path="KERNELBASE.dll"/>

<binaryImage start="0x0000000075A40000" end="0x0000000075BD8000" path="user32.dll"/>

<binaryImage start="0x0000000076DA0000" end="0x0000000076DB7000" path="win32u.dll"/>

<binaryImage start="0x0000000075580000" end="0x00000000755A1000" path="gdi32.dll"/>

<binaryImage start="0x0000000077160000" end="0x00000000772BD000" path="gdi32full.dll"/>

<binaryImage start="0x00000000760D0000" end="0x000000007614C000" path="msvcp_win.dll"/>

<binaryImage start="0x0000000075BE0000" end="0x0000000075D00000" path="ucrtbase.dll"/>

<binaryImage start="0x0000000076C40000" end="0x0000000076CBA000" path="advapi32.dll"/>

<binaryImage start="0x0000000076530000" end="0x00000000765EF000" path="msvcrt.dll"/>

<binaryImage start="0x0000000075500000" end="0x0000000075576000" path="sechost.dll"/>

<binaryImage start="0x00000000774F0000" end="0x00000000775AB000" path="rpcrt4.dll"/>

<binaryImage start="0x0000000074D80000" end="0x0000000074DA0000" path="sspicli.dll"/>

<binaryImage start="0x0000000074D70000" end="0x0000000074D7A000" path="CRYPTBASE.dll"/>

<binaryImage start="0x0000000075F00000" end="0x0000000075F62000" path="bcryptPrimitives.dll"/>

<binaryImage start="0x0000000076150000" end="0x0000000076194000" path="shlwapi.dll"/>

<binaryImage start="0x0000000076250000" end="0x00000000764C7000" path="combase.dll"/>

<binaryImage start="0x0000000073E20000" end="0x0000000073E28000" path="version.dll"/>

<binaryImage start="0x00000000772F0000" end="0x0000000077315000" path="imm32.dll"/>

<binaryImage start="0x000000006BEE0000" end="0x000000006C0EF000" path="comctl32.dll"/>

<binaryImage start="0x0000000070980000" end="0x00000000709A9000" path="ntmarta.dll"/>

<binaryImage start="0x000000006BBC0000" end="0x000000006BC18000" path="prntm.dll"/>

<binaryImage start="0x0000000074DA0000" end="0x0000000074E97000" path="ole32.dll"/>

<binaryImage start="0x00000000707A0000" end="0x000000007080B000" path="winspool.drv"/>

<binaryImage start="0x0000000075F80000" end="0x0000000076012000" path="oleaut32.dll"/>

<binaryImage start="0x000000006C4E0000" end="0x000000006C4EA000" path="secur32.dll"/>

<binaryImage start="0x0000000076DC0000" end="0x0000000076DCF000" path="kernel.appcore.dll"/>

<binaryImage start="0x0000000076F30000" end="0x0000000076F49000" path="bcrypt.dll"/>

<binaryImage start="0x000000006BC20000" end="0x000000006BD0E000" path="msvcr120.dll"/>

<binaryImage start="0x000000006BD10000" end="0x000000006BD81000" path="msvcp120.dll"/>

<binaryImage start="0x00000000746B0000" end="0x00000000746E2000" path="IPHLPAPI.DLL"/>

<binaryImage start="0x0000000070530000" end="0x00000000705F5000" path="propsys.dll"/>

<binaryImage start="0x0000000076CC0000" end="0x0000000076D44000" path="SHCore.dll"/>

<binaryImage start="0x0000000078AF0000" end="0x000000007AEB6000" path="adobe\Acrobat.dll"/>

<binaryImage start="0x0000000074F80000" end="0x00000000754FB000" path="shell32.dll"/>

<binaryImage start="0x0000000076DE0000" end="0x0000000076E1B000" path="cfgmgr32.dll"/>

<binaryImage start="0x000000007BEE0000" end="0x000000007C1C4000" path="adobe\CoolType.dll"/>

<binaryImage start="0x000000007B830000" end="0x000000007BE5F000" path="adobe\AGM.dll"/>

<binaryImage start="0x000000007C2A0000" end="0x000000007C433000" path="adobe\libeay32.dll"/>

<binaryImage start="0x00000000765F0000" end="0x0000000076BB0000" path="windows.storage.dll"/>

<binaryImage start="0x00000000755D0000" end="0x00000000755E7000" path="profapi.dll"/>

<binaryImage start="0x0000000077430000" end="0x000000007748E000" path="ws2_32.dll"/>

<binaryImage start="0x00000000719F0000" end="0x0000000071AB3000" path="winhttp.dll"/>

<binaryImage start="0x0000000076020000" end="0x0000000076063000" path="powrprof.dll"/>

<binaryImage start="0x000000006C0F0000" end="0x000000006C15F000" path="msvcp140.dll"/>

<binaryImage start="0x000000006C160000" end="0x000000006C174000" path="VCRUNTIME140.dll"/>

<binaryImage start="0x0000000077150000" end="0x000000007715D000" path="umpdc.dll"/>

<binaryImage start="0x00000000772D0000" end="0x00000000772E3000" path="cryptsp.dll"/>

<binaryImage start="0x0000000051A00000" end="0x0000000051A08000" path="SensApi.dll"/>

<binaryImage start="0x0000000006EC0000" end="0x0000000006EE1000" path="adobe\BIB.dll"/>

<binaryImage start="0x000000000C330000" end="0x000000000C424000" path="adobe\ACE.dll"/>

<binaryImage start="0x0000000070440000" end="0x00000000704BA000" path="uxtheme.dll"/>

<binaryImage start="0x0000000076E20000" end="0x0000000076F23000" path="msctf.dll"/>

<binaryImage start="0x0000000070410000" end="0x0000000070435000" path="dwmapi.dll"/>

<binaryImage start="0x0000000076BC0000" end="0x0000000076C40000" path="clbcatq.dll"/>

<binaryImage start="0x00000000672B0000" end="0x00000000672E1000" path="dataexchange.dll"/>

<binaryImage start="0x0000000067140000" end="0x00000000672AA000" path="dcomp.dll"/>

<binaryImage start="0x0000000066F60000" end="0x000000006713E000" path="d3d11.dll"/>

<binaryImage start="0x0000000066E90000" end="0x0000000066F51000" path="dxgi.dll"/>

<binaryImage start="0x0000000067670000" end="0x0000000067689000" path="DXCore.dll"/>

<binaryImage start="0x0000000066CA0000" end="0x0000000066E83000" path="twinapi.appcore.dll"/>

<binaryImage start="0x0000000066C80000" end="0x0000000066C9F000" path="rmclient.dll"/>

<binaryImage start="0x0000000070A80000" end="0x0000000070A98000" path="mpr.dll"/>

<binaryImage start="0x0000000077770000" end="0x0000000077779000" path="drprov.dll"/>

<binaryImage start="0x000000006F950000" end="0x000000006F994000" path="winsta.dll"/>

<binaryImage start="0x000000000B410000" end="0x000000000B422000" path="ntlanman.dll"/>

<binaryImage start="0x000000000B450000" end="0x000000000B469000" path="davclnt.dll"/>

<binaryImage start="0x0000000077760000" end="0x000000007776A000" path="davhlpr.dll"/>

<binaryImage start="0x0000000073EA0000" end="0x0000000073EAB000" path="netutils.dll"/>

<binaryImage start="0x0000000070350000" end="0x000000007035E000" path="cscapi.dll"/>

<binaryImage start="0x0000000071CF0000" end="0x0000000071E9A000" path="urlmon.dll"/>

<binaryImage start="0x0000000071AC0000" end="0x0000000071CEA000" path="iertutil.dll"/>

<binaryImage start="0x000000007C440000" end="0x000000007C47C000" path="adobe\AXE8SharedExpat.dll"/>

<binaryImage start="0x000000000B490000" end="0x000000000B738000" path="msftedit.dll"/>

<binaryImage start="0x0000000078900000" end="0x0000000078A4F000" path="Windows.Globalization.dll"/>

<binaryImage start="0x0000000052540000" end="0x0000000052585000" path="Bcp47Langs.dll"/>

<binaryImage start="0x0000000052260000" end="0x0000000052283000" path="BCP47mrm.dll"/>

<binaryImage start="0x00000000788E0000" end="0x00000000788FC000" path="globinputhost.dll"/>

<binaryImage start="0x000000000B760000" end="0x000000000B7D1000" path="adobe\AdobeXMP.dll"/>

<binaryImage start="0x000000007BEB0000" end="0x000000007BEDB000" path="adobe\BIBUtils.dll"/>

<binaryImage start="0x0000000050060000" end="0x0000000050130000" path="nvdaHelperRemote.dll"/>

<binaryImage start="0x0000000073F40000" end="0x00000000740CF000" path="dbghelp.dll"/>

<binaryImage start="0x0000000060750000" end="0x00000000607A3000" path="oleacc.dll"/>

<binaryImage start="0x0000000073F10000" end="0x0000000073F34000" path="dbgcore.dll"/>

<binaryImage start="0x0000000050020000" end="0x000000005003E000" path="minHook.dll"/>

<binaryImage start="0x0000000060090000" end="0x00000000600A7000" path="usp10.dll"/>

<binaryImage start="0x0000000051A10000" end="0x0000000051A2C000" path="IAccessible2Proxy.dll"/>

<binaryImage start="0x0000000050040000" end="0x0000000050059000" path="ISimpleDOM.dll"/>

<binaryImage start="0x0000000078A50000" end="0x0000000078AE8000" path="adobe\Accessibility.api"/>

<binaryImage start="0x000000006B580000" end="0x000000006B608000" path="sxs.dll"/>

<binaryImage start="0x000000005FD00000" end="0x000000005FD82000" path="TextInputFramework.dll"/>

<binaryImage start="0x000000005FA10000" end="0x000000005FC6E000" path="CoreUIComponents.dll"/>

<binaryImage start="0x000000005FC70000" end="0x000000005FCF9000" path="CoreMessaging.dll"/>

<binaryImage start="0x0000000060650000" end="0x0000000060727000" path="WinTypes.dll"/>

<binaryImage start="0x000000000CDB0000" end="0x000000000DC11000" path="adobe\AcroForm.api"/>

<binaryImage start="0x0000000077320000" end="0x0000000077421000" path="crypt32.dll"/>

<binaryImage start="0x0000000075F70000" end="0x0000000075F7E000" path="msasn1.dll"/>

<binaryImage start="0x000000007B220000" end="0x000000007B2CC000" path="adobe\AXSLE.dll"/>

<binaryImage start="0x000000007B2D0000" end="0x000000007B449000" path="adobe\DigSig.api"/>

<binaryImage start="0x000000000E540000" end="0x000000000ECB2000" path="adobe\PPKLite.api"/>

<binaryImage start="0x0000000061180000" end="0x0000000061188000" path="wsock32.dll"/>

<binaryImage start="0x000000000EE20000" end="0x000000000EE9B000" path="adobe\PDDom.api"/>

<binaryImage start="0x0000000060DC0000" end="0x0000000060FB3000" path="UIAutomationCore.DLL"/>

<binaryImage start="0x0000000077780000" end="0x00000000777BB000" path="OneCoreCommonProxyStub.dll"/>

<binaryImage start="0x0000000011A10000" end="0x0000000011B93000" path="explorerframe.dll"/>

<binaryImage start="0x00000000608B0000" end="0x000000006094F000" path="apphelp.dll"/>

<binaryImage start="0x0000000060730000" end="0x0000000060743000" path="NetworkExplorer.dll"/>

<binaryImage start="0x0000000008400000" end="0x000000000845E000" path="adobe\reflow.api"/>

<binaryImage start="0x0000000009050000" end="0x00000000090CA000" path="adobe\sqlite.dll"/>

<binaryImage start="0x0000000009160000" end="0x00000000091C0000" path="adobe\CRClient.dll"/>

<binaryImage start="0x0000000076D50000" end="0x0000000076D96000" path="wintrust.dll"/>

<binaryImage start="0x0000000070360000" end="0x0000000070368000" path="dpapi.dll"/>

<binaryImage start="0x0000000014DA0000" end="0x0000000014DF1000" path="adobe\PaperCapture.api"/>

<binaryImage start="0x0000000073E90000" end="0x0000000073EA0000" path="wkscli.dll"/>

<binaryImage start="0x0000000060FE0000" end="0x0000000061074000" path="mscms.dll"/>

<binaryImage start="0x0000000060FC0000" end="0x0000000060FD1000" path="ColorAdapterClient.dll"/>

<binaryImage start="0x0000000074230000" end="0x000000007424E000" path="userenv.dll"/>

<binaryImage start="0x0000000073EB0000" end="0x0000000073F02000" path="mswsock.dll"/>

<binaryImage start="0x000000006F940000" end="0x000000006F948000" path="winnsi.dll"/>

<binaryImage start="0x0000000076DD0000" end="0x0000000076DD7000" path="nsi.dll"/>

<binaryImage start="0x00000000719D0000" end="0x00000000719E3000" path="dhcpcsvc6.DLL"/>

<binaryImage start="0x0000000073D10000" end="0x0000000073D25000" path="dhcpcsvc.dll"/>

<binaryImage start="0x000000006C630000" end="0x000000006C6A7000" path="webio.dll"/>

<binaryImage start="0x000000006C4F0000" end="0x000000006C521000" path="PeerDist.dll"/>

<binaryImage start="0x0000000060190000" end="0x0000000060206000" path="schannel.dll"/>

<binaryImage start="0x0000000060810000" end="0x0000000060821000" path="mskeyprotect.dll"/>

<binaryImage start="0x000000006BEB0000" end="0x000000006BED1000" path="ncrypt.dll"/>

<binaryImage start="0x000000006BE80000" end="0x000000006BEA8000" path="ntasn1.dll"/>

<binaryImage start="0x00000000607B0000" end="0x00000000607CF000" path="ncryptsslp.dll"/>

<binaryImage start="0x0000000073E40000" end="0x0000000073E6F000" path="rsaenh.dll"/>

<binaryImage start="0x000000006E0B0000" end="0x000000006E0CE000" path="gpapi.dll"/>

<binaryImage start="0x000000001BAC0000" end="0x000000001BC3B000" path="adobe\LogSession.dll"/>

<binaryImage start="0x0000000074250000" end="0x00000000746AC000" path="wininet.dll"/>

<binaryImage start="0x000000001BC40000" end="0x000000001C172000" path="adobe\MakeAccessible.api"/>

</binaryImageSet>

<dumpType>

Mini

</dumpType>

<hbLogSessionDllStatus>

ERROR_HB_UNABLE_TO_LOAD_DLL

</hbLogSessionDllStatus>

</crash>



END OF ADOBE REPORT CRASH




 
 


Re: Resource: Youtube Video From Thee Quinn: How to Use Microsoft Access With NVDA: Part 1

 

While I'll agree that any method to use MS-Access with a screen reader that works is absolutely amazing, this is an instance where I think that "going the GUI route" is a way to make things far, far more difficult than they need be.

I cut my teeth with databases before the age of the GUI interface learning SQL, which is still very widely in use to this day and which is supported (or was, anyway) by MS-Access and a lot of other relational databases.

The amount of work to learn SQL to commit and manipulate databases is not herculean.  The ability to deal with it when you're a screen reader user, since SQL is just plain text code, and pretty directly understandable plain text code for most of the basic database wizardry, it's just so much easier to deal with overall.  And that even applies to report formatting and generation.  

It's worth having a look at SQL as a possible option.  You might be pleasantly surprised at what you find.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

Nothing in all the world is more dangerous than sincere ignorance and conscientious stupidity.

         ~Martin Luther King, Jr.

 


locked Re: Tips on using windows10

 

Ladies and Gentlemen, after this message this topic is being locked.  Questions about how to use Windows 10 are not NVDA related, nor are the answers even screen reader specific.

If you wish to have this conversation among only other members of this group who wish to engage in off-topic questions, that is the purpose of the Chat Subgroup.  Most of the traffic there is actually very similar to this in that it's technical questions about how to use other software.

There is also a dedicated, and very active group now called Windows Access for Screen Reader Users that was up until recently the Windows 10 for Screen Reader Users group.  It has been retitled in anticipation of Windows 11, as at that point both Windows 10 and 11 related questions will be fair game there.

Here are the addresses related to the Chat Subgroup and the Windows Access for Screen Reader Users Group.

Windows Access with Screen Readers (Formerly: Windows 10 for Screen Reader Users Group)

Group Archive: https://winaccess.groups.io/g/winaccess/topics

Subscribe: winaccess+subscribe@winaccess.groups.io

Post: winaccess@winaccess.groups.io  

Unsubscribe: winaccess+unsubscribe@winaccess.groups.io  

Group Owner: winaccess+owner@winaccess.groups.io  

       Help: winaccess+help@winaccess.groups.io  

NVDA Chat Subgroup Archive:  https://nvda.groups.io/g/chat/topics

NVDA Chat Subgroup Addresses

To join:  chat+subscribe@nvda.groups.io

To post:  chat@nvda.groups.io

To unsubscribe:  chat+unsubscribe@nvda.groups.io

To receive a message containing the group description, and a list of these commands:  chat+help@nvda.groups.io

To stop receiving messages via email (you may still read messages on the Web):  chat+nomail@nvda.groups.io

This can also be used to put a vacation stop on group messages, then use one of the addresses below to resume delivery in the format of your choice.

To receive each group messages individually:  chat+single@nvda.groups.io

This is the default delivery unless you send a message to one of the addresses that follows.

To receive group messages in an HTML formatted digest:  chat+fulldigest@nvda.groups.io

To receive group messages in a plain text digest:  chat+digest@nvda.groups.io

To receive a daily summary instead of individual messages:  chat+summary@nvda.groups.io

To receive only special messages:  chat+special@nvda.groups.io

To contact the group owner(s):  chat+owner@nvda.groups.io

This topic is now locked.

--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

Nothing in all the world is more dangerous than sincere ignorance and conscientious stupidity.

         ~Martin Luther King, Jr.

 


locked Re: Tips on using windows10

Chris Mullins
 

Hi

“My Computer” does not feature in Windows 10, to open “File Explorer” in it’s Windows 10 e1quivalent, press Windows+e.

 

Cheers

Chris

 

Sent from Mail for Windows 10

 

From: Ibrahim Ajayi
Sent: 06 August 2021 15:00
To: nvda@nvda.groups.io
Subject: Re: [nvda] Tips on using windows10

 

Hi good people:

I've just successfully upgraded my laptop computer to windows10.

But the system still appears very difficult for me to understand and navigate.

I attempted to install some downloaded programs includdddinnng NVDA,

but each time I attempted, windows defender prevened th installation.

I attempted to install the apps, but windows defender prevented the

installation. I was prompted to restart my computer, aaaaandwhen I did

aaaall the downloaded programs I atteempted tto install, all

disappeeeaaarred.

On the other hand, I cannot open the flash drive where I have these

programs backed up. I cannot find the computer icon or my computer on

the desktop.

So, my questions are: how can I open the fllaaasssssssh

drrrivvvveeee,,,,   aaaaaand ssseeeeccccoonnnndlyyyyy,,,,

hhhoooooow ccaaaan   I prevent windows defender from preventing

mmmmmeeeee frrrromm  installing the apps. or how can I remove windows

defender.

Hope my questions are very well understoodddddd.... I am currenly

using narrator to access the computer.

I'm sorry about the bad typing of this mail. I am typing it on my

phone, using a bluetooth keyboard. I just don't uunnnnndeeersttand

wwwhyyy ssssooome letterrs appear many times and some get missing.

Thanking you in advance for your help.

Ibrahim.

 

On 8/2/21, hurrikennyandopo ... <hurrikennyandopo@...> wrote:

> Hi

> The following page from off my website might help.

> These were some of the things I changed on my windows 10 computer.

> The link to this page is

> http://www.accessibilitycentral.net/nvda%20tutorials%20for%20windows%2010.html

> <http://www.accessibilitycentral.net/nvda%20tutorials%20for%20windows%2010.html>

> Jump down by a few heading until you get to the tutorials as the earlier

> stuff is where to get nvda etc.

> Gene nz

> On 2/08/2021 11:44 pm, Ibrahim Ajayi wrote:

>> 

>> I'm just about to upgrade my laptop computer to windows10 from

>> windows7, and I have no knowledge about this operating system windows10.

>> So, my questions are these: how is the layout of the operating system.

>> Is it like that of windows7 or XP. what about the desktop, how is it

>> laid out. Then the user section where you have the folders like

>> documents pictures music control panel and all that: how are they laid

>> out. Then, are there any new features in this operating system that

>> are not found in windows7? then what about the start menu: how isit

>> laid out. How does one launch a program.

>> I am asking all these because I am a layman, as far as windows10 is

>> concerned.

>> Hope to get some help as always.

>> Kind regards.

>> Ibrahim.

>> 

>> 

>

 

 

 

 

 


locked Re: Tips on using windows10

Ibrahim Ajayi
 

Hi good people:
I've just successfully upgraded my laptop computer to windows10.
But the system still appears very difficult for me to understand and navigate.
I attempted to install some downloaded programs includdddinnng NVDA,
but each time I attempted, windows defender prevened th installation.
I attempted to install the apps, but windows defender prevented the
installation. I was prompted to restart my computer, aaaaandwhen I did
aaaall the downloaded programs I atteempted tto install, all
disappeeeaaarred.
On the other hand, I cannot open the flash drive where I have these
programs backed up. I cannot find the computer icon or my computer on
the desktop.
So, my questions are: how can I open the fllaaasssssssh
drrrivvvveeee,,,, aaaaaand ssseeeeccccoonnnndlyyyyy,,,,
hhhoooooow ccaaaan I prevent windows defender from preventing
mmmmmeeeee frrrromm installing the apps. or how can I remove windows
defender.
Hope my questions are very well understoodddddd.... I am currenly
using narrator to access the computer.
I'm sorry about the bad typing of this mail. I am typing it on my
phone, using a bluetooth keyboard. I just don't uunnnnndeeersttand
wwwhyyy ssssooome letterrs appear many times and some get missing.
Thanking you in advance for your help.
Ibrahim.

On 8/2/21, hurrikennyandopo ... <hurrikennyandopo@...> wrote:
Hi


The following page from off my website might help.

These were some of the things I changed on my windows 10 computer.


The link to this page is
http://www.accessibilitycentral.net/nvda%20tutorials%20for%20windows%2010.html

<http://www.accessibilitycentral.net/nvda%20tutorials%20for%20windows%2010.html>

Jump down by a few heading until you get to the tutorials as the earlier
stuff is where to get nvda etc.


Gene nz


On 2/08/2021 11:44 pm, Ibrahim Ajayi wrote:

I'm just about to upgrade my laptop computer to windows10 from
windows7, and I have no knowledge about this operating system windows10.
So, my questions are these: how is the layout of the operating system.
Is it like that of windows7 or XP. what about the desktop, how is it
laid out. Then the user section where you have the folders like
documents pictures music control panel and all that: how are they laid
out. Then, are there any new features in this operating system that
are not found in windows7? then what about the start menu: how isit
laid out. How does one launch a program.
I am asking all these because I am a layman, as far as windows10 is
concerned.
Hope to get some help as always.
Kind regards.
Ibrahim.






Re: Resource: Youtube Video From Thee Quinn: How to Use Microsoft Access With NVDA: Part 1

Richard B. McDonald
 

WOW, this girl is *SO* good!  She is to be commended.  I have always wondered, and struggled with, how to use Access.  Finally, someone did it!

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of David Goldfield
Sent: Friday, July 16, 2021 6:46 AM
To: nvda@nvda.groups.io
Subject: [nvda] Resource: Youtube Video From Thee Quinn: How to Use Microsoft Access With NVDA: Part 1

 

 

User Thee Quinn has uploaded the first in a series of videos discussing using Microsoft Access with the NVDA screen reader.

https://www.youtube.com/watch?v=9jWI0YylFU8

 

 

David Goldfield,

Blindness Assistive Technology Specialist

JAWS Certified, 2019

Subscribe to the Tech-VI announcement list to receive emails regarding news and events in the blindness assistive technology field.

Email: tech-vi+subscribe@groups.io

 

www.DavidGoldfield.org

 

 

 


Re: Vocalizer Compact Voices for NVDA

Daniel McGee
 

Hi Rui


Good news, I managed to register an account and use the temp activation you provided. The bad news, is this the latest version of the compact voices you have? because the voice sounds like it was back in the IOS 9 days / Mac OS Mavericks. Since then, they have been significantly improved.


I look forward to hearing from you about this.


Regards


Daniel

On 05/08/2021 12:20, Rui Fontes wrote:
Hello!


You can use this activation code temporarly:

tiflotecnia-wuvrDGn8HlbCLRh5Fc8zcfaaJHWt61o6


Have you read how to create an account and activate it?


Best regards,

Rui Fontes
Tiflotecnia, Lda.



Às 22:28 de 05/08/2021, Daniel McGee escreveu:
So there isn't a trial before purchase?

On 5 Aug 2021, at 20:49, Rui Fontes <rui.fontes@...> wrote:

The synth is not loaded without a valid license.


Rui Fontes

Tiflotecnia, Lda.



Às 18:47 de 05/08/2021, Daniel McGee escreveu:
Hello Rui


So I have downloaded the Tiflotecnia, addons for NVDA 2021.1


However, when I bring up the select synthesizer dialog box, I don't see the Tiflotecnia, version of the voices.


Here are the addon versions I have installed below.


Vocalizer Expressive 1.1 Driver bl...
3.1.6
Tiflotecnia, LDA.


Nuance Vocalizer Expressive - english Compact Voices (Australia, British, Irish, Scotish, South African and United States. Version: 1.1.1


Hope this is of some help.


Daniel


   On 04/08/2021 11:11, Rui Fontes wrote:

Vocalizer for NVDA from Tiflotecnia allows the use of compact voices...


Rui Fontes

Tiflotecnia, Lda.


Às 18:10 de 04/08/2021, Daniel McGee escreveu:
Hello everyone


Are there any versions of the vocalizer voices that support, the compact variant which can be used with NVDA?


Using latest versions of NVDA and Windows 10.


Thank you


Daniel















Re: Vocalizer Compact Voices for NVDA

Rui Fontes
 

Sorry!


This code is deactivated!


Rui Fontes

Tiflotecnia, Lda.


Às 00:20 de 06/08/2021, Rui Fontes via groups.io escreveu:

Hello!


You can use this activation code temporarly:

tiflotecnia-wuvrDGn8HlbCLRh5Fc8zcfaaJHWt61o6


Have you read how to create an account and activate it?


Best regards,

Rui Fontes
Tiflotecnia, Lda.



Às 22:28 de 05/08/2021, Daniel McGee escreveu:
So there isn't a trial before purchase?

On 5 Aug 2021, at 20:49, Rui Fontes <rui.fontes@...> wrote:

The synth is not loaded without a valid license.


Rui Fontes

Tiflotecnia, Lda.



Às 18:47 de 05/08/2021, Daniel McGee escreveu:
Hello Rui


So I have downloaded the Tiflotecnia, addons for NVDA 2021.1


However, when I bring up the select synthesizer dialog box, I don't see the Tiflotecnia, version of the voices.


Here are the addon versions I have installed below.


Vocalizer Expressive 1.1 Driver bl...
3.1.6
Tiflotecnia, LDA.


Nuance Vocalizer Expressive - english Compact Voices (Australia, British, Irish, Scotish, South African and United States. Version: 1.1.1


Hope this is of some help.


Daniel


   On 04/08/2021 11:11, Rui Fontes wrote:

Vocalizer for NVDA from Tiflotecnia allows the use of compact voices...


Rui Fontes

Tiflotecnia, Lda.


Às 18:10 de 04/08/2021, Daniel McGee escreveu:
Hello everyone


Are there any versions of the vocalizer voices that support, the compact variant which can be used with NVDA?


Using latest versions of NVDA and Windows 10.


Thank you


Daniel















Re: Vocalizer Compact Voices for NVDA

Rui Fontes
 

Hello!


You can use this activation code temporarly:

tiflotecnia-wuvrDGn8HlbCLRh5Fc8zcfaaJHWt61o6


Have you read how to create an account and activate it?


Best regards,

Rui Fontes
Tiflotecnia, Lda.



Às 22:28 de 05/08/2021, Daniel McGee escreveu:

So there isn't a trial before purchase?

On 5 Aug 2021, at 20:49, Rui Fontes <rui.fontes@...> wrote:

The synth is not loaded without a valid license.


Rui Fontes

Tiflotecnia, Lda.



Às 18:47 de 05/08/2021, Daniel McGee escreveu:
Hello Rui


So I have downloaded the Tiflotecnia, addons for NVDA 2021.1


However, when I bring up the select synthesizer dialog box, I don't see the Tiflotecnia, version of the voices.


Here are the addon versions I have installed below.


Vocalizer Expressive 1.1 Driver bl...
3.1.6
Tiflotecnia, LDA.


Nuance Vocalizer Expressive - english Compact Voices (Australia, British, Irish, Scotish, South African and United States. Version: 1.1.1


Hope this is of some help.


Daniel


On 04/08/2021 11:11, Rui Fontes wrote:

Vocalizer for NVDA from Tiflotecnia allows the use of compact voices...


Rui Fontes

Tiflotecnia, Lda.


Às 18:10 de 04/08/2021, Daniel McGee escreveu:
Hello everyone


Are there any versions of the vocalizer voices that support, the compact variant which can be used with NVDA?


Using latest versions of NVDA and Windows 10.


Thank you


Daniel












Re: NVDA audio routing

Sarah k Alawami
 

Actually, it's tab once, not twice, at least on my copy of nvda. I've also done config profiles for this, but I don't care to do such, not all the time.

On 5 Aug 2021, at 12:56, Jujube wrote:

Yes there is. Press nvda control s to open synthesizer dialog and press tab twice to get to the sound device box, choose your option and press enter. Alternatively you can also configure in windows sound mixer (type sound mixer into windows search).

On 8/5/21, JinYoun healthytaeshim@... wrote: > Hello, I was just curious, is there a way to route NVDA sound to > headset and > have all other sound play through the default speaker for the pc? > Thank you > > > > > >


Re: how to switch speech language

Sauro Cesaretti
 

Hello everyone,
Very helpful, thanks for all the suggestions.
Best regards,Sauro


2021-08-05 9:02 GMT+02:00, Ali Colak <alish54@...>:

If you commonly switch between two languages and want to this on the
fly instead of going through the voices dialogue, then Fawaz Abdul
rahman's suggestion is the best option.
1: press nvda+control+p to go to the configurations profiles menu.
2: Tab until you get the new button.
3: Name it whatever you wish, ideally a discriptive name.
4: Press tab to check the manual activation radio button.
5: Press OK.
6: Close the menue.
7: Switch to whatever language you want in the profile through
control+nvda+v, then save that configuration with control+nvda+c.
8: Go the nvda preferences menu, then input gestures.
9: Down arrow until you see Configuration profiles and right arrow to
expand.
10: Down arrow until you hear the name of the profile you created,
than tab until you hear add and press enter or the space bar.
11: Press the key combination you want to associate with that profile,
ideal a combination that isn't already associated with something.
12: A context menue will appear asking you which keyboard leyout you
want the combination associated with, select whichever you wish, --I
advise all keyboard layouts-- then press enter.
13: tab until you hear OK and press enter.
14: Press the key combination to activate and deactivate the profile,
which will switch you the language you associated with the account and
back.

On 8/4/21, Jujube <ellaxyu@...> wrote:
I believe the command to access the voice dialog is control nvda V.
Press control nvda g to change interface language.

On 8/4/21, Sauro Cesaretti <saurocesaretti1983@...> wrote:
Hello everyone,
I'm Sauro Cesaretti from italy.
I'd like to kindly ask if there is a shortcut to switch quickly the
language speech.
In particular, I need to switch form Italin to english voice with
windows core voices, is it possible to do it with a shortcut?
Thanks in advance
Best regards,Sauro Cesaretti














Re: Vocalizer Compact Voices for NVDA

Daniel McGee
 

So there isn't a trial before purchase?

On 5 Aug 2021, at 20:49, Rui Fontes <rui.fontes@...> wrote:

The synth is not loaded without a valid license.


Rui Fontes

Tiflotecnia, Lda.



Às 18:47 de 05/08/2021, Daniel McGee escreveu:
Hello Rui


So I have downloaded the Tiflotecnia, addons for NVDA 2021.1


However, when I bring up the select synthesizer dialog box, I don't see the Tiflotecnia, version of the voices.


Here are the addon versions I have installed below.


Vocalizer Expressive 1.1 Driver bl...
3.1.6
Tiflotecnia, LDA.


Nuance Vocalizer Expressive - english Compact Voices (Australia, British, Irish, Scotish, South African and United States. Version: 1.1.1


Hope this is of some help.


Daniel


On 04/08/2021 11:11, Rui Fontes wrote:

Vocalizer for NVDA from Tiflotecnia allows the use of compact voices...


Rui Fontes

Tiflotecnia, Lda.


Às 18:10 de 04/08/2021, Daniel McGee escreveu:
Hello everyone


Are there any versions of the vocalizer voices that support, the compact variant which can be used with NVDA?


Using latest versions of NVDA and Windows 10.


Thank you


Daniel














Re: NVDA audio routing

JinYoun
 

Wow, thank you all for the simple tip! Much appreciate it.

On 8/5/21, Sarah k Alawami <marrie12@...> wrote:
This was actually just discussed. Nvda control s, tab, choose device,
enter.



From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of JinYoun
Sent: Thursday, August 5, 2021 12:30 PM
To: nvda@nvda.groups.io
Subject: [nvda] NVDA audio routing



Hello, I was just curious, is there a way to route NVDA sound to headset and
have all other sound play through the default speaker for the pc?
Thank you









Re: speech rate changes to defaults

George Kerscher
 

Hello,

 

Two items as follow up:

The NVDA+CTRL+R worked most of the time. Only occasionally I had to made a change.

I did run SFC and it showed no errors. I switched to Eloquence, and have not had the problem again. I think the old Eloquence, which did not work with 2021 and was disabled was somehow causing the problem.

 

So, life is good.

 

Best

George

 

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gene
Sent: Monday, July 19, 2021 4:43 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] speech rate changes to defaults

 

Do I  understand that you are using a profile for Outlook and the standard settings for most else?  I don’t know what is causing the problem or if that has anything to do with anything.

 

This may or may not work, but you may be able to deal with the problem so quickly that solving it no longer  matters.  The next time this happens, issue the apply configuration command, NVDA key control r.  the setting may not be lost at all.  For some reason, NVDA may not be using it and applying the saved configuration may cause it to do so again.  Since this is just one command, if it works getting the setting to work again will be so fast and convenient that you may not ;particularly care about solving the problem.

 

Gene

-----Original Message-----

Sent: Monday, July 19, 2021 5:36 PM

Subject: Re: [nvda] speech rate changes to defaults

 

Hello again,

 

Today, the rate changed to the default setting. I am running Windows 10 2021H1.

I was in Outlook and was switching between an open message and the inbox. Both the Outlook profile and the normal general configuration was impacted. I could save the profile immediately after it changed.

 

I also was in outlook with an open message and was running on battery. I left the computer, and it went to sleep.  When I woke it up, the rate changed. Here too the Outlook configuration and the default reverted to the slow speech rate.

 

I am getting pretty fast correcting this behavior, so it is not a horrible inconvenience, but it would be good to figure out what is going on.

 

Best

George

 

 

Best

George

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel
Sent: Sunday, July 18, 2021 1:49 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] speech rate changes to defaults

 

On Sun, Jul 18, 2021 at 03:39 PM, George Kerscher wrote:

I will report back here if the issue reappears. It has gone away for now, i.e. I can no longer force the behavior.

-
First, thank you for such a fine report on your findings, how to force the issue you had, and how you've resolved it.

Please report back even if the issue does not reappear for a period of time where you're reasonably confident that "the fix has taken."  That's valuable information to have, too.  Also, if it should recur at some unspecified point in time in the future, please report that, too, as these things can often have multiple contributing factors.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

Travel is fatal to prejudice, bigotry, and narrow-mindedness, and many of our people need it sorely on these accounts. Broad, wholesome, charitable views of men and things cannot be acquired by vegetating in one little corner of the earth all one's lifetime.

     ~ Mark Twain

 


Re: NVDA audio routing

Sarah k Alawami
 

This was actually just discussed. Nvda control s, tab, choose device, enter.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of JinYoun
Sent: Thursday, August 5, 2021 12:30 PM
To: nvda@nvda.groups.io
Subject: [nvda] NVDA audio routing

 

Hello, I was just curious, is there a way to route NVDA sound to headset and have all other sound play through the default speaker for the pc?
Thank you 


Re: NVDA audio routing

Jujube
 

Yes there is. Press nvda control s to open synthesizer dialog and
press tab twice to get to the sound device box, choose your option and
press enter. Alternatively you can also configure in windows sound
mixer (type sound mixer into windows search).

On 8/5/21, JinYoun <healthytaeshim@...> wrote:
Hello, I was just curious, is there a way to route NVDA sound to headset and
have all other sound play through the default speaker for the pc?
Thank you






Re: NVDA audio routing

Rui Fontes
 

Hello!


Press NVDA+Control+S;

Tab once and select the sound card you want...


Rui Fontes


Às 20:30 de 05/08/2021, JinYoun escreveu:

Hello, I was just curious, is there a way to route NVDA sound to headset and have all other sound play through the default speaker for the pc?
Thank you 

11581 - 11600 of 98336