W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > January to March 2004

RE: CSS Accessibility Analyzer

From: Michael Cooper <michaelc@watchfire.com>
Date: Mon, 16 Feb 2004 16:11:54 -0500
Message-ID: <D9ABD8212AFB094C855045AD80FB40DD033FB56C@1wfmail.watchfire.com>
To: 'WAI WCAG List' <w3c-wai-gl@w3.org>

I agree - I greatly dislike the practice of tuning Web sites to particular
browsers and don't want to be seen as encouraging that. With Techniques,
though, we've been faced with a couple difficult questions:

* What happens if one technique is required for optimal functionality in
browser A and a different technique is required for browser B, and it's
impossible to apply both techniques at the same time?

* What generation of browsers do we write techniques for? A lot of WCAG 1.0
itself was written for problems of the current generation of browsers - the
famous "until user agent" issues. 

* What if one technique is required for or supported by one widely used
browser, but not required for or supported by another widely used browser?

These issues are why we associated user agent information with the
techniques. It does not ultimately answer the question of what techniques to
apply, it simply gives a more complete set of information. I don't know if
WAI will be able to recommend a single universal set of content authoring
techniques that work as desired in all user agents currently in use. 

That's why, in the case of relative vs. absolute size, I think we have to
inventory the possibilities and the effects of each of those possibilities.

Michael

> -----Original Message-----
> From: Yvette P. Hoitink [mailto:y.p.hoitink@heritas.nl]
> Sent: Monday, February 16, 2004 2:06 PM
> To: Michael Cooper; 'WAI WCAG List'
> Subject: RE: CSS Accessibility Analyzer
> 
> 
> Personally, I utterly dislike the idea of tuning your website to the
> browsers you expect your audience uses. That's just one step 
> away from only
> supporting the market leader (read: Internet Explorer), a 
> practice which can
> be very bad for accessibility. If we encourage authors to 
> write only for
> browsers they expect, many of them will not take speech 
> browsers and other
> assistive technologies into consideration. 
> 
> To me, one of the key elements of web accessibility is that 
> you acknowledge
> you cannot know which user will visit your site, and you 
> create your website
> to be flexible and robust to meet the user's need. 
> 
Received on Monday, 16 February 2004 16:11:21 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 07:17:55 UTC