Readability Analyzer Manual

The Howard Forge Press Readability Analyzer is designed to help educators, parents, students, readers, and writers examine the readability of a text and identify features that may make it easier or harder to decode.

The analyzer evaluates measurable characteristics of writing—including sentence length, word complexity, syllable count, passive voice, rare or abstract vocabulary, and sensory language—and combines them into an overall Readability Score. The software currently reports this value as a Dyslexia-Friendly Score (DF Score), so that terminology still appears in validation reports, graphs, and tables.

For longer works, the analyzer can also compare readability from chapter to chapter, helping identify sections that may present greater or lesser reading difficulty.

The analyzer is intended for educational, research, comparison, and visualization purposes. It is not a diagnostic tool and should not be treated as a definitive measure of whether an individual reader can or cannot read a particular work.

---

1. Quick Start

If this is your first time using the analyzer, the easiest way to learn it is to begin with the provided Sample Text.

1. Download the sample text file.
2. Open it in a plain-text editor such as Notepad.
3. Look at the special tags beginning with ###.
4. Launch the Readability Analyzer.
5. Upload the sample file.
6. Run the analysis.
7. Review the overall score, chapter results, and visualizations.

The sample file is a prepared version of Nathaniel Hawthorne’s The Scarlet Letter. It has already been successfully analyzed, so you can use it to see exactly how a working input file should be structured.

2. Preparing Your Text

For the best results, prepare your document as a plain-text (.txt) file.

The analyzer uses several special tags to understand the structure of your document:

### METADATA START
### METADATA END

### START
### END

### CHAPTER 1
### CHAPTER 2
### CHAPTER 3

Each type of tag has a different purpose. Metadata identifies the document, START and END determine what text will be analyzed, and CHAPTER tags divide longer works into sections for comparison.

3. Adding Metadata

The metadata section tells the analyzer what document it is working with. Place it near the beginning of the file.

Use this format:

### METADATA START

Title: The Scarlet Letter
Author: Nathaniel Hawthorne

### METADATA END

Additional information may also be included if desired:

### METADATA START

Title: Pride and Prejudice
Author: Jane Austen
Genre: Classic Fiction

### METADATA END

Keep the tags exactly as shown. Text inside the metadata section identifies the document and is not intended to be treated as part of the prose being analyzed.

4. Choosing What Part of the File to Analyze

You do not have to analyze everything contained in your text file.

Use:

### START

to identify where the text you want analyzed begins.

Use:

### END

to identify where the text you want analyzed ends.

This is particularly useful when working with documents that contain material you do not want included in the analysis, such as:

• Project Gutenberg license information
• tables of contents
• introductions
• editorial notes
• appendices
• acknowledgments
• other front or back matter

For example:

### METADATA START

Title: Sample Book
Author: Sample Author

### METADATA END


Material here will not be analyzed.


### START

Text you want analyzed appears here.

### END


Material here will not be analyzed.

Only the text between ### START and ### END should be included in the analysis region.

5. Formatting Chapters

For books or other long-form texts, use chapter tags so the analyzer can divide the text into sections and compare readability across the work.

Format them like this:

### CHAPTER 1

Chapter text begins here.

### CHAPTER 2

The next chapter begins here.

### CHAPTER 3

And so on.

The analyzer can then calculate chapter-level results and create visual comparisons that show how readability changes throughout the text.

For consistency, use the same format throughout the document:

### CHAPTER 1
### CHAPTER 2
### CHAPTER 3

6. Complete Recommended File Structure

A properly prepared book will generally look like this:

### METADATA START

Title: Your Book Title
Author: Author Name
Genre: Optional Genre

### METADATA END


Material that you do not want analyzed may appear here.


### START


### CHAPTER 1

Chapter 1 text...


### CHAPTER 2

Chapter 2 text...


### CHAPTER 3

Chapter 3 text...


### END


Material that you do not want analyzed may appear here.

This structure gives the analyzer three kinds of information:

