mirror of
https://github.com/twbs/bootstrap.git
synced 2024-11-29 11:24:18 +01:00
Docs: clarify that pointer events classes don't affect keyboard interaction (#31134)
* Docs: clarify that pointer events classes don't affect keyboard interaction * Neutralise example links that are `pe-none`
This commit is contained in:
parent
dca5ad0288
commit
386f9e327e
@ -18,10 +18,14 @@ Change the way in which the content is selected when the user interacts with it.
|
||||
|
||||
## Pointer events
|
||||
|
||||
Bootstrap provides `pe-none` and `pe-auto` classes to prevent or add element interactions.
|
||||
Bootstrap provides `.pe-none` and `.pe-auto` classes to prevent or add element interactions.
|
||||
|
||||
{{< example >}}
|
||||
<p><a href="#" class="pe-none">This link</a> can not be clicked.</p>
|
||||
<p><a href="#" class="pe-none" tabindex="-1" aria-disabled="true">This link</a> can not be clicked.</p>
|
||||
<p><a href="#" class="pe-auto">This link</a> can be clicked (this is default behaviour).</p>
|
||||
<p class="pe-none"><a href="#">This link</a> can not be clicked because the <code>pointer-events</code> property is inherited from its parent. However, <a href="#" class="pe-auto">this link</a> has a <code>pe-auto</code> class and can be clicked.</p>
|
||||
<p class="pe-none"><a href="#" tabindex="-1" aria-disabled="true">This link</a> can not be clicked because the <code>pointer-events</code> property is inherited from its parent. However, <a href="#" class="pe-auto">this link</a> has a <code>pe-auto</code> class and can be clicked.</p>
|
||||
{{< /example >}}
|
||||
|
||||
{{< callout warning >}}
|
||||
The `.pe-none` class (and the `pointer-events` CSS property it sets) only prevents interactions with a pointer (mouse, stylus, touch). Links and controls with `.pe-none` are, by default, still focusable and actionable for keyboard users. To ensure that they are completely neutralized even for keyboard users, you may need to add further attributes such as `tabindex="-1"` (to prevent them from receiving keyboard focus) and `aria-disabled="true"` (to convey the fact they are effectively disabled to assistive technologies), and possibly use JavaScript to completely prevent them from being actionable. For form controls, consider using the `disabled` HTML attribute instead.
|
||||
{{< /callout >}}
|
Loading…
Reference in New Issue
Block a user