[Bug 24272] New: area element that creates a hyperlink should have cirka same role options a element that creates a hyperlink

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

            Bug ID: 24272
           Summary: area element that creates a hyperlink should have
                    cirka same role options a element that creates a
                    hyperlink
           Product: HTML WG
           Version: unspecified
          Hardware: PC
               URL: http://www.w3.org/html/wg/drafts/html/master/dom.html#
                    sec-strong-native-semantics
                OS: All
            Status: NEW
          Keywords: a11y
          Severity: major
          Priority: P3
         Component: HTML5 spec
          Assignee: dave.null@w3.org
          Reporter: xn--mlform-iua@xn--mlform-iua.no
        QA Contact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-admin@w3.org,
                    public-html-wg-issue-tracking@w3.org

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.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Saturday, 11 January 2014 21:59:21 UTC