Accessibility in EJ2 TypeScript Signature control
24 Jan 20242 minutes to read
The Signature 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 Signature component is outlined below.
| Accessibility Criteria | Compatibility |
|---|---|
| WCAG 2.2 Support |  |
| Section 508 Support | |
| Screen Reader Support | |
| Right-To-Left Support | Not Applicable |
| 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.Keyboard interaction
The Signature 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 Signature component.
| Press | To do this |
|---|---|
| Ctrl + Z | Undo the last action. |
| Ctrl + Y | Redo the last action. |
| Ctrl + S | To save the signature. |
| delete | Erases all the signature strokes signed by user. |
Ensuring accessibility
The Signature component’s accessibility levels are ensured through an accessibility-checker and axe-core software tools during automated testing.
The accessibility compliance of the Signature component is shown in the following sample. Open the sample in a new window to evaluate the accessibility of the Signature component with accessibility tools.