[whatwg] Accessibility for Drag and Drop
ian at hixie.ch
Wed Aug 12 01:42:48 PDT 2009
On Mon, 3 Aug 2009, Aron Spohr wrote:
> It's the same case here. Just like with "'a' elements that have an href
> attribute" we should also add "elements that have a draggable attribute
> set to true" to the list of elements that "should be made focusable by
> the user agent" at the bottom of section 7.5.1 of the spec.
Fair enough. Added.
> Btw. there is no information on what criteria the qualification is made
> for the elements in that "should" list in the spec. Maybe that should be
> added as well.
I don't know what the qualifications would be. That's why it's a "should"
and not a "must" with explicit exceptions.
> > The user agent can actually find where drops can occur by just acting
> > as if the user had tried to drop everywhere. I'm not really sure how
> > we could make an attribute work for this, since the model allows any
> > element to be a drop target already.
> Fair enough. I thought it might come in handy some day to identify both
> draggable elements as well as elements that can "receive" drops without
> the use of scripting. E.g. in a parser or for search spiders to creater
> indexes for that faster...
I don't disagree in principle, I just don't see how it could work given
the model we have.
Ian Hickson U+1047E )\._.,--....,'``. fL
http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
More information about the whatwg