Add abillity for braille to be tethered to speech

[Emil-18]

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

As some features in NVDA and add-ons don't work with braille, the braille display should be able to show what NVDA is speaking to give users who only use braille access to the same functions

Describe the solution you'd like

A new tether option, that tethers the braille display to speech.

Describe alternatives you've considered

Additional context

[Adriani90]

How should this work? Speech is actually tetered to a certain cursor, i.e. to system cursor, system caret, mouse cursor or review cursor / navigator.
Braille is already supporting this as well.
What exactly would you like to have shown in braille?
Note that speech itself is not a cursor or caret, I guess it is technically even impossible to match speech and braille completely but I might be wrong.

[Emil-18]

When braille is tethered to speech, I would like speech.speech.speak to join every string in speechSequence with a space between them, and create a text region with it as an argument. I think this text region should be appended to a list containing everything NVDA has spoken since speech was last canceled, and then show this list of regions on the braille display in the main buffer. Hope this makes sence.

[josephsl]

Hi,

If I understand you correctly, you would like something similar to speech history? If I remember right, JAWS's speech history (formerly called speech box) feature shows the last spoken utterance on the braille display, not necessarily a history of speech up to a certain point.

Thanks.

[Emil-18]

@josephsl More like a speech replacement for braille users, but i guess speech history also works. I could make a pull request to show what I mean, but aren't I supposed to wait until the issue is triaged before making a pull request?

[Adriani90]

You can do a pull request even without creating an issue at all. Triage does no affect the process of creating pull requests.Von meinem iPhone gesendetAm 10.12.2023 um 21:42 schrieb Emil-18 ***@***.***>: @josephsl More like a speech replacement for braille users, but i guess speech history also works. I could make a pull request to show what I mean, but aren't I supposed to wait until the issue is triaged before making a pull request? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>

[Adriani90]

Did you test this already? I imagine such things like "linefeed" or "space" or any other punctuation is completely displayed on the braille display when it is tetered to speech. Correct?
Is this really practical for a braille user to have these things displayed completely?

[josephsl]

Hi, I get a feeling that this issue is a duplicate of another one. Thanks.

[seanbudd]

You can do a pull request even without creating an issue at all. Triage does no affect the process of creating pull requests.

While you can do this, it's not recommended.
Pull requests are a lot of work, it's not worth starting one if a feature suggestion gets rejected, or further advice is provided by NV Access.

See contributing docs

[Adriani90]

There is the related issue #6905.

[LeonarddeR]

You can do a pull request even without creating an issue at all.

While this is technically possible, it is generally discouraged unless it is very obvious from the pr that it fixes an issue that needs fixing.

In this case, I guess it is the add-ons primary responsibility to respect braille users. That said, I think the current proposal makes sense. It will however make the options at this point even more complex.

[CyrilleB79]

As explained before speech is not a specific part of the system, nor a precise location, on contrary to system or review cursors.

Thus, the concept of tethering to speech may be confusing from a UX point of view.

Why not create a completely distinct option: "Braille only logs the speech" which could be enabled or disabled. When this option is enabled, various items of the braille settings panel do not apply and should be disabled, e.g. Tether to, message displaying, display selection, etc.
A better name than my suggestion should be found though.

[seanbudd]

@CyrilleB79's proposal makes sense