Techniques for WCAG 2.0 submission form

This form provides a mechanism for those interested in submitting techniques to submit content for consideration in Techniques for WCAG 2.0. Submissions are publicly archived in the public-wcag2-techs@w3.org Mail Archives. Please note that submissions are subject to WCAG Working Group approval and that there is no guarantee that they will be included in a techniques working draft.

When submitting a technique, please be sure that you check it against the following list:

  1. The writeup follows the instructions and guidelines below for each section.
  2. The writeup does not include the words "required," "must," or "shall."
  3. The technique is written to be descriptive, not imperative. That is, the sentences say "with this technque you xyz" not "do xyz". The only exception to this is the tests section, where the steps in the procedure should be be imperative.
  4. No comment about sufficiency or advisory, etc. should be in the technique document. Again, the information should be at the Understanding WCAG 2.0 level instead. There are several reasons for this. First, it is confusing to say that the technique is sufficient for a success criteria for one technique but the same technique is not sufficient for another (because it might only be sufficient to use a combination of techniques). Also, some techniques may be sufficient in one place and advisory in another. Finally, you can end up with something where the techniques document differs from the understanding document which makes it difficult for people to review and tomake sure they have things correct when the information is in multiple places and is not exactly the same.

Submit a Technique

Submitter Information

Technique Information

Note: If the proposed technique relates to multiple success criteria, please indicate the additional criteria in the additional notes field at the end of this form.

Includes information about when it is technically appropriate to use the technique. (Note: Do not include information on when you should or should not use the technique for accessibility or conformance. Example: Use for data tables, but not for layout tables)

Include notes on any known issues regarding lack of support for this technique with commonly used user agents or assistive technologies. Leave blank for general techniques.

Start with a sentence saying "The objective of this technique is..." and follow that with information necessary to understand what they are trying to achieve and how to carry out the technique.


Examples of the technique in action. Rendered examples as well as descriptions of examples are useful. For technology specific techniques, code samples are highly recommended.


Links to free resources that support the technique, provide educational information, are Public-Domain test tools for this technique, or citations of specific sections of standards related to this technique.

This should include only closely related techniques such as techniques for going beyond what this technique requires. For example, a technique for attaching short text alternatives may also list general techniques for the content of the text alternative (i.e. writing good text alternatives). To select multiple related techniques, hold down the control key.


Provide a numbered list of the steps in the testing procedure. Be sure to not go beyond this technique. If it is a technique to attach alternative text, do not talk about sufficiency of the text (which is covered by another technique), just test to see that it is there.

List what should be true when the technique is implemented successfully (ex. Checks #3 and #4 above are true).

If possible, test files should demonstrate both pass and fail conditions. Leave this field blank for general techniques.

Test file 1 will [ ] / [ ] this technique.

If possible, test files should demonstrate both pass and fail conditions. Leave this field blank for general techniques.

Test file 2 will [ ] / [ ] this technique.

Please also note whether you feel this technique is sufficient to meet the success criterion (or criteria) it relates to.

Last updated: $Date: 2014-01-17 22:16:05 $