• Monday, May 28, 2012

Previous

Next

Use Your Operating System’s Accessibility Features to Proofread Documents

October 11, 2011, 3:00 pm

One of my current research projects involves digitizing different versions of Hawthorne short story. I’ve been encoding different versions of the text so that I can discover the changes that editors made to the story as it circulated around the country in the nineteenth century. One of the most time-tested ways of transcribing documents accurately, however, is to work through a text with a partner: one partner reads the original text aloud while the second partner follows along in the transcribed text. When the two texts don’t match up, the team works together to figure out where the discrepancy lies and what changes need to be made to the transcription. Editors use such a system because our eyes and memory are, when unassisted, unreliable—one writer or editor is unlikely to catch all his or her own errors. For most of my project’s history, however, I’ve been transcribing alone: at first because I was a graduate student without funds to hire editors, and now because I work at a small college and—well—don’t have the funds to hire editors.

Early in my project, though, I discovered a way I could use my operating system’s built-in accessibility features as an editing partner (I will describe how to set this up in OS X, but I’ve heard from friends who use Windows that similar features can be activated in Windows’ accessibility settings). If you go to System Settings –> Speech and then click the box next to “Speak selected text when the key is pressed,” you will activate OS X’s Text to Speech fuctionality. You can assign a particular key combination to this feature by pressing the “Set Key…” button in this menu. You can also adjust the speaking rate, which you will probably want to tweak until you find the right setting for you and your project.

Once this feature is activated, you can select a block of text in any program, press the key combination you’ve chosen, and OS X will read the selected text aloud to you. The reading is a bit monotone, and the computer occasionally stumbles through an uncommon words—while working on my project, I always chuckle over the computer’s pronunciation of “Beelzebub”—but overall the reading is very solid. Whenever I transcribe a text for my project, I then check it by selecting paragraphs from my transcription, telling the computer to speak that text, and then reading along using the original document (usually a PDF scan of the original nineteenth-century newspaper or magazine page). Whenever what’s on the page doesn’t match with what the computer reads aloud, I stop and check my transcription. This system isn’t perfect, but has allowed me to work with much greater editorial precision than I could with my eyes and memory alone.

Not all of you are likely working on similar editorial projects, but I suspect that text-to-speech features could be used for other purposes, as well. We all know how difficult it is to proofread our own articles, for instance—perhaps asking the computer to read that text aloud could help us catch errors before we send those articles to editors or reviewers. How about you? Have you used text-to-speech (or other built-in features of your operating system) to meet unexpected needs? Tell us about your OS hacks in the comments.

[Creative Commons licensed photo by Flickr user Nic McPhee.]

This entry was posted in Software and tagged , , . Bookmark the permalink.

  • Print
  • Comment
  • acavender

    Thanks for the tip, Ryan! I just tested this in Google Documents, and it works like a charm. It might be a handy way for writing students to check some of their work.

  • http://twitter.com/KathrynTomasek Kathryn Tomasek

    What a great idea, Ryan!  Will definitely use the idea myself and pass it along to others, including my students.

  • sharkness

    The read text features are also a great way to review how our students using adaptive tools who may have low vision or who are blind hear the text we post- especially in online courses. Using these tools is a great way to make sure we communicate clearly and with accuracy.

  • hhopf

    Great idea!  If you are working with documents (not pdfs), you can use the compare documents tool in Track Changes as well.

  • http://www.facebook.com/kturnerunc Kathryn Turner

    This is wonderful! Thanks!

  • adenn

    Ryan is right: Editing your own work (even when “your own work” constitutes transcribing others’ work) is like treating yourself for shock–you *think* you can do it, but you really can’t.

    Research reveals that our brains process written material we see on paper and on a computer screen differently, and different mistakes are picked up when proofreading in each case. This applies to what we hear (as opposed to what we see) as well. We always benefit from a different perspective–another set of eyes, or in this case, ears.

    Utilizing the speech feature on your computer provides an additional editorial pass that engages a different part of the brain. This is an excellent suggestion, Ryan, thanks for sharing!

  • http://www.facebook.com/profile.php?id=15302996 Ryan Weberling

    I haven’t experimented with this yet, but it seems like it could be handy for language learning, especially with pronunciation and oral comprehension.

    To see the different options, go to Speech options in System Preferences. Click on the “System Voice” drop-down menu and select “Customize…” You can download a variety of different voices and languages—NOTE: these files are quite large: several hundred megabytes apiece.

  • kfoxt11

    I have two students this semseter with impaired vision: one with low vision and the other with no vision. I know that the blind student uses something that reads the text to him. It’s a great built in option.

    Also, I’m already thinking of other uses for this tool.

  • Frithweaver

    Honestly students could do a lot worse than just listening to their own papers before submitting them — the most boneheaded grammar issues might actually get caught before submission.

  • The Chronicle of Higher Education
  • 1255 Twenty-Third St, N.W.
  • Washington, D.C. 20037