RE: CSS Accessibility Analyzer

Perhaps this issue will be addressed in part by an approach we are taking in
the techniques, which is, for each technique, we log the user agents for
which there is a known problem the technique addresses. So we could create a
technique that says, in effect, "If your target browser includes IE, the
author must use relative font sizes. If your target browser is only Opera,
the author can use absolute sizes and still be assured that the page will be
WCAG-compliant for the user." It is of course the author's responsibility to
be realistic about the browsers used by their audience and not try to use
this browser profiling as a way to wriggle out of the techniques, but a
level of good faith in implementors of our guidelines must be presumed at
some point. It is also of course probable that the set of browsers out there
will be larger than the set of browsers we have tested and aligned with our
techniques, but all we can do is our best at getting a good cross section,
and the techniques are easily updated if we become aware of a browser with
its own issues.

Michael

> -----Original Message-----
> From: John M Slatin [mailto:john_slatin@austin.utexas.edu]
> Sent: Monday, February 16, 2004 10:27 AM
> To: Yvette P. Hoitink; Roberto Scano - IWA/HWG; WAI WCAG List
> Subject: RE: CSS Accessibility Analyzer
> 
> 
> 
> I think Yvette's right; as Joe Clark has pointed out (often) in the
> past, the fact that IE won't allow users to enlarge fonts specified in
> px is primarily a user agent  problem, though for the time 
> being it has
> implications for content.  So the Techniques documents should
> acknowledge the problem and encourage use of relative sizes, while the
> user agent issue should be addressed as well.
>

Received on Monday, 16 February 2004 13:53:50 UTC