EK7: An Arrow in a Screenshot Does Not Mean Selected

Read EK7 tutorial annotations accurately: separate the control an arrow identifies from the active option, then check a before-and-after teaching example.

A red arrow points at “Detailed”, yet the highlighted option still says “Simple”. That screenshot can be entirely intentional: it may show what to choose next. It can also be badly captioned. For an EK7 tutorial reader, the arrow alone cannot settle which interpretation is correct. We should read the original interface state and the added teaching marks separately. The worked design example below shows how a small annotation can accidentally tell two different stories.

The picture before the action

Imagine a practice settings panel with two layout options, Simple and Detailed. Simple has a filled selection circle; Detailed has an empty circle. A tutorial author adds a red arrow pointing towards Detailed. These are invented controls for this explanation. The circles belong to the panel; the arrow belongs to the lesson. The visible state is Simple selected. The intended next action may be to select Detailed, but that requires words or a later frame.

Write a caption that matches the current moment: “Before changing the layout, Simple is selected. Choose Detailed next.” That sentence resolves the apparent conflict without changing the screenshot. A caption saying “Detailed is active” would conflict with our stated panel markings. The problem is not that the arrow is inaccurate about location. It is that a location pointer was used to imply a state change the picture does not yet show.

The after-frame needs its own evidence. In our practice sequence, the reader selects Detailed and its circle becomes filled while Simple's becomes empty. A short caption can now say “Detailed selected; change not yet applied” if a separate Apply step exists in the model. This introduces another useful boundary: selection and application may be distinct. Do not add that extra step to a real tutorial unless the actual interface and instructions establish it.

Give each annotation a purpose

A clear annotation describes its purpose. “Tap here next” identifies an action target. “Current selection” identifies a state. “Result after applying” identifies a later result. Using the same arrow style for all three without captions makes the lesson harder to follow. In an EK7 explanation, keep the original button label visible and place the added note beside it. Covering the label with an arrowhead removes information the learner needs to recognise the control.

Colour alone is a fragile explanation. A learner may see the image in greyscale, on a small screen or with a colour-vision difference. Pair a highlight with a circle, text label or numbered callout that has an explicit meaning. This is a practical teaching choice rather than a claim that one colour universally means active. Interfaces use visual cues differently, so a guide should identify the cue it is relying on instead of assuming a shared colour code.

Now test a deliberately ambiguous caption: “Change this.” The arrow identifies Detailed, but the sentence does not say whether the screenshot is before or after the change, whether a single selection is enough, or what should appear afterwards. Improve it by naming the action and expected visible evidence: “Select Detailed. The filled circle should move from Simple to Detailed.” That gives learners something specific to compare without requiring them to infer the author’s timing.

Review the caption against the frame

For authors, a useful review is to hide the caption temporarily and describe only what the interface proves. Then hide the screenshot and read what the caption claims. Do the two descriptions refer to the same moment? If not, mark them Before and After or obtain the missing frame. This catches a common editing problem: a new instruction is added to an older screenshot whose active selection was never updated.

Readers can report uncertainty without guessing the author's intention: “The arrow points to Detailed, but the filled circle remains beside Simple. Is this a before-action image?” That question is stronger than “your screenshot is wrong”. It describes the two conflicting cues and asks about their relationship. Include the tutorial heading or step number so the response can address the right frame, especially when several nearly identical settings images appear on one page.

An EK7 guide becomes easier to use when every picture answers two questions: what is true now, and what should the reader do next? Sometimes one image can answer both; sometimes a second image is needed. Keep the arrow's job limited to the meaning the caption assigns it. The learner can then follow a sequence through observed states, rather than treating every added mark as proof that an action has already happened.