CoChat

The DOI matches its Crossref record; 22 of the 22 references it cites were found in a registry or an index.

Adaptive and accessible user interfaces for seniors through model-driven engineering

Open access
Wickramathilaka, Shavindra, Grundy, John, Madampe, Kashumi, Haggag, Omar · 2025 · Automated Software Engineering

Abstract

The use of diverse mobile applications among senior users is becoming increasingly widespread. However, many of these apps contain accessibility problems that result in negative user experiences for seniors. A key reason is that software practitioners often lack the time or resources to address the broad spectrum of age-related accessibility and personalisation needs. As current developer tools and practices encourage one-size-fits-all interfaces with limited potential to address the diversity of senior needs, there is a growing demand for approaches that support the systematic creation of adaptive, accessible app experiences. To this end, we present AdaptForge , a novel model-driven engineering (MDE) approach that enables advanced design-time adaptations of mobile application interfaces and behaviours tailored to the accessibility needs of senior users. AdaptForge uses two domain-specific languages (DSLs) to address age-related accessibility needs. The first model defines users’ context-of-use parameters, while the second defines conditional accessibility scenarios and corresponding UI adaptation rules. These rules are interpreted by an MDE workflow to transform an app’s original source code into personalised instances. We also report evaluations with professional software developers and senior end-users, demonstrating the feasibility and practical utility of AdaptForge .

Overview

The claims and statistics of this paper haven’t been checked yet.

Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.

A few free checks a day · papers already verified open instantly · results are public

Integrity signals

Registry

Crossref · 10.1007/s10515-025-00547-z

Cites

22 of 22 references verified0 citation errors · 0 not checkable

Statistics

Figures

Image 1
CC-BY · From the PDF
Fig. 2 The overall Research Methodology
Fig. 2 The overall Research MethodologyCC-BY · From the PDF
Fig. 3 The overall architecture of AdaptForge . Note that the scalability of tailored app instance generation is not restricted to the three personas in the preliminary persona corpus; these are illustrative examples of how the overall approach can tailor personalised app instances for a variety of senior needs. The modelling of accessibility needs and app personalisations can be extended to other users and user groups (senior or otherwise)
Fig. 3 The overall architecture of AdaptForge . Note that the scalability of tailored app instance generation is not restricted to the three personas in the preliminary persona corpus; these are illustrative examples of how the overall approach can tailor personalised app instances for a variety of senior needs. The modelling of accessibility needs and app personalisations can be extended to other users and user groups (senior or otherwise)CC-BY · From the PDF
Fig. 4 An example Context-of-use model for the senior persona: Judy in AdaptForge . Here we show a semi-graphical editor developed using Eclipse's Sirius modelling workbench
Fig. 4 An example Context-of-use model for the senior persona: Judy in AdaptForge . Here we show a semi-graphical editor developed using Eclipse's Sirius modelling workbenchCC-BY · From the PDF
Fig. 5 The Context DSL metamodel. At the root of the class diagram hierarchy is the ContextDSL metaclass. It has a composition relationship with the UserContainer class, which is designed to hold multiple instances of the User class. The User class links to an abstract ContextOfUse class, which is further specialised into three subclasses: UserContext , PlatformContext , and EnvironmentContext . In a runtime context-of-use model instance, a developer can instantiate User, Platform, and Environment context nodes under a selected user and populate them with various subnodes in a layered tree-node hierarchy, as illustrated in the metamodel
Fig. 5 The Context DSL metamodel. At the root of the class diagram hierarchy is the ContextDSL metaclass. It has a composition relationship with the UserContainer class, which is designed to hold multiple instances of the User class. The User class links to an abstract ContextOfUse class, which is further specialised into three subclasses: UserContext , PlatformContext , and EnvironmentContext . In a runtime context-of-use model instance, a developer can instantiate User, Platform, and Environment context nodes under a selected user and populate them with various subnodes in a layered tree-node hierarchy, as illustrated in the metamodelCC-BY · From the PDF
Fig. 7 The Adapt DSL metamodel. At the root of the class diagram is the AdaptDSL meta-class, which has a composition relationship with the Adaptation Rules Model class. This allows users to instantiate multiple Adaptation Rule objects within the Adapt DSL editor. The Adaptation Rule class includes three key meta-classes: (1) Comment , used to define metadata for adaptation rules; (2) Conditional Statement , which enables users to construct complex conditional logic; and (3) Operation , where users define concrete app adaptations targeting supported Flutter widget meta-classes such as Text , Container , and Icon
Fig. 7 The Adapt DSL metamodel. At the root of the class diagram is the AdaptDSL meta-class, which has a composition relationship with the Adaptation Rules Model class. This allows users to instantiate multiple Adaptation Rule objects within the Adapt DSL editor. The Adaptation Rule class includes three key meta-classes: (1) Comment , used to define metadata for adaptation rules; (2) Conditional Statement , which enables users to construct complex conditional logic; and (3) Operation , where users define concrete app adaptations targeting supported Flutter widget meta-classes such as Text , Container , and IconCC-BY · From the PDF
Image 7
CC-BY · From the PDF
Image 8
CC-BY · From the PDF
Fig. 10 An example of multi-modality adaptation with source code transformation. The previous presentation adaptation example is extended to integrate text-to-speech and speech-to-text functionality for the defined TextFormField widgets. In (C), when the speech-to-text and/or text-to-speech proper -ties are set to true, the MDE pipeline identifies the relevant widget (A.1) and adapts the source code to include the necessary functionality, as shown in (B.1) and (B.2). This transformation is reflected in the app's front end, where the adaptation evolves from instance (A.2) to (B.3)
Fig. 10 An example of multi-modality adaptation with source code transformation. The previous presentation adaptation example is extended to integrate text-to-speech and speech-to-text functionality for the defined TextFormField widgets. In (C), when the speech-to-text and/or text-to-speech proper -ties are set to true, the MDE pipeline identifies the relevant widget (A.1) and adapts the source code to include the necessary functionality, as shown in (B.1) and (B.2). This transformation is reflected in the app's front end, where the adaptation evolves from instance (A.2) to (B.3)CC-BY · From the PDF
Fig. 11 An example of navigation adaptation with source code transformation. The previously adapted UI source code (A.1) is further transformed into a segmented form through automatically modified source code (B.1). (B.2) shows the additional classes and functionalities applied to the original code to enable this operation. To trigger this transformation, the developer defines the grouping and ordering of the relevant TextFormField widgets through the adaptation rules model (C). The final transformation to the UI instance is shown, evolving from (A.2) to (B.3)
Fig. 11 An example of navigation adaptation with source code transformation. The previously adapted UI source code (A.1) is further transformed into a segmented form through automatically modified source code (B.1). (B.2) shows the additional classes and functionalities applied to the original code to enable this operation. To trigger this transformation, the developer defines the grouping and ordering of the relevant TextFormField widgets through the adaptation rules model (C). The final transformation to the UI instance is shown, evolving from (A.2) to (B.3)CC-BY · From the PDF

