Identify the decision the diagram supports
Choose whether the reader needs to understand component identity, packing, proposed layout or another actual task. A diagram can help show relationships but should not imply a certified installation method if it is conceptual. Record the assembly reference, version and relevant source or provider instructions. Keep measured dimensions and illustrative geometry distinct. The reader should know what the image describes before trying to use it as a practical instruction.
Use stable component labels
Give essential parts references matching the asset register and pick list. Show connections or positions with clear labels and sufficient visual distinction. Do not rely on colour alone or tiny unexplained icons. Separate optional components and proposed substitutes. A numbered drawing becomes useful when the same numbers appear in a text list stating description, quantity, role and any confirmed relationship. This also helps people using printouts or a different viewing scale.
Provide an accessible equivalent
Explain the relationships and intended reading order in text. A component table or ordered list should preserve information needed for the task, including relevant dimensions, assumptions and unresolved questions. Online diagrams should be accompanied by appropriate text rather than an unhelpful label such as image. W3C’s non-text contrast guidance can inform digital presentation; it does not establish physical assembly acceptance. Keep actual technical or safety instructions with the responsible provider.
Worked example — fictional
A fictional learning resource explains a portable display kit with a frame, two feet, connectors and a case. The illustration uses component references matching a written pick list. A learner can identify the missing connector from the list without relying on colour perception or dragging an object. The resource labels the assembly conceptual and links to the actual equipment instructions for real use. A graphic replacement appears as a separate component with its own dimensions and review questions, not as evidence that the kit is ready or certified.
Common pitfalls
A detailed sketch can look authoritative while its configuration is only illustrative. A legend can describe colours without describing component relationships. Tiny text can become unreadable when printed or zoomed. A conceptual arrow does not prove safe assembly order. Do not copy manufacturer drawings beyond permission or publish private site photos as educational diagrams automatically. Keep unknown compatibility visibly unresolved.
Test the explanation through the task
Use the disassembly tool and component list to build a numerical or text equivalent. Ask whether a reader can identify parts, quantities and open questions using either representation. Check keyboard and zoom use for interactive outputs. Export a readable list with the same references. The final resource should improve understanding and handover while leaving actual physical method, compatibility and competent acceptance with their responsible owners.
Decision checkpoint
Ask what information would be lost if the diagram could not be seen. Add that information to the equivalent list or explanation. A complete alternative should preserve the relevant relationships and decision inputs, rather than merely state that the illustration depicts a display.
Take this to the next job
- Define diagram task and scope
- Use stable component references
- Avoid colour-only meaning
- Provide equivalent text or data
- Keep conceptual and accepted methods separate
