W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > April to June 2006

FW: References to WCAG 1.0 in UAAG and UAAG Techniques

From: Jim Allan <jimallan@tsbvi.edu>
Date: Thu, 20 Apr 2006 13:09:11 -0500
To: WAU-ua <w3c-wai-ua@w3.org>
Message-id: <HDEAKIPKOHBCMDILOOPNKEGFFNAB.jimallan@tsbvi.edu>
-----Original Message-----
From: Jan Richards [mailto:jan.richards@utoronto.ca]
Sent: Tuesday, April 18, 2006 3:09 PM
To: Jim Allan
Subject: Re: References to WCAG 1.0 in UAAG and UAAG Techniques


Hi Jim,

Before I spend a ton of time going off in a different direction, I 
wanted to run some ideas past you...

It seems to me that there are three possible relationships between WCAG 
success criteria (the only normative things in WCAG) and the UAAG 
requirements:

1. UAAG reqs that replace WCAG reqs (i.e. if this in the baseline UA 
then WCAG success criteria can be waived) = "Replaces WCAG"

2. UAAG reqs that support WCAG reqs (i.e. these must be in baseline UA 
for that WCAG success criteria to be used) = "Supports WCAG"

3. UAAG reqs that extend WCAG reqs (i.e. no real effect on WCAG success 
criteria) = "Bonus for WCAG"

(I have started marking them in the doc - but am not even close to being 
done)

SO WHAT?

Maybe we can recommend that the WCAG baseline include a UAAG conformance 
profile.
- If the profile missed any UAAG reqs that act as supports (2-Support 
WCAG) then those WCAG success criteria couldn't be used in a WCAG 
conformance claim.
- If on the other hand the profile contained UAAG reqs that act as 
replacements (1-Replaces WCAG), then the WCAG conformance claim could 
lock in those WCAG success criteria in as if done.


Thoughts?

Cheers,
Jan



Jim Allan wrote:
> As per my task. Below is a list of direct references to WCAG 1.0 in  UAAG
> 1.0
> [http://www.w3.org/TR/2002/REC-UAAG10-20021217/uaag10.html]
> and the UAAG Techniques document
> [http://www.w3.org/TR/UAAG10-TECHS/guidelines.html]
> 
> UAAG 1.0
> 
> Section 1.1 Relation to WAI accessibility guidelines
> Guideline 2
> Checkpoints
> 	2.3 Render conditional content (P1)
> 	2.8 No repair text (P3)
> 	4.4 Slow multimedia (P1)
> 	7.3 Respect operating environment conventions (P2)
> 	8.1 Implement accessibility features (P1)
> 	8.2 Conform to specifications (P2)
> 	12.1 Provide accessible documentation (P1)
> Section 3. Conformance
> Section 4. Glossary
> 
> UAAG Techniques
> Checkpoints
> 	2.1 Render content according to specification (P1)
> 	2.3 Render conditional content (P1)
> 	2.7 Repair missing content (P2)
> 	2.8 No repair text (P3)
> 	4.4 Slow multimedia (P1)
> 	7.3 Respect operating environment conventions (P2)
> 	8.1 Implement accessibility features (P1)
> 	8.2 Conform to specifications (P2)
> 	12.1 Provide accessible documentation (P1)
> 
> Jim Allan, Webmaster & Statewide Technical Support Specialist
> Texas School for the Blind and Visually Impaired
> 1100 W. 45th St., Austin, Texas 78756
> voice 512.206.9315    fax: 512.206.9264  http://www.tsbvi.edu/
> ---> Share to Win!! <---
> 

-- 
Jan Richards, M.Sc.
User Interface Design Specialist
Adaptive Technology Resource Centre (ATRC)
Faculty of Information Studies
University of Toronto

   Email: jan.richards@utoronto.ca
   Web:   http://jan.atrc.utoronto.ca
   Phone: 416-946-7060
   Fax:   416-971-2896




Received on Thursday, 20 April 2006 18:06:12 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 06:51:34 GMT