W3C home > Mailing lists > Public > public-html@w3.org > August 2008

RE: question about the draft:

From: T.V Raman <raman@google.com>
Date: Wed, 6 Aug 2008 10:23:49 -0700
Message-ID: <18585.56869.66819.330290@retriever.corp.google.com>
To: j_james@mindspring.com
Cc: ian@hixie.ch, P.Taylor@Rhul.Ac.Uk, public-html@w3.org

For the record, I've been successfully using CSSclassnames --
both the semantic and the nonce kind -- to provide myself
 (and others) intelligent spoken output and content filtering --

Justin James writes:
 > 
 > 
 > 
 > > -----Original Message-----
 > > From: public-html-request@w3.org [mailto:public-html-request@w3.org] On
 > > Behalf Of Ian Hickson
 > > Sent: Monday, August 04, 2008 8:32 PM
 > > To: Philip Taylor (Webmaster, Ret'd)
 > > Cc: public-html@w3.org
 > > Subject: Re: question about the draft:
 > > 
 > > > If this assertion is true, why do you need "an appropriate HTML
 > > element"
 > > > when you can create a nonce-element using the very techniques you
 > > have
 > > > proposed ?
 > > 
 > > A "nonce-element" doesn't help screen readers. Screen readers only know
 > > real HTML elements, they don't know about the inventions of the author.
 > > Extensibility solutions don't help accessibility.
 > 
 > They do, *if* we provide a mechanism to tie semantics/accessibility to the
 > class.
 > 
 > J.Ja
 > 

-- 
Best Regards,
--raman

Title:  Research Scientist      
Email:  raman@google.com
WWW:    http://emacspeak.sf.net/raman/
Google: tv+raman 
GTalk:  raman@google.com, tv.raman.tv@gmail.com
PGP:    http://emacspeak.sf.net/raman/raman-almaden.asc
Received on Wednesday, 6 August 2008 17:24:44 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:16:21 GMT