Microsoft Office Online
Sign in to My Office Online (What's this?) | Sign in

 
 
Help and How-to
Search
Search
 
Check for updates: (c) Microsoft
Microsoft Update
 
 
 
Warning: You are viewing this page with an unsupported Web browser. This Web site works best with Microsoft Internet Explorer 6.0 or later, Firefox 1.5, or Netscape Navigator 8.0 or later. Learn more about supported browsers.

Email this linkEmail this link Printer-Friendly VersionPrinter-Friendly Version Bookmark and ShareShare
Helpful feature in the spelling checker in Word 2007
 

04/11/2008

Rowena Portch, Accessibility Advocate

If spelling and grammar are not your strong suits, you will love the new feature in Microsoft Office Word 2007. Read on to learn how to ramp up your writing skills to a whole new level.

Applies to
Microsoft Office Word 2007

Earlier versions of Word

In earlier versions of Word, spelling checker was useful as long as you used the right word in the right context. Some of us, however, aren't always sure about which word to use when. For example, the words there (t h e r e), their (t h e i r), and they're (t h e y ' r e) all sound the same and are all spelled "correctly." If used in the wrong context, however, they create an incorrect sentence. How would you know?

It is also common to type the instead of they (with a y), or some times (with a space between the words) as opposed to sometimes (as one word). These types of spelling errors are not detected by earlier versions of Word and change the meaning or readability of your sentence.

Help is on the way

Word 2007 offers a feature that catches most contextual spelling errors. If you use a screen reader, contextual errors are announced as misspelled words. I would not rely on this feature completely, though. For example, you could still write an incorrect sentence, such as, "They're (t h e y ' r e) you go," and Word does not flag it as incorrect. So, don't fire your editor.

A little help from a screen reader

When you are visually impaired, using the traditional spell checker in Word can be a bit cumbersome. For example, the little squiggly lines that appear under a misspelled word can be very difficult to see or not seen at all. I use JAWS, an ingenious screen-reading computer program that reads text to me. Without it, I wouldn't be able to work on the computer. By default, however, spelling errors are not automatically detected.

Set up your environment

By default, JAWS is not configured to detect spelling and grammar errors. Word 2007 is configured by default, but just in case someone might have turned off these features, here is how to check the status of these settings and re-enable them if necessary:

  1. In Word, press ALT+F, and then press I.
  2. In the Word Options dialog box, press your DOWN ARROW key twice to open the Proofing page.
  3. To access the Check spelling as you type check box, press ALT+P . Make sure that this check box is selected. If it's not, press your SPACEBAR to select it.
  4. To access the Use contextual spelling check box, press your DOWN ARROW key once. Make sure this check box is selected. If it's not, press your SPACEBAR to select it.
  5. To access the Mark grammar errors as you type check box, press your DOWN ARROW key once . Make sure this check box is selected. If it's not, press your SPACEBAR to select it.
  6. To access the Check grammar with spelling check box, press your DOWN ARROW key once . Make sure this check box is selected. If it's not, press your SPACEBAR to select it.
  7. Press ENTER to save your changes and close the dialog box.

Configure JAWS

To configure JAWS to detect spelling and grammar errors, do the following:

  1. Make sure that JAWS is running and that a Word document is active.
  2. Press INSERT+V to open the verbosity settings for Word.
  3. Press your DOWN ARROW key to move through the selections.
  4. Under Editing Options, make sure that the following options are set. To change the setting, press your SPACEBAR:
    1. Set AutoCorrect Detection to On.
    2. Set Spelling Error Detection to On.
    3. Set Grammatical Error Detectionto On + Count (or On)
  5. Press ALT+C to save your changes, and then close the dialog box.

Check and correct your errors

If you press INSERT+UP ARROW to read the current line, JAWS reads the current line and informs you of any errors that you have on that line. If you set the Grammatical Error Detection setting to On + Count, JAWS informs you of how many errors are on that line.

To hear a list of spelling errors that are in your document, press ALT+SHIFT+L. Use your DOWN ARROW key to move through the list of errors. To go to the location of the error, press ENTER.

If you need help with a misspelled word, position your cursor over the word, and then press SHIFT+F10 for a list of word options. Press your DOWN ARROW key to move through the suggested words. To hear the spelling of the word, quickly press INSERT+NUM PAD 5 twice. If you are using a laptop computer, quickly press CAPS LOCK+K twice. When you find the correct word, press ENTER.

To hear a list of grammatical errors that are in your document, press CTRL+SHIFT+G. Use your DOWN ARROW key to move through the list of errors. To go to the location of the error, press ENTER.

Contact me

If you have comments or suggestions for articles that you would find helpful, please send me an e-mail message at accessad@microsoft.com. I do monitor this mailbox each day and personally respond to your inquiries.

Read more articles by the Accessibility Advocate


Introducing the Accessibility Advocate column

Making sense of HTML messages in Outlook

Become more efficient with accessibility tools

How to work with the visually impaired

Contribute an article

Each month, I publish an article from a contributing author. If you have something to share and want to see your name in the by line, send your article to accessad@microsoft.com


About the author

Three years ago, I lost my sight to Retinitis Pigmentosa. Prior to that, I was a technical editor. Learning how to use a screen reader and a Braille display proved challenging enough — having to deal with non-accessible applications was unbearable. To remain productive, I had to learn how to use accessibility tools and write scripts to interact with applications that were not accessible. Tasks that used to take me only minutes to perform were taking hours. My productivity went down, along with my confidence and self esteem. As a result, I felt that people had to be educated about the importance of accessibility features in tools and applications. I volunteered to be a beta tester for SharePoint technologies, Microsoft Office, and third-party vendors of accessibility tools. These opportunities enabled me to offer feedback and help develop applications that everyone can use. Now, I want to share my experiences with other people through this column.


advertisement