Accessibility in Blazor Query Builder component
4 Nov 20253 minutes to read
The Blazor Query Builder follows widely accepted 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 Query Builder 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
WAI-ARIA (Web Accessibility Initiative – Accessible Rich Internet Applications) defines a way to increase the accessibility of web pages, dynamic content, and user interface components. ARIA provides additional semantics to describe role, state, and functionality.
The following list of ARIA attributes is used in Blazor Query Builder.
| Attributes | Purpose |
|---|---|
role |
Identifies the Query Builder region and roles on interactive controls to assist screen readers. |
Keyboard interaction
The Blazor Query Builder follows keyboard interaction guidelines, making it accessible for people who use assistive technologies (AT) and those who rely on keyboard navigation. The following keyboard shortcuts are supported.
| Windows | Mac | Actions |
|---|---|---|
| Tab / Shift + Tab | Tab / ⇧ + Tab | Move focus between fields, operators, values, and action buttons within a rule. |
Ensuring accessibility
The Blazor Query Builder’s accessibility levels are verified using axe-core with Playwright tests.
The accessibility compliance of the Blazor Query Builder is shown in the following sample. Open the sample in a new window to evaluate the accessibility of the Blazor Query Builder with accessibility tools.