From 4b0a220fdcfde78376a63f731b916b147eea77a9 Mon Sep 17 00:00:00 2001
From: Nicolas Ettlin <nicolas.ettlin@me.com>
Date: Tue, 31 Dec 2024 08:37:29 +0100
Subject: [PATCH] =?UTF-8?q?Replace=20`<iframe>`=20=E2=86=92=20`<fencedfram?=
 =?UTF-8?q?e>`=20in=20the=20Accessibility=20section?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The documentation of `<fencedframe>` contains leftovers copied from the documentation of `<iframe>` in its *Accessibility* section, which makes it confusing to read.
---
 files/en-us/web/html/element/fencedframe/index.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/files/en-us/web/html/element/fencedframe/index.md b/files/en-us/web/html/element/fencedframe/index.md
index c9c3d4e1b4fb1a9..112b34c1a038a00 100644
--- a/files/en-us/web/html/element/fencedframe/index.md
+++ b/files/en-us/web/html/element/fencedframe/index.md
@@ -78,7 +78,7 @@ People navigating with assistive technology such as a screen reader can use the
   height="320"></fencedframe>
 ```
 
-Without this title, they have to navigate into the `<iframe>` to determine what its embedded content is. This context shift can be confusing and time-consuming, especially for pages with multiple `<iframe>`s and/or if embeds contain interactive content like video or audio.
+Without this title, they have to navigate into the `<fencedframe>` to determine what its embedded content is. This context shift can be confusing and time-consuming, especially for pages with multiple `<fencedframe>`s and/or if embeds contain interactive content like video or audio.
 
 ## Examples