GitHub IssuesEvent at 2015-01-01 15:02:01
Repository: addyosmani/a11y
Actor: addyosmani
Payload: {"action":"opened","issue":{"url":"https://api.github.com/repos/addyosmani/a11y/issues/26","labels_url":"https://api.github.com/repos/addyosmani/a11y/issues/26/labels{/name}","comments_url":"https://api.github.com/repos/addyosmani/a11y/issues/26/comments","events_url":"https://api.github.com/repos/addyosmani/a11y/issues/26/events","html_url":"https://github.com/addyosmani/a11y/issues/26","id":53221371,"number":26,"title":"Improve auditing for webapps","user":{"login":"addyosmani","id":110953,"avatar_url":"https://avatars.githubusercontent.com/u/110953?v=3","gravatar_id":"","url":"https://api.github.com/users/addyosmani","html_url":"https://github.com/addyosmani","followers_url":"https://api.github.com/users/addyosmani/followers","following_url":"https://api.github.com/users/addyosmani/following{/other_user}","gists_url":"https://api.github.com/users/addyosmani/gists{/gist_id}","starred_url":"https://api.github.com/users/addyosmani/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/addyosmani/subscriptions","organizations_url":"https://api.github.com/users/addyosmani/orgs","repos_url":"https://api.github.com/users/addyosmani/repos","events_url":"https://api.github.com/users/addyosmani/events{/privacy}","received_events_url":"https://api.github.com/users/addyosmani/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-01-01T15:02:01Z","updated_at":"2015-01-01T15:02:01Z","closed_at":null,"body":"When using the Chrome Accessibility DevTools extension, pages such as [this Angular Todo](http://todomvc.com/examples/angularjs/#/) app will display severity issues that are not reported by A11y when conducting an audit.\r\n\r\nExample: \r\n![](http://i.imgur.com/wROYEW7.png)\r\n\r\nvs:\r\n\r\n![](http://i.imgur.com/iCs2pet.png)\r\n\r\nMy current theory is that we're not giving the page sufficient time to complete JS execution so not all content is present and in an auditable state.\r\n\r\nAfter experimenting with adding a custom timeout (similar to [this](https://github.com/kevva/screenshot-stream/blob/681d34fd0c5e9be0a894397e8d9a1f6841953810/lib/index.js#L156)) and playing with timeouts of differing values, this doesn't appear to improve our ability to report back on such issues.\r\n\r\nThese issues aren't specific to this module (as far as I can tell). I've been able to repro the same with https://github.com/GoogleChrome/accessibility-developer-tools. Looking into this further."}}