Accessible calendar

The Product/Outcome
Exploitation Plans
Intellectual Property Rights
Technical & Socioeconomic considerations/challenges and impact
Collaborators and Future Work

The Product/Outcome
  1. Title of (final) product/outcome: Accessible Calendar application
  2. Developer (AEGIS beneficiary): CTU
  3. Purpose/main functionality & intended use: Calendar application that is providing accessible interface to online calendar solutions such as Google Calendar. Application can be used by developers as an example but also by end-users. See more in D3.5.1a and D1.4.2 (downloadable from here)
  4. Restrictions: Internet connection is required
  5. Main innovation and comparison to the State of the Art: Accessible and more efficient interface to online calendar solutions for impaired users. Application is created from accessible WAI-ARIA enabled widgets and provides better support for group time planning for visually impaired in comparison to standard calendar applications. The main innovation is that it is accessible and more efficient interface to online calendar solutions for impaired users.
  6. Maturity level/Stage: Accessible Calendar Application is finished
  7. Open Source (Yes/No): Yes
  8. Download/info: (user:aegis, password:cvut )
  9. End-user documentation:
  10. Contact details (of the principal developer): Jan Vystrcil ( This e-mail address is being protected from spambots. You need JavaScript enabled to view it )
Exploitation Plans
  1. Uptake by Open Source community: This application is not intended for further usage by third parties. It is an experimental implementation for testing and verification purposes
    • License: LGPL licence
Intellectual Property Rights
  1. Intellectual property rights: None besides open source protection
Technical & Socioeconomic considerations/challenges and impact
  1. Marketability: Application will be promoted within the University courses (e.g. Principles of mobile application design). It is expected that students will use this application as an example how to develop accessible applications.
  2. Deployment (so far or near future): Application is not intended for sale as it is developed mainly for demonstration and educational purposes.
  3. Expected impact: With the increasing importance of collaborative applications in the workplace, the ability for all users to be able to fully use those applications is critical. Unemployment is a major problem for people with disabilities, and employment requires the effective use of workplace software applications, such as email, intranets, chat tools, and shared calendars. If a workplace software tool is technically inaccessible, this may have the unintended effect of social exclusion from certain workplace activities, and may lower productivity. For instance, how would a person who is blind be perceived by colleagues, if they cannot do group scheduling, using the same web-based calendar that all of the other employees use?
  4. Customers: Students who wish to be trained on accessible web applications for visually impaired users
  5. Commercialisation barriers: Partly dependent on Google calendar services.
Collaborators & Future Work
  1. Collaborations:
  2. Further research and development steps-future collaboration: Based on the experience gained from the development of accessible calendar application we would design accessible applications from other domains – collaborative work with shared online documents.