[ac] (0) Try to address some possible concerns re dropzone and dragga…

…ble for ATs. Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=17807 Affected topics: HTML git-svn-id: http://svn.whatwg.org/webapps@7359 340c8d12-0b0e-0410-8428-c7bf67bfef74
whatwg · Sep 16, 2012 · 50bbda4 · 50bbda4
1 parent 231a7af
commit 50bbda4
Show file tree

Hide file tree

Showing 3 changed files with 60 additions and 0 deletions.
diff --git a/complete.html b/complete.html
@@ -81011,6 +81011,17 @@ <h4 id=the-draggable-attribute><span class=secno>8.7.7 </span>The <dfn title=att
   <i>false</i> state means that it is not. The <i>auto</i> state
   uses the default behavior of the user agent.</p>
 
+  <p>An element with a <code title=attr-draggable><a href=#the-draggable-attribute>draggable</a></code>
+  attribute should also have a <code title=attr-title><a href=#attr-title>title</a></code>
+  attribute that names the element for the purpose of non-visual
+  interactions. <!-- "should", not "must", only because this is a
+  relatively new attribute and its design implications are not
+  entirely obvious yet. For example, what happens if you use an
+  element with text as a drag source? Is that sufficiently clear for
+  ATs? Indeed, shouldn't the element generally be distinguishable
+  anyway for it to be useful to drag? See also the dropzone attribute.
+  --></p>
+
   <dl class=domintro><dt><var title="">element</var> . <code title=dom-draggable><a href=#dom-draggable>draggable</a></code> [ = <var title="">value</var> ]</dt>
 
    <dd>
@@ -81125,6 +81136,15 @@ <h4 id=the-dropzone-attribute><span class=secno>8.7.8 </span>The <dfn title=attr
   specified, the <code title=attr-dropzone-copy><a href=#attr-dropzone-copy>copy</a></code> value is
   implied.</p>
 
+  <p>An element with a <code title=attr-dropzone><a href=#the-dropzone-attribute>dropzone</a></code>
+  attribute should also have a <code title=attr-title><a href=#attr-title>title</a></code>
+  attribute that names the element for the purpose of non-visual
+  interactions. <!-- "should", not "must", only because this is a
+  relatively new attribute and its design implications are not
+  entirely obvious yet. For example, what happens if you use an
+  element with text as a drop zone? Is that sufficiently clear for
+  ATs? See also the draggable attribute. --></p>
+
   <div class=impl>
 
   <p>A <code title=attr-dropzone><a href=#the-dropzone-attribute>dropzone</a></code> attribute <dfn id=concept-dropzone-match title=concept-dropzone-match>matches a drag data store</dfn> if

diff --git a/index b/index
@@ -81011,6 +81011,17 @@ dictionary <dfn id=drageventinit>DragEventInit</dfn> : <a href=#mouseeventinit>M
   <i>false</i> state means that it is not. The <i>auto</i> state
   uses the default behavior of the user agent.</p>
 
+  <p>An element with a <code title=attr-draggable><a href=#the-draggable-attribute>draggable</a></code>
+  attribute should also have a <code title=attr-title><a href=#attr-title>title</a></code>
+  attribute that names the element for the purpose of non-visual
+  interactions. <!-- "should", not "must", only because this is a
+  relatively new attribute and its design implications are not
+  entirely obvious yet. For example, what happens if you use an
+  element with text as a drag source? Is that sufficiently clear for
+  ATs? Indeed, shouldn't the element generally be distinguishable
+  anyway for it to be useful to drag? See also the dropzone attribute.
+  --></p>
+
   <dl class=domintro><dt><var title="">element</var> . <code title=dom-draggable><a href=#dom-draggable>draggable</a></code> [ = <var title="">value</var> ]</dt>
 
    <dd>
@@ -81125,6 +81136,15 @@ dictionary <dfn id=drageventinit>DragEventInit</dfn> : <a href=#mouseeventinit>M
   specified, the <code title=attr-dropzone-copy><a href=#attr-dropzone-copy>copy</a></code> value is
   implied.</p>
 
+  <p>An element with a <code title=attr-dropzone><a href=#the-dropzone-attribute>dropzone</a></code>
+  attribute should also have a <code title=attr-title><a href=#attr-title>title</a></code>
+  attribute that names the element for the purpose of non-visual
+  interactions. <!-- "should", not "must", only because this is a
+  relatively new attribute and its design implications are not
+  entirely obvious yet. For example, what happens if you use an
+  element with text as a drop zone? Is that sufficiently clear for
+  ATs? See also the draggable attribute. --></p>
+
   <div class=impl>
 
   <p>A <code title=attr-dropzone><a href=#the-dropzone-attribute>dropzone</a></code> attribute <dfn id=concept-dropzone-match title=concept-dropzone-match>matches a drag data store</dfn> if

diff --git a/source b/source
@@ -94735,6 +94735,17 @@ dictionary <dfn>DragEventInit</dfn> : <span>MouseEventInit</span> {
   <i>false</i> state means that it is not. The <i>auto</i> state
   uses the default behavior of the user agent.</p>
 
+  <p>An element with a <code title="attr-draggable">draggable</code>
+  attribute should also have a <code title="attr-title">title</code>
+  attribute that names the element for the purpose of non-visual
+  interactions. <!-- "should", not "must", only because this is a
+  relatively new attribute and its design implications are not
+  entirely obvious yet. For example, what happens if you use an
+  element with text as a drag source? Is that sufficiently clear for
+  ATs? Indeed, shouldn't the element generally be distinguishable
+  anyway for it to be useful to drag? See also the dropzone attribute.
+  --></p>
+
   <dl class="domintro">
 
    <dt><var title="">element</var> . <code title="dom-draggable">draggable</code> [ = <var title="">value</var> ]</dt>
@@ -94872,6 +94883,15 @@ dictionary <dfn>DragEventInit</dfn> : <span>MouseEventInit</span> {
   specified, the <code title="attr-dropzone-copy">copy</code> value is
   implied.</p>
 
+  <p>An element with a <code title="attr-dropzone">dropzone</code>
+  attribute should also have a <code title="attr-title">title</code>
+  attribute that names the element for the purpose of non-visual
+  interactions. <!-- "should", not "must", only because this is a
+  relatively new attribute and its design implications are not
+  entirely obvious yet. For example, what happens if you use an
+  element with text as a drop zone? Is that sufficiently clear for
+  ATs? See also the draggable attribute. --></p>
+
   <div class="impl">
 
   <p>A <code title="attr-dropzone">dropzone</code> attribute <dfn