• Open Source e-Learning

Breadcrumb Navigation

Introduction

The aim of this section is to provide a roadmap for the achievement of common accessibility criterias within ILIAS. At first accessibility guidelines address the needs of people with disabilities like blindless, hearing loss, color deficit or distortions. But the guidelines are also a good basis for a set of usability guidelines that improve the user interface handling for all users.

In 1999 the World Wide Web Consortium has released the "Web Content Accessibility Guidelines" (WCAG1, see http://www.w3.org/WAI/). The guidelines have been adopted by many countries. The United States, Australia and EU states have passed national accessibility laws based on the WCAG1. Today the first major revision of the guidelines, the Web Content Accessibility Guidelines 2.0, is under development.

WCAG1 Priorities and Conformance Levels

The guidelines assigned to three priority levels. Based on the priorites three conformance levels are defined.
  • Priority 1: Must be satisfied. Otherwise, one or more groups will find it impossible to access information in the document.
  • Priority 2: Should be satisfied. Otherwise, one or more groups will find it difficult to access information in the document.
  • Priority 3: May be addressed. Satisfying this checkpoint will improve access to Web documents.
Conformance Levels:
  • Conformance Level "A": all Priority 1 checkpoints are satisfied
  • Conformance Level "Double-A": all Priority 1 and 2 checkpoints are satisfied
  • Conformance Level "Triple-A": all Priority 1, 2, and 3 checkpoints are satisfied

Top Priority Issues for ILIAS (Level A)

The next pages outline the 14 Web Content Accessibility Guidelines. The most important issues for the ILIAS development are highlighted with bold text. The first step will be to make ILIAS WCAG1 Level A conformant. This leads to the following top priority issues:
ILIAS developers should respect all accessibility guidelines. Violations of Priority 1 Guidelines will be considered as "Bugs" and should be reported in the Mantis Bug Tracker and be tackled by the relevant developer as soon as possible. This policy may be extended to the other priority levels in the future.