New to Telerik UI for Blazor? Download Free 30-day trial
TreeList - Keyboard Navigation
- VIEW SOURCE
- EDIT IN TELERIK REPL
- Change Theme
|First Name||Last Name||Hire Date|
|Daryl||Sweeney||2/7/2012 8:00:00 PM|
|Guy||Wooten||3/3/2010 8:00:00 PM|
|Buffy||Weber||7/11/2011 6:00:00 PM|
|Skyler||Cleveland||11/10/2014 12:00:00 AM|
|Priscilla||Frank||11/30/2014 12:00:00 AM|
|Ursula||Holmes||6/6/2011 12:00:00 AM|
|Melvin||Carrillo||7/21/2014 12:00:00 AM|
|Martha||Chavez||3/12/2013 12:00:00 AM|
|Oren||Fox||5/14/2013 12:00:00 AM|
|Amos||Barr||3/9/2010 12:00:00 AM|
Supported keys and user actions
The roving tab index for its data portion.key moves focus through all focusable elements on the page and the treelist does not block it - it uses
This means that you can go through the treelist toolbar and filter row with thekey, then the focus goes through the data portion of the treelist and you can navigate through the cells and rows with the arrow keys.
Pressingfrom the data portion will move the focus to the next focusable element on the page - this can be some focusable element in the currently focused row (like a button or an input in a cell or template), or the next focusable element on the page after the treelist (depending on the tab order of the page).
If the focus is in the data table and paging is enabled, pressing Tab key will move the focus to the Pager. You can refer to Pager - Keyboard Navigation for its supported shortcuts.
To exit the InLine edit mode, go to the Update or Cancel button in the command column.
To exit the PopUp edit mode, go to the Save or Cancel button in the popup itself.
To exit the InCell edit mode, move focus away from the grid. Pressing on the last row also ends edit mode, but on other rows it puts the next row in edit mode to allow fast data entry.
Keyboard navigation provides all web and app users with a fast keyboard-only navigation capability and is also part of the web accessibility features - it enables users with disabilities to fully control their website or app access through the keyboard.
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, keyboard navigation logic 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 the page navigation.
To enable the keyboard navigation of the Telerik UI for Blazor TreeList set
Navigable="true", as demonstrated in this demo.