Accessibility in Angular Skeleton
26 Sep 20263 minutes to read
The Angular Skeleton component 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 Angular Skeleton 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 | ![]() |
| Accessibility Checker Validation | ![]() |
| 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.WAI-ARIA attributes
The Angular Skeleton component followed the WAI-ARIA patterns to meet the accessibility. The following ARIA attributes are used in the Angular Skeleton component:
| Attributes | Purpose |
|---|---|
role=alert |
Used to convey important, time-sensitive or contextual message to the user. |
aria-label |
Attribute provides the text label for the Angular 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 Angular Skeleton component’s accessibility levels are ensured through an accessibility-checker and axe-core software tools during automated testing.
The accessibility compliance of the Angular Skeleton component is shown in the following sample. Open the sample in a new window to evaluate the accessibility of the Angular Skeleton component with accessibility tools.