# Keyboard Navigation

## Managing the Focus

The editor integrates the **Toolbar** component and inherits all shortcuts from it. So, the component has two tab stops - one the toolbar and one the content area. When using the single click tools by mouse, the focus remains on the content.

### Actions applied to Editor content area:

| Shortcut          | Behavior                    |
| ----------------- | --------------------------- |
| `Ctrl/Cmd(Mac)+B` | Executes bold command.      |
| `Ctrl/Cmd(Mac)+I` | Executes italic command.    |
| `Ctrl/Cmd(Mac)+U` | Executes underline command. |
| `Ctrl/Cmd(Mac)+Z` | Executes undo command.      |
| `Ctrl/Cmd(Mac)+Y` | Executes redo command.      |
| `Shift+Enter`     | Adds `<br/>` to content.    |
| `Enter`           | Adds `<p>` to content.      |

## Resources

[ARIA Authoring Practices: Toolbar](https://www.w3.org/WAI/ARIA/apg/patterns/toolbar/examples/toolbar/)

[Demo Source](https://demos.telerik.com/kendo-react-ui/editor/overview/func/source.txt)

## See Also

* [API Reference of the Editor](https://www.telerik.com/kendo-react-ui-develop/components/editor/api/editor)
* [Toolbar keyboard navigation](https://www.telerik.com/kendo-react-ui-develop/components/buttons/toolbar/keyboard-navigation)
* [Accessibility in KendoReact](https://www.telerik.com/kendo-react-ui-develop/components/accessibility)
* [Accessibility Compliance and Keyboard Support in KendoReact](https://www.telerik.com/kendo-react-ui-develop/components/accessibility/accessibility-compliance)