New
Introducing React Bench, see how different models perform on React code

react-doctor/iframe-has-title

Require a unique, descriptive title attribute on iframes so assistive-tech users can identify embedded content.

Status
Active
Category
Accessibility
Assessment
Evidence-required risk
Required evidence
source code, rendered UI, accessibility audit
Default configuration
Enabled
Default severity
warn
Show technical metadata
Scope
All supported frameworks
Active when
always (unless customRulesOnly=true)
Requirements
react
Tags
react-jsx-only
Priority
58 (P2)
Source
oxlint-plugin-react-doctor
Rule set
oxlint-plugin-react-doctor 0.9.3 (prompt schema 2)
On this page

Validation prompt

Confirm the detector match and collect the required evidence before deciding whether an edit is warranted.

Fires on <iframe> elements missing a title attribute, or with title set to an empty string, undefined, false, true, or a non-string literal. It checks that a usable title is statically present, not whether titles are unique or accurately describe the embedded content.

Suppress when: spread props like <iframe {...props} /> can forward a title that the static check cannot see: verify the rendered frame before editing. An aria-hidden frame is not a safe exemption when it remains focusable, because keyboard focus can then enter content omitted from the accessibility tree.

Evidence boundary

The diagnostic proves only that the detector’s modeled source pattern matched. It does not prove runtime impact, product intent, rendered failure, or that one remediation is correct.

Establish the environment, repository policy, exceptions, and required rendered or runtime evidence before deciding the occurrence.

Record one outcome:

  • Confirmed failure: The required evidence establishes the violation.
  • Rejected: A documented exception or false-positive predicate applies.
  • Needs evidence: Named evidence can still be collected.
  • Unavailable: Required evidence cannot be collected in this run.
  • Waived with evidence: An authorized, scoped exception applies to an established failure.
  • Observation: The review records an optional tradeoff without claiming a defect.

A waiver records its scope, authority, evidence, and review condition. It is not a pass or false positive.

Default severity is registry metadata. Use the occurrence’s JSON severity after repository configuration when ordering real findings.

Fix prompt

Apply this candidate correction only after the required evidence confirms the risk.

For a functional frame, add a concise title that identifies its content or purpose: <iframe src='...' title='Q3 revenue chart' />. Avoid generic titles like 'iframe', 'frame', or 'content', and distinguish separate frames when their purposes differ. If a frame is genuinely decorative or inactive, prefer removing, unmounting, or fully hiding it rather than leaving a focusable iframe aria-hidden; do not use aria-hidden as a substitute for a title. See https://oxc.rs/docs/guide/usage/linter/rules/jsx_a11y/iframe-has-title

Repository-wide copy prompt

Use this repository-wide prompt only after validating each occurrence. For one occurrence, use the guidance above.

Show repository-wide prompt

Fix every confirmed react-doctor/iframe-has-title diagnostic in the current repository.

Required change:

  • For a functional frame, add a concise title that identifies its content or purpose: <iframe src='...' title='Q3 revenue chart' />. Avoid generic titles like 'iframe', 'frame', or 'content', and distinguish separate frames when their purposes differ. If a frame is genuinely decorative or inactive, prefer removing, unmounting, or fully hiding it rather than leaving a focusable iframe aria-hidden; do not use aria-hidden as a substitute for a title. See https://oxc.rs/docs/guide/usage/linter/rules/jsx_a11y/iframe-has-title.

Validation before editing:

Fires on <iframe> elements missing a title attribute, or with title set to an empty string, undefined, false, true, or a non-string literal. It checks that a usable title is statically present, not whether titles are unique or accurately describe the embedded content.

Suppress when: spread props like <iframe {...props} /> can forward a title that the static check cannot see: verify the rendered frame before editing. An aria-hidden frame is not a safe exemption when it remains focusable, because keyboard focus can then enter content omitted from the accessibility tree.

Constraints:

  • Make the smallest change that fixes the root cause.
  • Preserve behavior and interfaces unrelated to this diagnostic.
  • Reuse existing project components, utilities, and conventions.
  • Do not introduce render-phase side effects, render-phase state updates, or Hooks rule violations.
  • Preserve accessible names, focus order, keyboard behavior, and touch access not targeted by this rule.
  • Adapt identifiers and framework details instead of copying blindly.
  • Do not disable the rule or suppress matching code.
  • Confirm this rule is enabled for the project: always (unless customRulesOnly=true).

Assessment:

  • Record detector evidence, applicability facts, assumptions, missing evidence, and the rule class for this occurrence.
  • Return one outcome: Confirmed failure, Rejected, Needs evidence, Unavailable, Waived with evidence, or Observation.
  • A waiver records the established failure, scope, authority, evidence, and review or expiry condition. It is not a pass or false positive.

Verification:

  • Run focused tests for the changed behavior.
  • Run React Doctor and confirm this diagnostic no longer appears from changed code.
  • Run an unfiltered scan of the affected scope before claiming no cross-category regression.
  • Report the files changed and any checks you could not run.