Form error 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 field markup, error element and wrapper behavior. Check whether aria-describedby points to this field's current error or leaves the association unresolved.
Start with one field and its current validation state. For this pattern, the describedby list must resolve to the element containing that field's error. A nearby paragraph or aria-invalid flag alone does not provide that reference.
This exercise deliberately covers aria-describedby. A different association mechanism goes to Unclear rather than being called defective. Linked concerns the supplied markup only; announcement timing, keyboard behavior and assistive-technology support need separate browser testing.
This original markup-review exercise 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 run a browser, test a screen reader or establish that the upstream rule executed.

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

Provide the field markup, error element and wrapper behavior.

Open the decision rules and keep the intended distinction between Linked, Unlinked, Noerror, 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 |
|---|---|---|
| An explicit error link | Linked | 100% |
| Visually adjacent only | Unlinked | 99.0% |
| A missing target ID | Unlinked | 97.0% |
| An opaque field wrapper | Unclear | 53.0% |
| No error after validation | Noerror | 100% |
| Hint and error references | Linked | 99.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.
It marks invalid state. In this example the text connection comes from aria-describedby and the referenced element. Those are separate checks.
Yes. Supply both IDs and their elements. This rule checks whether the current error is among them; it does not require removing the hint.
This narrow example returns Unclear for a different mechanism. Review that mechanism with its own contract instead of interpreting Unclear as an accessibility failure.
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.