{"action":"opened","issue":{"url":"https://api.github.com/repos/searchkit/searchkit/issues/359","repository_url":"https://api.github.com/repos/searchkit/searchkit","labels_url":"https://api.github.com/repos/searchkit/searchkit/issues/359/labels{/name}","comments_url":"https://api.github.com/repos/searchkit/searchkit/issues/359/comments","events_url":"https://api.github.com/repos/searchkit/searchkit/issues/359/events","html_url":"https://github.com/searchkit/searchkit/issues/359","id":194441925,"number":359,"title":"SearchKit is not accessible","user":{"login":"singingwolfboy","id":132355,"avatar_url":"https://avatars.githubusercontent.com/u/132355?v=3","gravatar_id":"","url":"https://api.github.com/users/singingwolfboy","html_url":"https://github.com/singingwolfboy","followers_url":"https://api.github.com/users/singingwolfboy/followers","following_url":"https://api.github.com/users/singingwolfboy/following{/other_user}","gists_url":"https://api.github.com/users/singingwolfboy/gists{/gist_id}","starred_url":"https://api.github.com/users/singingwolfboy/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/singingwolfboy/subscriptions","organizations_url":"https://api.github.com/users/singingwolfboy/orgs","repos_url":"https://api.github.com/users/singingwolfboy/repos","events_url":"https://api.github.com/users/singingwolfboy/events{/privacy}","received_events_url":"https://api.github.com/users/singingwolfboy/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-12-08T20:55:15Z","updated_at":"2016-12-08T20:55:15Z","closed_at":null,"body":"SearchKit looks and works great for sighted users who can use a mouse, but not everyone is in that situation. In order to be accessible to a wider audience, SearchKit should have the following features:\r\n\r\n* The UI should be fully navigable using only a keyboard.\r\n* Any text elements that respond to mouse clicks should be [`<button>`](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/button) elements, so that the browser knows that they should be focusable when tabbing through the page. (They can be styled using CSS so that they don't visually appear to be buttons, if that is preferred.)\r\n* All checkboxes and other input elements should have associated [`<label>`](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/label) elements, so that screen readers can announce what the checkbox is for.\r\n* Lists should use `<ul>` or `<ol>` elements, and list items should use `<li>` elements. (This allows a screen reader to announce how long the list is.)\r\n* Lists of options should be grouped using a [`<fieldset>`](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/fieldset) element, and the list header should be a [`<legend>`](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/legend) element in that `<fieldset>`.\r\n\r\nI'm happy to provide more information or help out with this effort, if the SearchKit team is open to these changes."}}
{"actor":{"display_login":"singingwolfboy"}}