docs: update accessibility and keyboard-nav specs

telerik · Dec 5, 2024 · 989982b · 989982b
1 parent 8e7164f
commit 989982b
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 3 deletions.
diff --git a/components/grid/accessibility/wai-aria-support.md b/components/grid/accessibility/wai-aria-support.md
@@ -200,5 +200,4 @@ The Grid has been tested with the following screen readers and browsers combinat
 
 * [Blazor Grid Accessibility and Keyboard Navigation (Demo)](https://demos.telerik.com/blazor-ui/grid/keyboard-navigation)
 * [Accessibility in Telerik UI for Blazor]({% slug accessibility-overview %})
-* [Accessibility Theme]({% slug themes-accessibility-swatch %})
-* [Blazor Grid]({%slug grid-overview%})
+* [Accessibility Theme]({% slug themes-accessibility-swatch %})
diff --git a/components/splitter/accessibility/wai-aria-support.md b/components/splitter/accessibility/wai-aria-support.md
@@ -40,7 +40,7 @@ This section lists the selectors, attributes, and behavior patterns supported by
 | `.k-splitbar-horizontal` | `aria-orientation=vertical` | When a splitbar separates two panes horizontally, its aria-orientation must be explicitly set to 'vertical'. |
 |  | `aria-keyshortcuts=ArrowLeft ArrowRight ArrowUp ArrowDown` | Sets the aria-keyshortcuts attribute value to announce available keyboard shortcuts. Some are omitted for brevity. |
 
-> Note: Setting the value-now attribute of the separator element is not applicable, as the Splitter is a complex layout component allowing splitting the content into multiple panes across any number and level of nested Splitters and panes, thus announcing a value would not convey any meaningful information. Moreover, there is no specification, or WAI-ARIA recommendation that explains how value should be set in multiple panes scenario. Further information on this complicated scenario could be found in the following WAI-ARIA GitHub issue:
+> Note: Setting the value-now attribute of the separator element is not applicable, as the Splitter is a complex layout component allowing splitting the content into multiple panes across any number and level of nested Splitters and panes, thus announcing a value would not convey any meaningful information. Moreover, there is no specification, or WAI-ARIA recommendation that explains how value should be set in multiple panes scenario. If needed, developers can still apply attributes as they see fit, using the respective API option. Further information on this complicated scenario could be found in the following WAI-ARIA GitHub issue:
 
 [WAI-ARIA Practices on GitHub](https://github.com/w3c/aria-practices/issues/129#issuecomment-456976215)