Re: Word 2016 "find"
Adrian Spratt
Rebecca,
toggle quoted message
Show quoted text
Thanks for posting these steps. They do work in Word 2016. Unfortunately, they've made no difference on my system. If anything, I know longer get the benefit I described last night when I perform a second "find." With luck, the situation will return to normal. Did I hear someone say, "Situation normal. FUBAR"? -----Original Message-----
From: jaws-users-list@groups.io <jaws-users-list@groups.io> On Behalf Of Rebecca Lineberger Sent: Wednesday, July 10, 2019 7:34 AM To: jaws-users-list@groups.io Subject: Re: [jaws-users] Word 2016 "find" I saw this years ago in a Word tutorial that I got, I think, from National Braille Press. I changed it in my Word 2010. It may be worth looking at in Word 2016 or 365 to see if it's still doable. Rebecca Restoring the traditional find command in Word # Find Command for Word 2010 and above. Here are the steps for getting CTRL+F to work in the traditional manner. These steps work in Word 2013. I don't have Word 2016 but I think they should also work in that version of Word. 1. Use Alt with F followed by T to go into the Word options. 2. In the list of categories either use down arrow or press the letter C until you get to the "customize ribbon" category. 3. Press Alt with T to use the customize button. 4. Use down arrow until you get to the Home tab. 5. Tab to the commands list. 6. In the commands list press E until you find the "EditFind" command. 7. Tab a couple times to the "press new shortcut key" box. 8. Press CTRL with F. 9. Tab to the Save Changes In box and choose Normal.DOTM. 10. Tab to the Assign button and press spacebar. 11. Tab to the Close button and use spacebar. 12. Tab to OK and use spacebar. -----Original Message----- From: jaws-users-list@groups.io [mailto:jaws-users-list@groups.io] On Behalf Of Adrian Spratt Sent: Wednesday, July 10, 2019 12:12 AM To: jaws-users-list@groups.io Subject: Re: [jaws-users] Word 2016 "find" Hi Ann, With a similar configuration, I just tested Word's "find" feature and realize I'm having a similar experience. However, I'm so used to treating it as a trial-and-error function that I hadn't noticed. Let me detail two experiments I just tried. First, I pressed control-f and typed in my search term. The only way to read the term in context was to press escape and then insert-8 ("say line"). Initially, JAWS wouldn't read the line with insert-8, but it did so on my second press. So, how to reach the next result? I pressed control-f again. As I recall (I can't replicate this now JAWS verbalized "Next result." Assuming correctly that I was still on the first result, I pressed the spacebar. I landed on the second result, but JAWS remained uncooperative. The only way to read the context was, again, to press escape and then insert-8, the say line command. Now, this gets interesting. I abandoned that search and started one for a different term. This time JAWS read the results pretty much as I expected and wanted. I pressed control-f and enter. JAWS read the context and then "Next result." I could press escape if I wanted to stay at that point or the spacebar if I wanted to move on. I chose a term that had numerous occurrences in that document, and it proceeded the same way throughout. This is consistent with my experience. My first time through is hit-or-miss. The second time, for whatever reason, the "find" function works well. It's important because of the limitations of the JAWS search feature, which can find only whole words, not search strings that might or might not be words. Also, Word reports the number of instances of a search term. I hope this is helpful. I realize it may not sound like it is. And you never know with JAWS, what works for one person might not for another. -----Original Message----- From: jaws-users-list@groups.io <jaws-users-list@groups.io> On Behalf Of Ann Byrne Sent: Tuesday, July 9, 2019 9:05 PM To: jaws-users-list@groups.io Subject: Re: [jaws-users] Word 2016 "find" I have tried f6. I get the same result. At 07:27 PM 7/9/2019, you wrote: I had problems with the find command since I moved to windows 10. An |
|