Are Saudi Arabian banks' mobile applications accessible for blind or partially sighted users?: a customers' perspective and evaluation
Open accessThe DOI matches its Crossref record; 24 of the 24 references it cites were found in a registry or an index; none of the 11 sources its claims cite is checked for support yet.
Abstract
This study investigated the accessibility problems and barriers faced by visually impaired Arabic speakers when using banking mobile applications. The sample included mobile applications for the top three banks in Saudi Arabia in terms of their customer base, including applications for AlRajhi, SNB, and Riyad bank. The focus was on the three most popular e-services provided by those applications. Using a mixed method approach, accessibility was inspected manually according to current Web Content Accessibility Guidelines (WCAG 2.1). In addition, in-depth usability testing for those applications was conducted with 12 blind Arabic-speaking users. The results revealed that the accessibility level for all sample applications did not conform to WCAG 2.1, which reflected the low accessibility level provided by these applications. However, AlRajhi’s application was the best among the tested applications. In manual inspection, it had the lowest number of violations of success criteria compared to SNB’s and Riyad’s applications. It also achieved the best results in usability testing in terms of effectiveness, efficiency and satisfaction compared to the other two applications. The overall results showed that the current situation of accessibility of Saudi banking applications is not very satisfactory in terms of number of violations to WCAG 2.1 success criteria. The most violated principle by all the applications was operable, with around 37% of total violations, followed by perceivable, then robust and understandable.
Overview
CoChat Summary
TL;DR
This study evaluated the accessibility of the top three Saudi Arabian banks’ mobile applications for blind or partially sighted Arabic-speaking users using manual WCAG 2.1 inspection and usability testing with 12 blind participants. None of the evaluated applications conformed to WCAG 2.1 A/AA, and all showed low accessibility and usability, although AlRajhi performed best among the three.
Key findings
- None of the evaluated applications complied with WCAG 2.1 A and AA success criteria. Operable was the most violated principle, at around 37% of total violations, followed by Perceivable, Robust, and Understandable.
- Common violations included bypass blocks, focus order, link purpose, missing text alternatives for non-text content, inability to resize text, and missing name/role/value information. SNB and Riyad also violated contrast and status-message criteria; SNB had a login issue where the password cursor did not appear with VoiceOver.
- In usability testing, 11 of 12 participants stated they could not use their bank application independently and usually asked for help. Mean SUS scores were 63.75 for AlRajhi, 45.63 for SNB, and 48.75 for Riyad; SNB had the lowest usability, with an average task completion time of 300.13 s, the longest among the three.
- AlRajhi was the best among the tested applications: it had the lowest number of WCAG success-criteria violations and the best usability results in effectiveness, efficiency, and satisfaction.
Methods
- Mixed-method design. The top three Saudi banks by customer base were selected: AlRajhi, SNB, and Riyad. The evaluated apps were AlRajhi version 6.0.7, SNB version 1.1.7, and Riyad version 4.3.0. Only the Arabic version was evaluated, covering log-in plus the three most-used e-services: money transfer, bill payment, and bank account statement.
- Manual accessibility inspection assessed conformance to WCAG 2.1 A and AA criteria on an iPhone 12 Pro Max with iOS 15.6, using VoiceOver and a color-contrast tool. The analysis counted violated criteria rather than the number of times each criterion was violated.
- Usability testing involved 12 blind Arabic-speaking participants aged 21–30, all screen-reader users: 9 used iPhones with VoiceOver and 3 used Galaxy/Android with TalkBack. Measures included effectiveness (task success and errors), efficiency (task completion time), satisfaction (SUS), plus observation notes, user comments, and semi-structured interviews.
Limitations
- The paper states four main limitations: the small number of subjects who used each of the three tested applications; all participants were totally blind, as no partially sighted subjects willing to take part could be found; the limited number of services tested, three plus the log-in page; and the possibility that more varied banking services would reveal additional accessibility issues.
- The paper also notes that future work intends to inspect a wider range of banking and financial applications, include more services, and involve participants with different types of disabilities.
- Evident from the text: the manual inspection was conducted only on iOS with VoiceOver, only the Arabic versions of the top three banks’ apps were evaluated, and no video recording was made because of financial privacy concerns.
Model-written summary. Check it against the paper before relying on it.
Integrity signals
Registry
Cites
Statistics
Figures












