New to Telerik UI for Blazor? Download free 30-day trial

Blazor Notification Accessibility

Out of the box, the Telerik UI for Blazor Notification provides extensive accessibility support and enables users with disabilities to acquire complete control over its features.

The Notification is compliant with the Web Content Accessibility Guidelines (WCAG) 2.2 AA standards and Section 508 requirements, follows the Web Accessibility Initiative - Accessible Rich Internet Applications (WAI-ARIA) best practices for implementing the keyboard navigation for its component role, provides options for managing its focus and is tested against the most popular screen readers.


This section lists the selectors, attributes, and behavior patterns supported by the component and its composite elements, if any.

Selector Attribute Usage
.k-notification role=alert Notification element should be marked as an alert.
aria-live=polite The aria-live value must be set to polite, so that it will not obscure other essential information while announced.
aria-label or aria-labelledby The Notification needs an accessible name to be assigned to it. The label holds info about the type of the Notification (error, warning, info, etc.)
aria-describedby=.k-notification-content id USed so that the content of the Notification will be announced by the assistive technologies.
.k-i-close,.k-svg-i-close aria-hidden=true The close button of the notification (if any) should not be present in the accessibility tree.


WAI-ARIA spec: Role Alert

ARIA Practices: Alert

Section 508

The Notification is fully compliant with the Section 508 requirements.


The Notification has been extensively tested automatically with axe-core and manually with the most popular screen readers.

To report any accessibility issues, contact the team through the Telerik Support System.

Screen Readers

The Notification has been tested with the following screen readers and browsers combinations:

Environment Tool
Firefox NVDA
Chrome JAWS
Microsoft Edge JAWS

See Also

In this article