Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The speaking of the typed characters does not work in Universal apps in the latest build of the Windows Insider Preview #6017

Closed
k-kolev1985 opened this issue May 30, 2016 · 2 comments
Labels
blocked/needs-external-fix blocked p2 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority
Milestone

Comments

@k-kolev1985
Copy link

I've noticed that, with the latest build of the Windows Insider preview, NVDA does not speak the typed characters in the so called universal apps. That includes the search field in the Start menu. If I use the arrow keys to review the typed characters - it works as expected. If I use the DELETE or BACKSPACE keys to delete characters, it also works as expected. The only issue is with the characters not being spoken when entering them from the keyboard (keyboard echo). Both Windows and NVDA are the latest test builds.

Steps to reproduce it:

  1. Update the Windows Insider Preview to its latest build via Windows Update.
  2. Update the installed copy of NVDA to its latest "next" snapshot.
  3. Open one of the so called "universal" apps. The Microsoft Edge browser will do it.
  4. Make sure that the option "Speak typed characters" of NVDA is turned on.
  5. Find an edit field in that app and start typing text in it.

Expected results:
NVDA should speak the typed characters.

Actual results:
NVDA stays silent.

Test environment:

  • Operating system: Windows 10 Pro Insider Preview (build 14352.1002)), 32-bit, in English with all locale settings set to "Bulgarian", in a virtual machine in VMWare Player.
  • Input languages: "Bulgarian" and "English US".
  • VMware® Workstation 12 Player version: 12.1.1 build-3770994.
  • NVDA version: next-13343,73ee6b2a.
  • Processor: Intel Core i5-2320 at 3.00GHz.
  • RAM Memory: 3.00GB.
@k-kolev1985
Copy link
Author

Am I the only one that can reproduce this? Does it work OK on your machines?

@jcsteh
Copy link
Contributor

jcsteh commented Jun 17, 2016 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked/needs-external-fix blocked p2 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority
Projects
None yet
Development

No branches or pull requests

3 participants