Accessibility in Blazor Message

2 Apr 20243 minutes to read

The Blazor Message 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 Message component is outlined below.

Accessibility Criteria Compatibility
WCAG 2.2 Support Yes
Section 508 Support Yes
Screen Reader Support Yes
Right-To-Left Support Yes
Color Contrast Yes
Mobile Device Support Yes
Keyboard Navigation Support Yes
Axe-core Accessibility Validation Yes
Yes - All features of the control meet the requirement.
Intermediate - Some features of the control do not meet the requirement.
No - The control does not meet the requirement.

ARIA attributes

The Blazor Message component followed the WAI-ARIA patterns to meet the accessibility. The following ARIA attributes are used in the Blazor Message component:

Attributes Purpose
role=alert Used to convey a significant and contextual message to the user.
aria-label Provides an accessible name for the close icon.

Keyboard interaction

The Blazor Message 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 Message component.

Press To do this
Tab / Shift + Tab To focus the close icon in the message.
Enter / Space Closes the focused close icon’s message.

Ensuring accessibility

The Blazor Message component’s accessibility levels are ensured through an axe-core with playwright tests.

The accessibility compliance of the Blazor Message component is shown in the following sample. Open the sample in a new window to evaluate the accessibility of the Blazor Message component with accessibility tools.

See also