Input label association: six recorded examples
The downloads contain six original inputs, their expected labels and one recorded API observation per input revision. Disagreements stay visible.
Provide the input and its complete surrounding markup or wrapper contract. Compare supported labels with a placeholder-only field or an absent association.
The decision traces a relationship to one target input. Text beside the control or a label pointing to another ID does not establish that relationship. An enclosing label can provide it without a separate ID.
This small taxonomy covers the three patterns named in the question. Other naming mechanisms and unknown component output need separate inspection. Associated does not establish visible-label quality, styling, announcements or full accessibility compliance.
This original markup and policy review adapts a review-only rule in the taste-lint repository linked by the source post. The synthetic inputs and labels are ours. It does not execute the upstream check, run a browser or certify accessibility.

Use the sample to understand the rule, then test your own input for input label association.

Provide the input and its complete surrounding markup or wrapper contract.

Open the decision rules and keep the intended distinction between Associated, Placeholder, Absent, Unclear. Edit the choices only when testing your own rule.

Use a sample first, then try your own input. Compare the selected label with the other returned probabilities.

Review Unclear before using a result. The label is a decision about the supplied information, not an executed action.
| Original input | Observed label | Leading probability |
|---|---|---|
| Matching label reference | Associated | 100% |
| Enclosing label | Associated | 99.0% |
| An explicit ARIA label | Associated | 100% |
| Placeholder alone | Placeholder | 100% |
| Label points elsewhere | Absent | 81.0% |
| Unknown wrapper output | Unclear | 67.0% |
These are six original synthetic inputs, tested once per request revision. The percentage is the leading option probability, not measured accuracy. Authored expectations and any disagreements remain in the downloadable evidence. 6 of 6 results matched the authored fixture expectations.Verified
The downloads contain six original inputs, their expected labels and one recorded API observation per input revision. Disagreements stay visible.
The single-request SDK runner uses your private TYPESAFE_API_KEY. The offline consumer reads saved observations, checks request hashes and prints a pending output. It does not call the model or change any external system.
# Offline: inspect the downloaded saved observations. No API key is needed.
python preview_choice_workflow.py samples.json saved-api-results.json
# Optional live request: install the SDK and set TYPESAFE_API_KEY privately.
npm install @typesafe-ai/sdk@0.6.0
node run-choice-sample.mjs samples.json case-1
# The live response prints to the terminal; it does not update saved-api-results.json.The input contract and these limits define what the result means.
A matching for/id pair does, but an enclosing label can associate its text with the input without that pair.
That is outside this small set of supported patterns and returns Unclear unless another supported label is also established. Review its referenced elements separately; Unclear is not a defect verdict.
It describes the distribution over the supplied choices for this request. These six synthetic examples are functional tests with authored expectations, not a production accuracy benchmark.
No. The demo displays a label and distribution. The downloadable consumer produces a pending preview packet. Application code and a separate authorization policy would control any real action.
Edit the example above to see how a changed fact affects the decision, or open the Playground for another task.