Accessibility in ASP.NET MVC Query Builder
27 Aug 20263 minutes to read
The Query Builder control 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 Query Builder control 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 control meet the requirement.
- Some features of the control do not meet the requirement.
- The control does not meet the requirement.WAI-ARIA attributes
WAI-ARIA (Accessibility Initiative – Accessible Rich Internet Applications) defines a way to increase the accessibility of web pages, dynamic content, and user interface controls developed with Ajax, HTML, JavaScript, and related technologies. ARIA provides additional semantics to describe the role, state, and functionality of web controls.
The following list of ARIA attributes is used in Query Builder.
| Attributes | Purpose |
|---|---|
role |
Indicates the Query Builder control. |
Keyboard interaction
The Query Builder control 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 Query Builder control.
| Press | To do this |
|---|---|
| Tab / Shift + Tab | To focus the next item in the rule. |
Ensuring accessibility
The Query Builder control’s accessibility levels are ensured through an accessibility-checker and axe-core software tools during automated testing.
The accessibility compliance of the Query Builder control is shown in the following sample. Open the sample in a new window to evaluate the accessibility of the Query Builder control with accessibility tools.