- From: Bryan Garaventa <bryan.garaventa@ssbbartgroup.com>
- Date: Mon, 14 Sep 2015 17:05:13 +0000
- To: James Craig <jcraig@apple.com>
- CC: Richard Schwerdtfeger <schwer@us.ibm.com>, Joanmarie Diggs <jdiggs@igalia.com>, "lwatson@paciellogroup.com" <lwatson@paciellogroup.com>, WAI Protocols & Formats <public-pfwg@w3.org>
> 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. Granted, but how many years is that going to take? In the meantime, as a proof of concept, I've already built something that is accessible using the current API mappings, and if you want me to add mouse drag and drop I will be happy to do so. I'm sort of busy this week, but I can certainly add this if this is the only difference that is important to you. It's not going to make any difference to an AT user whether it is there or not. If anybody here would actually test this out using Firefox or Chrome with JAWS or NVDA, you can hear exactly what it does. -----Original Message----- From: James Craig [mailto:jcraig@apple.com] Sent: Sunday, September 13, 2015 11:15 PM To: Bryan Garaventa <bryan.garaventa@ssbbartgroup.com> Cc: Richard Schwerdtfeger <schwer@us.ibm.com>; Joanmarie Diggs <jdiggs@igalia.com>; lwatson@paciellogroup.com; WAI Protocols & Formats <public-pfwg@w3.org> 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
Received on Monday, 14 September 2015 17:05:46 UTC