W3C home > Mailing lists > Public > public-comments-wcag20@w3.org > July 2009

Your Posts to the public list

From: Gregg Vanderheiden <gv@trace.wisc.edu>
Date: Fri, 31 Jul 2009 09:10:23 -0500
Message-Id: <8024BFD2-B3AA-4B76-9C5B-1DA98F9439C4@trace.wisc.edu>
To: maffeonjr@yahoo.com
Cc: public-comments-wcag20@w3.org
Dear  N Maffeo

We have received a number of comments from you to the Public Comments  
list.	

Some of the comments you sent in are related to comments on the  
documents.   These we are processing and will send comments to back to  
you when we have time to review and respond to them (One is done and  
is below. The other one will follow when we get to it in queue).

Other comments you sent are not asking about the guidelines but are  
instead requests to comment on or advise you on aspects of pages you  
are writing.  We are not able to respond to these types of inquiries.

The WCAG Public Comments List is for public comments on the WCAG  
documents. Please use this public comment list only to submit errors,  
omissions, issues, or needed clarifications to the documents.  
Suggestions for new techniques should be submitted using the  
Techniques for WCAG 2.0 submission form.

Please note that the public list should not be used to ask questions  
about particular websites or implementation issues. We just don't have  
the ability to respond to these questions.  Questions about how to  
apply WCAG, or how to apply it to a particular page or site should be  
sent
        a) to one of the many consultants working in the area,
        b) to the WAI Interest Group (IG) mailing list (w3c-wai-ig@w3.org 
),
    or c) to one of the many other mailing lists and forums that focus  
on Web accessibility.

Some general comments that may be helpful to you.

1) NOTHING is required that is not specifically required in the WCAG  
2.0 Guidelines.

	- and in the WCAG 2.0 guidelines - the ONLY things required are the  
SUCCESS CRITERIA and the Conformance Requirements that you can find in  
the CONFORMANCE section of WCAG 2.0

2) TECHNIQUES  are NEVER required.      They as simply options that  
you may or may not use to meet the Success criterion in WCAG 2.0

3) Some techniques will conflict with other techniques.  Since neither  
is required this is not a problem.  If two techniques conflict - then  
don't use both.

4) Read the Understanding document carefully to understand the Success  
Criteria.

Thank you for your comments.  We will be responding to the ones that  
are suggesting changes to our documents (edits, errors or  
omissions).   Below are the items that do NOT fall in this category  
and that we are not in a position to address.

Thank You

Gregg and Loretta



YOUR COMMENTS ARE ALL LISTED BELOW  GROUPED INTO THREE CATEGORIES



1) WCAG Questions - Done
These are questions about the WCAG documents that we have answers for.  
And they are provided with each item.  In general however - questions  
are put in queue and will take some time to get to.  (see #3 below)


2) WCAG Questions -  Still in Queue
These are question about the WCAG documents that are in queue for  
discussion by the Working Group.    We will work on them in turn as we  
get to them.  Thank you for your comments.   We will let you know how  
they come out when they are processed.  It may take some time  
depending on other work items.
If you need quicker responses in order to do your work - please check  
with a consultant. They can probably help you to understand the  
guidelines while we work on making the language more understandable in  
our formal docs to be released later this year.

3) Consultant Questions
  These are questions that should be addressed to consultants.  They  
do not fall into the category of things we need to change in the next  
release of the WCAG support documents.



=====================
YOUR COMMENTS
=====================

