Accessibility in Blazor ProgressButton Component
28 Mar 20243 minutes to read
The Blazor ProgressButton 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 Blazor ProgressButton 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 | |
| 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 Blazor ProgressButton component followed the WAI-ARIA patterns to meet the accessibility. The following ARIA attributes are used in the Blazor ProgressButton component:
| Attributes | Purpose |
|---|---|
aria-label |
Provides an accessible name for the icon only ProgressButton. |
aria-disabled |
Indicates that the element is perceivable but disabled, so it is not editable or otherwise operable. |
Keyboard interaction
The Blazor ProgressButton 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 Blazor ProgressButton component.
| Press | To do this |
|---|---|
| Enter / Space | Starts the progress. |
Ensuring accessibility
The Blazor ProgressButton component’s accessibility levels are ensured through an axe-core with playwright tests.
The accessibility compliance of the Blazor ProgressButton component is shown in the following sample. Open the sample in a new window to evaluate the accessibility of the Blazor ProgressButton component with accessibility tools.