Skip to content

Latest commit

 

History

History
44 lines (28 loc) · 2.75 KB

overview.md

File metadata and controls

44 lines (28 loc) · 2.75 KB
title page_title description slug position
Overview
Accessibility Overview | Telerik UI for ASP.NET Core
General accessibility standards and keyboard navigation requirements for web applications and their support by Telerik UI for ASP.NET Core.
overview_accessibility
0

Accessibility Overview

Websites and applications are accessible when they provide full control over their features by enabling users with disabilities to access their content by using assistive technologies or keyboard navigation.

For the full list of components which support accessibility and keyboard navigation, refer to the article on [accessibility support by Telerik UI for ASP.NET Core]({% slug compliance_accessibility %}).

Standards and Requirements

Accessible websites and applications normally provide support for:

Section 508

Section 508 of the Rehabilitation Act is a set of accessibility standards set by the U.S. General Services Administration (GSA). They apply to electronic and information technology and contain technical criteria specific to various types of technologies and performance-based requirements which focus on the functional capabilities of the listed products.

WCAG 2.1

The W3C Web Content Accessibility Guidelines set the standards for applications regarding the provision of accessible content. Depending on the number of guidelines that are followed when building an application, W3C defines three levels of accessibility conformance—A, AA, and AAA levels.

WAI-ARIA

WAI-ARIA is a World Wide Web Consortium accessibility specification. It specifies steps for developing web components that make them more accessible to assistive technologies such as screen readers. The WAI-ARIA framework is designed to be a framework for web developers to apply while creating web applications that use Ajax, scripting, and other rich application techniques.

Keyboard Navigation

By default, users can only navigate to links, buttons, and form controls with a keyboard. The navigation order in which interactive items receive keyboard focus has to be logical and intuitive. Generally, it needs to follow the visual horizontal and vertical flow of the page. For example, left to right and top to bottom, header first followed by the main and then page navigation.

Suggested Links