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

Comparing version 2.13.1-develop.3 to 2.13.1-develop.4

dist/angular/aria/column-chooser_aria.md

@@ -32,2 +32,5 @@
 
+
+Disregard the AXE nested interactive rule as it lacks precise definition and does not account for specific use-cases individually. The current ColumnChooser specification does not violate any explicit WCAG success criteria, allowing us to safely ignore the newly introduced AXE interpretation.
+
 ## Resources
@@ -39,2 +42,6 @@
 
+[AXE Nested Interactive Rule](https://dequeuniversity.com/rules/axe/4.7/nested-interactive?application=AxeChrome)
+
+[Deque Github Issue Discussion for the Nested Interactive AXE Rule](https://github.com/dequelabs/axe-core/issues/2906)
+
 ## Section 508
@@ -41,0 +48,0 @@

dist/angular/keyboard/editor_keyboard.md

 ## Managing the Focus
 
 
-The editor integrates the **Toolbar** component and inherits all shortcuts from it. So, the component has two tab stops - one the toolbar and one the content area.
+The editor integrates the **Toolbar** component and inherits all shortcuts from it. So, the component has two tab stops - one the toolbar and one the content area. When using the single click tools by mouse, the focus remains on the content.
 
@@ -6,0 +6,0 @@ ### Actions applied to Editor content area:

dist/blazor/aria/column-chooser_aria.md

@@ -32,2 +32,5 @@
 
+
+Disregard the AXE nested interactive rule as it lacks precise definition and does not account for specific use-cases individually. The current ColumnChooser specification does not violate any explicit WCAG success criteria, allowing us to safely ignore the newly introduced AXE interpretation.
+
 ## Resources
@@ -39,2 +42,6 @@
 
+[AXE Nested Interactive Rule](https://dequeuniversity.com/rules/axe/4.7/nested-interactive?application=AxeChrome)
+
+[Deque Github Issue Discussion for the Nested Interactive AXE Rule](https://github.com/dequelabs/axe-core/issues/2906)
+
 ## Section 508
@@ -41,0 +48,0 @@

dist/blazor/keyboard/editor_keyboard.md

 ## Managing the Focus
 
 
-The editor integrates the **Toolbar** component and inherits all shortcuts from it. So, the component has two tab stops - one the toolbar and one the content area.
+The editor integrates the **Toolbar** component and inherits all shortcuts from it. So, the component has two tab stops - one the toolbar and one the content area. When using the single click tools by mouse, the focus remains on the content.
 
@@ -6,0 +6,0 @@ ### Actions applied to Editor content area:

dist/design-system/ColumnChooser.json

@@ -96,2 +96,5 @@ [
     {
+        "p": "Disregard the AXE nested interactive rule as it lacks precise definition and does not account for specific use-cases individually. The current ColumnChooser specification does not violate any explicit WCAG success criteria, allowing us to safely ignore the newly introduced AXE interpretation."
+    },
+    {
         "h3": "Keyboard Shortcuts"
@@ -187,2 +190,14 @@ },
                 }
+            },
+            {
+                "link": {
+                    "source": "https://dequeuniversity.com/rules/axe/4.7/nested-interactive?application=AxeChrome",
+                    "title": "AXE Nested Interactive Rule"
+                }
+            },
+            {
+                "link": {
+                    "source": "https://github.com/dequelabs/axe-core/issues/2906",
+                    "title": "Deque Github Issue Discussion for the Nested Interactive AXE Rule"
+                }
             }
@@ -189,0 +204,0 @@ ]

dist/design-system/Editor.json

@@ -42,3 +42,3 @@ [
     {
-        "p": "The editor integrates the **Toolbar** component and inherits all shortcuts from it. So, the component has two tab stops - one the toolbar and one the content area."
+        "p": "The editor integrates the **Toolbar** component and inherits all shortcuts from it. So, the component has two tab stops - one the toolbar and one the content area. When using the single click tools by mouse, the focus remains on the content."
     },
@@ -45,0 +45,0 @@ {

dist/jquery/aria/column-chooser_aria.md

@@ -32,2 +32,5 @@
 
+
+Disregard the AXE nested interactive rule as it lacks precise definition and does not account for specific use-cases individually. The current ColumnChooser specification does not violate any explicit WCAG success criteria, allowing us to safely ignore the newly introduced AXE interpretation.
+
 ## Resources
@@ -39,2 +42,6 @@
 
+[AXE Nested Interactive Rule](https://dequeuniversity.com/rules/axe/4.7/nested-interactive?application=AxeChrome)
+
+[Deque Github Issue Discussion for the Nested Interactive AXE Rule](https://github.com/dequelabs/axe-core/issues/2906)
+
 ## Section 508
@@ -41,0 +48,0 @@

dist/jquery/keyboard/editor_keyboard.md

 ## Managing the Focus
 
 
-The editor integrates the **Toolbar** component and inherits all shortcuts from it. So, the component has two tab stops - one the toolbar and one the content area.
+The editor integrates the **Toolbar** component and inherits all shortcuts from it. So, the component has two tab stops - one the toolbar and one the content area. When using the single click tools by mouse, the focus remains on the content.
 
@@ -6,0 +6,0 @@ ### Actions applied to Editor content area:

dist/react/aria/column-chooser_aria.md

@@ -32,2 +32,5 @@
 
+
+Disregard the AXE nested interactive rule as it lacks precise definition and does not account for specific use-cases individually. The current ColumnChooser specification does not violate any explicit WCAG success criteria, allowing us to safely ignore the newly introduced AXE interpretation.
+
 ## Resources
@@ -39,2 +42,6 @@
 
+[AXE Nested Interactive Rule](https://dequeuniversity.com/rules/axe/4.7/nested-interactive?application=AxeChrome)
+
+[Deque Github Issue Discussion for the Nested Interactive AXE Rule](https://github.com/dequelabs/axe-core/issues/2906)
+
 ## Section 508
@@ -41,0 +48,0 @@

dist/react/keyboard/editor_keyboard.md

 ## Managing the Focus
 
 
-The editor integrates the **Toolbar** component and inherits all shortcuts from it. So, the component has two tab stops - one the toolbar and one the content area.
+The editor integrates the **Toolbar** component and inherits all shortcuts from it. So, the component has two tab stops - one the toolbar and one the content area. When using the single click tools by mouse, the focus remains on the content.
 
@@ -6,0 +6,0 @@ ### Actions applied to Editor content area:

dist/vue/aria/column-chooser_aria.md

@@ -32,2 +32,5 @@
 
+
+Disregard the AXE nested interactive rule as it lacks precise definition and does not account for specific use-cases individually. The current ColumnChooser specification does not violate any explicit WCAG success criteria, allowing us to safely ignore the newly introduced AXE interpretation.
+
 ## Resources
@@ -39,2 +42,6 @@
 
+[AXE Nested Interactive Rule](https://dequeuniversity.com/rules/axe/4.7/nested-interactive?application=AxeChrome)
+
+[Deque Github Issue Discussion for the Nested Interactive AXE Rule](https://github.com/dequelabs/axe-core/issues/2906)
+
 ## Section 508
@@ -41,0 +48,0 @@

dist/vue/keyboard/editor_keyboard.md

 ## Managing the Focus
 
 
-The editor integrates the **Toolbar** component and inherits all shortcuts from it. So, the component has two tab stops - one the toolbar and one the content area.
+The editor integrates the **Toolbar** component and inherits all shortcuts from it. So, the component has two tab stops - one the toolbar and one the content area. When using the single click tools by mouse, the focus remains on the content.
 
@@ -6,0 +6,0 @@ ### Actions applied to Editor content area:

package.json

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

No alert changes

Improved metrics

Total package byte prevSize

4959283

increased by0.08%

Lines of code

66690

increased by0.02%

No dependency changes