Developing Accessible Mobile Applications with Cross-Platform Development Frameworks

We illustrate our experience, gained over years of involvement in multiple research and commercial projects, in developing accessible mobile apps with cross-platform development frameworks (CPDF). These frameworks allow the developers to write the app code only once and run it on both iOS and Android. However, they have limited support for accessibility features, in particular for what concerns the interaction with the system screen reader. To study the coverage of accessibility features in CPDFs, we first systematically analyze screen reader APIs available in native iOS and Android, and we examine whether and at what level the same functionalities are available in two popular CPDF: Xamarin and React Native. This analysis unveils that there are many functionalities shared between native iOS and Android APIs, but most of them are not available neither in React Native nor in Xamarin. In particular, not even all basic APIs are exposed by the examined CPDF. Accessing the unavailable APIs is still possible, but it requires additional effort by the developers who need to write platform-specific code in native APIs, hence partially negating the advantages of CPDF. To address this problem, we consider a representative set of native APIs that cannot be directly accessed from React Native and Xamarin and we report challenges encountered in accessing them.

[1]  Vincent Naessens,et al.  A Quantitative Assessment of Performance in Mobile App Development Tools , 2015, 2015 IEEE International Conference on Mobile Services.

[2]  Dragan Ahmetovic,et al.  WordMelodies: Supporting Children with Visual Impairment in Learning Literacy , 2019, ASSETS.

[3]  Yagiz Onat Yazir,et al.  Tradeoffs in cross platform solutions for mobile assistive technology , 2013, 2013 IEEE Pacific Rim Conference on Communications, Computers and Signal Processing (PACRIM).

[4]  Evangelos Bekiaris,et al.  Towards Open Access Accessibility Everywhere: The ÆGIS Concept , 2009, HCI.

[5]  Jacob O. Wobbrock,et al.  Slide rule: making mobile touch screens accessible to blind people using multi-touch interaction techniques , 2008, Assets '08.

[6]  Vicki L. Hanson,et al.  ACCESS: a technical framework for adaptive accessibility support , 2013, EICS '13.

[7]  Dragan Ahmetovic,et al.  MathMelodies 2: a Mobile Assistive Application for People with Visual Impairments Developed with React Native , 2018, ASSETS.

[8]  Jacob O. Wobbrock,et al.  Epidemiology as a Framework for Large-Scale Mobile Application Accessibility Assessment , 2017, ASSETS.

[9]  Renata Pontin de Mattos Fortes,et al.  A model-driven approach to cross-platform development of accessible business apps , 2020, SAC.

[10]  Stelios Xinogalos,et al.  A comparative analysis of cross-platform development approaches for mobile applications , 2013, BCI '13.

[11]  Andres Gonzalez,et al.  Platform-independent accessibility API: accessible document object model , 2005, W4A '05.

[12]  Yagiz Onat Yazir,et al.  Beyond user interfaces in mobile accessibility: Not just skin deep , 2013, 2013 IEEE Pacific Rim Conference on Communications, Computers and Signal Processing (PACRIM).

[13]  William W. Gaver Auditory Icons: Using Sound in Computer Interfaces , 1986, Hum. Comput. Interact..

[14]  Adriano Bessa Albuquerque,et al.  Cross platform app: a comparative study , 2015, ArXiv.