> Andreas Boehmer [Addictive Media] > to be accessible the site doesn't necessarily have to look great, but at least the content should show up in all browsers, even the old ones, right?
Well, just talking WCAG 2, the requirement would be to use accessibility-supported technologies (see http://www.w3.org/TR/WCAG20/#cc4 and http://www.w3.org/TR/WCAG20/#accessibility-supporteddef). This does not, however, take into account - or make any special requirement/concession to - potential browser bugs (as seems to be the case with what you're mentioning regarding IE5 not showing anything) or user agents which do not themselves conform or wrongly implement those technologies. > I went through WCAG 1 and WCAG 2, and I expected an appropriate guideline to show up under Priority 1 (or Level A), but nothing. Or am I missing something in the obscure wording of the document that is WCAG? WCAG's primary concern is to ensure accessibility for users with disabilities, not universal access on all devices, operating systems, user preferences, etc. Having said that, I'd say that regardless of WCAG or not, it would be best practice to try and work around browser bugs - particularly if there's evidence that the site does still have a sizeable portion of users coming in with IE5, making it a financially viable proposition. As a last resort, you *could* implement some specific conditional comments for version 5, for instance. P ________________________________ Patrick H. Lauke Web Editor Enterprise & Development University of Salford Room 113, Faraday House Salford, Greater Manchester M5 4WT UK T +44 (0) 161 295 4779 [email protected] www.salford.ac.uk A GREATER MANCHESTER UNIVERSITY ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [email protected] *******************************************************************
