E-mail List Archives
Number of posts in this thread: 1 (In chronological order)
If done intuitively, it shouldn't present any difficulties.
This situation matches the guidance at
Which was written in colaboration with various members of the ARIA Working Group when it was written.
Some parts of the tutorial are a bit dated now, but when ARIA 1.1 becomes spec I'll be revamping all of this to conform with the updated information.
All the best,
Principle Accessibility Architect
Level Access, Inc.
= EMAIL ADDRESS REMOVED =
From: WebAIM-Forum < = EMAIL ADDRESS REMOVED = > On Behalf Of Isabel Holdsworth
Sent: Monday, November 12, 2018 3:41 AM
To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
Subject: Re: [WebAIM] Accessible dragon drop component? â some questions
Ah, but what if there's more than one drop zone? We had a scenario just last week where there were I think 5 possible drop zones. The only way I could think to make that one work was by presenting a menu of possible drop zones when the draggable item was activated. This works well using a keyboard, but I wonder if using such a different paradigm could make things confusing for sighted keyboard users.
On 09/11/2018, Sonja Weckenmann < = EMAIL ADDRESS REMOVED = > wrote:
> Ok, thanks to all of you for your support!
> All the best,
> Am 09.11.2018 um 17:35 schrieb Bryan Garaventa:
>> The following article may be of help, it identifies common concerns
>> and best practices regarding accessible drag and drop.
>> All the best,
>> Bryan Garaventa
>> Principle Accessibility Architect
>> Level Access, Inc.
>> = EMAIL ADDRESS REMOVED =
>> 415.624.2709 (o)
>> -----Original Message-----
>> From: WebAIM-Forum < = EMAIL ADDRESS REMOVED = > On Behalf
>> Of Sonja Weckenmann
>> Sent: Friday, November 09, 2018 3:50 AM
>> To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
>> Subject: [WebAIM] Accessible dragon drop component? â some questions
>> I am looking for an accessible dragon drop example/implementation to
>> recommend. I have come across this one:
>> I think the first one using the "reorder"-button works quite well,
>> but I would prefer if the reorder button would work with space and
>> enter, do you agree? (In this example for FF only Enter works).
>> The grab-buttons are all aria-describedby a very long help text. This
>> gets announced after every movement. An aria-label or aria-labelledby
>> set on the ul wouldnât be announce, would it?
>> A also would prefer if the screen reader would be automatically set
>> in focus mode so that the message (and action) "Ensure screen reader
>> is in focus mode" would be superfluous Would it be a good idea to
>> recommend using role="application"? What would be the right place?
>> The section-Element? To an additional div?
>> I would appreciate any help or best practice recommendations.
>> Thanks, Sonja
> BITV-Test | BIK fÃ¼r Alle
> DIAS GmbH
> HaubachstraÃe 72, D - 22765 Hamburg
> Tel: +49 40 43 18 75 18
> Fax: +49 40 43 18 75 34
> E-Mail: = EMAIL ADDRESS REMOVED =
> www.bitvtest.de | www.bik-fÃ¼r-alle.de | www.dias.de
> Twitter: @bitvtest
> > > archives at http://webaim.org/discussion/archives