Your browser does not support JavaScript!
* PRODUCTS HOME
* CUSTOM CHECKS
ARROW Q&A
* Check Types
* Share Checks
ARROW Screen Shots
ARROW INFORMATION REQUEST
ARROW ORDER
ARROW CONTACT SALES
ARROW SERVICES
ARROW SUPPORT
ARROW HISOFTWARE BOOK STORE
 
* HiSoftware: Check Types
 
 
Build, Deploy, and Maintain Accessible, Usable and Searchable Content that complies with your quality standards.

Checklist FormOverview of Different Check Types
The custom checkpoint and Report generation tools allow the user to create and run custom validation that meets their unique organizational standards and policies. This testing can be incorporated by desktop users as part of the overall content quality analysis for content that they create and/or for enterprise wide monitoring purposes.
Checkpoint Details - Find Text in Document tab

Find Text in Document Checkpoint
This checkpoint allows you to search for text that in the source of a document. This text can either be plain text, or text marked up with HTML such as <a href="http://www.hisoftware.com/co/privacy.htm">.  Enter the text you wish to search for in the field.

Evaluating
The checkpoint will be evaluated to TRUE if the specified text is either found or not found in the page.  Select either Found or Not Found from the drop-down menu. There is also a checkbox to specify to note the location of the location of the text if it was found. You can also specify to include searching comment tags and script tags in the HTML of the page.  

A comment tag is HTML code formatted as:
<!-- Some Comment Value Here -->

A script tag is HTML code formatted as:
<script>Some Script Code here </script>

Clearing the Include Comments checkbox causes the program not to look for text within the comment or script tags.

Checkpoint Details - Conditional Find Text in Document

Find Text in Document Checkpoint
This checkpoint allows you to search for text that in the source of a document.  If that text is found, then an additional check is performed looking for a second string of text.  The text, in either field, can either be plain text, or text marked up with HTML such as <a href="http://www.hisoftware.com/co/privacy.htm">.  Enter the initial  text you wish to search for in the top field.

Evaluating
The first condition will be evaluated to TRUE if the specified text is either found or not found in the page.  Select either Found or Not Found from the drop-down menu. There is also a checkbox to specify to note the location of the location of the text if it was found. You can also specify to include searching comment tags and script tags in the HTML of the page.  

A comment tag is HTML code formatted as:
<!-- Some Comment Value Here -->

A script tag is HTML code formatted as:
<script>Some Script Code here </script>

Clearing the Include Comments checkbox causes the program not to look for text within the comment or script tags. When the primary condition evaluates to true, the checkpoint will then search for the second string of text.  Enter the second string of text in the second edit field on this screen. The checkpoint will be evaluated to TRUE if the specified text is either found or not found in the page.  Select either Found or Not Found from the drop-down menu.  There is also a checkbox to specify to note the location of the location of the text if it was found.

Checkpoint Details - Element Validation

Element Validation Checkpoints
The Element Validation tab allows you to search for HTML elements on a page and test them based on conditions you set.

  • Name of Element to Validate:  This is the name of the HTML element to validate. For example, if you were going to create a custom element check for an image tag such as <img src=images/hisoftware.gif"> , then you would enter IMG as the element.
  • Name is Case-Sensitive:  If you are searching for elements and need to make a distinction between a IMG and img tag, then select this checkbox.  By default, this checkbox is not checked.
  • Checkpoint Evaluates to true if (All/None/One/the First) of the elements are considered valid:  This checkpoint allows you to decide how this checkpoint evaluates to true.  Because there can be many elements on an HTML page, from just a few to hundreds depending on the tag, you can decide what is a valid element based on your custom criteria.  Based on determining valid elements, you can then with this option decide do ALL elements of this type need to be valid, or NONE of them, or ONE of them, or THE FIRST instance of the element.
  • List Element Locations:  When reporting the results, you can list locations of elements that are considered (Valid/Invalid) and then state whether they are (Failures/Warnings/Note). For example, if your images was invalid, you might consider it a failure.
  • An Element is considered valid when all conditions evaluate to (True/False):  There are three tabs for element conditions (Attribute Condition, Element Condition and Child Element Condition).  You can test using one, two or three of these tabs for your test depending on your needs.  If using only one of the condition tabs, you can decide whether the element evaluates to TRUE or FALSE using this option.  When working with two or three condition tabs, the tabs must all evaluate to either TRUE or FALSE (depending on your selection in the drop-down menu) in order for the element to be considered valid.  If one condition evaluates to true and the other to false, then the element will not be considered valid.

Conditions

Attribute Condition
The attribute condition does allows for testing of attributes of elements. If you wish to test using this condition, make sure the Use the Attribute Condition is checked.

  • Name of Attribute:  This is the name of the attribute that you are testing for.  For example, if you were looking for the alt tag for an image, you would look for the attribute named alt.
  • Name is Case-Sensitive:  If you are searching for attributes and need to make a distinction between a ALT and alt attribute, then select this checkbox.  By default, this checkbox is not checked.
  • Attribute value cannot be null:  If your test condition says that the attribute value cannot be null as in attribute="" then check this checkbox.
  • Attribute value length must be:  You can test to make sure an attribute value length in characters is (greater than/less than/equal to/not equal to) a specified number of characters.
  • Use attribute value comparison:  You can compare an attribute to state that the Comparison type (Must Contain/Must Equal/Must Not Contain/Must Not Equal) the text value contained in the Comparison text field.  You have the option of selecting a Case-sensitive compare.
     

Element Content Condition
The element content condition check tests to make sure an element, such as the <NOFRAMES> tag or other tag has element content.  Element content is test included within the element but is not ASP code or commented code.

  1. Select the Use the Element Content Condition checkbox if you want to use this condition.
  2. Click the Element is Required to contain element content checkbox if element content is required.
  3. If you wish to compare the element content to a specific text string, then click the Use element content value comparison checkbox.  You can compare contents to state that the Comparison type (Must Contain/Must Equal/Must Not Contain/Must Not Equal) the text value contained in the Comparison text field.  You have the option of selecting a Case-sensitive compare.
     

Child Element Condition
The Child Element Condition allows checks that once an element has been located, that a child or additional element is contained within the first element.  For example, if your main or parent element was the table element and you wanted to make sure that every table had a caption element, then you would enter caption as the child element.

  1. Click on the Use the Child Element Condition to use this feature.
  2. Enter the Name of Child Element.
  3. You can choose whether the child element Must Exist, or Must Not Exist in the parent element.