Karkhut Volodymyr

**Issue description:** Currently jsTree uses ‘keydown’ event for node activation. But this approach has some significant gaps: **1. Keyboard ‘keydown’ event could be triggered multiple times while user presses and...

Fix 'scrollable-region-focusable' AXE error to fix #2541

1

Fixed 'scrollable-region-focusable' AXE error described in #2541 By default tabindex='0' is set for jstree container. When focus is set on tree element tabindex for jstree container is set as '-1'...

Previosly aria-busy state, that was triggered by node loading, was set on li element which use role="none". According to specifications elements with role="none" shouldn't use any aria attributes. Hence such...

jsTree has no elements with tabindex="0" when focus is on tree item.

3

Currently, jsTree uses aria-activedescendant approach to manage focus inside tree [link](https://www.w3.org/TR/wai-aria-practices-1.1/#kbd_focus_activedescendant). In recommendation we can see next: > If a component container has an ARIA role that supports the aria-activedescendant...

[Accessibility]Aria-busy shouldn't be used on listitem elements

1

Currently, jsTree node is presented as listitem with role 'none' that contains anchor with role 'treeitem'. For example: ``` ``` Role 'none' needed here to hide listitem from assistive technologies...

JAWS ignores aria-label for <hr> element and doesn't recognize element with role='separator' in Fireforx

3

### Summary For the next code snippet ``` Content above Content in the middle Visible label Content in the middle Visible label2 Content below ``` User navigates through elements from...