Most WCAG tests are automated but some must still be verified manually by validating the pages against the Dutch Guidelines validation tool (See XHTML & CSS Coding Style).

Other WCAG validators

The following WCAG testing tools can also be used for additional checks and are listed for reference:

Links

Test Exceptions

Here are some exceptions that make the WCAG validators fail but that we consider valid (i.e. we consider the validators are overzealous in these cases):

  • We are using the H1 element several times on pages, once for the page title and once for the header level 1 from the page's content. We consider that this doesn't violate the rule "Do not skip any heading elements in the document hierarchy." since we're not skipping any level. Fails with Dutch Guidelines validation tool
  • RecentChanges.xml: "E858 [WCAG v1 5.6 (AAA)] Provide abbreviations for long header labels in data tables" for the following input:
    <th>Author and date</th>
    This is not really a long label and there's no way to make it shorter that would add value. Fails with Total Validator
  • "Use (at least) the meta element to specify the character set and place this element as high as possible in the head section of the markup.". The Content-Type META element is th first one in the HEAD element and cannot be placed higher. Fails with Dutch Guidelines validation tool
  • The ColorThemes application is using inline styles to display a preview of the colors and options of themes, this is something we cannot easily avoid.
  • The XWiki syntax allows using elements which are not allowed by accessibility guidelines. Sandbox.WebHome contains demonstrations which does not satisfy the following guidelines:
    • "Use the headers and id attributes to associate table labels (th cells) with individual cells in complex tables" 
    • "Use the scope attribute to associate table labels (th cells) with columns or rows. "
    • "The use of sub and sup tags is not allowed."
  • The XWiki syntax allows using elements which are not allowed by accessibility guidelines. XWiki.XWikiSyntax contains demonstrations which does not satisfy the following guidelines:
    • "Use the p (paragraph) element to indicate paragraphs. Do not use the br (linebreak) element to separate paragraphs."
    • "Use ol (ordered list) and ul (unordered list) elements to indicate lists."
    • "Use the headers and id attributes to associate table labels (th cells) with individual cells in complex tables" 
    • "Use the scope attribute to associate table labels (th cells) with columns or rows. "
    • "The use of sub and sup tags is not allowed."
    • "Links to e-mail addresses: the e-mail address to which the message is addressed must be visible in the link text.
    • "CSS should be placed in linked files and not mixed with the HTML source code."
  • The Panels.PanelWizard and XWiki.Treeview pages are relying on JavaScript libraries that needs some HTML elements to contain inline styles.

Testing Sessions

Since WCAG tests are not fully automated (and not full automatable) we have manual testing sessions that we do from time to time:

Tags:
Created by Vincent Massol on 2009/11/20 09:24
   

Get Connected