Jev input label association

Check how a text input keeps its label

Provide the input and its complete surrounding markup or wrapper contract. Compare supported labels with a placeholder-only field or an absent association.

input label associationLive API
Try an example

The label reference matches this field ID.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

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.

For the target text input: Associated if nonempty text labels it through matching label-for/id, an enclosing label or aria-label; Placeholder if only placeholder text remains after those patterns are ruled out; Absent if complete evidence shows neither a supported label nor placeholder; Unclear if markup/wrapper behavior is missing or only another naming mechanism is supplied.

Decision rules and labels
AssociatedPlaceholderAbsentUnclear
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

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.

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 input label association.

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

    Add the information to check

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

  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 Associated, Placeholder, Absent, 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
Matching label referenceAssociated100%
Enclosing labelAssociated99.0%
An explicit ARIA labelAssociated100%
Placeholder alonePlaceholder100%
Label points elsewhereAbsent81.0%
Unknown wrapper outputUnclear67.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

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.

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 supplied label and input pairs
  • Separating placeholder text from a persistent label
  • Finding a wrapper contract that needs inspection

Outside this demonstration

  • Computing the complete accessible-name algorithm
  • Operating a browser or screen reader
  • Certifying accessibility compliance
Example FAQ

Using this example

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

Does every labeled field require an ID?

A matching for/id pair does, but an enclosing label can associate its text with the input without that pair.

What if our field uses aria-labelledby?

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.

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.