nvaccess/nvda

Brief summary When NVDA starts automatically immediately after a successful Windows PIN sign-in, Screen Curtain fails to enable if the post-sign-in Windows OOBE ("You're almost done setting up your PC") is displayed. The problem has been reproduced with both NVDA 2026.1.1 and NVDA 2026.2 beta 11. This does not occur while NVDA is running on the PIN sign-in screen or secure desktop. The PIN sign-in completes successfully, NVDA starts in the user's normal Windows session, and the OOBE is hosted by WebExperienceHostApp.exe. NVDA attempts to enable Screen Curtain three times. All three attempts fail during the desktop capture used to verify that the screen is fully black. NVDA then reports that Screen Curtain could not be enabled, leaving the Windows OOBE and other screen contents visible. Steps to reproduce Configure NVDA to start automatically after signing in to Windows. Open NVDA Settings, go to Vision > Screen Curtain, and enable "Make screen black". Save the configuration so that Sc

Is your feature request related to a problem? Please describe. In NVDA"s command line options, there is an argument to run NVDA on the logon screen, but NOT one to start NVDA after signing in: https://download.nvaccess.org/documentation/userGuide.html#CommandLineOptions This would be useful, particularly for system admins installing NVDA. Report of this issue in the user group. Describe the solution you'd like A command line argument such as --start-after-signin=True|False which sets up NVDA to start after the user logs in, the same way the checkbox on the general settings screen does. Describe alternatives you've considered There is a request for this as an option during install as issue #10651, which is similar, and the work could likely be done at the same time. Additional context No response

Is your feature request related to a problem? Please describe. Currently, When We enter an emoji repeatedly more than 3, It will announce number of entered ones instead of announcing emoji name for all. For example If I enter this emoji 3 times 😭😭😭 And read it, I here crying face crying face crying face. But if I enter more than 3 like 4 times 😭😭😭😭 And read it, it announces 4 crying face. There is no setting controle to decrease, increase, or disable and enable this feature in nvda speach settings Describe the solution you'd like I didn't know that this can be configgered Untill recently That I was exploring recently updated talkback's settings, And I saw that they have made possible to configger this in talkback settings, So we can do it in nvda. Describe alternatives you've considered Always hardcoded to 4 and higher Additional context I don't know how this controle is being handled, Is it something that we need to handle explisitly in nvda, Or Espeak NG Already

Related issues, PRs or discussions No response What is the current state of the codebase? NVDA's .editorconfig declares C/C++ source files as UTF-8. Some cppjieba headers contain non-ASCII comments and have no UTF-8 BOM. When building with MSVC on a system whose ANSI code page is not UTF-8, the compiler can read these files using the wrong encoding. This caused many C++ syntax errors while building cppjieba. Why are changes required? The build should read UTF-8 source files the same way on all Windows systems. What technical changes are required? Add /utf-8 to the common MSVC compiler flags in nvdaHelper/archBuild_sconscript. Are the proposed technical changes API breaking? Unknown Are there potential risks or issues with the proposed implementation? No

Is your feature request related to a problem? Please describe. When browse mode is set to use screen layout navigation, paragraphs exceeding 250 characters are frequently encountered. Describe the solution you'd like Increase the maximum value limit for the "Maximum number of characters on one line" setting control. Describe alternatives you've considered Navigate directly by block. Additional context Related: #11717