Jev form error association

Check whether a validation error is linked to its field

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.

form error associationLive API
Try an example

The field references the ID of its own error.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

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.

For the target field: Noerror if no current validation error exists.

Decision rules and labels
LinkedUnlinkedNoerrorUnclear
A real response from the Jev API

Edit any input to explore a different decision. No request is sent until you run it.

Your next decision

Not run yet

Choose an example or write your own input, then run it to see the ranked choices.

Results are not stored by this site. Your submitted text is processed by the API provider.

The decision

What the decision checks

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.

Illustration of checking a code change and reviewing a flagged line
Illustration of the decision flow.
How it works

Try the example in four steps

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

  1. Illustration of adding the text or evidence for a decision

    Add the information to check

    Provide the field markup, error element and wrapper behavior.

  2. Illustration of defining a question and its allowed choices

    Confirm the question and labels

    Open the decision rules and keep the intended distinction between Linked, Unlinked, Noerror, Unclear. Edit the choices only when testing your own rule.

  3. Illustration of sending one input and comparing the returned choices

    Run the decision

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

  4. Illustration of reviewing a result and an uncertain item before using it

    Review the next step

    Review Unclear before using a result. The label is a decision about the supplied information, not an executed action.

Our API test

Recorded API observations

Recorded API observations
Original inputObserved labelLeading probability
An explicit error linkLinked100%
Visually adjacent onlyUnlinked99.0%
A missing target IDUnlinked97.0%
An opaque field wrapperUnclear53.0%
No error after validationNoerror100%
Hint and error referencesLinked99.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

Understand the results

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.

Using the result in your application

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.

Replay options

Inspect saved outputs or request a new decision

View the code example
Two independent commands
# 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.
Scope of this demo

Where this decision fits

Useful scope

  • Reviewing a captured field/error markup pair
  • Finding missing or mismatched description IDs
  • Recording when a shared wrapper needs inspection

Outside this demonstration

  • Certifying accessibility or WCAG conformance
  • Operating a screen reader or testing announcements
  • Treating every alternative association pattern as a defect
Example FAQ

Using this example

The input contract and these limits define what the result means.

Does aria-invalid link the error text?

It marks invalid state. In this example the text connection comes from aria-describedby and the referenced element. Those are separate checks.

Can an input reference both help text and an error?

Yes. Supply both IDs and their elements. This rule checks whether the current error is among them; it does not require removing the hint.

What if our component uses aria-errormessage?

This narrow example returns Unclear for a different mechanism. Review that mechanism with its own contract instead of interpreting Unclear as an accessibility failure.

Does the leading probability measure accuracy?

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.

Will a result change an external system?

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.

Test a different input

Edit the example above to see how a changed fact affects the decision, or open the Playground for another task.