WWW2003 Poster Template

EvalIris - A Web Service for Web Accessibility Evaluation

Julio Abascal
University of the Basque Country
Manuel Lardizabal 1; E-20018 Donostia
Phone: +34 943 018000; Fax: +34 943 219306
julio@si.ehu.es
Myriam Arrue
University of the Basque Country
Manuel Lardizabal 1; E-20018 Donostia
Phone: +34 943 018000; Fax: +34 943 219306
myriam@si.ehu.es
Nestor Garay
University of the Basque Country
Manuel Lardizabal 1; E-20018 Donostia
Phone: +34 943 018000; Fax: +34 943 219306
nestor@si.ehu.es
Jorge Toms
University of the Basque Country
Manuel Lardizabal 1; E-20018 Donostia
Phone: +34 943 018000; Fax: +34 943 219306
jorge@si.ehu.es

ABSTRACT

A Web Service, with the name of EvalIris, has been designed to evaluate the accessibility of HTML pages is presented. The analysis is based on easily updateable accessibility criteria, making this tool able to easily incorporate new sets of guidelines and updates. It can be used both, as an on-line stand-alone application, and as a web service. In this last case, it can be used by any other application to perform accessibility analysis and, in this way, to extend its features.

Keywords

Web Accessibility, Web Service, XML Schema.

1. INTRODUCTION

The Web Accessibility concept refers to the possibility of accessing any web content by anyone regardless to circumstances such as impairments, platforms, devices, browsers, etc. This is a very wide idea that must be clearly specified in order to be able to verify its application. For this reason, some organizations have issued web accessibility criteria as sets of guidelines. Currently, the most relevant and universally accepted guidelines are the ones produced by World Wide Web Consortium/Web Accessibility Initiative (W3C/WAI) [6], called Web Content Accessibility Guidelines (WCAG) [4].

Even if the criteria to verify if a web site is accessible are currently quite well defined, it is difficult to verify whether they are satisfied by a web site. There are two main reasons: the size of many web sites, with thousands of HTML code lines, and the difficulty for non-professionals to interpret, understand and verify some of the guidelines. For this reason, a number of tools tools to facilitate web contents accessibility evaluation, such as Bobby [2], TAW [5], A-Prompt [1], etc., have been developed. These tools are based on specific sets of guidelines as Section 508 [4] and WCAG 1.0.

Here we present an automatic accessibility evaluation tool: EvalIris, where accessibility criteria are easily updatable to allow for the rapid incorporation of new accessibility guidelines. This tool has been developed within the IRIS European project [3]. More information on the tool and a fully operating prototype can be found in http://www.sc.ehu.es/acwbbke/EvalIris.html.

2. XML SCHEMA FOR ACCESSIBILITY GUIDELINES

TFrom the analysis performed, it is possible to conclude that the accessibility knowledge included in the WCAG guidelines can be expressed in terms of HTML elements (i.e., tags, attributes). This allows for the creation of a well defined structure to specify accessibility guidelines, to be used as accessibility knowledge repository by the evaluation tool.

Therefore, the easily updatable feature of EvalIris is achieved by expressing the accessibility guidelines in a well defined XML format. For this purpose, a XML Schema has been designed (Figure 1). As seen, the proposed XML Schema follows this pattern: each guideline is defined as a list of checkpoints expressed in HTML tags and their attributes.

This scheme allows for the easy accommodation of new guidelines that adjust this structure into its database. Nowadays, this translation must be carried out manually but a tool to assist the designer to accommodate new guidelines to the XML scheme is being developed.

XML Schema for accessibility guidelines

Figure 1. XML Schema for accessibility guidelines

3. IMPLEMENTATION OF EVALIRIS

Different types of techniques have been used when implementing this Web Service, all based on Java technology. The Web Service runs on a Tomcat server and SOAP (Simple Object Access Protocol) technology is used in the communications, while the core of the system is implemented in Java.

In order to perform the accessibility evaluation, the system interacts with a native XML database (Xindice) where the guidelines transformed in the previously explained XML structure are stored.

3.1 Evaluation Algorithm

The algorithm directly evaluates the mark-up of the web page. EvalIris can perform this in two ways: on the one hand, it allows for the accessibility evaluation of a remote web page starting from its URL and, on the other hand, the mark-up code of then web page can be up-loaded into the EvalIris page in order to be analysed.

When the mark-up is available, it is divided into its HTML components (image, table, header). Afterwards, the accessibility of each component is verified separately. In order to perform this verification, EvalIris has to retrieve accessibility information from the native XML database, taking the accessibility of each component into account.

A number of these accessibility requirements contained in the database are automatically verified by EvalIris, however, there are others that need manual verification. This is because the translations to HTML tags of certain guidelines and checkpoints are hardly attainable. Therefore, if a component does not conform to any automatically verifiable accessibility requirement, an Error will be produced whereas, if this verification requires manual checking, a Warning will be produced. In this way, a set of Errors and Warnings is produced and collected in the final report compiled by the system. This report is also returned in XML format.

The entire process can be seen in Figure 2.

Evaluation process

Figure 2. Evaluation process.

4. CONCLUSIONS

The experience acquired in the development of EvalIris shows that it is possible to express diverse sets of guidelines through a well-defined XML structure that has been designed. In addition, EvalIris has the added advantage that it can be invoked by any application connected to Internet, independently of the programming language and the platform, due to the fact that it has been implemented as a Web Service.

In the future, we will produce a tool that will assist the conversion of the accessibility guidelines into their related XML structures. In addition, we are working on a tool to assist the designer in the repairing of non- accessible web pages.

3. ACKNOWLEDGEMENTS

The work presented in this article has been partially financed by the European Commission within the IST-2000-26211 IRIS project (Incorporating the Requirements of People with Special Needs or Impairments to Internet-based Systems and Services) developed by European Dynamics (GR), Fraunhofer for Institute Applied Information Technology (D); the University of the Aegean (GR); the University of the Basque Country-Euskal Herriko Unibertsitatea (E) and the ISdAC International Association (Information Society disAbilities Challenge) (B).

4. REFERENCES

  1. A-Prompt Accessibility Toolkit Project. Adaptive Technology Resource Center (University of Toronto) and Trade Center (University of Wisconsin), Canada & USA. WD-xml, World Wide Web Consortium, 1998. http://aprompt.snow.utoronto.ca/.
  2. Bobby Version 2.0. HTML Web Analyzer.http://bobby.watchfire.com/bobby/html/en/index.jsp.
  3. IRIS: Incorporating Requirements of People with Special Needs or Impairments to Internet-based Systems and Services. IST-2000-26211.http://www.iris-design4all.org/.
  4. Section 508.http://www.section508.gov/.
  5. TAW Test de Accesibilidad Web.http://www.tawdis.net/.
  6. Web Accessibility Initiative (WAI)http://www.w3c.org/WAI.
  7. Web Content Accessibility Guidelines (WCAG)http://www.w3.org/TR/WCAG10/.