nvaccess / nvda

NVDA, the free and open source Screen Reader for Microsoft Windows
https://www.nvaccess.org/
Other
2.13k stars 639 forks source link

Show formatting on Braille viewer raw text line #14146

Open Qchristensen opened 2 years ago

Qchristensen commented 2 years ago

Steps to reproduce:

  1. Turn on the Braille viewer
  2. Go into Word
  3. Ensure NVDA's document formatting is set to report "Font attributes".
  4. Type some text, say "The quick brown fox".
  5. Set some of it bold, say the word "brown".
  6. Read the line and observe what is displayed in Braille viewer.

Actual behavior:

Braille viewer displays the correct symbol (dot 4, 5 and dot 2) to indicate the word is in bold, however the text underneath simply reads "The quick brown fox".

(Additionally, if you arrow through the text and the caret is in the middle of the bold word, the bold symbol disappears from the Braille viewer, although it was still reported audibly when focus moved into the word. I have separated THIS aspect into a new issue #14151 )

Expected behavior:

I don't have a hardware display handy to text how it actually behaves, however the English text in the braille viewer should accurately represent what the Braille cells are showing.

NVDA logs, crash dumps and other attachments:

System configuration

NVDA installed/portable/running from source:

NVDA version:

NVDA 2022.3 Beta 4 installed

Windows version:

Windows 11 (64-bit) Version: 21H2 (2009), Build: 22000.978

Name and version of other software in use when reproducing the issue:

Office 365 (64-bit) Version: 16.0.15601.20072

Other information about your system:

Other questions

Does the issue still occur after restarting your computer?

Yes

Have you tried any other versions of NVDA? If so, please report their behaviors.

2021.3.5 (portable) 2020.2 (portable)

If NVDA add-ons are disabled, is your problem still occurring?

Yes

Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?

feerrenrut commented 2 years ago

NVDA doesn't have enough information (currently) to be able to do this. The (non-braille) text is there only to give some context about the cells displayed. The main intention was to support developer use-cases. It would be great if we could expand this to support a wider set of use-cases more thoroughly.

feerrenrut commented 2 years ago

After the technical challenge of getting a backtranslation for each braille cell (or group of cells). There are some unknowns about the UX: