Jev modal focus containment

Review keyboard focus containment in a modal dialog

Supply forward and backward keyboard observations for an open modal. Check whether focus stays inside, escapes to the background or lacks enough evidence for a conclusion.

modal focus containmentLive API
Try an example

Both required paths remain inside.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

This original code and behavior review adapts a review-only rule in the taste-lint repository linked by the source post. Synthetic inputs and labels are ours. Review-only source status does not establish an executed upstream check; this page does not run code or certify an application.

Use the supplied modal setting and observed keyboard behavior.

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

This check concerns the interval while a modal is open. It is separate from selecting a destination for focus after closing, announcing the dialog, or deciding whether a particular interaction should be modal.

The inputs are synthetic behavior reports. Contained means the supplied observations support this narrow claim, not that the page has passed a browser or accessibility audit. Test the actual interface with a keyboard before relying on it.

This original code and behavior review adapts a review-only rule in the taste-lint repository linked by the source post. Synthetic inputs and labels are ours. Review-only source status does not establish an executed upstream check; this page does not run code or certify an application.

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 modal focus containment.

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

    Add the information to check

    Supply forward and backward keyboard observations for an open modal.

  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 Contained, Escape, Nonmodal, 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
Both directions wrapContained99.0%
Forward escapeEscape88.0%
Backward escapeEscape99.0%
One direction unknownUnclear85.0%
An explicit nonmodal panelNonmodal99.0%
Library name onlyUnclear100%

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

Modal focus containment: 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 recorded keyboard-test observations
  • Keeping forward and backward paths distinct
  • Recognizing when the modal rule does not apply

Outside this demonstration

  • Operating a browser or moving focus
  • Certifying accessibility compliance
  • Inferring behavior solely from component imports
Example FAQ

Using this example

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

Does role=dialog prove focus is contained?

No. It identifies semantics, while containment concerns keyboard behavior. Supply the modality and both focus paths.

Does this check closing and focus restoration?

No. It evaluates focus while the modal remains open. Escape-key closure and the destination after closing need separate observations.

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.