@progress/wct-a11y-spec - npm Package Compare versions

dist/angular/aria/splitter_aria.md

		@@ -27,2 +27,3 @@
		\| `.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. \|

		@@ -29,0 +30,0 @@ > 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:

dist/blazor/aria/splitter_aria.md

		@@ -27,2 +27,3 @@
		\| `.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. \|

		@@ -29,0 +30,0 @@ > 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:

dist/design-system/Splitter.json

		@@ -64,2 +64,7 @@ [
		"Usage": "When a splitbar separates two panes horizontally, its aria-orientation must be explicitly set to 'vertical'."
		},
		{
		"Selector": "",
		"Attribute": "`aria-keyshortcuts=ArrowLeft ArrowRight ArrowUp ArrowDown`",
		"Usage": "Sets the aria-keyshortcuts attribute value to announce available keyboard shortcuts. Some are omitted for brevity."
		}
		@@ -66,0 +71,0 @@ ]

dist/jquery/aria/splitter_aria.md

		@@ -27,2 +27,3 @@
		\| `.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. \|

		@@ -29,0 +30,0 @@ > 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:

dist/react/aria/splitter_aria.md

		@@ -27,2 +27,3 @@
		\| `.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. \|

		@@ -29,0 +30,0 @@ > 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:

dist/vue/aria/splitter_aria.md

		@@ -27,2 +27,3 @@
		\| `.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. \|

		@@ -29,0 +30,0 @@ > 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:

package.json

		{
		"name": "@progress/wct-a11y-spec",
		"version": "2.13.1-develop.4",
		"version": "2.13.1-develop.5",
		"description": "Contains accessibility and keyboard navigation specification of Telerik and Kendo web components.",
		@@ -5,0 +5,0 @@ "type": "module",

Improved metrics