Re: comments on guidelines

"Leonard R. Kasday" wrote:
> 
> My comments on your comments preceded by LRK2::
> 
> >
> > >  > Guideline 4. Ensure user control over styles
> > >
> > > LRK: IMPORTANT
> > > Authors can associate a meaning with a style (e.g. "new", "sale",
> > > "obsolete"), but there is presently no standard way to specify what it
> > > is.  As a workaround, the UA should give access to the name of the
> > > style.
> >
> >This is probably covered by 2.1: ensure access to all content.
> 
> LRK2: First, let me correct what I said:  I really meant names of classes.
> 
> This was discussed in the Sept and October wai-er-ig archives under "CSS
> abuse". It may be true that technically speaking class names are required
> to be accessible, although I'm having trouble seeing that.
> 
> However, at best, most readers will miss that.    2.1 talks about
> "alternative equivalents for content".   Hence it is talking about
> alternatives to what a sighted user sees, or what a hearing person hears,
> but doesn't address alternatives to things that nobody normally sees or
> hears.  For example, sighted users don't see image filenames.  Hence, 2.1
> doesn't require agents to provide alternative representations of image
> filenames.  Similarly, users don't see names of classes. So 2.1 doesn't
> seem to require alternatives here either.
> 
> Therefore I think this has to be an explicit requirement or few if any
> implementors will do it.

Added as a proposal (Issue 154)
http://cmos-eng.rehab.uiuc.edu/ua-issues/issues-linear.html#154

 - Ian

-- 
Ian Jacobs (jacobs@w3.org)   http://www.w3.org/People/Jacobs
Tel/Fax:                     +1 212 684-1814
Cell:                        +1 917 450-8783

Received on Saturday, 4 December 1999 12:45:35 UTC