Accessibility in EJ2 JavaScript Progress button control

24 Jan 20243 minutes to read

The Progress button 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 Progress button component is outlined below.

Accessibility Criteria Compatibility
WCAG 2.2 Support Yes
Section 508 Support Yes
Screen Reader Support Yes
Right-To-Left Support Yes
Color Contrast Yes
Mobile Device Support Yes
Keyboard Navigation Support Yes
Accessibility Checker Validation Yes
Axe-core Accessibility Validation Yes
Yes - All features of the component meet the requirement.
Intermediate - Some features of the component do not meet the requirement.
No - The component does not meet the requirement.

WAI-ARIA attributes

The Progress button component followed the WAI-ARIA patterns to meet the accessibility. The following ARIA attributes are used in the Progress button component:

Attributes Purpose
aria-label Provides an accessible name for the icon only Progress button.
aria-disabled Indicates that the element is perceivable but disabled, so it is not editable or otherwise operable.

Keyboard interaction

The Progress button 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 Progress button component.

Press To do this
Enter / Space Starts the progress.

Ensuring accessibility

The Progress button component’s accessibility levels are ensured through an accessibility-checker and axe-core software tools during automated testing.

The accessibility compliance of the Progress button component is shown in the following sample. Open the sample in a new window to evaluate the accessibility of the Progress button component with accessibility tools.

See also