{"action":"created","issue":{"url":"https://api.github.com/repos/vakata/jstree/issues/1492","repository_url":"https://api.github.com/repos/vakata/jstree","labels_url":"https://api.github.com/repos/vakata/jstree/issues/1492/labels{/name}","comments_url":"https://api.github.com/repos/vakata/jstree/issues/1492/comments","events_url":"https://api.github.com/repos/vakata/jstree/issues/1492/events","html_url":"https://github.com/vakata/jstree/issues/1492","id":162971584,"number":1492,"title":"Accessiblity: Up/Down arrow keys focus <a> elements and not <li role=\"treeitem\"> elements... ","user":{"login":"Zroon","id":3638609,"avatar_url":"https://avatars.githubusercontent.com/u/3638609?v=3","gravatar_id":"","url":"https://api.github.com/users/Zroon","html_url":"https://github.com/Zroon","followers_url":"https://api.github.com/users/Zroon/followers","following_url":"https://api.github.com/users/Zroon/following{/other_user}","gists_url":"https://api.github.com/users/Zroon/gists{/gist_id}","starred_url":"https://api.github.com/users/Zroon/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Zroon/subscriptions","organizations_url":"https://api.github.com/users/Zroon/orgs","repos_url":"https://api.github.com/users/Zroon/repos","events_url":"https://api.github.com/users/Zroon/events{/privacy}","received_events_url":"https://api.github.com/users/Zroon/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":8,"created_at":"2016-06-29T16:35:23Z","updated_at":"2016-08-04T08:27:12Z","closed_at":null,"body":"I could be wrong about this but the WAI ARIA TreeView specs (https://www.w3.org/TR/2016/WD-wai-aria-practices-1.1-20160317/#TreeView) defines:\r\n\r\n> node: An item in a tree.\r\n\r\n...and specifies:\r\n\r\n> Each node in a tree has the role treeitem and should be a DOM child of tree.\r\n\r\n> Up Arrow and Down arrow keys move between visible nodes. \r\n\r\nIt's \"Up Arrow and Down arrow keys move between visible nodes\" that seems to be problematic.\r\n\r\nI've tested with JAWS (http://www.freedomscientific.com/Products/Blindness/JAWS) and NVDA (http://www.nvaccess.org/) and found some unexpected behavior.\r\n\r\nWhen initially entering the tree or using the up/down arrow keys I only hear the information associated with the links nested in the treeitems instead of the information about the treeitem.\r\n\r\nFor example, I hear \"(link text here) link\" instead of something like \"Level 1 group expanded (link text here) open 3 of 5\" (JAWS) or \"Group expanded (link text here) expanded 3 of 5 level 1\" (NVDA).\r\n\r\nI think the reason this is happening is that focus switching is happening on the jstree-anchor link elements rather than on the jstree-node elements (i.e. elements with role=\"treeitem\").\r\n\r\nWhen the focus switch occurs, it should switch focus between elements with role=\"treeitem\" and not anything nested within them. Otherwise the screen reader won't get the information it needs when navigating the TreeView.\r\n\r\nAs it stands jsTree only seems to be keyboard accessible and not screen reader accessible. When entering into jsTree or using the arrow keys while inside of it, I'm not hearing vital information like whether or not the current node is expanded or collapsed or what level or how many items are in the level... (...unlike when I navigate this example TreeView http://www.oaa-accessibility.org/examplep/treeview1/ which switches between treeitems and not nested links)."},"comment":{"url":"https://api.github.com/repos/vakata/jstree/issues/comments/237487131","html_url":"https://github.com/vakata/jstree/issues/1492#issuecomment-237487131","issue_url":"https://api.github.com/repos/vakata/jstree/issues/1492","id":237487131,"user":{"login":"vakata","id":146052,"avatar_url":"https://avatars.githubusercontent.com/u/146052?v=3","gravatar_id":"","url":"https://api.github.com/users/vakata","html_url":"https://github.com/vakata","followers_url":"https://api.github.com/users/vakata/followers","following_url":"https://api.github.com/users/vakata/following{/other_user}","gists_url":"https://api.github.com/users/vakata/gists{/gist_id}","starred_url":"https://api.github.com/users/vakata/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vakata/subscriptions","organizations_url":"https://api.github.com/users/vakata/orgs","repos_url":"https://api.github.com/users/vakata/repos","events_url":"https://api.github.com/users/vakata/events{/privacy}","received_events_url":"https://api.github.com/users/vakata/received_events","type":"User","site_admin":false},"created_at":"2016-08-04T08:27:12Z","updated_at":"2016-08-04T08:27:12Z","body":"@aadrian I agree with you - thank you for the input. I guess we really need someone used to using screen readers, who can say what is expected."}}
{"actor":{"display_login":"vakata"}}