Build an accessibility correction budget from specific findings in the book, the formats affected, and the work required to verify each change. Separate diagnosis, source-file repair, export, and reader testing. An automated report can help identify issues, but the number of warnings alone does not describe the full effort or establish that a finished book is accessible.
Start with an issue inventory
Record each observed barrier with its location, affected format, and the reader task it interferes with. Examples may involve navigation, image explanations, heading structure, or information conveyed only through visual differences. Keep uncertain findings separate from issues that have already been confirmed.
Group repeated instances by cause without losing their locations. A heading-style problem across twenty chapters may have one source fix, while twenty different diagrams may each need a distinct explanation. Counting both situations as twenty identical tasks would produce an unhelpful estimate.
Separate shared repairs from format-specific work
Some corrections belong in the common manuscript, such as a clearer heading hierarchy or an explanation missing from the prose. Others depend on the exported format or reading environment. Identify where each change should be made so you do not pay for the same underlying repair independently in several files.
Then list the checks required for each delivered format. A successful correction in an editable document does not establish that every export preserves it. Budget the work needed to confirm the result in the actual publication artifacts rather than assuming that one clean source file completes the task.
Estimate from representative repairs
Choose a small sample of issues with different levels of difficulty. Time or otherwise record the work of understanding the problem, making the change, and checking the result. Use those observations to estimate similar items, while leaving unusual or uncertain cases as separate entries.
For example, correcting a repeated heading style may be straightforward after the cause is known. Writing a useful explanation for a complex diagram can require subject knowledge and editorial review. The estimate should reflect that difference instead of assigning one average amount to every item in a report.
Include the expertise needed to judge the result
Identify who can make each correction and who can assess whether it works. A designer may adjust contrast or layout, an editor may revise an explanation, and a subject reviewer may check that the new wording preserves meaning. Some projects also need testing with readers who use relevant assistive tools or reading methods.
Define the reviewer's deliverable before requesting a quote. A general opinion, a documented issue list, repaired source files, and verification of a final export are different scopes of work. Comparing prices without those distinctions can hide unfinished tasks in an apparently inexpensive proposal.
Allow for changes to layout and production files
Corrections can affect pagination, image placement, contents entries, or the relationship between a figure and its explanation. Include the necessary re-export and production checks in the plan. A useful change should not introduce a new broken reference or separate an instruction from the material it explains.
Keep the estimate tied to a particular manuscript version. If new chapters or illustrations arrive after the review, identify the additional scope rather than silently expecting the original allowance to cover it. Record which findings have been resolved and which still require a decision before final preparation.
Compare completion evidence with the agreed scope
Close each budget item against an observable result: a repaired source element, a verified export behavior, or a documented review outcome. A paid invoice confirms that work was billed; it does not by itself establish that the intended barrier was removed.
Retain the issue inventory and the evidence of checks with the project. Describe the completed work precisely and avoid turning a limited review into a universal accessibility claim. For the next edition, use the actual effort and remaining findings to improve the estimate rather than starting again with an arbitrary percentage of the book budget.
Frequently asked questions
Clear answers for this publishing decision.
Can I budget from the number of automated warnings?
Use the warnings as inputs to investigation, not as equal units of work. Repeated symptoms may share one cause, while a single complex finding may require several kinds of review.
Should accessibility work wait until the final export?
Early decisions can prevent repeated repairs, but the delivered files still need checking. Plan both source-level work during production and verification of the formats readers will receive.
Does a paid accessibility review guarantee the book is accessible?
The result depends on the review scope, methods, and findings. Record what was examined and resolved, and do not claim more than the evidence supports.
What does this book cost to print and produce, and what should the list price be?
Printing cost follows from the trim, ink, and page count, the list price sets the royalty after that cost, and the production budget should be estimated before generation starts, so compare these numbers before you commit to a format or a plan.
See what a book project costs in credits