area elements that create hyperlinks should have same role options as a elements that create hyperlinks

[stevefaulkner]

original bug:https://www.w3.org/Bugs/Public/show_bug.cgi?id=24272

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.

[stevefaulkner]

wontfixing this as area elements are problematic in regards to ARIA role/state/property representation as implemented.