{"action":"created","issue":{"url":"https://api.github.com/repos/WordPress/twentysixteen/issues/253","labels_url":"https://api.github.com/repos/WordPress/twentysixteen/issues/253/labels{/name}","comments_url":"https://api.github.com/repos/WordPress/twentysixteen/issues/253/comments","events_url":"https://api.github.com/repos/WordPress/twentysixteen/issues/253/events","html_url":"https://github.com/WordPress/twentysixteen/issues/253","id":107728885,"number":253,"title":"Accessibility user test results","user":{"login":"RRWD","id":2351479,"avatar_url":"https://avatars.githubusercontent.com/u/2351479?v=3","gravatar_id":"","url":"https://api.github.com/users/RRWD","html_url":"https://github.com/RRWD","followers_url":"https://api.github.com/users/RRWD/followers","following_url":"https://api.github.com/users/RRWD/following{/other_user}","gists_url":"https://api.github.com/users/RRWD/gists{/gist_id}","starred_url":"https://api.github.com/users/RRWD/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/RRWD/subscriptions","organizations_url":"https://api.github.com/users/RRWD/orgs","repos_url":"https://api.github.com/users/RRWD/repos","events_url":"https://api.github.com/users/RRWD/events{/privacy}","received_events_url":"https://api.github.com/users/RRWD/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-09-22T14:42:48Z","updated_at":"2015-09-22T19:26:27Z","closed_at":null,"body":"Accessibility usertest: Twenty Sixteen\r\nhttps://make.wordpress.org/accessibility/2015/09/22/accessibility-usertest-twenty-sixteen/\r\n\r\n## Summary\r\nThe main opinion: This theme tested pretty well!\r\nNo drastic errors. Yay!\r\n\r\n**First**: can someone reproduce Jeff’s error?\r\n\r\n**Missing context for sighted users** (maybe also a usability issue): The author, category, and tag links in the post meta simply state just that. That is, “themedemos”. Or “Uncategorized”. Nothing else, no context. For screen reader usres there is extra text to give context.\r\n\r\n**Landmarks**: A lot of the remarks where about landmarks. W3C and VAWE now mark elements with the same role as warnings (not errors). Like: Element nav does not need a role attribute role=nav.\r\n\r\nNote Rian: We discussed this in the team chat and decided that the roles should stay for now, for backwards compatibility with old assistive technology.\r\n\r\n**Navigation**: three the same remarks:\r\n\r\n* Users should be able to select ‘ESC’ to close a drop-down menu, and then when tabbing or arrowing again they are taken to the next main menu item.\r\n* Screen reader user have to go through all submenu items in order to get to another tab item\r\n* Currently, if you want to navigate to “Page B,” you have to tab through the entire main nav, sub items included.\r\n\r\nNote Rian: this is not an accessibility error, but a keyboard user usability issue. Might be worth to find a solution for this.\r\n\r\n**Featured image**: There was confusion about the featured image with the link being skipped. This is on purpose to prevent extr noise for screen readers by adding an aria-hidden=”true” to the link.\r\n\r\n**Input fields**: The color contrast for the border or background colors could be increased.\r\n\r\n**Focus errors**:\r\n\r\n* search button should show up on focus\r\n* inconsistent focus for responsive Menu toggle button\r\n* submenu toggle responsive menu should have an outline\r\n\r\n**Page navigation**\r\n\r\n* no ARIA indicator current page number for a screen reader\r\n* color is not enough to indicate this is the current page number\r\n"},"comment":{"url":"https://api.github.com/repos/WordPress/twentysixteen/issues/comments/142392249","html_url":"https://github.com/WordPress/twentysixteen/issues/253#issuecomment-142392249","issue_url":"https://api.github.com/repos/WordPress/twentysixteen/issues/253","id":142392249,"user":{"login":"davidakennedy","id":1473618,"avatar_url":"https://avatars.githubusercontent.com/u/1473618?v=3","gravatar_id":"","url":"https://api.github.com/users/davidakennedy","html_url":"https://github.com/davidakennedy","followers_url":"https://api.github.com/users/davidakennedy/followers","following_url":"https://api.github.com/users/davidakennedy/following{/other_user}","gists_url":"https://api.github.com/users/davidakennedy/gists{/gist_id}","starred_url":"https://api.github.com/users/davidakennedy/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/davidakennedy/subscriptions","organizations_url":"https://api.github.com/users/davidakennedy/orgs","repos_url":"https://api.github.com/users/davidakennedy/repos","events_url":"https://api.github.com/users/davidakennedy/events{/privacy}","received_events_url":"https://api.github.com/users/davidakennedy/received_events","type":"User","site_admin":false},"created_at":"2015-09-22T19:26:27Z","updated_at":"2015-09-22T19:26:27Z","body":"> Missing context for sighted users (maybe also a usability issue): The author, category, and tag links in the post meta simply state just that. That is, “themedemos”. Or “Uncategorized”. Nothing else, no context. For screen reader usres there is extra text to give context.\r\n\r\nI'm not seeing this. I see that there is hidden text for each of the post meta items. I see them on archive and single pages. Is there another place where they're missing? Worth noting that the hidden text is not inside the links, but before it. But I think that's fine."}}