[nabs-l] Fwd: TestPage 1.3 released

[David Andrews]

>Date: Tue, 2 Feb 2010 17:59:49 -0500 (EST)
>From: Jamal Mazrui <empower at smart.net>
>To: dean at topdotenterprises.com, jeff at jeffbishop.com,
>         editor at blindaccessjournal.com, curtischong at earthlink.net,
>         lpovinelli at aol.com, sweeties2 at verizon.net, pyyhkala at gmail.com,
>         kkellyp at gmail.com, skp1066 at aol.com, mmazrui at aol.com,
>         kforde-mazrui at virginia.edu, jansley2 at gmail.com, gosarah at yahoo.com,
>         john.oliveira at state.ma.us, paltschul at centurytel.net,
>         dbmusic at cybernex.net, don.barrett at ed.gov, rmshah at starpower.net,
>         mark.loeffler at ed.gov, dandrews at visi.com, scott.marshall at fcc.gov,
>         lazzaro at rcn.com, john at jamsite.us, jaws at hartgen.org
>Subject: TestPage 1.3 released
>
>http://EmpowermentZone.com/tpgsetup.exe
>
>This version generates a report in structured text format, including 
>a new section containing the source code of the page tested.  This 
>is useful so that a web developer can easily reference the HTML that 
>was tested, locating the places where issues were raised in other 
>sections of the report.
>
>Below I am pasting the introductory section of the TestPage documentation.
>
>Jamal
>
>TestPage is a command-line utility and dialog interface for doing a 
>simple, automated test of a web page for problems related to 
>accessibility for users with disabilities, or to other aspects of 
>HTML validity according to standards of the World Wide Web 
>Consortium, located at
>http://w3.org
>
>The command-line syntax is
>
>TestPage.exe URLPath FilePath
>
>The first parameter specifies the URL to test and the second 
>parameter specifies the file name of the resulting report.
>
>The TestPage installer, tpgsetup.exe, creates a shortcut for 
>launching an input box that prompts for the URL to test, which is 
>then passed onto the command-line utility.  The default hotkey for 
>invoking the input box is Alt+Control+Shift+T.  This may be changed 
>by modifying properties of the TestPage shortcut on the Windows desktop.
>
>The installer also creates a TestPage program group in the Windows 
>Start Menu, with options for launching the program, unstalling it, 
>browsing generated reports, or reading this documentation.  The 
>default program folder is
>C:\Program Files\TestPage
>
>The TestPage dialog is built with the PowerBASIC compiler from
>http://PowerBASIC.com
>Source code is also provided for VBScript and Visual Baisic .NET 
>versions of the same, simple dialog.
>
>If a URL is passed as a command-line parameter to TestPageGui.exe, 
>then it will be the default value in the input box.  If no parameter 
>is passed and Internet Explorer is open, the URL of its  web page is 
>used as the default value.  The domain name of the URL tested is 
>used for the file name of the report.  It is a structured text file 
>with sections titled web Accessibility Problems, HTML Validity 
>Problems, and Source Code of the Page.  The report is automatically 
>opened with the program associated with .txt files in the Windows 
>registry.  The default is Notepad, which may be changed, e.g., via 
>the Open With command on the context menu of Windows Explorer.
>
>The command-line utility, TestPage.exe, does the main work.  It is 
>built with the Ruby language and several related 
>packages.  Subsequent sections of this documentation provide more 
>detail using excerpts from material on the web.
>
>Please note that this program is only intended as a convenient, 
>mechanized test of web accessibility.  Hopefully, its ease of use 
>will enable more people to do accessibility checks and send them to 
>web developers, as appropriate.  In addition, since TestPage is open 
>source, programmers are encouraged to contribute improvements.  A 
>list of more sophisticated web evaluation tools is available at
>http://www.w3.org/QA/Tools/