ATutor
From Wikipedia, the free encyclopedia
ATutor course home page |
|
Developer: | Adaptive Technology Resource Centre University of Toronto |
---|---|
Latest release: | 1.5.3.3 / 30 November 2006 |
OS: | Cross-platform |
Use: | Learning Management System |
License: | GPL |
Website: | [1] |
ATutor is an Open Source Web-based Learning Content Management System (LCMS) designed with accessible and adaptability in mind. It is a tool used to develop and manage online courses, much like other Learning Management Systems (LMS), but with the added ability to create, share, and manage learning content.
[edit] Background
ATutor was first released in late 2002. It came in response to two studies conducted by the developer in the years prior that looked at the accessibility of online learning systems to people with disabilities. Results of the studies showed none of the popular Learning Management Systems at the time even provided minimal conformance with accessibility guidelines. At the time a blind person for instance, could not participate fully in online courses.
Two, of many, accessibility features in the system are text alternatives for all visual elements, and keyboard access to all features. With these a blind person can, with the help of a screen reader, listen to the entire interface of the system, and he or she can access the system without needing a mouse. These features also allow ATutor to adapt to a wide variety of technologies including cell phones, personal data assistants (PDAs), and text-based Web browsers, to name a few. A full list of accessibility features can be found on the ATutor Web site.
As ATutor developed, a content authoring tool was introduced that prompts content developers to create accessible learning materials. It might prompt authors to add a text alternative if they forget to include one when adding an image, for instance. The authoring tool also includes a Web service that evaluates the accessibility of authored content against various international standards. In addition to creating accessible content, the tool is itself accessible, allowing a blind user to create content themselves.
A second goal in the development of ATutor was to create a system that was easily adapted to any teaching/learning scenario that might arise. Four main areas have been focused on in an effort to create a highly adaptable system: themes, privileges, tool modules, and groups.
In mid 2004 ATutor introduced its theme system to allow administrators to easily customize the look and layout of the system to their particular needs. Themes are used to give ATutor a new look, to give categories of courses their own look, or they can be used to provide multiple versions of ATutor on a single system, from which users could choose one as a preference setting.
By early 2005 the privilege system had been introduced which allowed instructors to assign tool management privileges to particular members of a course. Instructors could then create assistants or course tutors that had limited control over any of the authoring or management tools. They could also assign partial or all privileges to all members of a course to create a workspace where students could participate fully in the development of course materials.
Later in 2005 tool modules were introduced into the system. Essentially, the learning tools that already existed in ATutor were separated from the core system. This allowed ATutor administrators to customize the system, deciding which learning tools would be available on the system, and which default tools would be available in a newly created course. It also allowed instructors to choose from the available tools only those that might be used in a particular course. Perhaps the most important aspect of the modules system was to allow developers to easily extend ATutor with new features. Third party programs could be integrated into the system. New tools could be created by any developer to customize the system to their particular needs. And, ultimately, spread the development of ATutor as a whole from its central core of developers during its early years, out into its community of users.
Groups were introduced in early 2006. Groups essentially allowed instructors to create sub-courses within a course, where he or she maintains control over the management of the larger course, but can assign course members to groups that have their own group specific versions of many of the tools available to the instructor or to the course as a whole.
ATutor is now used around the world, available in 30+ languages, and has more than 50 modules available.
TBC