W3C home > Mailing lists > Public > w3c-wai-eo@w3.org > July to September 2009

Re: There are problems for assistive technologies interpreting accessibility beta.w3.org

From: Shawn Henry <shawn@w3.org>
Date: Thu, 20 Aug 2009 15:09:10 -0500
Message-ID: <4A8DAD66.7020109@w3.org>
To: Wayne Dick <wed@csulb.edu>
CC: EOWG <w3c-wai-eo@w3.org>
Hi Wayne,

It was a problem of a missing </q>. Fixed now.

Best,
~Shawn

Wayne Dick wrote:
> If you remove style, there are quotes everywhere.  I think we are using 
> the <q> element in ways that cannot be determined pro programmatically.  
> In some style sheet the page must have a direction to render <q> </q> 
> with a quote character of space or null. Why?
> 
> The document seems to use this element to designate something different 
> from quotation.
> 
> I think that violates WCAG 2. Having a quote element present as space or 
> null expresses meaning in a way that depends on visual presentation, 
> because the meaning of spaces and nulls is ambiguous.
> 
> I found this stuff trying to read the page.
> 
> Wayne
> 
> 
> 
> 
> 
Received on Thursday, 20 August 2009 20:09:22 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 20 August 2009 20:09:22 GMT