{"action":"created","issue":{"url":"https://api.github.com/repos/whatwg/html/issues/100","labels_url":"https://api.github.com/repos/whatwg/html/issues/100/labels{/name}","comments_url":"https://api.github.com/repos/whatwg/html/issues/100/comments","events_url":"https://api.github.com/repos/whatwg/html/issues/100/events","html_url":"https://github.com/whatwg/html/issues/100","id":104859192,"number":100,"title":"Consider aligning WHATWG main element definition with W3C definition","user":{"login":"stevefaulkner","id":835859,"avatar_url":"https://avatars.githubusercontent.com/u/835859?v=3","gravatar_id":"","url":"https://api.github.com/users/stevefaulkner","html_url":"https://github.com/stevefaulkner","followers_url":"https://api.github.com/users/stevefaulkner/followers","following_url":"https://api.github.com/users/stevefaulkner/following{/other_user}","gists_url":"https://api.github.com/users/stevefaulkner/gists{/gist_id}","starred_url":"https://api.github.com/users/stevefaulkner/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/stevefaulkner/subscriptions","organizations_url":"https://api.github.com/users/stevefaulkner/orgs","repos_url":"https://api.github.com/users/stevefaulkner/repos","events_url":"https://api.github.com/users/stevefaulkner/events{/privacy}","received_events_url":"https://api.github.com/users/stevefaulkner/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":12,"created_at":"2015-09-04T09:39:52Z","updated_at":"2015-09-04T19:11:56Z","closed_at":null,"body":"The main element was designed and implemented based on the concept of there being a single instance within a document, the markup pattern was based on data of [id value usage](http://www.w3.org/TR/html-main-element/#notes) in the wild. The whatwg definition differs markedly from the orginal definition. This leads to [confusion for developers](https://twitter.com/peeja/status/639451464608432128).\r\nThe [W3C nu html checker](https://validator.w3.org/nu/), which is used by many, throws an error when main is used as per whatwg. Data derived from [webdevdata.org](http://webdevdata.org/) shows that >97% of usage of the &lt;main> element is as per the W3C definition and anecdata from users that consume the semantics suggests that one main element per page is the expected and most useful pattern. In general consumers landmark semantics report that the utility of landmarks is reduced as the number/instances of landmark elements in a document increases. \r\nThe alignment would involve changes to the main and body element definitions.\r\ncurrent W3C definitions:\r\n* [main element](http://www.w3.org/TR/html51/semantics.html#the-main-element)\r\n* [body element](http://www.w3.org/TR/html51/semantics.html#the-body-element)\r\n"},"comment":{"url":"https://api.github.com/repos/whatwg/html/issues/comments/137827381","html_url":"https://github.com/whatwg/html/issues/100#issuecomment-137827381","issue_url":"https://api.github.com/repos/whatwg/html/issues/100","id":137827381,"user":{"login":"domenic","id":617481,"avatar_url":"https://avatars.githubusercontent.com/u/617481?v=3","gravatar_id":"","url":"https://api.github.com/users/domenic","html_url":"https://github.com/domenic","followers_url":"https://api.github.com/users/domenic/followers","following_url":"https://api.github.com/users/domenic/following{/other_user}","gists_url":"https://api.github.com/users/domenic/gists{/gist_id}","starred_url":"https://api.github.com/users/domenic/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/domenic/subscriptions","organizations_url":"https://api.github.com/users/domenic/orgs","repos_url":"https://api.github.com/users/domenic/repos","events_url":"https://api.github.com/users/domenic/events{/privacy}","received_events_url":"https://api.github.com/users/domenic/received_events","type":"User","site_admin":false},"created_at":"2015-09-04T19:11:56Z","updated_at":"2015-09-04T19:11:56Z","body":"My perspective is that multiple mains do make sense. I've used them in a few large apps before (internal mostly, for finance firms), and the spec documents how to do so. As such, I like the current spec.\r\n\r\nHowever, if such usage of mains is causing problems for users of accessibility technology, then we need to reconsider.\r\n\r\nSo basically: (1) is false (I know some people love to debate this, but from the perspective of the current spec and at least a couple of its editors, that's the case). (2) would mean we should change the spec. (3) would mean we probably shouldn't change the spec, depending on what \"correctly\" means. Although even if it's (3), there have been some comments about screen reader _user expectations_ on this thread that might change things."}}