24272 2014-01-11 21:59:19 +0000 area elements that create hyperlinks should have cirka same role options as a elements that create hyperlinks 2015-06-05 14:37:36 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified PC All RESOLVED MOVED http://www.w3.org/html/wg/drafts/html/master/dom.html#sec-strong-native-semantics a11y P3 major --- 1 xn--mlform-iua faulkner.steve faulkner.steve mike public-html-admin public-html-wg-issue-tracking xn--mlform-iua public-html-bugzilla oldest_to_newest 98286 0 xn--mlform-iua 2014-01-11 21:59:19 +0000 Please reconsider the possible ARIA roles for area elements that forms hyperlinks. Area elements that create hyperlinks are currently placed in the strong native ARIA semantics table and is thereby only allowed to have a single role - the link role. By contrast, anchor elements that create hyperlinks are placed in the table over the weak native ARIA semantics table and can take a number of roles: “If specified, role must be one of the following: link, button, checkbox, menuitem, menuitemcheckbox,menuitemradio, tab, or treeitem”. However, as a matter of fact, an area elements area always linked to graphics of some sort. So e.g. they can for instance be attached to an area of an image that has the shape of a button. So at the very least, it should be able to take the button role as well. But please consider if it may take even more role. E.g. a button may occur in navigation menus, so perhaps menuitem role should be considered as well. Tab role also seems like a possibility. And perhaps others. 98290 1 faulkner.steve 2014-01-11 22:44:12 +0000 hi leif(In reply to Leif Halvard Silli from comment #0) > Please reconsider the possible ARIA roles for area elements that forms > hyperlinks. > > Area elements that create hyperlinks are currently placed in the strong > native ARIA semantics table and is thereby only allowed to have a single > role - the link role. > > By contrast, anchor elements that create hyperlinks are placed in the table > over the weak native ARIA semantics table and can take a number of roles: > “If specified, role must be one of the following: link, button, checkbox, > menuitem, menuitemcheckbox,menuitemradio, tab, or treeitem”. > > However, as a matter of fact, an area elements area always linked to > graphics of some sort. So e.g. they can for instance be attached to an area > of an image that has the shape of a button. > > So at the very least, it should be able to take the button role as well. But > please consider if it may take even more role. E.g. a button may occur in > navigation menus, so perhaps menuitem role should be considered as well. > Tab role also seems like a possibility. And perhaps others. hi leif, agree there is a disparity without obvious reason, will look into it. 120731 2 faulkner.steve 2015-06-05 14:37:36 +0000 moved to aria MODULE https://github.com/webspecs/html-aria/issues/20