WPSS Validator Tool Test Cases
About the PWGSC WPSS Validation Tool
Password Protected Applications
Web Server Password Protection
Accessibility Checking Profiles
WCAG 2.0 Techniques Reported Under Other Techniques
Layout and Design Checking Profiles
SWU – Standard on Web Usability Layout and Design test cases
TBS Web Analytics – Standard on Privacy and Web Analytics test cases
SWI – Standard on Web Interoperability test cases
PWGSC SWU – PWGSC Standard on Web Usability Departmental Check Test Cases
The PWGSC WPSS Validation Tool combines a number of individual analysis and validation functions into a single tool. This tool provides web developers and quality assurance testers the ability to perform a number of Web site and Web page analysis and validation tasks at the same time. The analysis and validation functions applied to Web sites and Web documents include:
- markup validation
- link violation checking
- metadata checking
- accessibility checking
- content checking
- reporting HTML document features, such as forms and tables.
Each of these analysis or validation functions is described in this document.
There are limitations within the Validation Tool that may affect the analysis or validation results, these are:
- The Validation Tool does not support JavaScript. Sites that rely on JavaScript may not be crawled or analysed accurately.
- The Validation Tool does not use a standard Web browser User Agent name. The Validation Tool may not crawl or analyse sites that rely on the User Agent name accurately.
- The Validation Tool’s default behaviour is to respect robots directives. If a site has a robots.txt file to prohibit crawlers, then no validation of the site’s documents are performed. You can configure the Validation Tool to ignore robots.txt directives. See the PWGSC WPSS Validation Tool User Guide for more information.
- The output of the individual Validation Tools is in English only. It is using 3rd-party software components. The source of these components is available only in the language that it was authored.
- Markup validation cannot be performed on HTML 5 documents.
The Validation Tool includes a crawler that follows links and retrieves web documents from sites. Care should be taken with this tool to:
- ensure entry page URLs for the sites are accurate so the crawler does not go beyond the site being analysed.
- ensure that document retrieval from the site being analysed, and any links to other sites, do not impose excessive loads on web servers and the network.
The list of Web documents or URLs that the WPSS Validation Tool analyses can be supplied either in a list or by performing a crawl of a site.
A Web site crawler module is included with the Validation Tool. It crawls a site to get the list of documents to analyze. The crawler uses the site directory URL and the entry page address for the English and French entry points to perform the crawl.
The site directory URL is the URL of the top level directory or folder containing the site documents. The entry page address is the file name and URL arguments portion of the entry page. The crawler starts at the entry page and extracts any URL references from that page. These can be links, images or any other HTML tag containing a URL. If the URLs are references to other documents in the site, they are added to the set of URLs to analyze. They are in turn retrieved and analyzed for URL references. This process of retrieving and analyzing documents continues until either a the Validation Tool reaches the preset crawl limit, or there are no more URLs to analyze. After analyzing each document for URLs, the other analysis modules of the Validation Tool use that URL information.
A URL is deemed to be part of the site being crawled if the URL matches the site directory URL pattern. If it does not match the pattern, it is assumed to be a document outside the site. This is true for all URL references except those related to JavaScript files and style sheets (CSS files). References to these file types that appear in either a <script> tag or a <link> tag are also considered to be part of the site. This is due to the nature in which these files affect the display and performance of the site.
Web applications typically have a login or authentication page that limits many automated testing tools to only access Web pages outside the login. The Validation Tool has the capability to handle sites or application that employ a single login page with a form for entering credentials, and login pages to get at Web pages behind the login. By providing the Validation Tool with the URL of the login page, it will:
- retrieve the login page.
- locate the login form and form fields.
- prompt the user for credentials.
- submit the form to accomplish application login.
Once these steps are complete, the Validation Tool can proceed with crawling for Web documents behind the login. This ensures a more complete site/application analysis. See the PWGSC WPSS Validation Tool User Guide for more information.
A Web server can be configured to password protect portions of a site. When a user tries to access a protected portion, the Web server returns an “HTTP 401 (Unauthorized)” message. Web browsers prompt the user for credentials to retrieve the Web document. When the Validation Tool receives this message, it can also prompt the user for credentials to retrieve the document.
The Markup Validation module of the WPSS Validation Tool checks the mark-up, or syntax, of various file types. It checks that the files conform to the appropriate standard, such as HTML. The Validation Tool checks the following content types:
- HTML/XHTML
- Cascading Style Sheets
- JavaScript
- Robots.txt
The Validation Tools checks all content with a mime-type of text/html, which includes HTML and XHTML content, using the Web Design Group (WDG) validator. This is an open source validator based on the W3C validator. The markup is validated to the DTD specified in the content.
NOTE: This tool does not validate HTML5 mark-up.
The Validation Tools checks CSS markup using the open source W3C CSS validator. CSS content is validated from the following sources:
-
All content with a mime-type “text/css”.
-
Files listed in tags with a type attribute value of “text/css” found in HTML content. For example:
<link href="/comm/css/internet.css" rel="stylesheet" type="text/css" /> -
Content found in
<style>tags with a type attribute value of text/css. For example:<style type="text/css" > body { color: purple; background-color: #d8da3d } </style>
The Validation Tools checks JavaScript markup using the open source JavaScript Lint program. JavaScript content is validated from the following sources:
- All content with a mime-type application/x-javascript.
- URLs with a .js suffix.
- Files listed in
<script>tags with a type attribute value of text/javascript found in HTML content. For example,<script src="/source/scripts/pe-ap.js" type="text/javascript"></script>
The Validation Tool does not validate inline JavaScript in HTML content that uses the <script> tag. This content may not conform to proper JavaScript syntax due to the way browsers read and interpret inline scripts.
All robots.txt files found at the root of a web server domain, for example, http://<domain name>/robots.txt, is validated using the PWGSC Robots.txt validator. Any robots.txt file that exists somewhere other than the top level is not validated as it would not be a valid location for a robots.txt file.
The Link Checker module of the WPSS Validation Tool performs a number of link violation checks in addition to the standard broken link check. These checks include:
- broken links
- cross language links
- redirected links
- bad network scope links
- broken anchors
- firewall blocked links
- IPV4 links.
Link checking is applied to all URL references found in any tag. This includes, but is not limited to:
- anchor tags
<a> - image tags
<img> - link tags
<link> - script tags
<script>
Link violations are described in the following sections.
Broken links are links or references to URLs that do not exist. This is the most basic form of link checking. When trying to retrieve a document, if it does not exist, the web server returns a “404 (Not Found)” response.
A cross language link occurs when a document in one language references a document in another. For example an English web page contains a link to a French document.
The language of a document is determined by one of the following techniques:
-
File name suffix – use the characters before the file type extension to determine language.
English: index-eng.html, report_eng.pdf, sign_e.gif, sign-e.gif
French: index-fra.html, rapport_fra.pdf, sign_f.gif, sign-f.gif
-
Language variable in URL string – check for presence of the lang variable in URL string. English: index.cfm?lang=eng French: index.cfm?lang=fra
-
Content – determine language of content for HTML, PDF or text files.
If content is available in only one language, such as a document in English only, then any links from French documents would appear as cross language links. You can avoid errors from the Validation Tool by including a language attribute within the HTML tag.
For example, a link from a French web page would look like:
<html xmlns="http://www.w3.org/1999/xhtml" lang="fr" xml:lang="fr">
<a href="http://www.tpsgc-pwgsc.gc.ca/comm/index-eng.html" lang="en" xml:lang="en">English</a>
The lang and xml:lang attributes indicate the link references an English document, which is a different language than the main French document. If the Validation Tool cannot determine the language of either the source document or the target document, no cross language link violations are reported.
A redirected link is one in which the URL of a link is different from the final location of the document. The final URL may differ by the domain name and or the file name. Redirects may be used translate vanity domains into official domains or to direct users to new file names for documents. There is a risk that redirects may be removed on the target site resulting in broken links.
Domain redirect : http://www.pwgsc.gc.ca/ > http://www.tpsgc-pwgsc.gc.ca/
File redirect : http://www.canada.gc.ca/main_e.html > http://www.canada.gc.ca/home.html
The Validation Tool only reports redirect link violations for permanent redirects; not for temporary redirects.
Network scope refers to a level of the network; PWGSC Intranet, Government of Canada Intranet or Internet. A bad network scope link occurs when a document at a higher scope references a document at a lower scope. For example, an Internet document has a link to a Government of Canada Intranet document. Some users may experience a broken link when selecting the link while others may get the referenced document. For example, public users versus users on the Government of Canada network.
A named anchor is a link marker on an HTML page. If an anchor is referenced in a URL, the browser positions the user at the anchor in the document. This allows for linking to particular section in a larger web document. If the named anchor does not exist in the target document, the browser placees the user at the top of the document.
A firewall blocked link is a link to a site or document that is prohibited by the departmental firewall. This is essentially a broken link as the user cannot get to the target document.
An IPV4 link is a link that has an IP address rather than using a domain name. For example, http://10.11.12.13/index.html.
The metadata checking of the WPSS Validation Tool analyses metadata within HTML/XHTML and PDF documents. It checks HTML/XHTML documents for:
- the presence of required metadata tags.
- that non-white space content is provided where required.
- the content value where the value set is known. For example, language values.
- the content format where it must have a specific pattern. For example, date values.
The metadata check also checks PDF documents for the presence of required file properties. Details on the PWGSC HTML/XHTML metadata tags and content is detailed at http://source.tpsgc-pwgsc.gc.ca/comm/web/w2/inter-meta-eng.html.
The Validation Tool uses a profile to check for the required metadata tags or PDF file properties. The profile specifies the metadata tag name or PDF file property name, whether or not they need content and the content type. The metadata profiles used are:
- PWGSC SWU – Standard on Web Usability metadata tags,
- TBS SWU – Treasury Board Standard on Web Usability metadata tags,
- PWGSC – CLF 2.0 tags plus additional PWGSC tags,
- TBS CLF 2.0 – Treasury Board CLF 2.0 list of metadata tags,
- None – No metadata tags are required.
The PDF file property profiles used are:
- PWGSC – PWGSC properties (Title),
- None – No properties required.
The PWGSC SWU metadata profile requires:
| dcterms.subject | dcterms.creator | dcterms.modified | description | title |
| dcterms.language | dcterms.issued | dcterms.description | keywords |
The Treasury Board SWU metadata profile requires:
| dcterms.title | dcterms.language | dcterms.issued | description |
| dcterms.subject | dcterms.creator | dcterms.modified | title |
The PWGSC metadata profile requires:
| dc.title | dc.language | dc.publisher | dcterms.modified | keywords |
| dc.subject | dc.creator | dcterms.issued | description | pwgsc.contact.email |
The Treasury Board CLF 2.0 (TBS CLF 2.0) metadata profile requires:
| dc.title | dc.language | dc.publisher | dcterms.modified | keywords |
| dc.subject | dc.creator | dcterms.issued | description |
The PWGSC PDF file property set includes the “Title” property.
While the metadata profiles are required, not all the items require content. Those items that do require content, those metadata tags and PDF file properties must contain meaningful text. The Validation Tool checks for the absence of required text, or if the text consists of white space only (spaces, tabs, etc). The set of metadata items that require content is specified in a profile supplied to the Validation Tool.
The PWGSC SWU metadata items that require content are:
| dcterms.title | dcterms.subject | dcterms.creator | description | title |
| dcterms.language | dcterms.issued | dcterms.modified | dcterms.description | keywords |
The PWGSC metadata items that require content are:
| dcterms.title | dc.language | dc.publisher | dcterms.modified | keywords |
| dc.subject | dc.creator | dcterms.issued | description | pwgsc.contact.email |
The Treasury Board CLF 2.0 (TBS CLF 2.0) metadata items that require content are:
| dcterms.title | dc.language | dc.publisher | dcterms.modified | keywords |
| dc.subject | dc.creator | dcterms.issued | description |
Some metadata tags must contain specific values or values in a specific format. The Validation Tool checks for a specific content formats, such as date values, or that content comes from a controlled vocabulary. It cannot check that the actual value is appropriate. Specific content formats and values are further specified below.
The content of the dcterms.issued and dcterms.modified metadata items is a date value that must be expressed in YYYY-MM-DD format. The Validation Tool checks that the content conforms to this format and that the month is in the range 01 to 12 and that the date is in the range 01 to 31. For example:
<meta name="dcterms.issued" scheme="W3CDTF" content="2005-11-21" />
The Validation Tool also checks that dates are consistent; dcterms.modified is not before dcterms.issued.
The content of the dc.language metadata item is a three character language code. For example:
<meta name="dc.language" scheme="ISO639" content="eng" />
The content of the dc.subject metadata item on PWGSC web pages is a list of terms that describe the topic of the web page. These terms must be selected from a controlled vocabulary, the Government of Canada Core Subject Thesaurus. The terms must be separated with a semicolon selected from the list of preferred terms, not the non-preferred terms. The Validation Tool verifies that the dc.subject terms are taken from the Thesaurus matching the language of the page. For example:
<meta name="dc.subject" scheme="gccore" content="Newsletters, Information, Information sources" />
The content of the pwgsc.contact.email item is a single email address. The Validation Tool verifies that the content is a well formed e-mail address. It does not verifies that it’s a valid address. For example:
<meta name="pwgsc.contact.email" content="questions@pwgsc-tpsgc.gc.ca"/>
The scheme attribute of some metadata tags must contain specific values. The TBS CLF 2.0 profile requires the following scheme value for the specified metadata tags:
| Tag Name | Scheme Attribute Value |
|---|---|
| dcterms.issued | W3CDTF |
| dcterms.modified | W3CDTF |
| dc.language | ISO639-2/T |
| dc.subject | gccore |
The PWGSC SWU profile requires the following scheme value for the specified metadata tags:
| Tag Name | Scheme Attribute Value |
|---|---|
| dcterms.issued | W3CDTF |
| dcterms.modified | W3CDTF |
| dcterms.language | ISO639-2 |
| dcterms.subject | gccore |
The Validation Tool reports invalid content errors for the metadata tags that do not have these scheme values.
The Validation Tool checks for the set of required PDF file properties specified by a profile. The PWGSC PDF File Properties profile contains the following item:
- Title
The accessibility checking module of the WPSS Validation Tool, also referred to Technical Quality Assurance (TQA) performs a number of accessibility tests on Web documents. A profile of test cases is used to determine which checks to perform and report on.
The Validation Tool uses the WCAG 2.0 – WCAG 2.0 test cases profile to check and create the report.
A list of test cases in each profile is outlined below. Each test case details what the Validation Tool checks for, and if it does not fully implement the checkpoint, it details what is not checked.
Accessibility checking is limited to verifying that appropriate mark-up is used and/or text is supplied where needed. There is no checking on the value of the content. A test case can check if alternative text is provided, but it cannot check if the text is appropriate. For example, it can verify there is a description for an image, but cannot verify that the description is valid for that image.
This profile contains WCAG 2.0 test cases.
| Description | Failure of Success Criterion 1.3.1 due to using changes in text presentation to convey information without using the appropriate markup or text. |
| Checks For | Text styled to look like a heading using HTML mark-up (e.g. <strong>). |
| Does Not Check | Text styled to look like a heading using CSS. |
| Images used to convey structural information. |
| Description | Failure of success criterion 1.1.1 due to using CSS to include images that convey important information. |
| Images are deemed non-decorative if they are specified through tool configuration (non-decorative image list) or if the first occurrence of an image in a site includes alt text. | |
| Checks For | If non-decorative images are loaded using CSS. |
| Does Not Check | If the information is provided to assistive technologies and is also available when the CSS image is not displayed. |
| Description | Failure of success criterion 2.2.2 due to using text-decoration:blink without a mechanism to sop it in less than five seconds. |
| Checks For | All styles for the text-decoration property with a value of blink. |
| Does Not Check | If the styles are actually used within the document. |
| Description | Failure of Success Criterion 2.2.2 due to including scrolling content where movement is not essential to the activity without also including a mechanism to pause and restart the content. |
| Checks For | The presence of a <marquee> tag. |
| Does Not Check | Any other mechanism, such as scripting, generates moving content. |
| Description | Failure of Success Criterion 1.3.1 and 4.1.1 due to insufficient information in DOM to determine one-to-one relationships, for example, between labels with same id in HTML. |
| Checks For | The accesskey and for attribute values are unique. |
| The attribute values that have an idref value have a corresponding id value. | |
| The accesskey values consist of a single character only. | |
| Note: Duplicate id values are reported under failure F77. | |
| Does Not Check | For tables that use the axis attribute, check that all values listed in the axis attribute have a corresponding id value in a table header cell in the same table. |
| For client-side image maps, check that the value of the usemap attribute has a corresponding id value if the usemap attribute is not a URI. |
| Description | Failure of Success Criterion 2.4.2 due to the title of a page not identifying the contents. |
| Checks For | If title is missing. |
| If the title is the same as the file name in the document URL. | |
| If the title matches any invalid values, such as “untitled”. | |
| Does Not Check | Other invalid title values. |
| Description | Failure of Success Criterion 1.1.1 and 1.2.1 due to using text alternatives that are not alternatives. |
| Checks For | If the alt attribute matches the src attribute for <img> tags. |
| If the alt attributes matches any invalid values in items such as photos, images, or graphs. | |
| Does Not Check | Other text alternatives that are not text alternatives. |
| Description | Failure of Success Criterion 1.3.2 due to using white space characters to control spacing within a word. |
| Checks For | Whitespace inside words. |
| Description | Failure of Success Criterion 1.1.1 by omitting the alt attribute for non-text content used for decorative purposes only in HTML. |
| Images or applets are deemed decorative if they are specified through tool configuration (decorative image list) or if the first occurrence of an image or applet in a site has no alt text. | |
| Checks For | If the alt attribute is missing on decorative images or applets. |
| Description | Failure of Success Criterion 1.1.1 due to providing a text alternative that is not null (alt="spacer" or alt="image") for images that should be ignored by assistive technology. |
| Images are deemed decorative if they are specified through tool configuration (decorative image list) or if the first occurrence of an image in a site has no alt text. | |
| Checks For | If the alt attribute is an empty string for images that are decorative. |
| Description | Failure of Success Criterion 2.2.1 and 2.2.4 due to using meta redirect with a time limit. |
| Checks For |
<meta http-equiv=”refresh”> with a timeout and a URL. |
| Description | Failure of Success Criterion 2.2.1, 2.2.4 and 3.2.5 due to using meta refresh with a time limit. |
| Checks For |
<meta http-equiv=”refresh”> with a timeout and a URL. |
| Description | Failure of Success Criterion 1.3.1 and 2.1.1 due to using scripting events to emulate links in a way that is not programmatically determinable. |
| Checks For |
onclick or onkeypress attributes on tags other than <a> <area> <button> <input> or <select>. |
| Description | Failure of Success Criterion 1.3.1 due to using structural markup in a way that does not represent relationships in the content. |
| Checks For |
<fieldset> used outside a <form>. |
<hr> used as decoration (<hr> followed by another <hr>, or heading followed by <hr>). |
|
| Does Not Check | The semantic meaning of other tags. |
| Description | Failure of Success Criterion 2.2.2 due to using the blink element. |
| Checks For | The <blink> tag. |
| Description | Failure of Success Criterion 2.1.1 due to using only pointing-device-specific event handlers (including gesture) for a function. |
| Checks For | Mouse only event handlers. |
| Description | Failure of Success Criteria 2.1.1, 2.4.7, and 3.2.1 due to using script to remove focus when focus is received. |
| Checks For | JavaScript this.blur function. |
| Description | Failure of Success Criterion 2.2.1 due to using server-side techniques to automatically redirect pages after a time-out. |
| Checks For | HTTP header for a “refresh” field with a time out greater than zero. |
| Description | Failure of Success Criterion 1.1.1 due to omitting the alt attribute on img elements, area elements, and input elements of type “image”. |
| Checks For |
alt attribute on <img>, <area> and <input type=“image”> tags. |
| Description | Failure of Success Criterion 3.2.3 due to presenting navigation links in a different relative order on different pages. |
| Checks For | The relative order of navigation links of all pages. The order of the navigation links on a site’s entry page is used as the expected relative order. |
| Does Not Check | If there are multiple site navigation links with the same anchor text. These links are not checked. |
| Description | Failure of Success Criterion 1.3.1 and 4.1.2 due to the association of label and user interface controls not being programmatically determinable. |
| Checks For | Implicit associate of labels and input or select tags. |
| Text acting as a label for input or select tags. |
| Description | Failure of Success Criterion 4.1.1 due to incorrect use of start and end tags or attribute markup. |
| Checks For | Missing close tag for tags that cannot be nested. For example, <a> and <h1>. |
| Does Not Check | If opening and closing tags are missing the opening (<) and closing (>) brackets. |
| If closing tag missing the initial forward slash (/) to indicate it is a closing tag. | |
| If attribute values that have an opening quote but not a closing quote. Attribute values must be either fully quoted or, in some markup languages, do not have quotes. | |
| If there is a lack of whitespace between attributes. | |
| If unquoted attribute values have whitespace in the value. | |
| If a closing element tag is missing for elements that do not accept empty-element syntax. |
| Description | Failure of Success Criterion 4.1.1 due to duplicate values of type ID. |
| Checks For | There are no duplicate id values. |
| Description | Failure of Success Criterion 1.3.1 due to inserting non-decorative content by using :before and :after pseudo-elements and the “content” property in CSS. |
| Checks For | The content property of styles using :before or :after pseudo-elements contains a quoted string. |
| Does Not Check | If the content is decorative. |
| Description | Failure of Success Criteria 2.4.4, 2.4.9 and 4.1.2 due to using null alt on an image where the image is the only content in a link. |
| Checks For | The alt attribute of an image is empty if the image is the only content of a link. |
| Description | Ensuring that a contrast ratio of at least 4.5:1 exists between text (and images of text) and background behind the text. |
| Checks For | CSS styles that specify a foreground and background colour. Checks colour contrast for an acceptable contrast ratio. |
| Does Not Check | Images |
| Does not take into account font size. | |
| The effect of multiple styles. |
| Description | Ensuring that no component of the content flashes more than three times in any one second period. |
| Note: Frames do not necessarily always result in a content flash. | |
| Checks For | All images of type image/gif to see if there are more than three frames displayed in any one second time period. |
| Does Not Check | Other animated content types such as Flash. |
| Description | Using semantic elements to mark up structure. |
| Checks For | PDF documents are tagged. |
| Does Not Check | Any other missing markup. |
| Description | Providing links to navigate to related Web pages. |
| Checks For | There is at least one link in HTML documents. |
| Does Not Check | If the links are to related information. |
| Description | Providing descriptive heading. |
| Checks For | If there are any headings (h1, h2, h3) found within the content area of Web pages. |
If there is text within the heading start and end tags. For example, <h1></h1>. |
|
| Does Not Check | If the heading identifies the section of the content. |
| Description | Providing descriptive labels. |
| Checks For | If there is text within the label start and end tags. For example, <label></label>. |
| Does Not Check | If the label identifies the purpose of the interface component. |
| Description | Validating Web pages. |
| Checks For | Reports the status of the content type validation tool, for example HTML, CSS, JavaScript). The details of any validation issues are reported by the specific validation tools. |
| Description | Ensuring that a contrast ratio of at least 3:1 exists between text (and images of text) and background behind the text. |
| Checks For | CSS styles that specify both a foreground and background colour. Checks colour contrast for an acceptable contrast ratio. |
| Does Not Check | Does not check images. |
| Does not take into account font size. | |
| The effect of multiple styles. |
| Description | Setting animated gif images to stop blinking after n cycles (within five seconds). |
| Checks For | Checks if GIF animation time is less than five seconds. |
| Description | Using labels, names, and text alternatives consistently for content that has the same functionality. |
| Links that are located within the content area of a page are only checked against other links in the same page. | |
| Links that are located in the navigation area of a page are checked against other navigation links in all pages. | |
| Checks For | Links, including image links, to the same URL have the same anchor, alt and title text. |
| Does Not Check | This check is for identical text, not similar text, so false errors may be reported. |
| Description | Combining adjacent image and text links for the same resource. |
| Checks For | If the anchor text of a link is the same as the alt text of an image contained within the link. |
| Does Not Check | That there is no a element in an adjacent table cell that has the same href attribute and the same description. |
| Description | Providing text alternatives for the area elements of image maps. |
| Checks For | An <area> tag has an alt attribute. |
| Does Not Check | That the text alternative specified by the alt attribute serves the same purpose as the part of image map image referenced by the area element of the imagemap. |
| Description | Providing a title using the title element. |
| Checks For | There is a non-empty <title> for the document. |
| Very long titles (e.g. greater than 500 characters). | |
| Does Not Check | That the title describes the document. |
| Description | Providing text and non-text alternatives for an object. |
| Checks For | There is some text contained within the <object> </object> tags. |
| Description | Providing link text that describes the purpose of a link for anchor elements. |
| Checks For | Multiple links with the same anchor text, but different href values. |
| “Click here” links. | |
| If the anchor text is the same as the href value (i.e. anchor text is a URL). | |
| Missing anchor text in link. | |
| Does Not Check | That the link text describes the purpose of the link. |
| Description | Providing submit buttons. |
| Checks For | All forms have a submit button (<input type="submit">, <input type="image">, or <button type="submit">). |
| Description | Supplementing link text with the title attribute. |
| Checks For | An anchor tag’s title attribute is not the same as the href value. |
| Does Not Check | Does not check that the title together with the link text describes the purpose of the link. |
| Description | Providing text alternatives on applet elements. |
| Checks For | The <applet> tags contain an alt attribute with content. |
There is text between the <applet> </applet> tags. |
| Description | Using alt attributes on images used as submit buttons. |
| Checks For | All inputs of type <input type="image"> contain an alt attribute with content. |
| Does Not Check | That the alt attribute indicates the button’s function. |
| Description | Using caption elements to associate data table captions with data tables. |
| Checks For | If a table has both a summary attribute and a <caption> element, that the summary is not identical to the <caption>. |
| Does Not Check | If the table is a layout table or a data table. |
That layout tables do not contain a <caption> element. |
|
| That the caption identifies the table. |
| Description | Using h1 to h6 to identify headings. |
| Checks For | The content is provided between the <h#> </h#> tags. |
| Very long headings (e.g. greater than 500 characters). | |
| Does Not Check | That heading markup is used when content is a heading. |
| That heading markup is not used when content is not a heading. |
| Description | Using id and headers attributes to associate data cells with header cells in data tables. |
| Checks For | Some headers exist in the table. |
| Undefined headers or headers outside the current table. | |
| Does Not Check | If the table is a layout table or a data table. |
| Description | Using label elements to associate text labels with form controls. |
| Checks For | A <label> with a for attribute matching the id attribute value exists for <input> that is not hidden or readonly. |
A <label> with a for attribute matching the id attribute value exists for <textarea>. |
|
A <label> appears before the <input> in the HTML stream for <input> of type ‘text’, ‘file’ or ‘password’. |
|
A <label> appears before the <textarea> in the HTML stream. |
|
A <label> appears after the <input> in the HTML stream for <input> of type ‘checkbox’ or ‘radio’. |
|
| Does Not Check | That the label is visible. |
| That the label identifies the purpose of the form control. |
| Description | Using the longdesc attribute. |
| Checks For | If an <img> tag has a longdesc attribute, that it has content. |
| The longdesc value is a valid URI. | |
| Does Not Check | That the target URI contains a description of the non-text content. |
| Description | Using <noembed> with <embed> elements. |
| Checks For | The number of <embed> and <noembed> tags match. |
| Does Not Check | That an <embed> element has a child <noembed> element. |
That an <embed> element has a <noembed> element immediately following it. |
| Description | Using ol, ul and dl for lists or groups of links. |
| Checks For | There is at least one <li> inside a <ol> or <ul>. |
There is at least one <dt> inside a <dl>. |
|
| Does Not Check | That content that has the visual appearance of a list is marked as a list. |
| That content is marked as a definition list when terms and their definitions are presented in the form of a list. |
| Description | Using the body of the <object> element. |
| Checks For | There is text between the <object> </object> tags. |
| Description | Using language attributes on the <html> element. |
| Checks For | There is a lang attribute in the <html> tag for HTML, and XHTML 1.0. |
There is an xml:lang attribute in the <html> tag for XHTML 1.0 and 2.0. |
|
| If both lang and xml:lang are provided, the values match. | |
| If the content language can be determined, the content language matches the lang attribute. | |
| Does Not Check | That the lang value reflects the primary language used by the Web page if there are fewer than 1000 characters of content. |
| That the lang value reflects the primary language used by the Web page if the content language cannot be determined (content closely matches two or more languages). |
| Description | Using language attributes to identify changes in the human language. |
| Checks For | XHTML 1.0 documents to verify that a xml:lang attribute is provided whenever a lang attribute is specified. |
| XHTML 1.0 documents to verify that a lang attribute is provided whenever a xml:lang attribute is specified. | |
| If both lang and xml:lang are provided, the values match. | |
| If the content language can be determined, the content language matches the lang attribute. | |
| Does Not Check | Does not check individual language spans. Content from all spans with the same language is concatenated into a single string for analysis. |
| That the lang value reflects the primary language used by spans if there are fewer than 1000 characters. | |
| That the lang value reflects the primary language used by the spans if the content language cannot be determined (content closely matches two or more languages). |
| Description | Using the title attribute of the frame and <iframe> elements. |
| Checks For | A title attribute is provided for <frame> <iframe> tags. |
| There is content in the title. | |
| Does Not Check | That the title identifies the frame. |
| Description | Using the title attribute to identify form controls when the label element cannot be used. |
| Form controls that do not have a label or title are reported as failures of H91. | |
| Checks For | If a title attribute is present, it has content. |
| Description | Using null alt text and no title attribute on img elements for images that AT should ignore. |
| Images are deemed decorative if they are specified through tool configuration (decorative image list), or if the first occurrence of an image in a site has no alt text. | |
| Checks For | If the alt and title attributes are empty string for images that are decorative. |
| Description | Providing a description for groups of form controls using <fieldset> and <legend> elements. |
| Checks For | Each <fieldset> tag has a <legend> tag. |
Inputs of type ‘checkbox’ or ‘radio’ with the same name attribute value in a single form are contained within a <fieldset>. |
|
| Does Not Check | That groups of logically related <input> elements are contained within a <fieldset> element. |
| Description | Using the summary attribute of the <table> element to give an overview of data tables. |
| Checks For | A table has both a summary attribute and a <caption> element, and that the summary is not identical to the <caption>. |
| Does Not Check | If the table is a layout table or a data table. |
That layout tables do not contain a <summary> element. |
| Description | Ensuring that opening and closing tags are used according to specification. |
| Checks For | Opening and closing tags are correctly nested. |
| There are no closing tags where closing tags are forbidden. |
| Description | Using HTML according to spec. |
| Checks For | Deprecated tags and deprecated attributes. |
| Description | Using HTML form controls and links. |
| Checks For | A <button> has text within the <button> </button> tags or a title attribute. |
Each <fieldset> tag has a <legend> tag. |
|
<input> of ‘type=“button”’, ‘type=“submit”’ or ‘type=“reset”’ has a value attribute. |
|
<input> of ‘type=“image”’ has either an alt or title attribute. |
|
<input> of ‘type=“text”’, ‘type=“password”’, ‘type=“checkbox”’ or ‘type=“radio”’ has either a <label> element associated with it or title attribute. |
|
<select> has either a <label> element associated with it or title attribute. |
|
<textarea> has either a <label> element associated with it or title attribute. |
| Description | Ensuring that elements do not contain duplicate attributes. |
| Checks For | No attribute occurs more than once on any element. |
| Description | Applying text alternatives to images with the Alt entry in PDF documents. |
| Checks For | Checks that images have either a /Alt or /AltText attribute. |
| Description | Creating bookmarks in PDF documents. |
| Checks For | Bookmarks exist in documents greater than four pages. |
| Does Not Check | That the bookmarks link to the correct sections in the document. |
| Description | Using table elements for table markup in PDF Documents. |
| Checks For | The tables have table headers. |
| Does Not Check | That table headers are in the proper reading order. |
| Description | Providing name, role, value information for form fields in PDF documents. |
| Checks For | A name (tooltip) attribute for form fields. |
| Does Not Check | The role, value or state attributes. |
| Description | Setting the default language using the /Lang entry in the document catalog of a PDF document. |
| Checks For | The Language property is set. |
| Does Not Check | That the /Lang value reflects the primary language used in the document. |
| Description | Specifying the document title using the Title entry in the document information dictionary of a PDF document. |
| Checks For | The Title property is set. |
| Description | Language of the page. |
| Checks For | The xml:lang attribute is set in web feeds. |
| The language matches the language of the content. |
| Description | Using both keyboard and other device-specific functions. |
| Checks For | If an event handler is present, the corresponding (mouse or keyboard) event handler is also present. For example, if mouseover is specified, then focus is also specified. |
| Description | Using functions of the Document Object Model (DOM) to add content to a page. |
| Checks For | The presence of any of the following JavaScript functions: document.write, innerHTML, outerHTML, innerText or outerText. |
WCAG techniques are separated into general techniques and technology specific techniques, such as HTML and CSS. In the event that there are multiple techniques that may apply, the WPSS Validation Tool reports failures under only one technique. Additionally, there are a number of WCAG 2.0 techniques that have duplicate tests. WPSS Validation Tool reports failures under only one technique.
The list of techniques below are not reported by this tool.
Failures are reported under technique G142: Using a technology that has commonly available user agents that support zoom.
Failures are reported under technique G142: Using a technology that has commonly available user agents that support zoom.
Failures are reported under technique G142: Using a technology that has commonly available user agents that support zoom.
F62: Failure of Success Criterion 1.3.1 and 4.1.1 due to insufficient information in DOM to determine specific relationships in XML
Failures are reported under technique F77: Failure of Success Criterion 4.1.1 due to duplicate values of type ID.
F70: Failure of Success Criterion 4.1.1 due to incorrect use of start and end tags or attribute markup
Failures are reported under technique G134: Validating Web pages.
F80: Failure of Success Criterion 1.4.4 when text-based form controls do not resize when visually rendered text is resized up to 200%
Failures are reported under technique C28: Specifying the size of text containers using em units.
F86: Failure of Success Criterion 4.1.2 due to not providing names for each part of a multi-part form field, such as a US telephone number
Failures are reported under technique H44: Using label elements to associate text labels with form controls.
F89: Failure of Success Criteria 2.4.4, 2.4.9 and 4.1.2 due to using null alt on an image where the image is the only content in a link
Failures are reported under techniques:
- H30: Providing link text that describes the purpose of a link for anchor elements.
- H91: Using HTML form controls and links.
Failures are reported under technique H32: Providing submit buttons.
Failures are reported under techniques:
- H25: Providing a title using the title element.
- PDF18: Specifying the document title using the Title entry in the document information dictionary of a PDF document.
Failures are reported under technique SCR20: Using both keyboard and other device-specific functions.
Failures are reported under technique H44: Using label elements to associate text labels with form controls
Failures are reported under technique G134: Validating Web pages.
Failures are reported under technique G134: Validating Web pages.
Failures are reported under technique F77: Failure of Success Criterion 4.1.1 due to duplicate values of type ID.
Failures are reported under technique SCR20: Using both keyboard and other device-specific functions.
The Layout and Design checking module of the WPSS Validation Tool performs a number of checks on the structure, layout and design of Web pages. The Validation Tool use a profile of test cases to determine which checks to perform and report on.
The WPSS Validation Tool uses a profile to specify the list of test cases to check and report on. The profiles are:
- SWU – Standard on Web Usability layout and design test cases.
- CLF 2.0 – CLF 2.0 layout and design test cases.
- None – No layout and design checking.
The list of test cases in each profile is outlined in the following pages.
This profile contains test cases for the Standard on Web Usability.
| Description | Template markers. |
| Checks For | All of the required page sections and subsections are found in web pages. The checks are done by looking for id, CSS class or role values on HTML tags. It also checks for required skip links (skip to content) in the page header. Web pages are expected to be implemented using the GC Web Usability theme of the Web Experience Toolkit (WET) templates. |
| Content Pages - Checks for GC navigation bar, Site banner, Content area, Date modified Site footer and Government of Canada footer. | |
| Splash Pages - Checks for Header (Federal Identity Program image), Site titles (left and right), Language links and Terms and conditions footer. | |
| Server Message Pages - Checks for Header (Federal Identity Program image), Site titles (left and right), Language links, Decoration bar (bar above Terms and conditions) and Terms and conditions footer. |
| Description | Archived Web page notice. |
| Checks For | All required archive markers on archived pages. A page is deemed archived if it has half of the markers. |
| Page <title> begins with the word “ARCHIVED” or “ARCHIVÉE”. | |
| The description metadata item begins with the word “ARCHIVED” or “ARCHIVÉE”. | |
A content area <h1> heading begins with the word “ARCHIVED” or “ARCHIVÉE”. |
|
A content area <h2> heading begins with the words “Archived Content” or “Information archivée dans le Web”. |
| Description | Displays the favicon prescribed by the Federal Identity Program. |
| Checks For | That Web pages specify a favicon using a link tag in the page <head> section <link rel=”shortcut icon” href=”fip-pcim/images/favicon.ico” />
|
| There is at most one favicon specified. | |
| The href is not a broken link and references an image file. | |
| Does Not Check | That the favicon image is one prescribed by the Federal Identity Program. |
| Description | Content pages, Federal Identity Program signature. |
| Checks For | An image is present in the GC Navigation bar section. |
| The image alt text is “Government of Canada” on English pages and “Gouvernement du Canada” on French pages. | |
| Does Not Check | The location or size of the image. |
| That the image is one prescribed by the Federal Identity Program. |
| Description | Canada Wordmark |
| Checks For | An image is present in the Site banner bar section. |
| That the image alt text is “Symbol of the Government of Canada” on English pages and “Symbole du gouvernement du Canada” on French pages. | |
| Does Not Check | The location or size of the image. |
| That the image is one prescribed by the Federal Identity Program. |
| Description | Content pages, Official language selection link. |
| Checks For | An optional language link in Government of Canada Navigation bar section. If there are more than the mandatory links, the first link after the mandatory links is expected to be the language link. |
| The link text is “Français” on English pages and “English” on French pages. | |
| Does Not Check | That the link is to the alternate language version of the document. |
| Description | Content pages, Header |
| Checks For | The required Government of Canada Navigation bar links exist with the correct anchor text and href values. |
| There are no more links in the Government of Canada Navigation bar than the required links plus the language link. | |
| There is only one input field for the Search form. | |
| The search text input field has a default. | |
| The search text input field default size is 27 characters. | |
| There is only one button in the Search form. | |
| The label on the Search form button is “Search” on English pages and “Recherche” on French pages. | |
| A single link in the Site Banner, the site title link. | |
| If there are Breadcrumb links, the anchor text of the first link is “Home” on English pages and “Accueil” on French pages. | |
| If there is a Home Breadcrumb link, the href value matches the href value of the site title link. | |
Links in the breadcrumb section appear in <li> tags. |
|
| All links in the site navigation section are text only links (no image links). | |
| The site navigation links are the same (anchor text and href) on all pages. | |
| Does Not Check | That the link in the site banner links to the home page. |
| The location or size of the header elements. |
| Description | Content pages, Body |
| Checks For | A definition list (dl) exists for the date modified subsection. |
| The date modified label appears in a dt tag with one of the following values: | |
| • Date modified:(on English pages) | |
| • Version: (on English pages) | |
| • Date de modification: (on French pages) | |
| • Version: (on French pages) | |
| There is only one date modified label. | |
| The date modified value appears in add tag and that it is not an empty string. | |
| If the date modified value is a date item (label is “Date modified:” or “Date de modification :”), is it a well formed date (YYYY-MM-DD). | |
| There is only one date modified value. | |
| If the date modified value is a date item (label is “Date modified:” or “Date de modification :”), see if the value matches the dcterms.modified metadata item. | |
| Does Not Check | The location or size of the body elements. |
| Description | Content pages, Footer |
| Checks For | “Terms and Conditions” (“Avis”) and “Transparency” (“Transparence”) links. |
| Required site footer links, for example, “About us”, “À propos de nous”. | |
| Required site footer link “Contact us”, “Contactez-nous” somewhere in the site footer links area. | |
| All links in the site footer section are text only links (no image links). | |
| The site footer links are the same (anchor text and href) on all pages. | |
| The required GC Footer links exist with the correct anchor text and href values. | |
| There are no more links in the GC footer than the required links. | |
| Does Not Check | The location or size of the footer elements. |
| For optional site footer links. | |
| The presentation aspects of links, for example, bold. | |
| href values of site footer links. |
| Description | Splash pages |
| Checks For | A Federal Identity Program image is present in the header section. |
| The image alt text is “Government of Canada / Gouvernement du Canada” on splash pages with the “English” language button to the left “Gouvernement du Canada / Government of Canada” on splash pages with the “Français” language button to the left. | |
| A left and right site title. | |
| The site titles are not empty strings. | |
| There are “English” and “Français” language links. | |
| An image (wordmark) is present in the language selection section. | |
| The image alt text is “Symbol of the Government of Canada / Symbole du gouvernement du Canada” on splash pages with the English language button to the left “Symbole du gouvernement du Canada / Symbol of the Government of Canada” on splash pages with the Français language button to the left. | |
| There are “Terms and Conditions” and “Avis” links. | |
| The order of the links matches the order of the language links. | |
| Does Not Check | The location or size of the splash page elements. |
| That the language links reference the home pages. |
| Description | Server message pages |
| Checks For | A Federal Identity Program image is present in the header section. |
| Checks that the image alt text is “Government of Canada / Gouvernement du Canada” on bilingual server pages with the English site title to the left “Gouvernement du Canada / Government of Canada” on bilingual server pages with the French site title to the left. | |
| “Government of Canada” on English server pages. | |
| “Gouvernement du Canada” on French server pages. | |
| An image (wordmark) is present in the header section. | |
| Checks that the image alt text is “Symbol of the Government of Canada / Symbole du gouvernement du Canada” on bilingual server pages with the English site title to the left “Symbole du gouvernement du Canada / Symbol of the Government of Canada” on bilingual server pages with the French site title to the left. | |
| “Symbol of the Government of Canada” on English server pages. | |
| “Symbole du gouvernement du Canada” on French server pages. | |
| A left and optional right site title. | |
| The site titles are not empty strings. | |
| The site titles are links. | |
| Does Not Check | The location or size of the server message page elements. |
| That the site title links reference the home pages. | |
| The href values of links. |
The Web analytics checking module of the WPSS Validation Tool performs a number of checks on the encoding of Web pages. The Validation Tool uses a profile of test cases to determine which checks to perform and report on.
The WPSS Validation Tool uses a profile to specify the list of test cases to check and report on. The profiles referred to are:
- TBS Web Analytics – Standard on Privacy and Web Analytics test cases.
- None – no web analytics checking
A list of test cases is outlined in the following pages.
This profile contains test cases for the Standard on Privacy and Web Analytics.
| Description | Web Analytics De-Identification |
| Checks For | The use of the anonymize IP feature of Google web analytics on Web pages that use Google web analytics. |
| Does Not Check | Other web analytics packages. |
The Web interoperability checking module of the WPSS Validation Tool performs a number of checks on the structure, encoding and presentation of Web pages and Web feeds. The Validation Tool uses a profile of test cases to determine which checks to perform and report on.
The Validation Tool uses a profile to specify the list of test cases to check and report on. The profiles referred to are:
- SWI – Standard on Web Interoperability test cases.
- None – no interoperability checking
A list of test cases is outlined in the following pages.
This profile contains test cases for the Standard on Web Interoperability.
| Description | Web Feed Requirements |
| Checks For | A Web site’s news feeds are created according to the Atom standard. |
| There is an Atom news feed available on the Web site for all non Atom (RSS) news feeds. Atom and RSS feeds match if they have the same title. | |
| The xml:lang attribute declares the language of a feed. | |
| Atom feeds contain all required tags to structure and describe Web feed entities. | |
The Atom feed’s ‘self’ link (<link rel=“self”>) links to the web feed. |
|
The Atom feed’s <id> value is unique. |
|
If the following tags <author>, <id>, <name>, <published>, <title>, <updated>, <uri> are present, that they contain content. |
|
The format of the Atom tag’s <published> and <updated> content is a valid date. |
|
| Atom entries for a tag. If the references the HTML version of the entry, the entry attributes match these HTML document’s metadata values. | |
• <title> matches dcterms.title
|
|
• <updated> matches dcterms.modified
|
|
• <published> matches dcterms.issued
|
|
• <author> <name> matches dcterms.creator
|
|
The Atom entries <id> values are unique within a web feed. |
|
All <uri> values are URLs. |
|
| Does Not Check | That the feeds contain frequently updated content. |
That the <uri> value is the URL of primary departmental Web site. |
| Description | Character Encoding Requirements |
| Checks For | UTF-8 is used for encoding of HTML Web pages and Web feeds. |
| Description | Mark-up Language Requirements |
| Checks For | Checks that HTML5 is used for encoding HTML Web pages. |
Checks that a rel attribute appears in <link> tags. |
|
Checks that any rel attribute contains a valid value for <a>, <area> and <link> tags. |
|
Checks that <link> tags that reference CSS files have the value “stylesheet” in the rel attribute. |
|
Checks that <a> or <area> tags that reference documents of the current site do not have the value “external” in the rel attribute. |
|
Checks that <a> or <area> tags that reference non text/html (e.g. PDF) documents in the same domain, with the same title, the value “alternate” in the rel attribute. |
|
| Does Not Check | That specific HTML5 semantic properties are used where applicable. |
| That HTML5 link types are used where applicable. | |
| That links to CSS files outside the current site have the value external in the rel attribute. | |
| Any other rel attribute values. |
The list of valid rel attribute values is taken from the following sources
- http://www.w3.org/TR/2011/WD-html5-20110525/links.html#linkTypes
- http://microformats.org/wiki/existing-rel-values#HTML5_link_type_extensions
| Description | HTML data requirements |
| Checks For | Checks that RDFa Lite syntax is used. |
| Checks that schema.org is the primary vocabulary. | |
| Does Not Check | Properties or values. |
This module of the WPSS Validation Tool performs a number of departmental specific tests on Web documents. A profile of test cases is used to determine which checks to perform and report on.
The Validation Tool uses a profile to specify the list of test cases to check and report on. The list of available Departmental Check profiles is:
- PWGSC SWU – test cases for
- Common – common test cases.
Below is the list of test cases in each profile.
Checks that language of the URL matches the language of the content. The URL language is determined from the page address by:
- One of the folder names is a language (english) or a three-letter ISO 639-2/T language code (eng).
- The file name is terminated by a three-letter ISO 639-2/T language code (-eng as in menu-eng.html).
- The three-letter ISO 639-2/T language code is a parameter or variable in the query string (index.cfm?lang=eng)
The language of the content is determined by analyzing the text of the Web document using a text categorization tool.
Check for duplicate headings within a document. A heading is duplicate if:
- It has the same text as one of its parents (a
<h2>having the same text as its<h1>). - It has the same text as one of its peers (two
<h2>having the same text under the same<h1>).
Checks for multiple documents of the same format, for example HTML, with the same title. Documents of different formats, such as HTML and PDF, can have the same title.
Checks that the title of an HTML document and its corresponding PDF format version, if one exists, have the same title. An HTML and PDF document are deemed to be different formats of the same document if their URL is identical with the exception of the file name suffix.
For example, document-eng.html and document-eng.pdf.
Checks that the number of headings match in documents that are available in multiple languages. For example, document-eng.html and document-fra.html.
Checks that the heading levels (<h1>, <h2> …) match in documents that are available in multiple languages.
Checks that the <title> and the dc.title metadata content match.
| Description | Heading Structure |
| Checks For | Headings are properly nested. For example, <h1> followed by <h2>, <h2> followed by <h2> or <h3>, <h3> followed by <h3> or <h4> and so on. |
There is at most one <h1> in the content section. |
| Description | Invalid e-mail address in anchor in mailto link. |
| Checks For | The anchor text in a mailto: link matches the address in the mailto: attribute and verifies that the address is well formed. |
| Does Not Check | That the e-mail address is a valid address. |
| Description | Baseline Technologies |
| Checks For | If s are used that the DOCTYPE is ‘Frameset”. |
| If XHTML is used, that the version is 1.0 or later. | |
| If HTML is used, that the version is 5.0 or later. |
| Description | Template integrity |
| Checks For | All references to template files (images, CSS, JavaScript) are to the same web server. |
| A manifest file in the template files directory on the web server. | |
| All files listed in the manifest exist on the server with the correct checksum, that is, they have not been modified. | |
| HTML web page supporting files (CSS, JavaScript) are from the template files. | |
| The template package version is not out of date. | |
| Does Not Check | If there are extra files in the template directory on the web server. |
| Description | Page addresses |
| Checks For | Any language specification in the URL follows the guideline. |
| If the language is specified in multiple places, the language is consistent. | |
| The URL language is determined from the page address as: | |
| • One of the folder names is a language (English) or a three-letter ISO 639-2/T language code (eng). | |
| • The file name is terminated by a three-letter ISO 639-2/T language code (-eng as in menu-eng.html). | |
| • The three-letter ISO 639-2/T language code is a parameter or variable in one of the first three parameter/variable pairs of the query string (index.cfm?lang=eng). |
The HTML document features module of the WPSS Validation Tool reports which HTML documents contain certain HTML features, such as forms or tables. A profile is used to determine which features to report on.
The tool uses a profile to specify the list of features to report on. The list of available HTML Features profiles is:
- All –all HTML Features.
Pages that contain the following HTML tags or tag attributes are reported.
<applet> |
<onchange> |
<onload> |
<onselect> |
<embed> |
<onclick> |
<onmousedown> |
<onsubmit> |
<form> |
<ondbclick> |
<onmousemove> |
<onunload> |
<frame> |
<onfocus> |
<onmouseout> |
<pre> |
<ismap> |
<onkeydown> |
<onmouseover> |
<table> |
<object> |
<onkeypress> |
<onmouseup> |
<tabindex> |
<onblur> |
<onkeyup> |
<onreset> |
<usemap> |
Pages that contain references to the following non-HTML document types, such as links are reported.
- Flash
- Multimedia (video or audio)
- Non-HTML (PDF, MS Word, text)
Pages that contain any of the following features are reported.
- Links that open new or popup windows (target=”_blank”).
- Documents marked as Archived on the Web.
A number of content reports are generated by the WPSS Validation Tool that help the user perform content related tests. These reports are in HTML format and are generated by going to File > Save As from the WPSS Validation Tool Results Window. The report types and details are outlined below.
The Image Details report provides information for all images referenced by all documents analysed by the Validation Tool, either through a site crawl or list of URLs. The report file name has a _img.html suffix. It is stored in the same folder as the other results reports.
The report consists of a sorted list of images with the following details:
- The complete URL of the image file.
- The image itself. The report includes an
<img>tag to display the image. - A table that provides:
- The language of the image context; whether it is located on an English or French page.
- The alt attribute value.
- The title attribute value.
- A list of URLs that reference the image file.
The following is a sampling of an image details report.
http://webdev02.tpsgc-pwgsc.gc.ca/clf20/images/lffl.gif
http://webdev02.tpsgc-pwgsc.gc.ca/clf20/images/sig-eng.gif
| lang | alt | title | URLs that contain the image |
|---|---|---|---|
| eng | “Public Works and Government Services Canada” | “” | * http://webdev02.tpsgc-pwgsc.gc.ca/comm/cn-cu-eng.html |
| * http://webdev02.tpsgc-pwgsc.gc.ca/comm/index-eng.html | |||
| * http://webdev02.tpsgc-pwgsc.gc.ca/comm/services-eng.html |
The Heading Outline report provides a list of all the headings found within the content area of all the documents analysed by the Validation Tool, either through a site crawl or a list of URLs. The report file name has a _h.html suffix. It is stored in the same folder as the other results reports.
The report consists of a sorted list of document URLs with the following details.
- The complete URL of the document.
- The
<title>of the document. - A list of all headings and heading level in the content area.
The following is a sampling of a heading outline report.
http://webdev02.tpsgc-pwgsc.gc.ca/comm/cn-cu-eng.html
Title ="Contact Us - PWGSC"
- H1: Contact Us
- H2: General Inquiries
- H3: Mail
- H3: E-mail
- H3: Form
- H2: Privacy Notice Statement