W3C home > Mailing lists > Public > www-style@w3.org > January 2011

RE: [css3-speech] ISSUE-153 speak: none; usage incompatible with other values of speak

From: Belov, Charles <Charles.Belov@sfmta.com>
Date: Mon, 24 Jan 2011 12:45:30 -0800
Message-ID: <E17F75B6E86AE842A57B4534F82D03769C35D9@MTAMAIL.muni.sfgov.org>
To: "Daniel Weck" <daniel.weck@gmail.com>
Cc: <www-style@w3.org>, "fantasai" <fantasai.lists@inkedblade.net>


 

Daniel Weck [mailto:daniel.weck@gmail.com] wrote on Monday, January 24,
2011 12:05 PM
> 
> Charles wrote:
> > http://www.w3.org/TR/WCAG20/#text-equiv
> > states:
> >
> > 1.1.1 Non-text Content: All non-text content that is 
> presented to the 
> > user has a text alternative that serves the equivalent 
> purpose, except 
> > for the situations listed below. (Level A) ...
> > Decoration, Formatting, Invisible: If non-text content is pure 
> > decoration, is used only for visual formatting, or is not 
> presented to 
> > users, then it is implemented in a way that it can be ignored by 
> > assistive technology.
> >
> > speak:none (or speakability:none as Fantasai suggested) would allow 
> > exclusion of such displayed content from being read aloud.
> 
> 
> Thanks Charles. Obviously I totally agree on the principle, 
> but I was making a point about the way this can be achieved. 
> My impression was (and still is, although I am not adamant, I 
> just have a strong
> preference) that "display:none" could also be set in an aural 
> style sheet to achieve the most suitable presentation for a 
> screen-reader user (by effectively overriding the main 
> "visual" styles). I do appreciate the point about separating 
> "display" and "speakability"  
> aspects though, which has benefits beyond the mere purist 
> satisfaction. I will explore Fantasai's suggestion. Any other 
> thoughts welcome! Regards, Daniel

If it's any help, my concern would be that using display:none to achieve
this would require that the aural styles be in a separate style sheet
from the visual styles.  Perhaps there are other reasons that this would
be desirable.   On the other hand, there are those out there who are
trying to get us to reduce the number of separate HTTP requests to load
a single Web page, and requiring the aural styles to be in a separate
style sheet would be at odds with this (although my personal concern is
maintainability; it also feels like a semantic change for display,
although now that I think about it, it probably isn't).

Hope this helps,
Charles Belov
SFMTA Webmaster
Received on Monday, 24 January 2011 23:29:39 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:36 GMT