• METADATA tells the analyzer what the document is.
• START and END tell it what portion of the document should be analyzed.
• CHAPTER tags tell it how to divide that material into sections for readability comparisons.

7. Analyzing a Short Passage

You do not necessarily need to analyze an entire book. If you want to analyze only a passage or selected section, place that material between the START and END tags.

### METADATA START

Title: Classroom Passage
Author: Unknown

### METADATA END


### START

The passage to be analyzed goes here.

### END

Chapter tags are primarily useful when you want section-by-section comparisons across a longer work.

8. Running the Analyzer

Once your text has been properly prepared:

1. Launch the Readability Analyzer

Use the ANALYZE TEXT button in the Howard Forge Press Reading Lab.

2. Load Your Prepared Text

For your first attempt, we recommend using the provided sample file.

3. Run the Analysis

The program examines the selected text and calculates its readability features.

4. Review the Output

Depending on the text, the analysis may include an overall readability score, chapter-level results, tables, graphs, and heat maps.

9. Understanding the Readability Score

The analyzer combines several measurements into an overall Readability Score.

In the current software and validation reports, this value is labeled the Dyslexia-Friendly Score (DF Score). Because the software output has not been renamed, you will still see DF Score in reports, graphs, and tables.

Higher scores generally indicate greater predicted readability.

DF Score	Interpretation
Below 40	Highly Challenging
40–50	Challenging
50–55	Dyslexia-Friendly
55–60	Highly Dyslexia-Friendly
Above 60	Extremely Dyslexia-Friendly

These category names are retained here because they are the labels currently used by the analyzer’s validation reports.

For example, The Scarlet Letter received an overall DF Score of 43.60, placing it in the Challenging range.

The score should be used as a comparison and screening tool, not as an absolute judgment about a book or reader.

A challenging score does not mean a text has no educational or literary value. Likewise, a high readability score does not guarantee that every reader will find a text easy.

10. What the Analyzer Measures

The analyzer examines several measurable characteristics of writing that can influence readability.

Sentence Count

The number of sentences within the section being analyzed.

Word Count

The number of words in the section.

Average Sentence Length

Longer sentences often require readers to retain more information while decoding the sentence.

Average Word Length

Longer words can require greater decoding effort.

Average Syllables per Word

Words containing more syllables generally increase word complexity.

Passive Sentences

Indirect grammatical constructions may make relationships between subjects and actions harder to follow.

Rare or Abstract Words

Uncommon vocabulary and words representing abstract concepts may create additional reading difficulty.

Sensory Words

Sensory language can support visualization and comprehension.

11. Chapter-by-Chapter Readability

One of the analyzer’s most useful features is its ability to show that readability can vary substantially within the same book.

A book with a challenging overall score may still contain relatively accessible chapters. Likewise, a generally readable book may contain unusually difficult sections.

For example, the Scarlet Letter analysis found:

• Chapter 24: DF Score 39.75
• Chapter 17: DF Score 53.71

This information can help an educator, parent, reader, or writer identify sections of a text that deserve closer attention.

12. The Readability Score Trend

For a chaptered text, the analyzer can graph the readability score across the entire work. In the current validation report, this graph is labeled Dyslexia-Friendly Score Trend.

Instead of seeing only one average score, the graph shows how readability rises and falls from chapter to chapter.

This can help identify:

• unusually difficult chapters
• unusually accessible chapters
• abrupt shifts in readability
• portions of a work that deserve closer examination

13. Understanding the Z-Score Heat Map

For longer works, the validation system can display readability features as a Z-score heat map.

A Z-score describes how far a measurement is from the average for that particular work.

• 0 = approximately average
• Positive value = above the book’s average
• Negative value = below the book’s average

The heat map lets you compare individual readability features across chapters.

Instead of merely telling you, “This chapter is more difficult,” the visualization can help answer a more useful question: “What changed in this chapter?”

For example, a section might contain:

• longer sentences
• longer words
• more syllables per word
• more passive sentences
• more rare or abstract vocabulary

