Sorry to see that you have been also spammed by some jerk. I have received
11 e-mails spam from 

different people who were contacted by the same "Group".

 

Some person, if one would call them that has done it to us all. I have
another word for them. Spammers.

It is unfortunate that some people have nothing constructive to do with
their lives except raise hell.

 

I sent a question to a forum at Web Standards Group but I am not Christian
nor is that related to my question.

 

Houstin

 

  _____  

From: [email protected] [mailto:[email protected]] On
Behalf Of Chabot, Elliot
Sent: Wednesday, January 13, 2010 4:30 PM
To: [email protected]
Subject: RE: [WSG] AAA Accessibility and validation

 

The requirement for validation in WCAG 1.0 is contained in checkpoint 3.2,
<http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-identify-grammar>
http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-identify-grammar.   

Incidentally, checkpoint 3.2 is a requirement for Double-A conformance in
WCAG 1.0.

Elliot Chabot

Web Solutions Branch

House Information Resources

U.S. House of Representatives

http://www.house.gov 

-----Original Message-----
From: [email protected] [mailto:[email protected]] On
Behalf Of David Dorward
Sent: Wednesday, January 13, 2010 7:46 AM
To: [email protected]
Subject: Re: [WSG] AAA Accessibility and validation

 

On 13 Jan 2010, at 04:02, [email protected] wrote:

> Now, this Accessibility Appendix lists CSS validation (point 3) as a
required attribute for compliance.

No, it doesn't. The document says, under conformance:

        . Conformance Level "Triple-A": all Priority 1, 2, and 3 checkpoints
are satisfied;

Appendix A doesn't list any checkpoints.

> I guess my question is: Do IE-related CSS hacks cause a document to fail
AAA (or A/AA for that matter) Accessibility compliance?

Maybe and no. There are IE-related CSS hacks that are valid, and others that
are not.

The valid ones don't cause it to fail any checkpoint, as far as I know.

Guideline 3 says "Use markup and style sheets and do so properly" and you
could make a case that invalid CSS is not "using style sheets properly".

Checkpoint 3.2 says "Create documents that validate to published formal
grammars.", but it can be argued that a style sheet is not a document.

Meanwhile, WCAG 2.0 makes no requirement that CSS be valid (and when refers
to 'markup' rather than 'documents').

-- 

David Dorward

http://dorward.me.uk

 

*******************************************************************

List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm

Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm

Help: [email protected]

*******************************************************************


*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [email protected]
*******************************************************************


*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [email protected]
*******************************************************************

Reply via email to