{"action":"created","issue":{"url":"https://api.github.com/repos/mumble-voip/mumble/issues/2292","repository_url":"https://api.github.com/repos/mumble-voip/mumble","labels_url":"https://api.github.com/repos/mumble-voip/mumble/issues/2292/labels{/name}","comments_url":"https://api.github.com/repos/mumble-voip/mumble/issues/2292/comments","events_url":"https://api.github.com/repos/mumble-voip/mumble/issues/2292/events","html_url":"https://github.com/mumble-voip/mumble/issues/2292","id":155639998,"number":2292,"title":"a11y: Make comment accessible in channels tree","user":{"login":"jcsteh","id":4166475,"avatar_url":"https://avatars.githubusercontent.com/u/4166475?v=3","gravatar_id":"","url":"https://api.github.com/users/jcsteh","html_url":"https://github.com/jcsteh","followers_url":"https://api.github.com/users/jcsteh/followers","following_url":"https://api.github.com/users/jcsteh/following{/other_user}","gists_url":"https://api.github.com/users/jcsteh/gists{/gist_id}","starred_url":"https://api.github.com/users/jcsteh/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jcsteh/subscriptions","organizations_url":"https://api.github.com/users/jcsteh/orgs","repos_url":"https://api.github.com/users/jcsteh/repos","events_url":"https://api.github.com/users/jcsteh/events{/privacy}","received_events_url":"https://api.github.com/users/jcsteh/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/mumble-voip/mumble/labels/a11y","name":"a11y","color":"b60205"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2016-05-19T02:08:44Z","updated_at":"2016-05-24T00:47:03Z","closed_at":null,"body":"The comment for a user appears in a tool tip when you mouse over that user in the channels tree. Unfortunately, this is not easily accessible to users of screen readers. It would be good if this could be exposed as the accessible description for the tree item.\r\n\r\nI have no experience with QT programming, but glancing at the API and the Mumble code, I believe you should be able to manage this by exposing the comment via the [Qt::AccessibleDescriptionRole](http://doc.qt.io/qt-5/qt.html#ItemDataRole-enum)."},"comment":{"url":"https://api.github.com/repos/mumble-voip/mumble/issues/comments/221137156","html_url":"https://github.com/mumble-voip/mumble/issues/2292#issuecomment-221137156","issue_url":"https://api.github.com/repos/mumble-voip/mumble/issues/2292","id":221137156,"user":{"login":"jcsteh","id":4166475,"avatar_url":"https://avatars.githubusercontent.com/u/4166475?v=3","gravatar_id":"","url":"https://api.github.com/users/jcsteh","html_url":"https://github.com/jcsteh","followers_url":"https://api.github.com/users/jcsteh/followers","following_url":"https://api.github.com/users/jcsteh/following{/other_user}","gists_url":"https://api.github.com/users/jcsteh/gists{/gist_id}","starred_url":"https://api.github.com/users/jcsteh/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jcsteh/subscriptions","organizations_url":"https://api.github.com/users/jcsteh/orgs","repos_url":"https://api.github.com/users/jcsteh/repos","events_url":"https://api.github.com/users/jcsteh/events{/privacy}","received_events_url":"https://api.github.com/users/jcsteh/received_events","type":"User","site_admin":false},"created_at":"2016-05-24T00:47:03Z","updated_at":"2016-05-24T00:47:03Z","body":"A dialog with all of that info would be nice. However, that alone would \nmake for a fairly inefficient UX for a screen reader user, as they'd \nhave to open the dialog just to check whether a user even has a comment. \nThat's much faster for a sighted user; they can just mouse over the \nuser, and as I understand it, there's even an icon indicating that the \nuser has a comment.\n\nLet me ask this question: what states have visual indication in the \ntree? Are there icons for all of those (comment, muted, deafened, etc.)? \nIf so, we probably want to expose at least some of those in the \naccessible description as well. The key point is that it'd be good if \nthe experience were just as efficient for a screen reader user.\n"}}
{"actor":{"display_login":"jcsteh"}}