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

Speak typed characters and words applied to edit fields only. #16848

Open
SamuelV04 opened this issue Jul 11, 2024 · 8 comments · May be fixed by #17505
Open

Speak typed characters and words applied to edit fields only. #16848

SamuelV04 opened this issue Jul 11, 2024 · 8 comments · May be fixed by #17505
Labels
feature p4 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority triaged Has been triaged, issue is waiting for implementation.

Comments

@SamuelV04
Copy link

Is your feature request related to a problem? Please describe.

No.

Describe the solution you'd like

NVDA should be able to speak characters in edit fields, but act like speak typed characters is off in other places. For example, NVDA could continue to speak characters in notepad, but in file explorer, NVDA will not speak the characters, even if speak typed characters is turned on. If the user wishes, they can select whether to have NVDA not speak characters, speak characters everywhere, or only in edit boxes. The INSERT+2 keystroke would be able to cycle between the 3, and the speak typed characters checkbox in keyboard settings would be replaced by a combo box to select which setting the user wants. This would go for speak typed words as well.

Describe alternatives you've considered

There is the typing settings addon that allows for this, but it isn't compatible with the latest NVDA.

Additional context

More often than not, we are not working in an edit field. In areas such as file explorer, It can be somewhat verbose when using first letter navigation because the characters are being echoed every time they move to a new item in say, a list or a combobox. The user would end up turning speak typed characters off, and potentially forget to turn it back on when inside of an edit field. My suggestion would eliminate that problem, allowing the user greater flexibility in how they want things echoed.

@Adriani90
Copy link
Collaborator

Closing as duplicate and in favor of #10331 which contains more technical discussion.
That one applies for speak typed characters as well.

@XLTechie
Copy link
Collaborator

XLTechie commented Jul 11, 2024 via email

@SamuelV04
Copy link
Author

Right. #10331 doesn't have anything whatsoever about configuring how typed characters and words are echoed. Also, what if the user wants characters and words echoed everywhere as in prior versions? Like new keyboard learners for instance. There isn't any configurability mentioned in the issue, which to me makes it not a duplicate. People are going to have situations where they will want characters spoken globally in one application, while keeping them on only in edit boxes or off entirely in others.

@XLTechie
Copy link
Collaborator

Re-opening per #16848 (comment)
I don't necessarily support the feature request, but it is a valid request and IMO not a duplicate.

@XLTechie XLTechie reopened this Jul 12, 2024
@seanbudd seanbudd added p4 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority feature triaged Has been triaged, issue is waiting for implementation. labels Jul 15, 2024
@cary-rowen
Copy link
Contributor

Hi,

I developed an add-on some time ago with features that I thought could cover this feature request.
And I'd like to contribute this as a PR to NVDA core. It may involve configuration key changes, which I think would be best done in 2025.1.

Add-on repo:
https://github.com/cary-rowen/NVDA-CustomSpeakTypedCharacters

@seanbudd
Copy link
Member

@cary-rowen this issue is triaged - is there anything you are waiting on from our side?

@cary-rowen
Copy link
Contributor

Hi @seanbudd
This involves a configuration key change that wouldn't require setting up backwards compatibility if done during the 2025.1 development cycle, right?

Many thanks!

@seanbudd
Copy link
Member

Correct, if it comes after 2025.1 we will need to figure out a compatibility strategy

@cary-rowen cary-rowen linked a pull request Dec 11, 2024 that will close this issue
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature p4 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority triaged Has been triaged, issue is waiting for implementation.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants