# axe-core frame-focusable-content error: frame has focusable content without title - how to fix it

## TL;DR

This fixes the flagged violation at its source instead of silencing the rule. A frame or iframe contains focusable content but has no title, so screen-reader users get no context for what is inside. Follow the steps, re-run the scan, and gate the rule in CI so it stays fixed.

## The error, verbatim

```text
axe-core frame-focusable-content error: frame has focusable content without title
```

## Fix it step by step

### Step 1

Add a concise title attribute to the frame describing its content, like Advertisement or Checkout form.

Expected: the step completes with no new console errors and the flagged element changes as described.

### Step 2

Make each title unique when several frames sit on one page.

Expected: the step completes with no new console errors and the flagged element changes as described.

### Step 3

Re-run axe; the rule passes once every frame with focusable content has a non-empty title.

Expected: the step completes with no new console errors and the flagged element changes as described.

## When to use this skill

- Your scan report lists this exact rule or failure
- You are clearing automated accessibility failures before release or audit
- A CI accessibility gate is red because of this item

## When NOT to use this skill

- Frames with no focusable content do not need titles under this rule, but giving them one is still good practice.
- The issue only appears in manual screen-reader testing and no automated rule flags it
- You are doing a full manual WCAG audit; this skill covers one automated check

## Compatibility

axe-core 4.8+ (rule frame-focusable-content, WCAG 4.1.2).

## Variant phrasings

### axe frame-focusable-content: frame without title has focusable content

Same underlying issue and the same fix. Searchers phrase it different ways; the remediation does not change.

## Why it happens

A frame or iframe contains focusable content but has no title, so screen-reader users get no context for what is inside. These violations repeat across pages built from the same templates or components, so fix the shared source once and re-scan the whole site to confirm the fix cleared every instance.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_y8NYnRbE6CMRUdqxRUE0mQ