W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > October 2011

[Bug 13265] Should disallow <a> elements to be made into buttons, checkboxes, radio buttons, tabs, or tree items, since those are all semantic abuse

From: <bugzilla@jessica.w3.org>
Date: Sun, 02 Oct 2011 05:12:29 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1RAELl-00056P-6D@jessica.w3.org>

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
         Resolution|WONTFIX                     |FIXED

--- Comment #3 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-10-02 05:12:27 UTC ---
That isn't the point of ARIA. ARIA is primarily for developers creating custom
widgets and other web application components. It allows authors to provide
accessibility hooks for ATs in cases where the user agent would otherwise have
nothing useful to provide. It is not intended for use by authors who are trying
to convey the very semantics that HTML can already convey.

In any case, having an AT label a link as being a button actually hurts
accessibility, it doesn't improve it, as it makes it impossible for the user to
understand instructions. For example, if they visit a page that has a link
labeled as role=button, and they read instructions telling them to click on the
link, they would not be able to find it, as they would be looking for a link
and not a button. Similarly, labeling an interactive control such as a link as
being a tree item would harm accessibility, as it would hide from the user the
fact that the link could be activated and followed.

Ergo, I am reopening this bug.

EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, please change the state of this bug to CLOSED. If
you have additional information and would like the editor to reconsider, please
reopen this bug. If you would like to escalate the issue to the full HTML
Working Group, please add the TrackerRequest keyword to this bug, and suggest
title and text for the tracker issue; or you may create a tracker issue
yourself, if you are able to do so. For more details, see this document:

Status: Partially Accepted
Change Description: see diff given below
Rationale: However, the initial request is not entirely correct either. It
does, to some extent, make sense for links to be used as tabs. So I've left
that as conforming.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Sunday, 2 October 2011 05:12:31 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:02:05 UTC