From 4af483c7994beed123638af9cf9656ca4ade71cb Mon Sep 17 00:00:00 2001
From: Giacomo Petri <giacomo.petri@usablenet.com>
Date: Thu, 24 Jul 2025 14:28:06 +0200
Subject: [PATCH 1/2] Remove Failed Example 2 since it's currently passing the
 ACT rule

---
 _rules/focusable-no-keyboard-trap-80af7b.md | 22 +++------------------
 1 file changed, 3 insertions(+), 19 deletions(-)

diff --git a/_rules/focusable-no-keyboard-trap-80af7b.md b/_rules/focusable-no-keyboard-trap-80af7b.md
index 1872cb5e8d3..97eb88aee46 100755
--- a/_rules/focusable-no-keyboard-trap-80af7b.md
+++ b/_rules/focusable-no-keyboard-trap-80af7b.md
@@ -164,22 +164,6 @@ This [focusable][] element creates a keyboard trap bringing focus to the `button
 
 #### Failed Example 2
 
-These [focusable][] `button` elements create a keyboard trap preventing the last `button` to be reached using the keyboard.
-
-```html
-<button onblur="setTimeout(() => this.nextElementSibling.focus(), 10)">
-	Button1
-</button>
-<button onblur="setTimeout(() => this.previousElementSibling.focus(), 10)">
-	Button2
-</button>
-<button>
-	Button3
-</button>
-```
-
-#### Failed Example 3
-
 This `button` element is between other `button` elements creating a keyboard trap.
 
 ```html
@@ -188,7 +172,7 @@ This `button` element is between other `button` elements creating a keyboard tra
 <button onblur="setTimeout(() => this.focus(), 10)">Button 3</button>
 ```
 
-#### Failed Example 4
+#### Failed Example 3
 
 These focusable `button` elements create a keyboard trap with no instructions.
 
@@ -205,7 +189,7 @@ These focusable `button` elements create a keyboard trap with no instructions.
 <a id="link2" href="#">Link 2</a>
 ```
 
-#### Failed Example 5
+#### Failed Example 4
 
 These focusable `button` elements create a keyboard trap with instructions that don't give advice on the method for proceeding.
 
@@ -223,7 +207,7 @@ These focusable `button` elements create a keyboard trap with instructions that
 <a id="link2" href="#">Link 2</a>
 ```
 
-#### Failed Example 6
+#### Failed Example 5
 
 These focusable `button` elements create a keyboard trap with help text, where the method advised doesn't work.
 

From a9a9e315503279f693aabad62d619d9a5b6ffe68 Mon Sep 17 00:00:00 2001
From: Giacomo Petri <giacomo.petri@usablenet.com>
Date: Thu, 24 Jul 2025 18:08:01 +0200
Subject: [PATCH 2/2] Update focusable-no-keyboard-trap-80af7b.md

---
 _rules/focusable-no-keyboard-trap-80af7b.md | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/_rules/focusable-no-keyboard-trap-80af7b.md b/_rules/focusable-no-keyboard-trap-80af7b.md
index 97eb88aee46..a45c1f62361 100755
--- a/_rules/focusable-no-keyboard-trap-80af7b.md
+++ b/_rules/focusable-no-keyboard-trap-80af7b.md
@@ -148,6 +148,22 @@ These focusable `button` elements have scripts that create a keyboard trap. The
 <a id="link2" href="#">Link 2</a>
 ```
 
+#### Passed Example 7
+
+The [focusable][] `button` labeled "Button3" creates a keyboard trap when navigating forward, as it moves focus back to "Button1" preventing users to focus "Button3". However, when navigating backward, all focusable elements receive focus as expected. Therefore, according to the background notes, this behavior is considered compliant with the rule, despite being recognized as a poor practice in terms of keyboard accessibility.
+
+```html
+<button onblur="setTimeout(() => this.nextElementSibling.focus(), 10)">
+	Button1
+</button>
+<button onblur="setTimeout(() => this.previousElementSibling.focus(), 10)">
+	Button2
+</button>
+<button>
+	Button3
+</button>
+```
+
 ### Failed
 
 #### Failed Example 1