=============================================================
1) WCAG Questions - Done
These are questions about the WCAG documents that we have answers for.  
And they are provided with each item.  In general however - questions  
are put in queue and will take some time to get to.  (see #3 below)

   From: N Maffeo <maffeonjr@yahoo.com>
Date: July 24, 2009 12:16:57 AM CDT
To: public-comments-wcag20@w3.org, gv@trace.wisc.edu
Subject: The techniques listed only satisfy the Success Criterion if  
all of the WCAG 2.0 conformance requirements have been met

Please change the requirements for Images of Text, level AA, and  
Resize Text, Meaningful Sequence, Bypass Blocks. It is almost  
impossible to pass because it requires all conformance requirements.  
There is a decleration at the bottom of the page

"The techniques listed only satisfy the Success Criterion if all of  
the WCAG 2.0 conformance requirements have been met."

Also, please see http://www.w3.org/TR/WCAG20/#conformance note 2.  
Please remove Images of Text as a requirement from AA, since it is  
also a level AAA requirement. This way it is harmonized with note 2

There are additional requirements that have the same scenario.

If I am wrong and the level A, or AA requirement, does not need to be  
synchronized with level AAA requirements, then at least change the  
language "The techniques listed only satify the Succession Criterion  
if all of the WCAG 2.0 conformance requirements have been met:" so it  
makes more sense to what you mean.

My interpretation of "all of the conformance requirements" means level  
AAA conformance.

Please clean up the language or the requirements that have these  
statements. The statement is very confusing.




RESPONSE :

Level A, AA, and AAA are Success Criteria - not "Conformance  
Requirements"

The conformance Requirements can be found in the Conformance  
Section.    You will note that the phrase "WCAG 2.0 conformance  
Requirements" in your quoted text above is a link. If you click on it  
-- it will take you to the conformance requirements.

(


=============================================================
2) WCAG Questions -  Still in Queue
These are question about the WCAG documents that are in queue for  
discussion by the Working Group.    We will work on them in turn as we  
get to them.  Thank you for your comments.   We will let you know how  
they come out when they are processed.  It may take some time  
depending on other work items.
If you need quicker responses in order to do your work - please check  
with a consultant. They can probably help you to understand the  
guidelines while we work on making the language more understandable in  
our formal docs to be released later this year.


--------------
From: N Maffeo <maffeonjr@yahoo.com>
Date: July 25, 2009 6:56:33 PM CDT
To: public-comments-wcag20@w3.org
Cc: gv@trace.wisc.edu
Subject: Text color, G148 1.4.3 & 1.4.6

Is the intent of this G148 http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/G148 
  used to evaluate the paragraph, link color, heading color, or all?



=============================================================
3) Consultant Questions
These are questions that should be addressed to consultants.  They do  
not fall into the category of things we need to change in the next  
release of the WCAG support documents.



From: N Maffeo <maffeonjr@yahoo.com>
Date: July 25, 2009 8:58:56 PM CDT
To: public-comments-wcag20@w3.org
Cc: gv@trace.wisc.edu
Subject: FOCUS VISIBLE, 2.4.7 and Color Contrast

At example C15, can I specify a:focus to be the same color as the  
primary active link link?

I have it currently set up so  it is a:active, a:visited, a:hover,  
a:focus, all receive the same color.

Does this cause Focus Visible problems?

Does it cause Color Contrast problems?

The color selection for all links passed the 3:1, 4:5:1, and the 7:1  
ratio.



From: N Maffeo <maffeonjr@yahoo.com>
Date: July 23, 2009 8:30:28 AM CDT
To: public-comments-wcag20@w3.org
Subject: 2.4.1 Skip Links/Bypass Blocks

I have a question. Is the page at http://www.w3.org/WAI/intro/ 
wcag20.php "Skip to Content" an example of G1, G123, or G124.


From: N Maffeo <maffeonjr@yahoo.com>
Date: July 25, 2009 8:58:56 PM CDT
To: public-comments-wcag20@w3.org
Cc: gv@trace.wisc.edu
Subject: FOCUS VISIBLE, 2.4.7 and Color Contrast

At example C15, can I specify a:focus to be the same color as the  
primary active link link?

I have it currently set up so  it is a:active, a:visited, a:hover,  
a:focus, all receive the same color.

Does this cause Focus Visible problems?

Does it cause Color Contrast problems?

The color selection for all links passed the 3:1, 4:5:1, and the 7:1  
ratio.


From: N Maffeo <maffeonjr@yahoo.com>
Date: July 22, 2009 6:59:20 PM CDT
To: public-comments-wcag20@w3.org
Cc: 508@access-board.gov
Subject: Focus Visibe: C15 and G195

If my page has an a:hover, and a:visited to be exactly the same as the  
regular a tag, how does impact Focus Visible?

I am not using SCR31, because I am not using any scripting.

Do I need to setup an a: hover that is of a different color than the  
primary a tag?



  ====================
From: N Maffeo <maffeonjr@yahoo.com>
Date: July 25, 2009 6:56:33 PM CDT
To: public-comments-wcag20@w3.org
Cc: gv@trace.wisc.edu
Subject: Text color, G148 1.4.3 & 1.4.6

Is the intent of this G148 http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/G148 
  used to evaluate the paragraph, link color, heading color, or all?
Received on Friday, 31 July 2009 14:11:08 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:11:12 UTC