Nick Zoom:1 is not bad enough to warrant a conditional comment and separate style sheet. It's a valid rule that basically says show the screen at 100%. A user style sheet can still over-ride this rule. It's an easy way to add hasLayout without causing other issues. This is what Microsoft recommended when they introduced IE7 and there's not a strong reason to avoid it.
-----Original Message----- From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] On Behalf Of Nick Stone Sent: Wednesday, January 13, 2010 9:26 AM To: wsg@webstandardsgroup.org Subject: Re: [WSG] AAA Accessibility and validation Christian, You said you've been told to place IE specific rules in a separate sheet, but you don't mention why you haven't done so. In the example you provided, I'd do this: 1) move "zoom: 1" to your IE6 rule (and to IE7 rule if necessary) 2) place the IE6 and IE7 rules in an IE ONLY sheet 3) use a conditional comment to call the IE sheet Would that work? If so, please explain your reasons for not doing so. Here are the pros and cons I'm aware of. I'd be interested to hear others. Pros A) enables CSS validation B) avoids possible failure of automated accessibility test C) facilitates site maintenance (easy to find and modify IE specific rules) Con A) Delays initial page load by requiring additional call to the server Aloha, Nick Stone -- Nick Stone, MBA SEO & Web Accessibility || coding, writing & consulting boa...@nick-stone.com http://nick-stone.com/ 434-284-2840 c...@fagandesign.com.au wrote: > > > > From: <c...@fagandesign.com.au> > > I guess my question is: Do IE-related CSS hacks cause a document to > > fail AAA (or A/AA for that matter) Accessibility compliance? > > ------------------------------------------------------------ > > > > Hi Christian, > > > > If you mean things like zoom or even proprietary -Moz or -KHTML > > properties... no, that doesn't affect accessibility. Guidelines are > > subjective in that it's up to the site's owner to say whether or not > > his site is accessible after testing it against the various guidelines. > > The W3 validator is the issue. It should have been programmed years ago > > to ignore most, if not all, proprietary properties. > > > > -- > > Al Sparber - PVII > > http://www.projectseven.com > > Dreamweaver Menus | Galleries | Widgets > > http://www.projectseven.com/go/hgm > > The Ultimate Web 2.0 Carousel > > Specifically, I mean something like this > > .element {float:left;display:inline;zoom:1;margin-right:30px;} > * html .element {float:none;} /* IE6 */ > *+ html .element {float:right;} /* IE7 */ > > I've been told to put these IE specific attributes in a seperate IE > stylesheet in order to avoid validation errors that supposedly affect > the AAA Acessibility check. > > > ******************************************************************* > List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm > Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm > Help: memberh...@webstandardsgroup.org > ******************************************************************* ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ******************************************************************* ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org *******************************************************************
