This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 17807 - draggable and dropzone regions require labels
Summary: draggable and dropzone regions require labels
Status: RESOLVED FIXED
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-18 06:52 UTC by contributor
Modified: 2012-09-16 03:27 UTC (History)
4 users (show)

See Also:


Attachments

Description contributor 2012-07-18 06:52:30 UTC
This was was cloned from bug 15193 as part of operation convergence.
Originally filed: 2011-12-15 00:29:00 +0000
Original reporter: Everett Zufelt <everett@zufelt.ca>

================================================================================
 #0   Everett Zufelt                                  2011-12-15 00:29:49 +0000 
--------------------------------------------------------------------------------
There is, in the dnd API spec, no method of associating a textual label with @draggable
and @dropzone elements.  This can obviously be done with aria-label, aria-labelledby, or <label for="idref">. Should this be part of the API spec?  It
is essential for accessibility that drag and drop targets have a textual label associated in order to conform with WCAG 2.0.

I suggest that text be added to the API directing implementers how to provide accessible names for draggable and dropzone regions.
================================================================================
 #1   Ian 'Hixie' Hickson                             2012-01-28 21:59:39 +0000 
--------------------------------------------------------------------------------
What do you mean by API? Do you mean the DOM interface?

What's wrong with using title="" here?
================================================================================
 #2   Everett Zufelt                                  2012-01-29 12:02:18 +0000 
--------------------------------------------------------------------------------
Sure, we can use title, let's make sure that the spec (somewhere relevant) states that @title * must * be used to provide accessible names to draggable and dropzone elements.
================================================================================
 #3   Ian 'Hixie' Hickson                             2012-02-01 00:02:18 +0000 
--------------------------------------------------------------------------------
Why? What problem is this solving?
================================================================================
 #4   Everett Zufelt                                  2012-02-01 12:50:17 +0000 
--------------------------------------------------------------------------------
WCAG 2.0 SC 4.1.2 requires that the name for all interactive elements be programmatically determinable. I really don't care what you do in the spec, but pick one method that authors ought to use to specify the name for draggable and dropzon elements.

If this already clearly exists in the spec then please point that out.
================================================================================
Comment 1 contributor 2012-09-16 03:27:31 UTC
Checked in as WHATWG revision r7359.
Check-in comment: Try to address some possible concerns re dropzone and draggable for ATs.
http://html5.org/tools/web-apps-tracker?from=7358&to=7359