Accessibility in ASP.NET MVC Block Editor control
18 Nov 20184 minutes to read
The Block Editor control followed the 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 Block Editor control is outlined below.
- 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.WAI-ARIA attributes
The following ARIA attributes are recommended for the Block Editor to improve discoverability and operable by assistive technologies.
| Attribute | Purpose |
|---|---|
contenteditable="true" + role="textbox"
|
Marks the editable block container as an editable text region. The editable region must have an accessible name to satisfy input-field-name checks. |
role="toolbar" |
Applied to inline formatting toolbars and action-menu containers to group related controls for assistive technologies. |
role="grid" |
Table blocks are exposed as a grid/table for screen readers and keyboard navigation; ensure header cells (th) and proper scope/headers attributes are present. |
role="img" |
Ensure accessible name is present for informative images. |
aria-label / aria-labelledby
|
Provides the accessible name for the editor, toolbar, or specific editable region. The running sample is missing this on the main editable container (axe reports aria-input-field-name). |
aria-orientation |
Specifies the orientation of the toolbar. |
aria-disabled |
Indicates whether the toolbar or element is currently disabled and not interactive. |
aria-haspopup / aria-expanded
|
Used by menus and popups (command/context/action menus). aria-expanded reflects open/closed state. |
aria-hidden |
Hides non-interactive or offscreen content (e.g., closed popups) from assistive technologies. |
Keyboard interaction
The Block Editor control follows keyboard interaction guidelines, making it easy for people who use assistive technologies (AT) or rely solely on keyboard navigation. The control supports a variety of keyboard shortcuts for common actions.
For a complete list of keyboard shortcuts, refer to the Keyboard Support
Ensuring accessibility
The Block Editor control’s accessibility levels are ensured through an accessibility-checker and axe-core software tools during automated testing.