chore: bump @progress/wct-a11y-spec from 2.7.0 to 2.8.0 in /src-a11y (#1738)

* chore: bump @progress/wct-a11y-spec from 2.7.0 to 2.8.0 in /src-a11y

Bumps [@progress/wct-a11y-spec](https://github.com/telerik/web-components-ux) from 2.7.0 to 2.8.0.
- [Commits](https://github.com/telerik/web-components-ux/commits)

---
updated-dependencies:
- dependency-name: "@progress/wct-a11y-spec"
  dependency-type: direct:development
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>

* docs: update accessibility and keyboard-nav specs

---------

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: kendo-bot <[email protected]>

Author: dependabot[bot]

components/daterangepicker/accessibility/wai-aria-support.md

@@ -32,7 +32,7 @@ This section lists the selectors, attributes, and behavior patterns supported by
 |  | `aria-haspopup=grid` | Indicates the component has a Calendar Popup that implements `role="grid"`. |
 |  | `aria-expanded=true/false` | Announces whether the Popup is visible or not. |
 |  | `aria-controls=.k-calendar-container id` | Points to the popup element. Signifies that the `combobox` element controls the Calendar `grid`. |
-|  | `aria-activedescendant=.k-calendar-td.k-focus id` | Points to the focused item (date/month/year) in the Calendar Popup. Should only be present when the Popup is open. |
+| `.k-input-inner.k-focus` | `aria-activedescendant=.k-calendar-td.k-focus id` | Points to the focused item (date/month/year) in the Calendar Popup. Should only be present when the Popup is open. |
 |  | `readonly=readonly` or `aria-readonly=true` | Attribute is rendered only when the DateRangePicker is readonly. |
 |  | `tabindex=0` | The element should be focusable. |
 | `.k-invalid .k-input-inner,.ng-invalid .k-input-inner` | `aria-invalid=true` | Attribute is rendered only when the combobox is in form and announces the valid state of the component. |

components/multiselect/accessibility/wai-aria-support.md

@@ -43,7 +43,7 @@ The following table summarizes the selectors and attributes supported by the Mul
 |  | `aria-busy=true` | The attribute is rendered only when the MultiSelect is loading data. |
 |  | `tabindex=0` | The element must be focusable. |
 | `.k-disabled .k-input-inner` | `aria-disabled=true` | The attribute is rendered only when the MultiSelect is disabled. |
-| `.k-input-button` | `role=button` | The element must either be a `<button>` element or have the `role="button"` assigned. |
+| `.k-input-button` | `role=button` or `nodeName=button` | The element must either be a `<button>` element or have the `role="button"` assigned. |
 |  | `aria-label` | The button needs an accessible name that will be assigned to it. |
 |  | `tabindex=-1` | The button element must not be focusable. |
 

components/pdfviewer/accessibility/wai-aria-support.md

@@ -16,7 +16,7 @@ position: 50
 Out of the box, the Telerik UI for Blazor PDFViewer provides extensive accessibility support and enables users with disabilities to acquire complete control over its features.
 
 
-The PDFViewer is compliant with the [Web Content Accessibility Guidelines (WCAG) 2.1  AA](https://www.w3.org/TR/WCAG21/) standards](https://www.w3.org/TR/WCAG21/) and [Section 508](http://www.section508.gov/) requirements, follows the [Web Accessibility Initiative - Accessible Rich Internet Applications (WAI-ARIA)](https://www.w3.org/WAI/ARIA/apg/) best practices for implementing the [keyboard navigation](#keyboard-navigation) for its `component` role, provides options for managing its focus and is tested against the most popular screen readers.
+The PDFViewer is compliant with the [Web Content Accessibility Guidelines (WCAG) 2.2  AA](https://www.w3.org/TR/WCAG22/) standards](https://www.w3.org/TR/WCAG22/) and [Section 508](http://www.section508.gov/) requirements, follows the [Web Accessibility Initiative - Accessible Rich Internet Applications (WAI-ARIA)](https://www.w3.org/WAI/ARIA/apg/) best practices for implementing the [keyboard navigation](#keyboard-navigation) for its `component` role, provides options for managing its focus and is tested against the most popular screen readers.
 
 ## WAI-ARIA
 

components/window/accessibility/wai-aria-support.md

@@ -25,7 +25,7 @@ This section lists the selectors, attributes, and behavior patterns supported by
 
 | Selector | Attribute | Usage |
 | -------- | --------- | ----- |
-| `.k-window` | `role=dialog` | Announces the dialog role of the component. |
+| `.k-window:not(.k-dialog)` | `role=dialog` | Announces the dialog role of the component. |
 |  | `aria-labelledby=.k-window-title id` | Associate the title of the dialog. |
 | `.k-overlay + .k-window` | `aria-modal=true` | Announces that the dialog is modal. Attribute is added only when the dialog is modal. |
 

src-a11y/package-lock.json

@@ -8,7 +8,7 @@
   "author": "",
   "license": "ISC",
   "devDependencies": {
-    "@progress/wct-a11y-spec": "^2.7.0",
+    "@progress/wct-a11y-spec": "^2.8.0",
     "gulp": "^4.0.2",
     "gulp-json-editor": "^2.5.6",
     "gulp-rename": "^2.0.0",