Accessibility in EJ2 TypeScript Skeleton control
30 Jan 20242 minutes to read
The Skeleton 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 Skeleton control 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 | |
| Accessibility Checker Validation | |
| Axe-core Accessibility Validation | |
- All features of the control meet the requirement.
- Some features of the control do not meet the requirement.
- The control does not meet the requirement.WAI-ARIA attributes
The Skeleton control followed the WAI-ARIA patterns to meet the accessibility. The following ARIA attributes are used in the Skeleton control:
| Properties | Functionality |
|---|---|
role=alert |
Used to convey important, time-sensitive or contextual message to the user. |
aria-label |
Attribute provides the text label for the Skeleton. |
aria-live |
Attributes which indicates the content changes which are not interactable are live regions. |
aria-busy |
Set to true until loading is complete, then set to false. |
Ensuring accessibility
The Skeleton control’s accessibility levels are ensured through an accessibility-checker and axe-core software tools during automated testing.
The accessibility compliance of the Skeleton control is shown in the following sample. Open the sample in a new window to evaluate the accessibility of the Skeleton control with accessibility tools.