Quality Assurance

Getting Started with Literature QA

#1 Quality Assurance (QA) Introduction

QA is the final step in the process of creating an audiobook. In a nutshell, it means playing our books back just like our students will, and checking for anything that interferes with an enjoyable reading experience. Some of the things we test for:

  • Navigation. Can the reader move through the book easily and get where they need to go? Is the structure of the book sound?
  • Synchronization. Our finished VOICEtext books feature audio that is synchronized to match up with highlighted text on the screen, with the highlighting “following” the voice as the book progresses. So it’s important we check to make sure everything stays “in sync.”
  • Typographical errors or other problems with the text. Obviously, this one can be a real distraction!
  • Performance. Is the narrator creating an engaging listening experience for our students?
  • The Learning Ally Audiobook app is the software our members use to access their audiobooks, and includes both audio (the narration) and visual elements (the text of the book and the highlighting). We also use it for our QA review– that way we can be sure we’re testing the same experience our members will have. It’s a web app, so reading (or testing, in our case) can be done almost anywhere! Please be sure to view the following videos for an overview of the app interface and a tutorial on how to approach testing a book.

#2 Training Videos

Watch the following two short training videos.

Audiobook App Controls & Book Management

Note that a link to our audiobook app is below…but don’t log in yet!

How to QA

Note that links to your Assignments, Guidelines and Worksheet are linked in #5 below and at the top of this page.

#3 Join the Twist Team QA chat channel

Here’s the place for any questions you may have regarding reviewing titles in the QA community.

  1. Join us on Twist!
  2. Change email notifications to @mention only
  3. Link to Team QA Channel

#4 Open the Learning Ally Audiobook app

You MUST USE a special username and password for QA! Please do not try to create or use your own login.

Username: QAVolunteers
Password: learningally

Click here to open the web-based Audiobook app.

Guide to Getting Started with Learning Ally’s Audiobook app.

#5 Complete your first QA title review

  1. Select your audiobook on the Assignments page;
  2. Load the audiobook you’re reviewing in the web-based Audiobook app;
  3. Open the Literature QA Worksheet. This form will ask for concrete questions about potential problems you may find in the book. Read the form before starting the review of the book, so you will know what to look for. You need to complete one form for every book you review;
  4. Begin the QA process and jot down any issues you find along the way (review the Guidelines if needed);
  5. Sign up for another book if you can; you can review as many books as you like!
  6. Be sure to log your service hours at our Log Hours page.

Resources for Literature QA

See Guidelines

Expand Guidelines

  1. Synchronization is the most important thing to look for. Since our primary goal is to help students with their reading comprehension, if our highlighting does not align with the audio being read, they may become frustrated and discouraged with reading.
    • Any instance of the sync being off needs to be reported, no matter how minor.
    • Sync issues can be caused by long pauses, repeated sentences, or unfamiliar words.
    • Any sentences, phrases, or words left out can alter the sync.
  2. Headings (chapters, parts, books, etc.) must all be in the correct order and navigable, and all headings must be announced in a consistent way. For example, if the reader says “Chapter 1,” they should continue to say “Chapter” for each remaining section. Alternatively, if they just announce “One” they must continue to only say the number.
    • Check that no headings are skipped and that everything proceeds in the correct order, i.e., Chapter 1 does not go directly to Chapter 3.
  3. Typographical errors. While in theory errors should be caught before the QA stage, sometimes things do slip by. Please focus on titles and headings, where errors would be most distracting for our students.
    • Look to make sure all titles and headings are correctly capitalized and spelled, and please communicate any issues to the staff.
    • Point out any other spelling errors you may come across.
  4. Images. Many of our VOICEtext books contain images. It is vital that we check the synchronization, especially around the images.
    • A good tip is to click the last sentence before an image and let it play through to see how it flows.
    • The audio should play through the last sentence and pause on the image for no more than 2-3 seconds before continuing back into the text.
    • If there’s text or text bubbles in the image, let it play through to be sure the highlighting is not affected on the next page.
    • If you think an image’s text should not have been read, please report it. (MORE EXPLANATION)
    • Any instance of “image caption” being announced needs to be reported.
  5. Page Numbers. We do not announce any page numbers in VOICEtext books. However, the page references within the table of contents will be read. If a reader announces a page number elsewhere, please report it. This should not be done for ANY section of the book, Roman pages (book preface) or otherwise. No page announcements!
  6. If you see the words “empty heading” in a book, report it. This is a placeholder that should have been removed.
  7. Audio issues. If you hear anything that sounds wrong, point it out.
    • Background noise (hum, buzzing, mouse or mouth clicks)
    • Drastic changes in the volume of the recording
    • Loud sounds
    • Reader errors or ad libs (there has been the occasional curse word)
    • Plosives or sibilance
  8. Reader grade. Feel free to tell us what you liked or didn’t like about the book you QA’d.
    • What did the reader do well? Was it engaging? How was the pacing and tone of the book?
    • What could have been better? Did it fall flat? Was the reader engaging?