Publication type: Conference paper
Type of review: Editorial review
Title: Verifying screen reader accessibility of apps developed using Google Flutter
Authors: Darvishy, Alireza
et. al: No
DOI: 10.54941/ahfe1001641
Proceedings: Human Factors in Accessibility and Assistive Technology
Editors of the parent work: Zallio, Matteo
Volume(Issue): 37
Conference details: 13th AHFE International Conference on Human Factors in Accessibility and Assistive Technology (HFAAT), New York, USA, 24-28 July 2022
Issue Date: 2022
Publisher / Ed. Institution: AHFE International
ISBN: 978-1-958651-13-1
ISSN: 2771-0718
Language: English
Subjects: Google Flutter; Accessibility; Visual impairment; Screen reader; Accessible mobile app
Subject (DDC): 004: Computer science
Abstract: This paper presents the results of a study to verify whether the Google UI framework Flutter can create accessible apps for iOS and Android platforms simultaneously. Flutter provides mechanisms such as semantic classes to optimise accessibility during app development. Optimising accessibility for mobile apps and especially for screen readers is a major challenge for many app developers. One key reason for this is that optimisations should ideally always be made for both Apple and Android. A possible solution is offered by the UI framework Flutter, which aims to enable development in only one codebase. This means that accessibility optimisations made in the Flutter codebase should take effect in both Apple and Android platforms simultaneously as well as with their respective screen readers, so that users are provided with a consistent and accessible user experience, regardless of the platform chosen. The purpose of this study was to test this hypothesis. To this end, a sample app was developed using Flutter and a usability test was conducted with six visually impaired screen reader users. Based on the initial test results, the app was then optimised in terms of accessibility using Flutter's semantics classes, and then tested and evaluated again with the same test group. The results showed that some user interface elements were still not accessible. In order to overcome these accessibility issues, workarounds such as writing additional code for each specific platform were implemented, before a final usability test showed that the sample app was fully accessible.
Fulltext version: Published version
License (according to publishing contract): Licence according to publishing contract
Departement: School of Engineering
Organisational Unit: Institute of Applied Information Technology (InIT)
Appears in collections:Publikationen School of Engineering

Files in This Item:
There are no files associated with this item.

Items in DSpace are protected by copyright, with all rights reserved, unless otherwise indicated.