How to develop accessible Information Systems: a practical case in tourism and proposal of a roadmap to support the development of accessible solutions

Abstract

Abstract Purpose The right to tourism and leisure has become a crucial aspect of society. In that sense, through more accessible tourism, it is possible to improve travel conditions for people with disabilities (PwD). Nonetheless, barriers still exist, with the lack of information about accessibility conditions, as well as communication accessibility itself, representing some of the main obstacles. Information systems (IS) can help overcome these hurdles. However, it is verified, that methodologies to support the development of accessible IS are currently very scarce. Thus, this study intends to develop an accessible IS for accessible tourism and propose a roadmap to support the creation of accessible IS solutions. Methods To obtain the intended accessible tourism solution, an action research methodology was followed, which involved adapting already established frameworks, that combine Agile development and user-centered design techniques. Adjustments were made to incorporate accessibility, taking into consideration the requirements of the accessible tourism market. Results In this study, a web application named access@tour by action was created. This mobile solution is capable of improving information management within the accessible tourism market. From this experimental study, a proposal for a methodological roadmap emerged. This roadmap helps better understand how to develop accessible IS, by demonstrating techniques for gathering accessibility requirements and validating them. Conclusion The access@tour by action is a much-needed solution, to enhance accessible tourism conditions. The roadmap is adaptable and suitable for IS projects involving accessibility, regardless of the area. Both results provide a better perspective on how to integrate accessibility during the development of IS, possibly supporting future researchers in creating accessible solutions.

Cite this work

No public copy is stored for this record, so only the metadata is cited.

Stored only when both papers are in the corpus — 2 citations exist upstream.

Papers that cite the same references — the relational fallback while embeddings are still backfilling.