# Choose a next action the post and destination can actually deliver

Original constructed teaching cases with complete context. No real financial records, sponsorships, contracts, people, interviews, tests, preferences or payments.

Choose one useful reader action, state what happens next and make the actual destination fulfill that promise. Distinguish a question, download, service enquiry and purchase. Review readable link purpose, required information, errors and confirmation across the complete route before calling the action finished. A click does not establish understanding, consent, a qualified lead or a customer.

## Start with the reader’s next useful task

A post explaining how to check a reporting period can reasonably offer a complete worksheet or ask which boundary is still unclear. A post about an available service can invite a scoped enquiry. Choose the action that follows from the explanation rather than append a request to comment, follow, message, download and buy simultaneously.

Write the intended outcome in ordinary language: “Download the blank source-check worksheet” is a different promise from “Send a question about a supplied worksheet.” State meaningful conditions, such as a required account, file format, actual price or response process, when they apply. Do not invent scarcity, a guaranteed result or a free download that quietly begins a paid order.

## Match the action label to the actual destination

Inspect the real target in the intended signed-out or authorized state. Read its heading, available artifact and next step. W3C’s link-purpose guidance supports understandable link text or programmatically associated context and continuity between a link and its destination; it does not predict a conversion-rate increase from a preferred verb.

If the route redirects, requires authentication or has expired, retain what you actually observed and repair or withdraw the promise before a real release. Keep a source reference distinct from an application action. A native profile button, post link and external form have different availability and behavior; this guide does not assert that every LinkedIn account has a custom button.

## Check required input and the result after an action

For a request form, specify the information genuinely needed for that request and label its controls. W3C treats visible labels/instructions and the programmatic naming of controls as related but distinct accessibility concerns. A placeholder alone can disappear while someone types; a visual check alone does not establish complete accessibility.

Walk through relevant empty, invalid, successful and recovery states using permitted fictional inputs in a test context. Error text should identify the affected item and what failed rather than silently altering an entry. A successful send needs an actual saved/received confirmation appropriate to the system; a spinning button or thank-you screen alone does not establish delivery to another person.

## Resolve three constructed action mismatches

A1 — Constructed download: the post offers a blank source-check worksheet, but the target only shows a newsletter sign-up. Decision: supply the promised artifact through the appropriate route or explicitly change the offer before publishing. Outcome: an honest destination plan; no presumed download, subscription or preference.

A2 — Constructed service question: the action says “Ask about one worksheet review,” while the form silently requires a phone number and an unrelated marketing choice. Decision: review the actual necessity, purpose and applicable consent process; keep the request separate from other choices. Outcome: no inferred consent merely because someone wanted the review.

A3 — Constructed apparent success: a request button displays a success message after a simulated response, but no authoritative receipt was checked. Decision: label the result as a test state and verify the appropriate saved/received outcome before claiming delivery. Outcome: no real enquiry or customer attributed to the post.

## Measure the named action without changing its meaning

Define the actual event, denominator, observation period and exclusions before reviewing results. A link click can measure an entered transition; a completed worksheet task needs its own evidence. A preference requires an explicit response, and a payment requires the appropriate verified source. Keep unavailable observations unknown.

If comparing alternative wording, retain the assignment and analysis plan and inspect competing changes in audience, offer and destination. A more descriptive label may be worth adopting because it tells the truth and is easier to understand, even when no causal conversion lift has been established.

## Save one promise-to-result review

The private record keeps intended reader/task, exact action wording, destination/version/access state, required information, failure/recovery states, authoritative finish evidence and measurement limits. The packet contains complete original cases and a blank record. It does not create a landing page, form, enquiry or marketing list.

W3C’s relevant Understanding sections were read on 1 November 2026; they explain individual success criteria and are not a complete conformance certificate. All journeys here are constructed. No message, subscription, purchase, participant task or conversion experiment was performed.

## Primary sources

- [W3C: Link Purpose in Context](https://www.w3.org/WAI/WCAG22/Understanding/link-purpose-in-context.html)
- [W3C: Labels or Instructions](https://www.w3.org/WAI/WCAG22/Understanding/labels-or-instructions.html)
- [W3C: Error Identification](https://www.w3.org/WAI/WCAG22/Understanding/error-identification.html)