Re: css abuse

Briefly, the area under discussion has to do with class tokens that are
applied to elements in the HTML markup.

The DOM core requirements will expose these values because they are
attributes.  So the API requirement to share the document contents in
accordance with the W3C DOM means AT software has access to these through
this API.  

The part I am vague about is how the guideline that the browser through its
own UI should give the user access to all content is being interpreted as
regards CLASS tokens.  IMHO they should be covered; the CLASS tokens are
metadata and I am arguing that authors should set them in a mnemonic
fashion as well as eventually tie them to schemata for more precise
machine-processable definitions.  

This is just an intro; please glance over the thread on w3c-wai-er-ig in
the archives. Use "css abuse" in the subject to find the thread.

Al

At 10:22 AM 10/4/99 -0400, Ian Jacobs wrote:
>Al Gilman wrote:
>> 
>> At 09:17 PM 10/3/99 -0400, Leonard R. Kasday wrote:
>> >
>> >>And yes, a UAGL-conforming user agent not only has access to these
>> >>attribute values, but makes them available to the user and to add-on
>> >>assistive technologies.
>> >
>> >I think we'll have to coordinate with the Guideline and Authoring
groups to
>> >make that point explicit.
>> >
>> >I can't find any explicit mention of CLASS name being readable in the user
>> >agent guidelines or the web content guidelines.
>> 
>> Talk to Jon or Ian about where the drafts and issues are.  They are
>> wrestling with how to make the guideline transcend HTML and yet make the
>> checkpoints clear.
>
>Could you please describe the requirement?
> 
> - Ian
>

Received on Monday, 4 October 1999 12:28:22 UTC