{"action":"created","issue":{"url":"https://api.github.com/repos/w3c/respec/issues/971","repository_url":"https://api.github.com/repos/w3c/respec","labels_url":"https://api.github.com/repos/w3c/respec/issues/971/labels{/name}","comments_url":"https://api.github.com/repos/w3c/respec/issues/971/comments","events_url":"https://api.github.com/repos/w3c/respec/issues/971/events","html_url":"https://github.com/w3c/respec/issues/971","id":189808905,"number":971,"title":"Do processing on a hidden node to fix screen reader and permalink problems","user":{"login":"mcking65","id":7241781,"avatar_url":"https://avatars.githubusercontent.com/u/7241781?v=3","gravatar_id":"","url":"https://api.github.com/users/mcking65","html_url":"https://github.com/mcking65","followers_url":"https://api.github.com/users/mcking65/followers","following_url":"https://api.github.com/users/mcking65/following{/other_user}","gists_url":"https://api.github.com/users/mcking65/gists{/gist_id}","starred_url":"https://api.github.com/users/mcking65/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mcking65/subscriptions","organizations_url":"https://api.github.com/users/mcking65/orgs","repos_url":"https://api.github.com/users/mcking65/repos","events_url":"https://api.github.com/users/mcking65/events{/privacy}","received_events_url":"https://api.github.com/users/mcking65/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2016-11-16T19:00:47Z","updated_at":"2016-11-17T02:06:20Z","closed_at":null,"body":"Every DOM mutation creates an accessibility event. When thousands of mutations are occuring, the accessibility tree is driving screen readers to their knees.\r\n\r\nWhen people who do not use a screen reader receive a link to a section of a document, they lose their place when the document refreshes.\r\n\r\nThese problems could be fixed if the document is not displayed until processing is complete.  While document processing is occuring, display a single node with text like: \r\n\r\n>Respec script is formatting the document, please wait.\r\n\r\nAnd, then do all the format processing on a node that has display:none.\r\n\r\nThis may seem a bit old-school, forcing people who want to start reading at the beginning of the document to wait for 3 or 4 seconds, but the wait is worth it. Today, some screen readers crash and have to be restarted because of this processing. That means a minimum of 2 minutes to load a document, during which time the system is unusable. At a minimum, if things go well with a screen reader, it can take 30 to 60 seconds to load a spec like the ARIA spec.\r\n\r\ncc: @Joanmarie, @michael-n-cooper, @halindrome\r\n"},"comment":{"url":"https://api.github.com/repos/w3c/respec/issues/comments/261133643","html_url":"https://github.com/w3c/respec/issues/971#issuecomment-261133643","issue_url":"https://api.github.com/repos/w3c/respec/issues/971","id":261133643,"user":{"login":"marcoscaceres","id":870154,"avatar_url":"https://avatars.githubusercontent.com/u/870154?v=3","gravatar_id":"","url":"https://api.github.com/users/marcoscaceres","html_url":"https://github.com/marcoscaceres","followers_url":"https://api.github.com/users/marcoscaceres/followers","following_url":"https://api.github.com/users/marcoscaceres/following{/other_user}","gists_url":"https://api.github.com/users/marcoscaceres/gists{/gist_id}","starred_url":"https://api.github.com/users/marcoscaceres/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/marcoscaceres/subscriptions","organizations_url":"https://api.github.com/users/marcoscaceres/orgs","repos_url":"https://api.github.com/users/marcoscaceres/repos","events_url":"https://api.github.com/users/marcoscaceres/events{/privacy}","received_events_url":"https://api.github.com/users/marcoscaceres/received_events","type":"User","site_admin":false},"created_at":"2016-11-17T02:06:20Z","updated_at":"2016-11-17T02:06:20Z","body":"We've made a few attempts at this, but this is not straight forward unfortunately :( We are trying to address adding as few nodes as possible (using document fragments), while also trying to minimize the number of events. However, we don't have full control over things (e.g., highlighting and the handlebars template library - which makes most of the mutations... and then there is a crap ton of legacy jQuery cruft that has built up over the years)... so it will be challenging. \r\n\r\nWe could try \"display: none\" the document when processing starts, and returning the display to normal when processing ends. It's cheap and nasty and could potentially work. \r\n\r\nHaving said that, any reason why the ARIA spec is not being generated on the client side and published as processed HTML? It, could at least, immediately help your community of users."}}
{"actor":{"display_login":"marcoscaceres"}}