| I had my site tested with WATS. Why should I test my site again with CommonLook™? |
| WATS (Web Site Accessibility Testing Service) testing is a good way to get a feel for some of the accessibility issues, and to become more aware of the technologies that people with disabilities use when browsing the Web. CommonLook™ tests for all W3C Priority 1 and 2 checkpoints and reports on all instances of non-compliance. |
| How does CommonLook™ compare to content management products that support CLF compliance? |
|
It doesn't. Content Management, and similar technologies, focus on helping create, manage and present the contents of a Web site. CommonLook™, on the other hand, is a quality assurance tool that checks for compliance from the point of view of the person browsing the web site.
In the traditional software development lifecycle, content management products are analogous to development and delivery technologies, while CommonLook™ is a testing/quality assurance tool.
|
| I have a Web site that was developed using a variety of technologies. Can CommonLook™ verify my site for CLF compliance? |
| Yes. The way CommonLook™ verifies a site is independent of the technology that was used to create the site. |
| How much will my productivity increase if I were to use CommonLook™ to verify my site? |
| A tester utilizing CommonLook™ will take less than 5 minutes per Web page. Assuming it takes 4 hours, on average, to manually complete the compliance checklist (which typically has approximately 70 items to be checked) for a single page, your productivity will increase over 40 times. This translates into significant savings in time and money, as well as more comprehensive and consistent testing. |
| Can CommonLook™ fix compliance problems? |
| No. Since CommonLook™ is technology-independent, it is not possible, at this point, to automatically fix the problems. However, CommonLook provides comprehensive information to make it possible to pinpoint and fix the problems. |
| Can CommonLook™ verify my entire site at once? |
| Yes. The most efficient way to run CommonLook™ is to select the root of the site (or a folder within the site) and activate the verification for the automatic checkpoints. This will run unattended. The tester can then verify the "assisted" checkpoints (which require operator intervention) afterwards. |
| Does CommonLook™ perform incremental verification? |
| Yes. CommonLook™ will only verify pages if they have changed or if they weren't tested for a specific checkpoint. |
| What types of reports are provided with CommonLook™? |
CommonLook™ provides reports that:
- Give senior management a high-level view of the compliance status of an entire enterprise, including all sub-sites.
- Provide site management with a high-level view of the compliance status of a given Web site.
- Allow development managers to track the compliance status on a per page basis.
- Help developers fix the compliance issues by providing comprehensive information on the cause of the problems.
|
