Use a short identification for a complex diagram and provide its essential relationships in a nearby structured explanation or clearly linked description. A list of colors and shapes does not explain the process. Record the verified steps, branches or values in ordinary text so a reader can understand the information without depending on the image alone.
Inventory relationships before writing prose
Start from the actual approved visual, not its generation prompt. List each meaningful node, connection and condition. If the diagram contains data, preserve the values and units from a verified source. Do not turn an invented illustrative chart into an apparently factual measurement simply because it resembles a report.
Separate visual appearance from the message. The direction of an arrow may matter; a decorative texture may not. When labels in the image are unreadable or incorrect, rebuild the authoritative wording outside the raster artwork rather than treating the prompt's requested labels as evidence.
Make the explanation navigable
W3C WAI's complex-image tutorial discusses short descriptions together with longer descriptions of values, relationships and structure. It includes nearby or linked approaches. Choose an implementation that readers can find and navigate; a long flat string is not equivalent to headings and a table.
The publishing implementation owner should connect the description appropriately in the actual page. This guide provides a content handoff method, not a claim that Imagild automatically configures those relationships on another website. Supply a description title and the intended association with the approved image.
An original hypothetical three-node example
Imagine a diagram with “Upload approved photo,” “Choose visual treatment” and “Review actual result.” The final review can return to treatment selection if a protected detail changed. A text handoff records that loop explicitly, rather than merely saying three boxes are connected.
| Node | Next relationship | Condition |
|---|---|---|
| Approved photo | Treatment choice | Source ready |
| Treatment choice | Result review | Candidate created |
| Result review | Treatment choice or delivery | Revise if protected details fail; otherwise approve |
This is a hypothetical explanation, not a documented automatic Imagild workflow or a tested diagram. Ask a reviewer who cannot see the graphic to describe the order and revision branch using only the text. Compare their account with the intended diagram.
Verify both versions after revision
Accept when the text includes all essential relationships, is easy to locate and agrees with the delivered visual. Reject a description tied to an old version, missing branch conditions or numbers copied from unverified generated lettering. A visually attractive diagram with an inaccurate explanation has not passed.
Keep image version, short description, long description and source data together. Recheck them after any structural change. Imagild's Skills can help develop illustrative ideas; accurate labels, information structure and accessible publication require the external layout and website workflow. The useful output lets someone recover the diagram's meaning, rather than just hear an inventory of what it looks like.