How can I help you?
Accessibility in Blazor SpeechToText component
17 Feb 20262 minutes to read
The SpeechToText 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 SpeechToText component is outlined below.
| Accessibility Criteria | Compatibility |
|---|---|
| WCAG 2.2 Support | AA |
| Section 508 Support | ![]() |
| Screen Reader Support | ![]() |
| Right-To-Left Support | ![]() |
| Color Contrast | ![]() |
| Mobile Device Support | ![]() |
| Keyboard Navigation Support | ![]() |
| Accessibility Checker 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 following ARIA attributes are used in the SpeechToText component:
| Attributes | Purpose |
|---|---|
aria-label |
Provides an accessible name for the SpeechToText button. |
Keyboard interaction
The following keyboard shortcuts are supported by the SpeechToText component.
| Windows | Mac | Actions |
|---|---|---|
| Enter/Space | Enter/Space | When the SpeechToText button has focus, pressing the enter/space key changes the state of the button. |
Ensuring accessibility
The Blazor SpeechToText component’s accessibility levels are ensured through an axe-core software tool during automated testing.