iframe-title-unique
Frame title uniqueness (deprecated)
Replaced by identical-iframes-same-purpose since 1.8.0. A repeated title attribute is not a WCAG 4.1.2 violation, and identical-iframes-same-purpose already checks what ACT rule 4b1c6c asks: that frames sharing a name embed the same resource.
The id stays in the catalog and keeps running, but its result is fixed rather than decided per page — see the rule-ID deprecation policy for what that means for a stored baseline or a runOnly list that still names it.
Deprecated since 1.8.0 and always notApplicable: whether frames sharing a name embed the same resource is checked by identical-iframes-same-purpose.
Applies to. Nothing. The rule is deprecated and reports notApplicable on every page. Its id stays in the catalog, with meta.deprecated set and deprecation.replacedBy naming the successor, so a runOnly list, a stored baseline or an open Code Scanning alert that holds the id keeps resolving until the file is removed in 2.0.0 (docs/API_STABILITY.md, "Rule-ID deprecation policy").
Expectation. None. The check this rule used to make, that no two frames share a title attribute, is not a WCAG 4.1.2 requirement: the criterion asks that a frame's name be programmatically determinable, not unique, and ACT rule 4b1c6c accepts identical names on frames that embed equivalent resources. identical-iframes-same-purpose asks the question 4b1c6c does ask, of the computed accessible name, which for a frame is the title attribute unless aria-label or aria-labelledby overrides it.
Examples
<iframe title="Video player" src="a.html"></iframe><iframe title="Video player" src="b.html"></iframe>
Formerly a fail for the shared title. WCAG 4.1.2 does not require frame names to be unique; identical-iframes-same-purpose now raises this pair as cantTell, since the two frames share a name but embed different resources.