W3C home > Mailing lists > Public > www-style@w3.org > December 2012

Re: CSS issue: Need control of what is perceived by which technologies

From: Antony Kennedy <antony@silversquid.com>
Date: Fri, 7 Dec 2012 13:57:12 +0000
Cc: "Tab Atkins Jr." <jackalmage@gmail.com>, www-style list <www-style@w3.org>
Message-Id: <980FC996-A723-43E1-A8B2-3B264D6CA8D1@silversquid.com>
To: James Craig <jcraig@apple.com>
>> If this were true, then "speech" media would be completely useless.  I
>> believe browsers can tell when a page is being read by AT, and can
>> provide customized information for it.  (I could be wrong, though...)


At the moment, the "speech" media *is* completely useless. I don't know of a single ScreenReader that pays attention to it. Am I mistaken?

If so, please let me know how I can achieve what I'm after with a real world example.

On 26 Nov 2012, at 20:08, James Craig <jcraig@apple.com> wrote:

> On Nov 26, 2012, at 10:01 AM, Tab Atkins Jr. <jackalmage@gmail.com> wrote:
> 
>> On Mon, Nov 19, 2012 at 2:58 AM, Antony Kennedy <antony@silversquid.com> wrote:
>>> Is this something that can be sensibly achieved with media queries?  @media
>>> not speech and  @media speech seem like they should work great here.
>>> However, the screen reader attaches to the output of the browser (what the
>>> browser sends via Operating System APIs) and not the browser itself, so when
>>> the browser is parsing the CSS it never understands to expose or not expose
>>> these pieces. aria attributes work correctly here though, so there must be a
>>> solution!
>> 
>> If this were true, then "speech" media would be completely useless.  I
>> believe browsers can tell when a page is being read by AT, and can
>> provide customized information for it.  (I could be wrong, though...)
> 
> 
> AT is a broad term and browsers cannot detect all forms, though providing customized information on a per-AT case is usually unnecessary. 
> 
> I don't think a new "perceivable" property is necessary here, because I believe the @media type query fits well here:
> 
> 	element::before { content: ":"; }
> 	@media speech or reader { element::before { content: ""; } }
> 
> In this case, the UA should just not expose the text contents of the pseudo-element to the accessibility API, or mark it in the API as decorative or otherwise hidden.
> 
> I think what Antony is requesting is that the CSS spec should state something explicit to that effect.
> 
> James
> 
> 
Received on Friday, 7 December 2012 13:57:42 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:21:03 GMT