Accessibility in Angular Message component
24 Jan 20243 minutes to read
The Message 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 Message 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 Message component followed the WAI-ARIA patterns to meet the accessibility. The following ARIA attributes are used in the Message component:
| Attributes | Purpose |
|---|---|
role=alert |
Used to convey a significant and contextual message to the user. |
aria-label |
Provides an accessible name for the close icon. |
Keyboard interaction
The Message component followed the keyboard interaction guideline, making it easy for people who use assistive technologies (AT) and those who completely rely on keyboard navigation. The following keyboard shortcuts are supported by the Message component.
| Press | To do this |
|---|---|
| Tab / Shift + Tab | To focus the close icon in the message. |
| Enter / Space | Closes the focused close icon’s message. |
Ensuring accessibility
The Message component’s accessibility levels are ensured through an accessibility-checker and axe-core software tools during automated testing.
The accessibility compliance of the Message component is shown in the following sample. Open the sample in a new window to evaluate the accessibility of the Message component with accessibility tools.