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

Re: RE: Proposal for 1.3, "Ensure that information, functionality, and structure are separable from presentation"

From: <lguarino@adobe.com>
Date: Mon, 02 May 2005 16:18:33 -0700
To: Tim Boland <frederick.boland@nist.gov>
Cc: w3c-wai-gl@w3.org
Message-id: <1718c2173602.1736021718c2@adobe.com>

> In CSS2.1, content may be generated by two mechanisms:
> 
> (a) the "content" property (in conjunction with the :before and 
> :after pseudo-elements)
> 
> (b) elements with a value of "list-item" for the "display" property
> 
> How are such mechanisms to be treated in WCAG2.0?   More 
specifically, 
> is the use of such mechanisms to be encouraged or merely tolerated 
in 
> the context of web content accessibility?

I wonder if we need an additional success criterion for GL 2.4:
<proposal>
Chnages to content, structure or relationships within the content can 
be programmatically determined.
</proposal>

I'm not sure that "programmatically determined" is the right phrase 
here. But if applying a CSS style sheet or, especially, if changing a 
style sheet changes the information that is programmatically available 
to the user agent, there needs to be some sort of notification that 
things have changed. This also seems relevant to scripting issues.

Loretta
Received on Monday, 2 May 2005 23:18:43 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 23:39:37 UTC