In interactive diagrams eLearning, a schematic or illustration responds to the learner: each hotspot they select reveals a label, a short explanation or a change of state. For aircraft systems such as fuel, hydraulic and electrical, the design work is deciding what each hotspot says, in what order, and how it works without a mouse.
This guide is for instructional designers and subject-matter experts (SMEs) at aviation training providers who build system modules. It gives you a hotspot spec table, a layering method, and checks for accessibility, mobile use and SCORM tracking.
Key takeaways
- Use hotspots to identify parts, a stepped flow for paths and a state toggle for cause and effect.
- Build in layers by function, and write one spec row per hotspot before you open the authoring tool.
- Give every hotspot a text label, a keyboard stop and a target of at least 24 by 24 CSS pixels, plus a text version of the whole diagram.
- SCORM can report completion and a score. “Visited every hotspot” is a rule you build, and a click is not proof of understanding.
- Draw original schematics, because manufacturer figures carry license terms of their own, and keep a source log.
When do interactive diagrams eLearning modules beat a static figure?
Interactive diagrams eLearning modules beat a static figure when learners must identify parts, follow a flow path or see how a system state changes. A fuel schematic with twenty labels printed on it overwhelms a first-time learner. Revealing labels on demand, in layers, keeps attention on one idea at a time.
Not every need calls for a hotspot. The table maps each learning need to an interaction, using invented, simplified examples from a generic twin-engine system.
| Learning need | Best interaction | Example |
|---|---|---|
| Name and locate parts | Hotspot diagram | Select the boost pump to see its function |
| Follow a flow path | Stepped reveal that highlights the route | Fuel from tank to engine feed |
| See cause and effect | State toggle, such as open or closed | Close a crossfeed valve and see which tank feeds which engine |
| Recall without cues | Label-the-diagram or drag-and-drop check | Place the reservoir, pump and accumulator |
For a procedure, use steps instead. If the task is clicking through an EFB or maintenance system screen, build a software simulation instead. Our software simulation training guide for EFB and MRO systems covers that case.
How do you break an aircraft system schematic into layers?
Break an aircraft system schematic into layers by function, not by component. Start with an overview showing the system boundary, then add flow paths, then states such as valve positions, then abnormal conditions. Each layer answers one question, so learners never face the full drawing at once.
A four-layer pattern for a generic fuel system:
- Layer 1, overview: tanks, pumps and engine feed as grouped blocks, names only.
- Layer 2, flow: the normal path from tank to engine, highlighted one segment at a time.
- Layer 3, states: valves and pumps shown on, off, open and closed.
- Layer 4, abnormal: a failed pump or closed valve, and what changes downstream.
Keep each layer to a handful of hotspots. Maestro Learning’s design team says hotspots in an Articulate Rise labeled graphic should be used strategically, because overuse becomes tedious and disengaging. In our judgment, six to eight per screen is a sound starting point. That is a working rule, not a research finding.
Pro tip: Store Coordinates Apart From the Image. Keep hotspot positions as percentages of the image, in a field separate from the artwork file. A video-hotspot guide from Fora Soft recommends percentages so hotspots stay aligned on any screen size. A separate field also lets you swap a revised schematic without a rebuild. See eLearning templates and reusable interactive blocks for the reuse idea.
What should a hotspot spec for interactive diagrams in eLearning include?
A hotspot spec for interactive diagrams in eLearning should hold one row per hotspot: its ID, layer, reveal rule, states, content, text label, keyboard behavior, target size and tracking event. Writing the spec first lets SMEs approve content on paper and exposes accessibility gaps before the build.
The table is our own template, not a standard. The example column describes an invented crossfeed valve.
| Spec field | What to write | Invented example |
|---|---|---|
| ID and layer | System-based ID and layer number | F-03, layer 3 |
| Visible label | Plain name, worded as in the SME source | Crossfeed valve |
| Reveal rule | Free, ordered, or locked until others are visited | Locked until F-01 and F-02 are visited |
| States | Default, focus, active, visited, plus system states | Open and closed, shown by shape and text |
| Content on reveal | One idea, about 40 words or fewer, plus optional media | Joins the left and right feed lines. When open, either tank can feed both engines. |
| Accessible name | Short text a screen reader announces | Crossfeed valve, button |
| Keyboard | Tab order, open key, close key | Tab to reach, Enter or Space to open, Esc to close |
| Target size | Minimum size, larger on touch | 44 px marker, 24 px minimum |
| Tracking | What counts as visited, and where it is stored | Visited flag saved in suspend data |
How do you set reveal order and hotspot states?
Set reveal order by deciding whether learners explore freely, follow a sequence or unlock hotspots in groups. Free exploration suits reference diagrams, sequence suits flow paths, and gated groups suit complex systems. Then define four visible states for every hotspot: default, focused, active and visited, each distinguishable without color.
When order matters, say so. A ThingLink accessibility help page on the University of Arizona’s site advises telling learners directly, for example “Complete hotspots in numerical order.” WCAG 2.2 Success Criterion 1.4.1 (Level A) says color must not be the only visual means of conveying information or indicating an action.
Aircraft diagrams often color-code lines. Keep your source’s code, and add a pattern or text label so the meaning survives for color-blind learners and grayscale printouts. Mark visited hotspots with a check icon and text, not a tint alone. Avoid hover-only reveals, because touch screens have no hover.
How big should hotspots be on a phone or tablet?
Hotspots should be at least 24 by 24 CSS pixels under WCAG 2.2, and larger on phones and tablets. The Nielsen Norman Group recommends a physical minimum of 1 cm by 1 cm for touch targets and says larger targets suit use on the move. For tablet learners in a workshop, aim above both minimums.
WCAG 2.2 became a W3C Recommendation on 12 December 2024. Success Criterion 2.5.8, Target Size (Minimum), is Level AA. It allows smaller targets if a 24-pixel circle centered on each does not touch another target, or if the same function is available through another control on the page that meets the size rule.
Dense schematics are where this bites, because two valves a few millimeters apart cannot both be tapped reliably on a phone. Three fixes:
- Group neighboring parts into one hotspot that opens a zoomed view.
- Let learners pinch to zoom the diagram.
- Add a parts list beside the diagram, which can serve as the equivalent control.
How do you make interactive diagrams accessible to every learner?
Make interactive diagrams accessible with three layers: a text alternative that describes the whole schematic, a keyboard path through every hotspot, and a visible focus indicator on each stop. WCAG 2.2 requires text alternatives (SC 1.1.1) and keyboard operation of all functionality (SC 2.1.1), both at Level A.
The W3C’s tutorial on complex images (updated April 2026) lists diagrams and flow charts as complex images. It calls for a short description that identifies the image and a long description that holds the essential information, visible to everyone. For a fuel schematic, the long description lists tanks, pumps, valves and flow paths in order.
For keyboard use, order hotspots to follow the flow, activate with Enter or Space, and close with Esc. Articulate’s Storyline 360 support article (February 2026) describes this pattern for markers in 360 images. WCAG SC 2.4.7 (Level AA) adds that keyboard focus must be visible.
For the full standard, see our guide to accessible eLearning and WCAG 2.2 AA and accessibility in aviation eLearning.
Pro tip: Write the Long Description First. Draft the long description before you place a single hotspot. If you cannot say in text what the diagram teaches, the hotspots will not teach it either. The same text becomes the SME’s review script.
How do you track interactive diagrams eLearning results in SCORM?
Track interactive diagrams eLearning results in SCORM by turning hotspot visits into a completion rule, then reporting completion plus a score from a knowledge check. SCORM stores a learner’s status, score and resume data, but the course decides when “explored” counts as complete. A click shows engagement, not understanding.
Here are the four things to record, and where each one lives:
- Visited hotspots: one true-or-false course variable per hotspot, as Articulate community answers suggest. Unlock the next step once every variable is true.
- Resume position: suspend data. The SCORM run-time reference lists a suspend data limit of 4096 in SCORM 1.2, 4000 in SCORM 2004 2nd Edition and 64000 in 3rd and 4th Editions. One character per hotspot fits easily.
- Completion: the lesson status element in SCORM 1.2 and the completion status element in SCORM 2004.
- Understanding: a score from a knowledge check. Fora Soft’s guidance is to treat clicks as engagement and tie completion to a quiz result.
For per-hotspot analytics, xAPI statements on each activation are one option if your LMS accepts them. For the differences between versions, see SCORM 1.2 vs SCORM 2004.
Can you use manufacturer diagrams in an interactive diagram course?
Do not copy manufacturer manual figures into your course unless your license or the owner’s written permission covers training use. Draw original schematics instead, and keep a source log for every figure. Record the source, license, date and approver for each one.
Interactive use can raise new questions. Nucleus Medical Media, an illustration vendor, says licensing terms for interactive use may differ from those for static or video content. Ask any manual owner whether the license covers interactive, LMS-hosted use. This is not legal advice, so involve your legal contact.
An original schematic can show function rather than every line. Label it “Generic diagram for study, not representative of any aircraft type.” Tell learners to use current approved manual data for task work. Your approval holder decides the exact wording.
What should you do next?
Pick one system, such as fuel, and fill in the spec table for its overview layer only. Review it with an SME and build it. Then run a keyboard-only pass and a phone pass on a real device before adding more layers.
Disclosure: SimpliAuthor is a SimpliTrain product, made by the same company that publishes this site. Based on the vendor’s published documentation, the SimpliAuthor AI course authoring page describes placing interactive content such as accordions, interactive media and assessments on a course canvas, and producing SCORM-ready training. The page does not mention hotspots, and we did not test it for them, so check any trial against your spec table.
To see how a finished module is delivered and tracked in a training management system with a built-in LMS, request a SimpliTrain demo.
Frequently asked questions
What is an interactive diagram in eLearning?
An interactive diagram in eLearning is an image or schematic that responds to learner actions, usually by revealing text, media or a new state when a hotspot is selected. The learner chooses what to explore, and the course can record it.
How many hotspots should one diagram have?
No source we read sets a limit. Maestro Learning says the learning objective should decide and warns that overuse becomes tedious. Our working rule is six to eight per screen. If a layer needs more, split it or group neighboring parts.
Can SCORM track which hotspots a learner clicked?
SCORM has no built-in hotspot-visit field. It records status, score, interactions and resume data, so you build the rule in the course: set a variable per hotspot and report completion when all are visited. For click-level data, xAPI statements are one option if your LMS supports them.
How do I make a hotspot diagram work with a keyboard?
Make every hotspot a tab stop in logical order, open it with Enter or Space, close it with Esc and show a visible focus ring. WCAG 2.2 Success Criterion 2.1.1 requires all functionality to work from a keyboard at Level A. Test by finishing the whole diagram without a mouse.
Can I use manufacturer diagrams in my course?
Only if your license or the owner’s written permission covers training use, including interactive, LMS-hosted use. One illustration vendor notes that interactive licensing terms may differ from static use. We cannot give legal advice, so ask the licensor. Drawing an original, simplified schematic avoids the question.
Which authoring tools can build hotspot diagrams?
According to Adobe’s 2024 post, Adobe Captivate offers hotspot interactions alongside card, tab and carousel widgets. Maestro Learning describes the labeled graphic block in Articulate Rise. Articulate’s support site says Storyline 360 lets you add alt text to markers and hotspots in 360 images. Test any tool against your spec table.



