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

[Bug 15213] Drag-and-drop processing model

From: <bugzilla@jessica.w3.org>
Date: Thu, 15 Dec 2011 18:57:06 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1RbGUM-0000ls-MV@jessica.w3.org>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=15213

Everett Zufelt <everett@zufelt.ca> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |everett@zufelt.ca

--- Comment #2 from Everett Zufelt <everett@zufelt.ca> 2011-12-15 18:57:06 UTC ---
(In reply to comment #1)
> I thought the intention of ARIA was pure mapping to the accessibility API. I.e.
> we would not attach behavior to it.

I can't comment on the intention of ARIA in general, or of its role in the
spec. 

I can say that anchors and images are given the @draggable attribute by
default. The ARIA link and img roles are used by developers to represent links
(anchors) and images, where native markup is not sufficient. I expect that
role="link" and role="img" map to <a> and <img> respectively, in the a11y API
mapping. Therefore, I think that we should provide, by default, the @draggable
attribute for these roles, in the same way that @draggable is applied by
default to <a> and <img>.

-- 
Configure bugmail: https://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 Thursday, 15 December 2011 18:57:12 UTC

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