{"action":"created","issue":{"url":"https://api.github.com/repos/w3c/aria/issues/136","labels_url":"https://api.github.com/repos/w3c/aria/issues/136/labels{/name}","comments_url":"https://api.github.com/repos/w3c/aria/issues/136/comments","events_url":"https://api.github.com/repos/w3c/aria/issues/136/events","html_url":"https://github.com/w3c/aria/issues/136","id":125686459,"number":136,"title":"SVG-AAM: Consider explicit language regarding objects with presentational role and aria-label","user":{"login":"Joanmarie","id":3228171,"avatar_url":"https://avatars.githubusercontent.com/u/3228171?v=3","gravatar_id":"","url":"https://api.github.com/users/Joanmarie","html_url":"https://github.com/Joanmarie","followers_url":"https://api.github.com/users/Joanmarie/followers","following_url":"https://api.github.com/users/Joanmarie/following{/other_user}","gists_url":"https://api.github.com/users/Joanmarie/gists{/gist_id}","starred_url":"https://api.github.com/users/Joanmarie/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Joanmarie/subscriptions","organizations_url":"https://api.github.com/users/Joanmarie/orgs","repos_url":"https://api.github.com/users/Joanmarie/repos","events_url":"https://api.github.com/users/Joanmarie/events{/privacy}","received_events_url":"https://api.github.com/users/Joanmarie/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":7,"created_at":"2016-01-08T20:23:09Z","updated_at":"2016-01-11T19:58:37Z","closed_at":null,"body":"In the SVG-AAM's [5.1.1 Excluding Elements from the Accessibility Tree](https://rawgit.com/w3c/aria/master/svg-aam/svg-aam.html#exclude_elements) there is the following note text:\r\n\r\n> The other factors for excluding elements, as described in the Core Accessibility API Mappings, are as follows:\r\n> * If the first mappable role provided by the author is none or presentation, the element must not be exposed.\r\n\r\n> [...]\r\n\r\n> Consult the original document [CORE-AAM] for the normative text.\r\n\r\nOne should, of course, consult the CORE-AAM as the good note states. But a reader of the above text couldn't be blamed all that severely if they read the above note text and concluded that given\r\n\r\n    <rect role=\"none\" aria-label=\"Am I Here?\" x=\"1\" y=\"1\" width=\"10\"' height=\"10\"/>\r\n\r\nthere should be no accessible object.\r\n\r\nIf one consults the CORE-AAM for the normative text, [5.1.1 Excluding Elements from the Accessibility Tree](https://rawgit.com/w3c/aria/master/core-aam/core-aam.html#exclude_elements2), they would find something quite similar:\r\n\r\n> The following elements are not exposed via the accessibility API and user agents MUST NOT include them in the accessibility tree:\r\n> * Elements with none or presentation as the first mappable role in the role attribute string, according to the rules for the none and the presentation role defined in Accessible Rich Internet Applications (WAI-ARIA) 1.0 [WAI-ARIA].\r\n\r\nSo unless the ARIA spec defines a rule for `none`/`presentation` that says otherwise, it would seem that the `rect` element in the example above does indeed need to be excluded.\r\n\r\nThere's a lot of text in the ARIA spec regarding the [presentation role](https://rawgit.com/w3c/aria/master/aria/aria.html#presentation), but for the question at hand this statement seems to be the most relevant:\r\n\r\n> For any element with an explicit or inherited role of presentation, user agents MUST ignore any non-global, role-specific WAI-ARIA states and properties. **However, the user agent MUST always expose global WAI-ARIA states and properties to accessibility APIs, even if an element has an explicit or inherited role of presentation.** \r\n\r\n(emphasis added)\r\n\r\nThe `aria-label` attribute is global. So then the `rect` element in the example above would need to be exposed after all (right?).\r\n\r\nI mention all of this for a couple of reasons:\r\n\r\n1. By adding explicit language in the SVG-AAM regarding objects with presentational role and a valid value for `aria-label`, implementors would not have to do all of the work above I just did. ;) Plus it would be clear and eliminate lingering doubts (e.g. an implementor might think, \"A shape element whose role has been explicitly set to `none` is surely decorative and useless with respect to accessibility.\")\r\n\r\n2. The work-in-progress tests in the wiki include [shapes with role=\"none\" and an aria-label, along with expected results of NOAC](https://www.w3.org/wiki/SVG_Accessibility/Testing/Test_Assertions#Basic_shapes_role_.3D_none). If the those tests expectations are indeed correct, they seem to be in potential conflict with the text I quote above."},"comment":{"url":"https://api.github.com/repos/w3c/aria/issues/comments/170671753","html_url":"https://github.com/w3c/aria/issues/136#issuecomment-170671753","issue_url":"https://api.github.com/repos/w3c/aria/issues/136","id":170671753,"user":{"login":"Joanmarie","id":3228171,"avatar_url":"https://avatars.githubusercontent.com/u/3228171?v=3","gravatar_id":"","url":"https://api.github.com/users/Joanmarie","html_url":"https://github.com/Joanmarie","followers_url":"https://api.github.com/users/Joanmarie/followers","following_url":"https://api.github.com/users/Joanmarie/following{/other_user}","gists_url":"https://api.github.com/users/Joanmarie/gists{/gist_id}","starred_url":"https://api.github.com/users/Joanmarie/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Joanmarie/subscriptions","organizations_url":"https://api.github.com/users/Joanmarie/orgs","repos_url":"https://api.github.com/users/Joanmarie/repos","events_url":"https://api.github.com/users/Joanmarie/events{/privacy}","received_events_url":"https://api.github.com/users/Joanmarie/received_events","type":"User","site_admin":false},"created_at":"2016-01-11T19:58:37Z","updated_at":"2016-01-11T19:58:37Z","body":"@fredesch:\r\n\r\n> The testable statements in the wiki are not yet vetted, but feel free to review the testable statements in the wiki and see if they raise any issues.\r\n\r\nHow do you think I'm finding the issues I'm raising? ;) ;)\r\n\r\nWhile I fully realize your statements are not vetted and are subject to change, they are extremely handy. :) I've made several local WebKit \"Layout Tests\" with the assertions there. These automated tests run in a couple of seconds and tell me what all is failing. From there, I debug WebKit and either fix the bug (locally at the moment) or start reading your spec and opening issues like this one. :)\r\n\r\nOnce your group has consensus and I have proposed fixes for everything, I'll open a bug upstream (in the WebKit issue tracker) and ping you."}}