Verification

Claims the paper makes

The claims and statistics of this paper haven’t been checked yet.

Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.

A few free checks a day · papers already verified open instantly · results are public

Claims other papers make about this one

Each is checked against this paper’s own text: does it say what the citing paper says it does?

Self-check

Percentages, sums and reported differences re-computed from the paper’s own numbers.

The self-check needs the paper’s full text.

Citations

Cites

Show all 21 references

Research works printed but not linked: 5

  1. Calvary, G., Coutaz, J., Bouillon, L., Florins, M., Limbourg, Q., Marucci, L., Paterno, F., Santoro, C., Souchon, N., Thevenin, D., Vanderdonckt, J.: The cameleon reference framework. Technical report, CAMELEON Project (2002)
  2. Dodd, C.T., Athauda, R.I., Adam, M.T.P.: Designing user interfaces for the elderly: A systematic literature review. In: Australasian Conference on Information Systems (ACIS 2017). Association for Information Systems (AIS), Hobart, Australia. (2017).https://api.semanticscholar.org/CorpusID:209410212
  3. Johnson, J., Finn, K.: Designing User Interfaces for an Aging Population: Towards Universal Design. Morgan Kaufmann, 50 Hampshire Street, 5th Floor, Cambridge, MA 02139, United States. (2017)
  4. Steinberg, D., Budinsky, F., Paternostro, M., Merks, E.: EMF: Eclipse Modeling Framework, 2nd revised edn. The Eclipse Series. Addison-Wesley, 221 River Street, Hoboken, NJ (2009)
  5. Stephanidis, C., Akoumianakis, D., Antona, M., Bannon, L.: User Interfaces for All: Concepts, Methods, and Tools, 1st edn. Human Fact. Ergonom., 1. CRC Press, Boca Raton (2001)

Cited by

See all 11

Metadata

Authors
Wickramathilaka, S., Grundy, J., Madampe, K., & Haggag, O.
Affiliations
Monash University (AU)
Corresponding author
Wickramathilaka, Shavindra
Venue
Automated Software Engineering
Published
2025-08-11
Volume
32
Issue
2
ISSN
  • 0928-8910 (ISSN-L)
  • 1573-7535
OpenAlex
W4413129833
Cited by
11
References
21
Citations by year
2026: 10 · 2025: 1
FWCI
24.46
Type
journal article
Language
en
Open access
Licence
Locations
  • Automated Software Engineering (publishedVersion, cc-by)
  • arXiv (Cornell University) (submittedVersion)
  • Monash University Research Portal (Monash University) (submittedVersion, cc-by)
  • arXiv (Cornell University)
Funders
Monash University
Topics
  • Health Sciences › Medicine › Geriatrics and Gerontology › Technology Use by Older Adults
  • Physical Sciences › Computer Science › Human-Computer Interaction › Usability and User Interface Design
  • Social Sciences › Human Factors and Ergonomics › Digital Accessibility for Disabilities
Keywords
adaptive user interfaces, model-driven engineering, mobile application, domain-specific languages, context of use, personalization

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review

How to cite

Cite CoChat for the checks on this page, and the paper for its own findings.

This page
CoChat. (2026). Citation check: Adaptive and accessible user interfaces for seniors through model-driven engineering. https://app.cochat.ai/papers/10.1007/s10515-025-00547-z
The paper
Wickramathilaka, S., Grundy, J., Madampe, K., & Haggag, O. (2025). Adaptive and accessible user interfaces for seniors through model-driven engineering. Automated Software Engineering. https://doi.org/10.1007/s10515-025-00547-z

Data sources

Bibliographic data: Semantic Scholar, OpenAlex, Crossref.

Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).

Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.