This wiki has been archived and is now read-only.

Test template

From Automated WCAG Monitoring Community Group
Jump to: navigation, search

The test template contains a plain language description of the test, some background information, and a list of all assumptions. The test properties are summarized in a table. The actual test is defined by the selector, a number of steps and a formal description of the test outcomes.

The format of the test properties and outcomes is aligned with EARL.

Use the empty test template to create new auto-wcag tests on this wiki.

For the name of the test case use the following format: SC#-#-#-identifier

  • SC#-#-#: This is an identifier for the criterion to which the test case applies. #-#-# stands for the number of that criterion, such as SC4-1-2.
  • +SC#-#-#: This can be used if the test case applies to multiple success criteria, such as SC1-1-1+SC4-1-2-identifier. The numbers are in the same order as they are used in WCAG.
  • identifier: This must be a lower case identifier of the test, preferable no more then 3 words. It can only contain alphanumeric values or a dash (-).


Status of the test, such as draft, for review, or version 1.

Use the templates {{draft}} or {{status|version_number|oldid}} to record the status.


This test checks ...


  • Links to Techniques for WCAG 2.0
    Latest version: Techniques for WCAG 2.0 W3C Working Group Note 8 April 2014
  • Link to other methodologies, test specifications or tools
  • Links to test cases, test suites, unit tests, etc.
    The WCAG 2.0 Techniques already contain examples and code snippets to illustrate which content passes or fails the test. Whenever possible auto-wcag refers to those. Another source for test cases is the W3C Before and After Demonstration.
  • Other references


List of all assumptions

Test properties

Property Possible values W3C background
Test name Unique (short) identifier for the test case EARL: Use dct:title to provide a name for the earl:TestCase.
Success Criterion WCAG 2.0 Success Criterion EARL: Use dct:isPartOf to provide additional information about this earl:TestCase.
Test mode
  • automatic
  • SemiAuto
  • manual
EARL earl:TestMode
Test environment
  • HTML source (= unprocessed source of the web page)
  • DOM (= generated source after onload scripts are applied (no user interaction). CSS is taken into account so that elements that are not displayed are not tested.)
  • DOM and CSS (= same as above plus computed style for each element)
  • rendered page (= web page as it is presented in a browser)
  • rendered page + server connection
  • Remote Controlled User Agent (= A user agent containing a rendered page, in which the cursor and focus can be manipulated through scripting)
WAET Retrieving and rendering web content
Test subject
  • single web page
  • multiple web pages
  • web page state
  • DOM document fragment

WCAG EM Web page state
WAET DOM document fragments

User expertise and skills

For manual tests only:

  • no prior knowledge
  • basic understanding of HTML
  • basic understanding of HTML and WCAG
  • advanced understanding of HTML and WCAG
User profile For manual tests only:
any additional requirements, such as language skills, use of AT, or:
  • requires sight
  • requires hearing

Test procedure


{{mode-automatic}} or {{mode-manual}}

Natural language or machine-readable selector.

See introduction to selectors for further references.

Step 1

{{mode-automatic}} or {{mode-manual}}

Step of the test procedure in natural language.

Use the Template:UserInput to define manual steps of the test procedure.

If the step returns a result use one of the templates to specify it:

Step 2