Accessibility in Blazor In-place editor component
4 Nov 20252 minutes to read
The Blazor In-place editor component follows accessibility guidelines and standards, including ADA, Section 508, WCAG 2.2 standards, and WCAG roles 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 |  |
| 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. |
Ensuring accessibility
The Blazor In-place editor component’s accessibility levels are ensured through an axe-core software tool during automated testing.
The accessibility compliance of the In-place Editor component is shown in the following sample. Open the sample (https://blazor.syncfusion.com/accessibility/inplace-editor) in a new window to evaluate the accessibility of the In-place Editor component with accessibility tools.