W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > April to June 2004

RE: Access Key alternative -in the wrong place?

From: Lisa Seeman <seeman@netvision.net.il>
Date: Thu, 24 Jun 2004 16:10:56 +0300
To: 'Andy Heath' <a.k.heath@shu.ac.uk>
Cc: w3c-wai-gl@w3.org
Message-id: <01a201c459ec$b2db58d0$340aa8c0@lisaibm>

> I would argue that different kinds of Meta-data serving 
> different purposes needs treating differently. 

agreed

For example, 
> some needs attaching to the page, treating the page as an 
> object.  Some (as in the example that was given here) needs 
> treating differently for different contexts and to attach it 
> to the leaves is not to provide the required flexibility.
hmmmm, why am I attaching it to the leaves- 

attach it to the node, override at the leaves if you need to 
  
> There are also worlds outside of html to consider in the model.
yes

> I'm all in favor of an intermediate stage such as using
> EARL for tools output for some kinds of property.
you are loading me hear, Earl, as I understand it, gives you away to
report conformance.
we are talking about supplying role information, titles and description
at the node level -I don't see Earls application hear.
Dublin core can do the description and title bit, for the rest another
RDF language could do the trick -hold on, one comes to mind, ... what
was it's name again?

Keep well
Lisa
> 
> 
> 
> 
> 
> >>-----Original Message-----
> >>From: w3c-wai-gl-request@w3.org
> >>[mailto:w3c-wai-gl-request@w3.org] On Behalf Of Andy Heath
> >>Sent: Thursday, June 24, 2004 11:09 AM
> >>To: w3c-wai-gl@w3.org
> >>Subject: Re: Access Key alternative -in the wrong place?
> >>
> >>
> >>
> >>
> >>
> >>>Now why can't we attach DC metadata title  and description
> >>
> >>onto all
> >>
> >>>image files in place of filling in an alt and longdesc when
> >>
> >>ever the
> >>
> >>>images are used. (alt can override the meta title if the
> >>
> >>web author is
> >>
> >>>using an image/media in a different way to how the graphic artist
> >>>anticipated the image being used)
> >>>
> >>>That is why we need to design accessibility solutions from an
> >>>architectural level, and not from the html content symptom solving 
> >>>thing
> >>
> >>I agree.  An over-arching architectural framework is required
> >>otherwise its just ramdom wandering in a very large search 
> >>space. Nodes first then leaves.
> >>
> >>andy
> >>
> >>--
> >>andy
> >>_______________________________________________
> >>Andy Heath
> >>a.k.heath@shu.ac.uk
> >>
> >>
> > 
> > 
> > 
> > 
> 
> 
> -- 
> andy
> _______________________________________________
> Andy Heath
> a.k.heath@shu.ac.uk
> 
> 
Received on Thursday, 24 June 2004 09:11:01 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:30 GMT