Skip to content

[80af7b] Focusable element has no keyboard trap - move Failed Example 2 to passed since it's currently passing the ACT rule #2340

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Aug 21, 2025
Merged

[80af7b] Focusable element has no keyboard trap - move Failed Example 2 to passed since it's currently passing the ACT rule #2340

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4af483c
Remove Failed Example 2 since it's currently passing the ACT rule
giacomo-petri Jul 24, 2025
a9a9e31
Update focusable-no-keyboard-trap-80af7b.md
giacomo-petri Jul 24, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
38 changes: 19 additions & 19 deletions _rules/focusable-no-keyboard-trap-80af7b.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand All @@ -164,22 +180,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
Expand All @@ -188,7 +188,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.

Expand All @@ -205,7 +205,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.

Expand All @@ -223,7 +223,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.

Expand Down