From 386f9e327e93d98a8b160e5f3a60c2eb70f3c569 Mon Sep 17 00:00:00 2001 From: "Patrick H. Lauke" Date: Fri, 3 Jul 2020 12:23:28 +0100 Subject: [PATCH] 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` --- site/content/docs/5.0/utilities/interactions.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/site/content/docs/5.0/utilities/interactions.md b/site/content/docs/5.0/utilities/interactions.md index 4c0c71f1b5..8909e85587 100644 --- a/site/content/docs/5.0/utilities/interactions.md +++ b/site/content/docs/5.0/utilities/interactions.md @@ -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 >}} -

This link can not be clicked.

+

This link can not be clicked.

This link can be clicked (this is default behaviour).

-

This link can not be clicked because the pointer-events property is inherited from its parent. However, this link has a pe-auto class and can be clicked.

+

This link can not be clicked because the pointer-events property is inherited from its parent. However, this link has a pe-auto class and can be clicked.

{{< /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 >}} \ No newline at end of file