aboutsummaryrefslogtreecommitdiff
path: root/site
diff options
context:
space:
mode:
authorEricDunsworth <[email protected]>2023-06-13 17:03:34 -0400
committerGitHub <[email protected]>2023-06-14 00:03:34 +0300
commit6d24ccc9ccfd9b3ee8253c09b63102873ed29952 (patch)
tree221a504a0459e5f430badf7264a62aa004204f80 /site
parentd6a55b719c81ba7ea296f793768d886d13610314 (diff)
downloadbootstrap-6d24ccc9ccfd9b3ee8253c09b63102873ed29952.tar.xz
bootstrap-6d24ccc9ccfd9b3ee8253c09b63102873ed29952.zip
Docs (tooltips): Fix "them" typo in markup section (#38751)
Diffstat (limited to 'site')
-rw-r--r--site/content/docs/5.3/components/tooltips.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/site/content/docs/5.3/components/tooltips.md b/site/content/docs/5.3/components/tooltips.md
index d41b6e2cd..ee98dd058 100644
--- a/site/content/docs/5.3/components/tooltips.md
+++ b/site/content/docs/5.3/components/tooltips.md
@@ -157,7 +157,7 @@ const tooltip = new bootstrap.Tooltip('#example', {
The required markup for a tooltip is only a `data` attribute and `title` on the HTML element you wish to have a tooltip. The generated markup of a tooltip is rather simple, though it does require a position (by default, set to `top` by the plugin).
{{< callout warning >}}
-**Keep tooltips accessible to keyboard and assistive technology users** by only adding them to HTML elements that are traditionally keyboard-focusable and interactive (such as links or form controls). While other HTML elements can be made focusable by adding `tabindex="0"`, this can create annoying and confusing tab stops on non-interactive elements for keyboard users, and most assistive technologies currently do not announce tooltips in this situation. Additionally, do not rely solely on `hover` as the trigger for your tooltips as this will make theme impossible to trigger for keyboard users.
+**Keep tooltips accessible to keyboard and assistive technology users** by only adding them to HTML elements that are traditionally keyboard-focusable and interactive (such as links or form controls). While other HTML elements can be made focusable by adding `tabindex="0"`, this can create annoying and confusing tab stops on non-interactive elements for keyboard users, and most assistive technologies currently do not announce tooltips in this situation. Additionally, do not rely solely on `hover` as the trigger for your tooltips as this will make them impossible to trigger for keyboard users.
{{< /callout >}}
```html