I am not convinced that HTML has enough there yet although I agree that a
native solution would be far better and it needs to encompass SVG as well.
I think some strongly worded text, on the order of: "This ARIA feature is
planned for removal in a future release when more robust alternatives are
made available."
We have to make sure we have this alternative solution. When we pushed for
the JavaScript and CSS restriction to be removed in WCAG 2.0 from WCAG 1 we
had to prove that we could produce something that worked. I think that is
only fair to end users.
Rich
Rich Schwerdtfeger
From: James Craig <jcraig@apple.com>
To: Richard Schwerdtfeger/Austin/IBM@IBMUS
Cc: Bryan Garaventa <bryan.garaventa@ssbbartgroup.com>, Joanmarie
Diggs <jdiggs@igalia.com>, "lwatson@paciellogroup.com"
<lwatson@paciellogroup.com>, WAI Protocols & Formats
<public-pfwg@w3.org>
Date: 09/15/2015 06:03 PM
Subject: Re: ARIA 1.1: Deprecate @aria-grabbed and @aria-dropeffect
On Sep 15, 2015, at 1:02 PM, Richard Schwerdtfeger <schwer@us.ibm.com>
wrote:
> 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.
jQuery was just an example because Bryan mentioned it. My comment was:
>> jQuery *and other well-maintained libraries* update to include the most
performant native HTML features when they become available.
Certainly the fact that there are ~1000 JavaScript frameworks on the Web is
evidence that a native implementation is more desirable than putting the
onus on the framework developers.
I think there may be enough in the HTML 5.1 spec to make native HTML
drag&drag accessible. I know that there is not enough in the ARIA spec to
make drag&drop accessible on all platforms. We could let it limp along, or
we could deprecate it. I think the responsible decision is to deprecate it
and focus on the good parts of ARIA.
James
