From dc63f858b0b860b89ce71dde101ea62ee05302d8 Mon Sep 17 00:00:00 2001 From: Cory LaViska Date: Thu, 8 Jun 2023 15:41:03 -0400 Subject: [PATCH] fix typo --- docs/pages/components/visually-hidden.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pages/components/visually-hidden.md b/docs/pages/components/visually-hidden.md index 53278dc70..2196e4c21 100644 --- a/docs/pages/components/visually-hidden.md +++ b/docs/pages/components/visually-hidden.md @@ -7,7 +7,7 @@ layout: component According to [The A11Y Project](https://www.a11yproject.com/posts/2013-01-11-how-to-hide-content/), "there are real world situations where visually hiding content may be appropriate, while the content should remain available to assistive technologies, such as screen readers. For instance, hiding a search field's label as a common magnifying glass icon is used in its stead." -Since visually hidden content can receive focus when tabbing, the element will become visible when something inside receives focus. This behavior is intentional, as sighted keyboards user won't be able to determine where the focus indicator is without it. +Since visually hidden content can receive focus when tabbing, the element will become visible when something inside receives focus. This behavior is intentional, as sighted keyboard user won't be able to determine where the focus indicator is without it. ```html:preview