Skip to content

Commit 7889c78

Browse files
authored
primer/alpha/tooltip: Fix typos in the description of the component (#3711)
1 parent ac45681 commit 7889c78

1 file changed

Lines changed: 1 addition & 2 deletions

File tree

app/components/primer/alpha/tooltip.rb

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,9 +14,8 @@ module Alpha
1414
# - **Never set tooltips on static, non-interactive elements** like `span` or `div`. Tooltips should only be used on interactive elements like buttons or links to avoid excluding keyboard-only
1515
# and screen reader users. Use of tooltips through <%= link_to_component(Primer::Beta::Button) %>, <%= link_to_component(Primer::Beta::Link) %>, or <%= link_to_component(Primer::Beta::IconButton) %> will guarantee this.
1616
# - If you must use `Tooltip` as a standalone component, place it immediately after the trigger element in the DOM. This allows screen reader users to navigate to the tooltip and copy its contents if desired.
17-
# content.
1817
#
19-
# Semantically, a tooltip will either act an accessible name or an accessible description for the element that it is associated with resulting in either a
18+
# Semantically, a tooltip will either act as an accessible name or an accessible description for the element that it is associated with resulting in either an
2019
# `aria-labelledby` or an `aria-describedby` association. The `type` drastically changes semantics and screen reader behavior so follow these guidelines carefully:
2120
# - When there is already a visible label text on the trigger element, the tooltip is likely intended be supplementary, so set `type: :description`.
2221
# The majority of tooltips will fall under this category.

0 commit comments

Comments
 (0)