14. Chapter Outlier Explanations

Validation reports may also identify chapters in which one or more readability measurements are unusually high or low.

In the Scarlet Letter report, Chapter 24 was flagged for several features, including high word length, high syllables per word, passive sentences, and rare or abstract vocabulary.

These explanations provide more information than the overall score alone because they can help identify why a particular section may present additional reading difficulty.

15. Using the Analyzer as an Educator

Teachers can use readability analysis before assigning a text.

Possible uses include:

• identifying difficult chapters before students encounter them
• preparing vocabulary support
• deciding where guided reading may be useful
• comparing alternative texts
• evaluating classroom passages
• examining student writing
• planning additional instructional support

The goal is not necessarily to remove difficult books from the curriculum. Instead, identifying difficult sections can allow teachers to provide support before difficulty becomes frustration.

16. Using the Analyzer as a Parent or Reader

Reading fluency and intelligence are not the same thing.

A reader may understand sophisticated concepts while requiring significantly more effort and time to decode the text that communicates them.

Parents and readers can use readability analysis to anticipate where additional support may be useful.

That support might include:

• additional reading time
• vocabulary preparation
• discussion before reading
• an audiobook used alongside the text
• guided reading
• reviewing difficult passages in advance

The purpose is not to avoid challenging literature. It is to prepare the reader to succeed with it.

17. Using the Analyzer as a Writer

Writers can also use the analyzer to examine their own work.

Readability analysis does not mean every sentence should be made shorter or every difficult word removed.

A writer may intentionally use complex prose in one scene and simpler, faster-moving prose in another. The analyzer provides information that can help writers see those patterns and make stylistic decisions more consciously.

Clear, readable writing can still be rich, compelling, and intellectually or emotionally complex.

18. What the Analyzer Does Not Measure

The current analyzer focuses primarily on characteristics of the language that influence decoding and readability.

It does not fully measure higher-level cognitive complexity such as:

• complicated plots
• symbolism
• thematic depth
• abstract reasoning
• nonlinear chronology
• multiple points of view
• the difficulty of understanding character motivations

This distinction is important. A text may be relatively easy to decode while still being intellectually complex. Another text may tell a simple story using language that is difficult to decode.

The Readability Score primarily addresses the characteristics of the language itself rather than the intellectual complexity of the ideas being expressed.

19. Methodology and Development

The Readability Analyzer began with a real-world observation.

After reading an early draft of William and Hannah, a reader with dyslexia described the novel as a “super sweet, easy read.” That experience prompted a broader question: could measurable characteristics of writing help explain why some texts are easier for readers to decode than others?

Development focused on features that were meaningful but could also be measured computationally, including:

• sentence count
• word count
• sentence length
• word length
• syllables per word
• passive sentences
• rare or abstract words
• sensory words

Early versions of the model were compared against examples of more accessible and more challenging prose, including Great Expectations, Moby-Dick, and The Scarlet Letter.

A validation system was subsequently developed to examine differences not only between books but also among chapters within the same book.

20. Privacy and Responsible Use

The public Readability Analyzer should not be assumed to provide secure storage or protection for unpublished or confidential text.

Writers and researchers should exercise caution when evaluating private, sensitive, or unpublished material.

Users should upload only material they have the legal right to analyze.

The analyzer is intended for educational and research purposes and should be used for relative comparison and visualization rather than publication-quality statistical analysis.

21. Why Readability Matters

Readability is not simply a technical characteristic of writing.

For a reader who struggles with decoding, the effort required to process individual words and sentences can consume attention that might otherwise be available for following the story, recognizing themes, making connections, and interpreting ideas.

That is why readability should not be confused with intellectual difficulty. A reader who needs more time to decode a passage may still be fully capable of understanding and engaging with sophisticated ideas.

Readability analysis is therefore not about eliminating challenging literature or lowering expectations. It is about understanding where barriers may occur so that readers can receive the preparation and support they need.

“Readability isn’t about lowering the bar. It’s about building a better ladder.”