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

RE: CSS Accessibility Analyzer

From: Yvette P. Hoitink <y.p.hoitink@heritas.nl>
Date: Mon, 16 Feb 2004 20:06:19 +0100
To: "'Michael Cooper'" <michaelc@watchfire.com>, "'WAI WCAG List'" <w3c-wai-gl@w3.org>
Message-Id: <E1Aso4S-0003pI-EZ@smtp2.home.nl>

> Michael Cooper: 
> 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." 

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. 

Yvette Hoitink
CEO Heritas, Enschede, The Netherlands
E-mail: y.p.hoitink@heritas.nl
Received on Monday, 16 February 2004 14:06:22 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 21:07:33 UTC