No, the Checker can not find all barriers. It can only detect barriers which can be detected automatically. For a complete overview of barriers on your web site, a manual evaluation is required. However, a manual exhaustive evaluation of web accessibility is generally very labor intensive. In addtion to identifying barriers, the Checker also provides reports about parts of the web page that need further human judgment to confirm the accessibility. For instance test 2.4.6-2 reports problems with labels for form controls. If a label is defined the user of the checker is asked to verify that the label describes the purpose of the form control.

We used a subset of sites from the European eGovernment report from 2012. The subset includes a selection of national sites like tax and social welfare and a selection of municipalities.

The Checker automatically detects barriers and gives immediate feedback.

You can not use any automatic tool for certification of accessibility. Automatic tools can only be used to document that a site has barriers or, at best, has no barriers that can be automatically detected.

The page score is calculated from the intermediate results per Success Criterion. Where barriers are aggregated per success criterion. For a full overview of the calculation please refer to the report on Integration methodology (D4.1) available in the deliverables top

The site score is an average of the page scores weighted according to their size. For a full overview of the calculation please refer to the report on Integration methodology (D4.1) available in the deliverables top

This may not be the case. No barriers detected only means there were no barriers automatically detected. For a verification that your web page is completely barrier free / accessible, manual tests performed by an accessibility expert are needed in addition.

Not necessarily. The score is calculated based on the automatically detected barriers, aggregated according to Success Criteria. This means there may be barriers not found and that one user may percieve a better quality of the same site than an other user. However all sites in one benchmarking list are checked with the same set of tests and therfore can give an indication of the accessibility performance.

The colours reflect the score and how many tests passed and failed. Red means worst score and green means best score.

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 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. Please also note that formally, validation is not required for WCAG 2.0 conformance.

The test can be found at http://checkers.eiii.eu/en/tests/

You can find this in the list of checked pages of the site results.

W3C has compiled Web Accessibility Evaluation Tools List.

The tools available for interactive use are also used for the benchmarking. For more information on the available services please contact us.