Verification
Claims the paper makes
0 Valid · 7 Not valid · 9 Not checked · 94 Own results and interpretations
A result the paper reports from its own data — it cites no other source for it, so there is none to check. The quote shows it is in the paper.
In the paper
“The evaluated applications failed to comply with this success criterion.”
§ 4 Results > 4.1 Results of the manual accessibility inspection
plain- Asserted: passes — The authors put it forward as true.
- Checkable: passes — It can be checked against evidence.
- Load-bearing: passes — The paper’s conclusions depend on it.
- Based: passes — The paper gives a reason why it holds.
A result the paper states — it cites no source for it, so there is none to check. The quote shows it is in the paper.
In the paper
“Due to the difficulty, they faced in performing this task, the time taken to complete was the longest among all the other tasks.”
§ 4 Results > 4.2 Results of usability testing
plainn = 4- Asserted: passes — The authors put it forward as true.
- Checkable: passes — It can be checked against evidence.
- Load-bearing: unclear — It is unclear whether the paper’s conclusions depend on it.
- Based: passes — The paper gives a reason why it holds.
A result the paper reports from its own data — it cites no other source for it, so there is none to check. The quote shows it is in the paper.
In the paper
“they answered Yes, they would recommend the application to others, whether they are sighted or blind.”
§ 4 Results > 4.2 Results of usability testing
plain- Asserted: passes — The authors put it forward as true.
- Checkable: passes — It can be checked against evidence.
- Load-bearing: unclear — It is unclear whether the paper’s conclusions depend on it.
- Based: passes — The paper gives a reason why it holds.
A result the paper reports from its own data — it cites no other source for it, so there is none to check. The quote shows it is in the paper.
In the paper
“The results revealed that the accessibility level for all sample applications did not conform to WCAG 2.1, which reflected the low accessibility level provided by these applications.”
- Also stated in: § 4.1 Results of the manual accessibility inspection · plain
“The results revealed that none of the evaluated applications complied with WCAG 2.1 A and AA success criteria.”
plain- Asserted: passes — The authors put it forward as true.
- Checkable: passes — It can be checked against evidence.
- Load-bearing: passes — The paper’s conclusions depend on it.
- Based: passes — The paper gives a reason why it holds.
- Also stated in: § 4.1 Results of the manual accessibility inspection · plain
A result the paper reports from its own data — it cites no other source for it, so there is none to check. The quote shows it is in the paper.
In the paper
“The most violated principle by all the applications was operable, with around 37% of total violations, followed by”
- Also stated in: § 4.1 Results of the manual accessibility inspection · plain
“It can be seen that Operable was the most violated WCAG principle by all applications, followed by Perceivable, Robust and Understandable.”
- Also stated in: § 4.1 Results of the manual accessibility inspection · plain
“As illustrated in Fig. 4, the violations of the Operable success criterion reached 37% of the total violations.”
plain- Asserted: passes — The authors put it forward as true.
- Checkable: passes — It can be checked against evidence.
- Load-bearing: unclear — It is unclear whether the paper’s conclusions depend on it.
- Based: passes — The paper gives a reason why it holds.
- Also stated in: § 4.1 Results of the manual accessibility inspection · plain
43 more claims
Create a free account to see all 110 claims and every source verdict.
- Borderline: one of the tests for a substantial claim is unclear. 2
- It may state two separate claims as one. 47
- Probably not a substantial claim. 20
Citations
Cites
Sampling for qualitative research
Marshall, M. N. (1996) · Family Practice · doi:10.1093/fampra/13.6.522 · Cited by 4,293
When designing usability questionnaires, does it hurt to be positive?
Sauro, J., & Lewis, J. R. (2011) · Proceedings of the SIGCHI Conference on Human Factors in Computing Systems · doi:10.1145/1978942.1979266 · Cited by 363 · cited 1×
“This scale was chosen because it is a very easy scale to administer to participants; it can be used on small sample sizes with reliable results and is valid, which means it can easily differentiate between usable and unusable applications [53].”
Vigo, M., Brown, J., & Conway, V. (2013) · Proceedings of the 10th International Cross-Disciplinary Conference on Web Accessibility · doi:10.1145/2461121.2461124 · Cited by 215 · cited 2×
“The result would help to ensure that all WCAG 2.1 Success Criteria are covered and as many as possible accessibility violations are captured [39].”
InfluentialDetermining Usability Test Sample Size
Nielsen, J., Lewis, J., & Turner, C. (2006) · International Encyclopedia of Ergonomics and Human Factors, Second Edition - 3 Volume Set · doi:10.1201/9780849375477.ch597 · Cited by 193
The Current Status of Accessibility in Mobile Apps
Yan, S., & Ramachandran, P. G. (2019) · ACM Transactions on Accessible Computing · doi:10.1145/3300176 · Cited by 165 · cited 3×
“Different types of mobile applications are available: native, hybrid, and web [40].”
The accessibility of Saudi Arabia government Web sites: an exploratory study
Al-Khalifa, H. S. (2010) · Universal Access in the Information Society · doi:10.1007/s10209-010-0215-7 · Cited by 87
Revisiting the accessibility of Saudi Arabia government websites
Al-Khalifa, H. S., Baazeem, I., & Alamer, R. (2017) · Universal Access in the Information Society · doi:10.1007/s10209-016-0495-7 · Cited by 67 · cited 1×
“Although the homepage is the website’s entry point and would give an indication of the accessibility level for the website, following this approach in the current study would risk some accessibility aspects being underrepresented or not represented at all [29].”
Alahmadi, T. J., & Drew, S. (2017) · Journal of Open, Flexible and Distance Learning · doi:10.61468/jofdl.v21i1.273 · Cited by 57 · cited 1×
“Accessibility has been investigated for different website genres, including those in education [20–24], in the health sector, [25], Saudi governmental websites [26–31], as well as those for the Saudi railways and postal service [32], and E-commerce websites [33].”
Banking websites in India: an accessibility evaluation
Kaur, A., & Dani, D. (2014) · CSI Transactions on ICT · doi:10.1007/s40012-014-0040-x · Cited by 42
Corporate website accessibility: does legislation matter?
Loiacono, E. T., & Djamasbi, S. (2013) · Universal Access in the Information Society · doi:10.1007/s10209-011-0269-1 · Cited by 41
Research works printed but not linked: 9
- Khan, N.M., Adnan, A., Bakhsh, M.: Accessibility evaluation of banks websites in Pakistan for disabled. In: 1st International Conference on Technology Helping People with Special Needs (ICTHP-2013) (2013)
- Nazar, H.M.S.S. and U.Shoaib. “Web accessibility evaluation of banking website in Pakistan.” I.J. of C.S. and I.S. 15, no. 1 (2017): 642.: Web accessibility evaluation of banking website in Pakistan. Int. J. Comput. Scie. Inf. Secur. (IJCSIS). 15, 642–650 (2017)
- Nouman, N.: Website content accessibility of banks websites in Pakistan Using WCAG. ARPN J. Syst. Softw. 2, 2 (2012)
- Wentz, B., Nguyen, T., Pham, T.: The decline of branch banking and the transformation of bank accessibility. Rev. Integr. Bus. Econ. Res. 11, 1–19 (2021)
- Alnfiai, M., Alhakami, W.: The accessibility of taif university blackboard for visually impaired students. IJCSNS Int. J. Comput. Sci. Netw. Secur. 21, 258 (2021). https://doi.org/10.22937/IJCSNS.2021.21.6.34 · doi:10.22937/ijcsns.2021.21.6.34
- Abanumy, A., Al-Badi, A., Mayhew, P.: e-Government website accessibility: in-depth evaluation of Saudi Arabia and Oman. Electron. J. E-government 3(3), 149–156 (2005)
- Aljarallah, K., Chen, R.C.C., Alshathry, O.: Cognitive-based approach for assessing accessibility of e-government websites. LNCS 8010, 547–554 (2013)
- Khan, M.A., Abdulmohsen Buragga, K.: effectiveness of accessibility and usability of government websites in Saudi Arabia. SENRA Acad. Publ. 4, 1227–1231 (2010)
- Brooke, J.: SUS-A quick and dirty usability scale. Usability Eval. Ind. 189(3), 189–194 (2011)
Cited by
Krittika, K., & Shimray, S. R. (2025) · Universal Access in the Information Society · doi:10.1007/s10209-025-01218-2 · Cited by 1
Musiał, M., & Rachuba, J. (2025) · Central European Management Journal · doi:10.1108/cemj-10-2024-0289 · Cited by 1
Click, Watch, Enjoy! But Which Platform Is More User-Friendly
Dursun, F. (2026) · Yeni Medya Dergisi · doi:10.55609/yenimedya.1877962
FinTechHub for digital financial inclusion in Saudi Arabia
Dwivedi, Y. K., Helal, M. Y. I., Elgendy, I. A., Al-Sharafi, M. A., Hosny, M., Alzaeemi, S. A., Sohail, M. S., & Chae, I. (2026) · Revista de Gestão · doi:10.1108/rege-07-2026-0139
Metadata
- Authors
- Alayed, A.
- Affiliations
- Umm al-Qura University (SA)
- Corresponding author
- Alayed, Asmaa
- ORCID
- Alayed, Asmaa
- Venue
- Universal Access in the Information Society
- Published
- 2024-01-19
- Volume
- 24
- Issue
- 1
- Pages
- 585-606
- ISSN
- 1615-5289 (ISSN-L)
- 1615-5297
- OpenAlex
- W4391027648
- Cited by
- 7
- References
- 23
- Citations by year
- 2026: 5 · 2025: 2
- FWCI
- 14.69
- Type
- journal article
- Language
- en
- Open access
- hybrid
- doi.org
- Licence
- cc-by
- creativecommons.org/licenses/by/4.0 (tdm)
- creativecommons.org/licenses/by/4.0 (vor)
- Locations
- Universal Access in the Information Society (publishedVersion, cc-by)
- Topics
- Social Sciences › Human Factors and Ergonomics › Digital Accessibility for Disabilities
- Physical Sciences › Computer Science › Human-Computer Interaction › Usability and User Interface Design
- Health Sciences › Health Professions › Occupational Therapy › Assistive Technology in Communication and Mobility
- Keywords
- mobile banking applications, accessibility, visually impaired users, blind users, usability, Saudi Arabian banks, Arabic language, SNB
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.
A language model drew the claims from the paper on 2026-09-30, under version 3 of the claim definition (model deepseek-v4.1-flash, prompt extract-v3).
A second model labelled each claim on 2026-09-30 (model jev-1.13-20260917, definition revision gold-guideline-v0.2).
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: Are Saudi Arabian banks' mobile applications accessible for blind or partially sighted users?: a customers' perspective and evaluation. https://app.cochat.ai/papers/10.1007/s10209-023-01082-y
- The paper
- Alayed, A. (2025). Are Saudi Arabian banks' mobile applications accessible for blind or partially sighted users?: a customers' perspective and evaluation. Universal Access in the Information Society. https://doi.org/10.1007/s10209-023-01082-y
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.