diff --git a/_rules/aria-hidden-no-focusable-content-6cfa84.md b/_rules/aria-hidden-no-focusable-content-6cfa84.md index 92e3df5a97e..fe8832a0422 100755 --- a/_rules/aria-hidden-no-focusable-content-6cfa84.md +++ b/_rules/aria-hidden-no-focusable-content-6cfa84.md @@ -97,13 +97,28 @@ This `input` element is not part of the [sequential focus navigation][] because #### Passed Example 4 -This `a` element is part of the [sequential focus navigation][], but moves focus to the `input` element whenever it receives focus. +This `a` element is not [focusable][] because it moves focus to the `input` element whenever it receives focus. These elements +are sometimes referred to as 'focus sentinel' or 'bumper'. They are typically found before and after a modal / dialog in +order to contain focus within the modal. Page authors do not want the sentinel to be visible, nor do they want them to be read by +a screen reader. But, they do want the element to be part of the [sequential focus navigation][]. This allows the page author +to detect that focus has left the dialog in order to wrap it to the top/bottom as appropriate. ```html + - + ``` #### Passed Example 5 @@ -169,6 +184,27 @@ This `summary` element is part of the [sequential focus navigation][]. ``` +#### Failed Example 6 + +This `a` element is [focusable][] because it fails to move focus when it receives focus. This is in contrast to a focus sentinel that +immediately jumps focus to a valid location. Focus sentinels are typically used before and after a modal dialog in order to contain +and wrap focus. In this case, the `focus` event was removed, but the sentinel was not. + +```html + + + +``` + ### Inapplicable #### Inapplicable Example 1