Accessibility in Blazor Query Builder component
26 Mar 20243 minutes to read
The Blazor Query Builder 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 Query Builder 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 |
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 components developed with Ajax, HTML, JavaScript, and related technologies. ARIA provides additional semantics to describe the role, state, and functionality of web components.
The following list of ARIA attributes is used in Blazor Query Builder.
Attributes | Purpose |
---|---|
role |
Indicates the query builder component. |
Keyboard interaction
The Blazor Query Builder 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 Query Builder component.
Press | To do this |
---|---|
Tab / Shift + Tab | To focus the next item in the rule. |
Ensuring accessibility
The Blazor Query Builder component’s accessibility levels are ensured through an axe-core with playwright tests.
The accessibility compliance of the Blazor Query Builder component is shown in the following sample. Open the sample in a new window to evaluate the accessibility of the Blazor Query Builder component with accessibility tools.