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

Draft edits to Techniques Intro

From: David MacDonald <befree@magma.ca>
Date: Sun, 20 Jun 2010 10:38:56 -0400
Message-ID: <52889.1277044736@magma.ca>
To: <w3c-wai-gl@w3.org>, <gv@trace.wisc.edu>
Cc: <david100@sympatico.ca>
 

Here is the intro, with suggested edits reflecting Gregg’s comments: 

   

Rather than having technology specific techniques in WCAG 2.0, the
guidelines and success criteria themselves have been written in a
technology neutral fashion. In order to provide guidance and examples for
meeting the guidelines using specific technologies (for example HTML) the
working group has identified __ for each Success Criterion that are
sufficient to meet that Success Criterion. In some cases it's only when 
are used that it is considered sufficient. In these cases, the sufficient
combination of techniques are listed together on one numbered line in the
“how to meet” and “understanding” documents. Each numbered line is
sufficient to meet the Success Criteria it addresses, but the individual
Techniques on that line are not sufficient by themselves unless they are
on a numbered line by themselves.  

The list of techniques is maintained in the "Understanding WCAG 2.0" (and
mirrored in How to Meet WCAG 2.0). In this wayBy separating the WCAG 2
normative guidelines document from the techniques used to meet the Success
Criteria in those guidelines it is possible to update the list as new
techniques are discovered, and as Web Technologies and Assistive
Technologies progress. 

Note that all techniques are . The "sufficient techniques" are considered
sufficient by the WCAG Working Group to meet the success criteria.
However, it is not necessary to use these particular techniques. If
techniques are used other than those listed by the Working Group, then
some other method for establishing the technique's ability to meet the
success criteria would be needed.  

There are sometimes code examples in the sufficient techniques that are
intended to demonstrate the principle discussed in the description of the
technique. The code is not intended to demonstrate other aspects of
accessibility, usability or best coding practises not related to the
technique. 

Most success criteria have multiple sufficient techniques listed. Any of
the listed sufficient techniques can be used to meet the Success
Criterion. There may be other techniques which are not documented by the
working group that could also meet the Success Criterion. As new
sufficient techniques are identified they will be added to the listing.  

In addition to the sufficient techniques, there are a number of __ that
can enhance accessibility, but did not qualify as sufficient techniques
because are not sufficient to meet the full requirements of the success
criteria, they are not testable, and/or are good and effective techniques
in some circumstances but not effective or helpful in others. These are
listed as advisory techniques and are right below the sufficient
techniques. Authors are encouraged to use these techniques wherever
appropriate to increase accessibility of their Web pages. 

  

  

 w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org] Gregg
Vanderheiden
  June-20-10 10:01 AM
  befree@magma.ca
  w3c-wai-gl@w3.org; david100@symatico.ca
  Re: Editorial addition to the Techniques intro 

  

Good edits. 

  

Where we say “sufficient techniques” we need to say “sufficient
techniques or combination of techniques”.  

  

In a large number of cases it's only when you use a combination of
techniques that it is considered sufficient. Each numbered line in the
“how to meet” and “understanding” docs is sufficient. But the
individual Techniques on that line are not sufficient by themselves unless
they are on a numbered line by themselves. 

  

This is somewhat subtle but it is important. It also helps get by the idea
that techniques are themselves what you need to conform to. 

  

  

_Gregg_
 -----------------------
 Gregg Vanderheiden Ph.D.
 Director Trace R&D Center
 Professor Industrial COLOR: black"> 

  

On Jun 19, 2010, at 11:11 PM, David MacDonald wrote: 

  

As we get ready to republish the Techniques document, I’ve been looking
at the introduction. There is a typo to fix and I think we should add a
couple of  sentences  

  

There are examples in each technique which sometimes contain code snips
that are intended to demonstrate the principle discussed in the
description of the technique. The code is not intended to demonstrate
other aspects of accessibility, usability or best coding practises not
related to the technique.  

  

Here’s a shot at it in context with a couple of other edits which are
within 

   

Rather than having technology specific techniques in WCAG 2.0, the
guidelines and success criteria themselves have been written in a
technology neutral fashion. In order to provide guidance and examples for
meeting the guidelines using specific technologies (for example HTML) the
working group has identified __ for each Success Criterion that are
sufficient to meet that Success Criterion. The list of sufficient
techniques is maintained in the "Understanding WCAG 2.0" (and mirrored in
How to Meet WCAG 2.0). In this wayBy separating the WCAG 2 normative
guidelines document from the techniques used to meet the Success Criteria
in those guidelines it is possible to update the list as new techniques
are discovered, and as Web Technologies and Assistive Technologies
progress. 

Note that all techniques are . The "sufficient techniques" are considered
sufficient by the WCAG Working Group to meet the success criteria.
However, it is not necessary to use these particular techniques. If
techniques are used other than those listed by the Working Group, then
some other method for establishing the technique's ability to meet the
success criteria would be needed.  

There are examples in each technique which sometimes contain code snips
that are intended to demonstrate the principle discussed in the
description of the technique. The code is not intended to demonstrate
other aspects of accessibility, usability or best coding practises not
related to the technique. 

Most success criteria have multiple sufficient techniques listed. Any of
the listed sufficient techniques can be used to meet the Success
Criterion. There may be other techniques which are not documented by the
working group that could also meet the Success Criterion. As new
sufficient techniques are identified they will be added to the listing. 

In addition to the sufficient techniques, there are a number of __ that
can enhance accessibility, but did not qualify as sufficient techniques
because are not sufficient to meet the full requirements of the success
criteria, they are not testable, and/or are good and effective techniques
in some circumstances but not effective or helpful in others. These are
listed as advisory techniques and are right below the sufficient
techniques. Authors are encouraged to use these techniques wherever
appropriate to increase accessibility of their Web pages. 

  

  
 
Received on Sunday, 20 June 2010 14:39:27 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 20 June 2010 14:39:27 GMT