Frequently Asked Questions

Frequently Asked Questions on Web Accessibility Inspector

Q1

When I tried to use Web Accessibility Inspector to check the accessibility of a website, the program stopped with the error message, "Java.lang.StringIndexOutOfBoundExce . . .". What is the possible cause?

If the target HTML or CSS document has a grammatical or semantic problem, the program cannot analyze the content and generates the above message.
If possible, examine the grammar and semantics of the HTML or CSS document and correct any problem, then try to check the website again.

Q2

Web Accessibility Inspector fails to operate. I found a file named "hs err pid????.log" ("????" indicates a number) in the folder where the program is installed.

This problem could occur when Java™ version 6 or later is installed. If you downloaded the Windows® version of Web Accessibility Inspector on June 7, 2007 or before (version 5.00 or before), the program does not operate with Java version 6.
The latest version of the software supports Java version 6. If you are using an older version, please download the latest version.
The latest version is here

Q3

When I double-click on WebAccessibilityInspector.exe to start Web Accessibility Inspector, it fails to launch, with the error messages: "Mismatch in definition file. Web Accessibility Inspector will terminate. ..env/mode.def" and "Mismatch in definition file. Web Accessibility Inspector will terminate. ../checkselect.csv."

There are two possible causes.

[Cause 1:]

This problem occurs when Java version 1.4.2_10 is installed. Web Accessibility Inspector does not operate properly with Java 1.4.2_10 because the Java function for processing character codes is defective. A new version with the corrected function has already been released. Please use the latest Java version (1.4.2_11 or later) or a version other than 1.4.2_10.

[Cause 2:]

The Windows versions of Web Accessibility Inspector distributed on September 27, 2007 or before (version 5.02 or before) were in the zip-compressed format. Files in this format need to be decompressed before use. Some decompressing tools ignore the folder configuration of the compressed file or replace the periods in a file name with other characters (e.g. "mode.ja.def" changed to "mode_ja/def"). This problem can be circumvented by using Windows XP's standard decompressing function or another decompression tool.
The latest version of WebInspector is distributed in .exe format, which does not require decompression. If you are using an old version, please download the latest version.

The latest version is here

Q4

I can diagnose HTML documents stored on the hard disk of my personal computer (PC) and on the storage on the local area network (LAN). However, when I try to analyze HTML documents on the Internet, Web Accessibility Inspector stops with the error message: "An error occurred during URL acquisition: java.net.ConnectException;Connection times out:connect."

This error message is displayed when Web Accessibility Inspector stopped processing because it took too much time to search for the HTML document to be checked. One possible cause is that there is no response from the server because there are too many accesses to the server that contains the HTML document to be checked. Wait for a while and then repeat the procedure.

Q5

Does Web Accessibility Inspector support voice narration environments, such as screen readers?

The current version of Web Accessibility Inspector does not support voice narration. It is impossible to use voice capabilities, irrespective of the settings. Fujitsu intends to promote the increase in Web sites accessible to elderly and visually disabled people by providing Web page designers with Web Accessibility Inspector. Targeting Web site designers and administrators, Web Accessibility Inspector places the checking functions as the highest priority. We are investigating the possibility of voice narration support based on feedback from users.

Q6

We are planning to use Web Accessibility Inspector in our company, or government or municipal office with the intention of accessibility education and diagnosing our Web site. However, our intranet blocks access to the Internet, so we cannot download Web Accessibility Inspector by directly accessing the Fujitsu Web site. Therefore, we would like to load Web Accessibility Inspector on a storage device on our intranet and let our staff download it from the shared storage. Is this permissible?

In an environment where Internet access is not available, distributing or sharing of Web Accessibility Inspector for nonprofit purposes is permitted, but the product must be distributed on your own authority. In addition, please note the following precautions.

1. The Web download page must clearly indicate that the copyright of Web Accessibility Inspector is the property of Fujitsu Limited.

2. It should be clearly stated that the user should read the UserGuide_wi_en.html file contained in the download file before using the software.

The Web Accessibility Inspector Web site provides updates and other announcements. Please visit the website.

Q7

When I tried to check a Web site by specifying its URL I received the error message: "Server connection failed." This was followed by the message: "An invalid URL was specified or a proxy error occurred." I checked the proxy setting but could not find any problem.

This error occurs when you specify a URL without a filename (e.g. http://www.fujitsu.com/). Always enter a URL with the name of the file to be checked (e.g. http://www.fujitsu.com/index.html).

Q8

How can I set the ID and password when I check Web sites through a proxy that requires authentication?

It is impossible to set the ID and password for authentication by a proxy because Web Accessibility Inspector does not support checking through such a proxy. We are investigating the possibility of proxy authentication support based on feedback from users.

Q9

When I tried to check an error on a View on the screen, the checked page and the contents do not correspond (i.e. some images do not appear in the new window).

Such an inconsistency could occur depending on the structure of the Web page (source coding). If it is hard to locate the problem due to this phenomenon, please refer to the source code listing of the Web page.

Q10

The check result screen is too wide so that it is necessary to scroll horizontally in the browser.

This display problem occurs when there are long lines (without return characters) in the source code. To overcome this problem, remove the checkmarks from [Source display] and [Guideline/item order list] in [Set check result format] under [Environment].

Q11

Is it possible to run the English version of Web Accessibility Inspector in other language environments?

Guideline and check result display can not operate properly in other than English language environments (e.g. unstable operation, screen disorder, etc.).