Accessibility in EJ2 TypeScript Floating action button control
30 Jan 20243 minutes to read
The Floating action button 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 Floating action button 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 Floating action button control followed the WAI-ARIA patterns to meet the accessibility. The following ARIA attributes are used in the Floating action button control:
| Attributes | Purpose |
|---|---|
aria-label |
Provides an accessible name for the icon only floating action button. |
Keyboard interaction
The Floating action button control 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 Floating action button control.
| Press | To do this |
|---|---|
| Space | When the floating action button has focus, pressing the space key changes the state of the floating action button. |
Ensuring accessibility
The Floating action button control’s accessibility levels are ensured through an accessibility-checker and axe-core software tools during automated testing.
The accessibility compliance of the Floating action button control is shown in the following sample. Open the sample in a new window to evaluate the accessibility of the Floating action button control with accessibility tools.