Accessibility in Blazor In-place Editor
14 Aug 20263 minutes to read
The Blazor In-place editor component follows accessibility guidelines and standards, including ADA, Section 508, WCAG 2.2, and WAI‑ARIA specifications that are commonly used to evaluate accessibility.
The accessibility compliance for the Blazor In-place Editor component is outlined below.
| Accessibility Criteria | Compatibility |
|---|---|
| WCAG 2.2 Support | AA |
| Section 508 Support |  |
| Screen Reader Support | |
| Right-To-Left Support | |
| Color Contrast | |
| Mobile Device Support | |
| Keyboard Navigation Support | |
| Axe-core Accessibility Validation | |
- All features of the component meet the requirement.
- Some features of the component do not meet the requirement.
- The component does not meet the requirement.Keyboard interaction
Use the following key shortcuts to operate the Blazor In-place Editor efficiently with a keyboard:
| Windows | Mac | Actions |
|---|---|---|
| Tab | Tab | Move focus to the In-place Editor on the page and navigate forward between consecutive In-place Editor instances. |
| Shift + Tab | ⇧ + Tab | Move focus to the previous In-place Editor instance or to the previous focusable element. |
| Enter | Enter | Switches the In-place Editor to edit mode. |
| Esc | Esc | Cancels the edit and switches the In-place Editor back to display mode. |
Ensuring accessibility
The Blazor In-place editor component’s accessibility is validated with the axe-core tool during automated testing.
The accessibility compliance of the In-place Editor component is demonstrated in the following sample. Open the accessibility sample for In-place Editor in a new window to evaluate accessibility with your preferred tools.