Automatic Tools

What can be checked automatically?

Many programs provide a fast automatic test. After entering an internet address or uploading of files, verification is executed when you click. The extensive result is displayed after a few seconds.

In reality accessibility can not be proven automatically. The test result of an automatic test is incomplete and has significant gaps. For example it is tested if an alternative text is provided for an image. Whether this text describes the image accordingly has to be decided by a human.

Nearly all check steps can only be evaluated by qualified testers. Exceptions are the following which can be verified automatically:

  • Is the HTML and CSS valid?
  • Have automatic page reloads and redirections been avoided?
  • Have deprecated elements and attributes been avoided?

Symbol of W3C for valid CSS   Symbol of W3C for valid HTML 4.0

To the top

A signet for accessibility

There are already symbols on the internet that refer to the accessibility of a site. For some automatic tests symbols are provided. After a successful test these images may be installed into the internet presence. A site with such a symbol is not necessarily accessible as a test can never be processed completely automatically.

Symbol A-Prompt II-AAA   Symbol Bobby approved AAA   Web Access Symbol

Do you want to show on your website that it is designed as accessible?
Symbols should be avoided due to lacking force of expression. Instead, you could describe on a page, which BITV-criteria have been fulfilled and what you have considered. At this point, you could also note who performed the test. For people with disabilities it is important that the internet is accessible. Users are less interested in the presence of a symbol and more interested in accessible operability.

To the top

Precondition for testing

Tools for testing can simplify testing. They can not substitute the verification by an experienced tester. It is important that the tester is sufficiently qualified.

Following skills and experiences are required:

  • Modification of preferences of different browsers
  • Control of testing tools, for example AIS-toolbars
  • Requirements and conditions of BITV and WCAG
  •  Web design (layout, HTML, CSS)

.