It is definitely a deprecation. It is also an in your face warning that it
is going to go away so that if you hold onto it you proceed at your own
risk.
I think we need to do the work to ensure we or browser vendors provide a
replacement.
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/17/2015 05:12 AM
Subject: Re: ARIA 1.1: Deprecate @aria-grabbed and @aria-dropeffect
> On Sep 16, 2015, at 10:43 AM, Richard Schwerdtfeger <schwer@us.ibm.com>
wrote:
>
> 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."
Sounds a lot like "Deprecated" to me. ;)
> 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.
I've pointed out several existing alternative solutions in this thread.
It's not clear to me if you disagree with those, or if you did not see
them.
James
