Tingtun Checker

What can the Tingtun Checker be used for?

The Tingtun Checker automatically detects barriers the in your web page and gives you immediate feedback.

Can the Tingtun Checker find all barriers?

No, the Tingtun Checker can not find all barriers. It can only detect barriers which can be detected automatically (around 20% of all the tests defined in UWEM).

For a complete overview of barriers on your web site, a manual evaluation is required. However, due to the high level of detail, a manual evaluation of web accessibility takes much more time and effort than an automated assessment. Only a small number of pages can be tested by one person.

In contrast, automated checks can cover all much larger number of web sites and a also a larger number of pages per site. The process can run with a minimal amount of human supervision.
The low cost allows more frequent re-assessments of the web sites.

Why is the result from the eAccessibility checker different from other evaluations, such as the eGovernment quality assessment made by the Agency for Public Management and eGovernment (Difi)?

The Tingtun Checker evaluates only one page, and is evaluating according to UWEM.

Both the Agency for Public Management and eGovernment (Difi) and eGovMon approaches have selected a subset of all possible indicators of web accessibility. There is some overlap, but the emphasis is put on different parts.

Only the accessibility component of the eGovernment quality assessment percentage score should be considered in the comparison because usability and content are not covered by eGovMon. In Difi's assessment a higher percentage score corresponds to better accessibility, whereas in eGovMon it is the other way around; a high percentage score corresponds to a high number of potential barriers and thus to poor accessibility.

More information is available in the Comparison between eGovMon and norge.no (PDF in Norwegian). norge.no merged with two other public agencies to form Difi on 1 January 2008.

 

What is the difference between the Tingtun Checker and other tools such as CynthiaSays or the (X)HTML Validator by the W3C?

Tools like the (X)HTML Validator by the W3C test the code for validity.
But accessibility is more than just valid code. That is why the W3C HTML tests are integrated into the Tingtun Checker together with 22 further accessibility tests.

Compared to CynthiaSays and other tools, that check accessibility, there will be many similarities. But different approaches put the emphasis on different parts.

I get score 0 from the Tingtun Checker. Does this mean my web page is completely barrier free / accessible?

This may not be the case. No barriers detected by the Tingtun Checker (score 0) means there were no barriers detected using the automatic tests.

There may still exist barriers which the Tingtun Checker could not detect. For a verification that you web page is completely barrier free / accessible, manual tests performed by an accessibility expert are needed in addition.

Why is it that reliable and well linked sites like Google also fail 82 tests?

The accessibility of websites is not correlated with how known the website is, but with how it is implemented.

The Tingtun Checker uses 23 tests to evaluate the document automatically and you can get more information on the passed/failed tests on the result page.