Record who or what created each image description, where the description is used, and whether it survives into the publication file. An internal production note and text included in the book have different locations. Inspect the actual export before assuming that invisible-to-sight text is absent.
Separate the picture from its written description
A human-made illustration can have an AI-written description. Conversely, an AI-generated image can receive a description written entirely by its author. Keep these histories separate. One content record for the entire figure often hides a distinction that matters when reviewing how the finished book was produced.
Give the illustration and its description related identifiers. Record the image source, the description's initial authoring method, and any subsequent revision. This does not require storing every keystroke. It requires enough evidence to explain the material that actually reaches the reader.
Record the intended location of each text
A description might be an internal note for an illustrator, a visible caption, or alternative text attached to an image in a document. These are different uses. Label them clearly rather than placing all figure-related writing in an undifferentiated comments column.
For example, a generated sentence describing the mood of an illustration may exist only in an art brief. A second sentence explaining the figure's information may be attached to the exported image as alternative text. A review of visible pages alone could miss the second sentence even though it remains part of the delivered file.
Inspect the manuscript and the exported result
Check the editing application for image properties and related text fields. Then inspect the format-specific output using an appropriate preview and, where available, its accessibility inspection features. The question is whether the intended description survived and whether an obsolete working description survived with it.
Do not claim that a particular export preserves every field without testing it. A conversion can omit a useful description or carry an outdated one forward. Keep the source description available so that a missing field can be repaired without reconstructing its meaning from the finished picture.
Review descriptions for information and accuracy
Read each description beside the figure and the surrounding passage. Check whether it identifies the information a reader needs rather than inventing motives, emotions, or details that are not shown. A chart description should follow the actual chart; an ornamental image does not become an instructional diagram because a generated sentence says so.
When a human revises AI-written text, retain the history of that initial generation. KDP's content guidance distinguishes generated material from material a human created with AI assistance, and editing generated material does not automatically move it into the latter category. Consult the current guidance and submission questions for the publication decision.
Remove retired text deliberately
If the description changes, search for the old wording in the source package and exported files where inspection is possible. A visible caption may have been corrected while the attached image description still contains the earlier claim. Record which occurrence was replaced and which internal record is intentionally retained.
Keep archival production notes outside the release package when they are no longer needed there. Their presence in an authoring history is useful evidence; their accidental presence in a reader-facing file can create confusion. This cleanup is part of checking the actual deliverable, not a substitute for documenting its origins.
Finish with a content-location record
For each figure, mark the final description version, its destination, its origin, and the person who checked it. Add a brief note when the chosen format cannot carry a feature you expected. That note helps the next editor distinguish an intentional limitation from an unnoticed export failure.
An origin record does not certify that the description is accessible, accurate, or suitable. Those require their own review. It does, however, prevent the disclosure review from overlooking text merely because readers encounter it through a different reading mode or because it does not appear as a paragraph on the page.
Frequently asked questions
Clear answers for this publishing decision.
Is a human-made picture enough to classify its description?
No. The picture and its description can have different origins. Record how each was created and inspect which elements appear in the final publication file.
Does rewriting a generated description erase its origin?
Do not assume that it does. KDP explicitly distinguishes generated content from human-created content that received AI assistance, including cases where generated material is edited.
Can I check this only in the source document?
Check both source and output. Export behavior can change which descriptions survive, and the publication decision concerns the material actually delivered to readers.
What should the title, subtitle, description, and keywords look like before I upload?
Check the mechanical limits first, then make sure title, subtitle, categories, and description describe the same book for the same reader; a keyword is useful when it matches how that reader searches, not because it is popular.
Draft the listing fields in a book project