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.

Sign up for GitHub

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

Jump to bottom

Microsoft Word, Shift + F3 and F8, NVDA Doesn't Read Selected Text #3293

Closed
nvaccessAuto opened this issue Jun 20, 2013 · 10 comments · Fixed by #17424
Closed

Microsoft Word, Shift + F3 and F8, NVDA Doesn't Read Selected Text #3293

nvaccessAuto opened this issue Jun 20, 2013 · 10 comments · Fixed by #17424
Labels
app/microsoft-office bug p3 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority triaged Has been triaged, issue is waiting for implementation.
Milestone
2025.1

Comments

@nvaccessAuto
Copy link

Reported by jhomme on 2013-06-20 12:57
In Microsoft Word, F3 cycles through changing the case of text. NVDA is not speaking the text when the case changes. Steps to reproduce:

  1. Create a line of text with several words.
  2. Put the cursor on any of the words.
  3. Press F3.
  4. Word selects the text and changes the case. It would be good for NVDA to read the text, and possibly spell it so that the user can determine how the text case has changed.
  5. Select multiple words or the whole line of text.
  6. Once again, NVDA does not speak the selected text.
  7. I believe that Word also handles larger chunks of text this way, but usually, I use this feature to change the case of single words or lines.
  8. This same kind of thing happens when you use F8 to select larger and larger bits of text.
@LeonarddeR
Copy link
Collaborator

I can reproduce this in Word 2016, at least when I use shift+f3 as in the issue title.

I wonder whether it is possible to track down this command, similar to changing bold with ctrl+b, italic with ctrl+i, etc.

CC @michaelDCurran, @feerrenrut

@ehollig
Copy link
Collaborator

ehollig commented Jul 13, 2017

I am not sure if this is what the original poster is talking about, but I can also confirm this in Word 2016.
Shift+F3 = Change the case of letters
F8 = Extend a selection
Shift+F8 =Reduce the size of a selection
https://support.office.com/en-us/article/Keyboard-shortcuts-for-Microsoft-Word-on-Windows-95ef89dd-7142-4b50-afb2-f762f663ceb2

@LeonarddeR LeonarddeR mentioned this issue Jul 17, 2017
Closed
@CyrilleB79 CyrilleB79 mentioned this issue Sep 23, 2022
Open
@seanbudd seanbudd added app/microsoft-office p3 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority triaged Has been triaged, issue is waiting for implementation. bug and removed enhancement labels Sep 27, 2022
@Qchristensen
Copy link
Member

This is still reproduceable with:

NVDA 2024.4.1
Windows 11 (64-bit) Version: 23H2, Build: 22631.4460
Office 365 (64-bit) Version: 16.0.18227.20046

Note that a workaround for toggle case is to perform the actions (select text then shift+f3) then press Numpad 5 (NVDA+control+dot) twice quickly to spell the current word) which will also give you the capitalisation.

@Qchristensen
Copy link
Member

Also worth noting that testing with Narrator (on the same setup) - it re-reads the selected text each time I press shift+f3, but with nothing to indicate what the capitalisation is. I'm not sure if that's just I haven't set something correctly in Narrator, but I've sent Microsoft a query on this as well.

@Qchristensen
Copy link
Member

Sorry one more update - it does not matter how NVDA's advanced setting "Use UI Automation to access Microsoft Word document controls" is set.

@CyrilleB79
Copy link
Collaborator

Regarding shift+F3:

IMO, it's more useful to report the type of capitalization (e.g. no capitalization, word cap, sentence cap, all ca) depending on the selection than the selection itself, especially in case of a big selection.

By the way, I had tried to include it in #17197, using the same strategy as control+B/I/U with no avail. The idea was to report only the type of capitalization (lowercase, word cap, sentence cap, etc.). But the value returned by the object model was not stable in some case. Maybe implementing it with a manually twicked delay could be a solution?

So if you agree with this UX, the shift+F3 part of this request is covered by #10271 which remains open for this specific case.

@CyrilleB79 CyrilleB79 mentioned this issue Nov 22, 2024
Merged
5 tasks
@comanna
Copy link
Contributor

comanna commented Nov 22, 2024 via email

@CyrilleB79 CyrilleB79 mentioned this issue Nov 22, 2024
Merged
5 tasks
@github-actions github-actions bot added this to the 2025.1 milestone Nov 26, 2024
@Adriani90 Adriani90 reopened this Nov 26, 2024
@Adriani90
Copy link
Collaborator

The Pr referenced is a partial fix.

seanbudd pushed a commit that referenced this issue Nov 26, 2024
@CyrilleB79
Report the result of word switch case formatting command (#17425)
16cbc6f 
Fixes #10271 (last part)
Also could be considered a partial fix of #3293.

Summary of the issue:
In Word / Outlook, nothing is reported when using the switch case command (shift+f3 in both, control+shift+a in Outlook only). Since it is a toggle/cycle command, the user needs to have the result to be reported.

Description of user facing changes
Using the switch case formatting command in Word or Outlook now reports its result, i.e. the type of case in which the selection has been formatted.

When possible, the message being reported illustrates its own casing, as in Word menus, e.g. "lower case", "UPPERCASE", "Each Word Capitalized"; this may be useful in braille. Exception, for "Mixed case", I have not done something such as "mIxEd cAsE" because it is not correctly understandable through speech.

Description of development approach
Used Word object model as for other Word formatting scripts.
Introduced a delay (set empirically), since the property retrieved from the object model transitions through other values (no case or lower case) before reaching its definitive value.
Bind gestures according to the ones existing in Word and Outlook.
Note: shift+f3 performs case switch both in Word and Outlook, whereas control+shift+A does it only in Outlook. See "Notes about various capitalization shortcuts" in #17197 for more details.
@CyrilleB79
Copy link
Collaborator

@Adriani90 could you be more specific?

This issue was not well written, asking two different thing (shift+f3 and f8). I guess you are referring to f8? (but better explicit than implicit)

IMO, rather than reopening this issue, writing a brand new issue with what remains to do would be much better. Could you do this?

@CyrilleB79 CyrilleB79 mentioned this issue Nov 28, 2024
Open
@CyrilleB79
Copy link
Collaborator

@Adriani90, this issue covers various issues.

For clarity, I have opened #17450 to track and clarify what remains to do from this ticket. I'll close this one.

Let me know if I have missed something.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
app/microsoft-office bug p3 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority triaged Has been triaged, issue is waiting for implementation.
Projects
None yet
Milestone
2025.1
8 participants
@LeonarddeR @seanbudd @nvaccessAuto @Qchristensen @CyrilleB79 @ehollig @comanna @Adriani90