From c2ef9631341eb98e9b6961e10c7af71e0a8d46f1 Mon Sep 17 00:00:00 2001 From: Daniel Date: Mon, 19 Jan 2026 15:06:40 +0100 Subject: [PATCH] fix typo accessibility tree --- pages/glossary/included-in-the-accessibility-tree.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/glossary/included-in-the-accessibility-tree.md b/pages/glossary/included-in-the-accessibility-tree.md index 80f1bca3e9..0303c02914 100755 --- a/pages/glossary/included-in-the-accessibility-tree.md +++ b/pages/glossary/included-in-the-accessibility-tree.md @@ -15,4 +15,4 @@ For more details, see [examples of included in the accessibility tree][]. [Programmatically hidden](#programmatically-hidden) elements are removed from the accessibility tree. However, some browsers will leave [focusable](#focusable) elements with an `aria-hidden` attribute set to `true` in the accessibility tree. Because they are hidden, these elements are considered **not** included in the accessibility tree. This may cause confusion for users of assistive technologies because they may still be able to interact with these focusable elements using sequential keyboard navigation, even though the element should not be included in the accessibility tree. -[examples of included in the accessibility tree]: https://www.w3.org/WAI/standards-guidelines/act/rules/terms/included-in-the-accesibility-tree/examples/ +[examples of included in the accessibility tree]: https://www.w3.org/WAI/standards-guidelines/act/rules/terms/included-in-the-accessibility-ree/examples/