We cannot bank on one Widget library doing this. jQueryUI only has 4%
market share: http://www.perfectleads.com/marketshare/angular-js
There is strong indication that its use is dropping.
Also, regarding HTML5, that group is so fragmented right now. I look at the
Web Platforms Group and I see not leadership from either Apple or Google. I
also don't see drag and drop on any of their priority lists.
There was also a comment about using aria-selected early. aria-selected is
used in widgets for selection within the widget and not necessarily and not
necessarily for drag and drop. This is why aria-grabbed was used. In fact,
we have selection models in different platform APIs that this would mess
up.
Ditching it for nothing is a bad idea. I would support deprecating it with
the meaning "we intend to replace this with a better solution in the future
and to not plan on it being there."
IBM does not use it but if Bryan has customers that are using it then we
should not throw it completely out the door if we don't have a working
alternative. Why would we do harm to people who are currently depending on
it to do their work. That makes no sense.
Bryan, please weigh in on the number of customers you have that are using
it and the size of these companies. Are they federal agencies? What?
Rich
Rich Schwerdtfeger
From: James Craig <jcraig@apple.com>
To: Bryan Garaventa <bryan.garaventa@ssbbartgroup.com>
Cc: Richard Schwerdtfeger/Austin/IBM@IBMUS, Joanmarie Diggs
<jdiggs@igalia.com>, "lwatson@paciellogroup.com"
<lwatson@paciellogroup.com>, WAI Protocols & Formats
<public-pfwg@w3.org>
Date: 09/14/2015 01:15 AM
Subject: Re: ARIA 1.1: Deprecate @aria-grabbed and @aria-dropeffect
> On Sep 13, 2015, at 5:36 PM, Bryan Garaventa
<bryan.garaventa@ssbbartgroup.com> wrote:
>
> If you propose to the jQuery UI guys to completely revamp this widget to
make it accessible like this, it will never happen.
No. I'm proposing that when natively accessible drag&drop is available, the
jQuery UI implementation will update to use the native, accessible version
in capable browsers, leaving the current implementation as a fallback
polyfill. This assumption is consistent with the project's history. jQuery
and other well-maintained libraries update to include the most performant
native HTML features when they become available.
James
