Frequently Asked Questions

• What accessibility checks can aDesigner perform?
• What is the difference between aDesigner and other accessibility checkers?
• In the blind visualization mode, why does the background color on the right side of the screen become darker?
• Is aDesigner available on Linux® ?
• Which language versions of Windows does aDesigner support?
• Are there any language restrictions for Web pages?
• The overall rating in the blind mode presents three types of ratings: compliance, listenability, and navigability. Why are there three measurements?
• Why should we need to consider issues besides compliance?
• What is the problem map in the overall rating pane in the low-vision mode?

First, it checks regulations and guidelines such as Section 508 of the U.S. Rehabilitation Act, the W3C WAI Web Contents Accessibility Guidelines (WCAG), JIS (Japan Industrial Standard), and IBM's checklist. We call such items to be checked compliance items.

Second, it checks usability problems faced by people with visual impairments, going beyond compliance. An author can experience how low vision users see the Web pages by using "low vision simulation" modes, and an author can also understand how blind users listen to and navigate through the pages by using "blind visualization."

Back to index

Existing checkers mostly check the compliance items described above. For example, there is no tool for visualizing the time it takes to reach each element using voice browsers, nor is there any tool for detecting the problematic parts for low-vision users based on image-processing techniques. aDesigner tries not only to evaluate compliance but goes beyond compliance.

aDesigner synchronizes the error location with the browser view position, so an author can easily find out which part of the page has a problem.

aDesigner also has effective features for handling ALT texts. (ALT text is used as an alternative text for images, and voice browsers read such ALT texts for the images.) ALT texts are very important for voice browser users, but the proper usage of ALT texts is not widely known. aDesigner tells you if the ALT texts are not being used properly.

Back to index

The darker color indicates that it takes more time to get to the position using a voice browser or screen reader. A solid black background means it takes more than 90 seconds to get to that position.

Back to index

No; it only runs on Windows® XP or Vista.

Back to index

The aDesigner works with the English and Japanese versions of Windows, and the messages and descriptions are available in English and Japanese.

Back to index

In the low-vision mode, Web pages in any language can be simulated.

In the blind mode, English and Japanese languages are handled properly. Western European languages will be added later.

Back to index

The aDesigner provides three rating results for the blind mode. Compliance is basically a binary decision from the checklists; however, it is also very important to check how well the blind can hear as well as how quickly they can navigate in the page.

Back to index

Compliance is necessary to conform to the regulations and guidelines. However, compliance does not always cover all of the issues that visually impaired people face when navigating through Web pages. Therefore aDesigner evaluates other usability issues.

Back to index

The problem map indicates the positions of the problems on the target Web page. This helps authors understand which parts of the page have problems.

Back to index