Re: ARIA 1.1: Deprecate @aria-grabbed and @aria-dropeffect

> On Sep 12, 2015, at 1:24 PM, Bryan Garaventa <bryan.garaventa@ssbbartgroup.com> wrote:
> 
> What I don't understand about this whole argument is this, if what I've already built is accessible, which you can verify by testing it on desktop and touch devices, what is so inaccessible about it that requires a total functionality redesign?

I'm not arguing that you've built something inaccessible.

I'm arguing a few points about @aria-grabbed and @aria-dropeffect:

1. The attributes were never capable of solving the drag&drop problem they were intended to solve. Instead they created yet another way to simulate selection+action, and we already have numerous ways to do that in HTML and ARIA. For example, using two <button> elements is a much simpler way of accomplishing the same thing.

2. Because the API implies that it's somehow related to drag&drop, it's harmful to keep around, because it only serves to confuse authors.

3. We have evidence that no one inside the working group has built an example that works alongside real drag&drop, so there is no working example for the confused web authors to reference, just more confusing examples that don't clarify how this API is related to drag&drop.

4. We have little or no evidence that anyone outside the W3C working group has used these features at all, so the web authoring community is unlikely to miss them, or even notice that they've been deprecated.

> Keep in mind, we are not just talking about Apple devices, but all platforms like Windows using JAWS and NVDA.

:-/ 

I always keep that in mind. I work on the Web.

James

Received on Sunday, 13 September 2015 11:27:40 UTC