Jev tooltip action access

Review access to actions inside a tooltip or popover

Provide the popup's content and opening, action and dismissal paths. Compare hover-only access with supplied keyboard and touch paths without assuming behavior from a component name.

Which action access paths are actually supplied?Live API
Try an example

The action is confined to the supplied hover-only path.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

The API-collected roundup links the cited project. Its pinned source defines the decision adapted here. These synthetic inputs and explicit missing-context outcomes are original to this demonstration. The window returns a label; it does not run the linked application, execute its downstream actions or verify its performance claims.

Inspect content and supplied access paths.

Decision rules and labels
Hover-only interactiveOperable popover shownNoninteractive hintNeed interaction evidenceAccess gap shown
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

A help link is still an action when it sits inside a hover hint.

The hover-only preset places an action behind a pointer-only opening path. The keyboard-only preset supplies keyboard access but explicitly lacks touch access, so it receives Access gap shown. The text-only hint has no control that needs to be reached.

The popover preset supplies keyboard and touch paths for opening, reaching its link and dismissing the content. A HoverCard wrapper with no implementation details establishes none of those behaviors. It remains unresolved instead of inheriting capabilities from its name.

The linked rule is review-only and calls for actual keyboard and touch checks. This original window classifies supplied interaction descriptions. Operable popover shown does not certify accessibility or prove that the described paths work in a browser.

The API-collected roundup links the cited project. Its pinned source defines the decision adapted here. These synthetic inputs and explicit missing-context outcomes are original to this demonstration. The window returns a label; it does not run the linked application, execute its downstream actions or verify its performance claims.

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 tooltip action access.

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

    Add the information to check

    Provide the popup's content and opening, action and dismissal paths.

  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 Hover-only interactive, Operable popover shown, Noninteractive hint, Need interaction evidence, Access gap shown. 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 Need interaction evidence 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
Hover-only delete actionAccess gap shown77.0%
Popover interaction pathsOperable popover shown98.0%
Text-only hintNoninteractive hint100%
Keyboard access, no touch pathAccess gap shown98.0%
Unknown HoverCardNeed interaction evidence50.0%
Hint text aloneNeed interaction evidence83.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. 5 of 6 results matched the authored fixture expectations. For Hover-only delete action, the expectation was Hover-only interactive; the observed choice was Access gap shown.Verified

Understand the results

Replay the saved synthetic requests to inspect each recorded decision

Replay the saved synthetic requests to inspect each recorded decision. Authored expectations and model disagreements remain available; these examples are not a production accuracy benchmark.

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.

Runnable offline example

Run one sample, then inspect the local packet

View the code example
Single-request replay
npm install @typesafe-ai/sdk@0.6.0
# Set TYPESAFE_API_KEY privately in your shell.
node run-choice-sample.mjs samples.json case-1
python preview_choice_workflow.py samples.json saved-api-results.json
Scope of this demo

Where this decision fits

Useful scope

  • Reviewing access paths for popup actions
  • Separating text hints from actionable content
  • Finding missing focus or dismissal behavior

Outside this demonstration

  • Certifying accessibility
  • Claiming keyboard or touch testing occurred
  • Assuming a primitive name guarantees behavior
Example FAQ

Questions about tooltip action access.

Input scope and downstream handling determine what this judgment means.

What if keyboard access works but touch access is explicitly absent?

The complete supplied path has a known access gap. It receives Access gap shown, rather than being mistaken for a hover-only popup or missing evidence.

Is every tooltip with a link unusable?

The relevant question is how users can open it, reach the link and dismiss it. A supplied operable popover path differs from a pointer-only hint.

Why is hint text alone unresolved?

The text does not establish the component structure or whether other actionable controls exist. The complete content is needed for the noninteractive result.

Is the leading probability an accuracy measurement?

No. It is one value in the returned distribution over this request’s choices. The six synthetic fixtures have authored expectations; they do not measure production accuracy.

What happens on an API failure?

The window displays an error without a fresh judgment. An incomplete-input outcome describes the supplied evidence and is not used as a fallback for provider failure.

Try your own tooltip action access input

Edit the input above, or open the Playground to explore another decision.