Common Missing Labels in Banking Apps: Causes and Fixes

Missing labels in banking apps can have severe consequences, including frustrated users, negative store ratings, and revenue loss. At the root of this issue are technical problems, such as incomplete

Introduction to Missing Labels in Banking Apps

Missing labels in banking apps can have severe consequences, including frustrated users, negative store ratings, and revenue loss. At the root of this issue are technical problems, such as incomplete or incorrect implementation of accessibility guidelines, inadequate testing, and insufficient consideration for diverse user personas.

Technical Root Causes of Missing Labels

The technical root causes of missing labels in banking apps can be attributed to several factors, including:

• Inadequate implementation of accessibility guidelines, such as the Web Content Accessibility Guidelines (WCAG 2.1 AA)
• Insufficient testing, particularly with regards to dynamic content and complex user interactions
• Incomplete or incorrect use of accessibility attributes, such as the android:contentDescription attribute in Android or the aria-label attribute in web development
• Lack of consideration for diverse user personas, including users with disabilities, elderly users, and users with limited technical expertise

Real-World Impact of Missing Labels

The real-world impact of missing labels in banking apps can be significant, resulting in:

• User complaints and negative feedback, which can lead to a loss of trust and reputation
• Negative store ratings, which can affect the app's visibility and download rates
• Revenue loss, as users may abandon the app or switch to a competing service
• Increased support requests, as users may struggle to use the app and require assistance

Examples of Missing Labels in Banking Apps

Missing labels can manifest in banking apps in various ways, including:

• Login and Registration Forms: Missing labels for username and password fields can make it difficult for users to understand what information is required.
• Transaction Lists: Missing labels for transaction types, such as "deposit" or "withdrawal", can make it challenging for users to understand their account activity.
• Button and Icon Labels: Missing labels for buttons and icons, such as "pay" or "transfer", can make it difficult for users to understand the purpose of each element.
• Error Messages: Missing labels for error messages, such as "invalid username or password", can make it challenging for users to understand what went wrong and how to correct it.
• Graphs and Charts: Missing labels for graphs and charts, such as "account balance" or "transaction history", can make it difficult for users to understand the data being presented.
• Navigation Menus: Missing labels for navigation menus, such as "accounts" or "settings", can make it challenging for users to find the information they need.
• Alerts and Notifications: Missing labels for alerts and notifications, such as "low balance" or "payment due", can make it difficult for users to understand the purpose of each alert.

Detecting Missing Labels

To detect missing labels, developers can use a variety of tools and techniques, including:

• Automated Testing Tools: Tools like SUSA (SUSATest) can automatically explore the app and identify missing labels, including those that may not be immediately apparent.
• Accessibility Audits: Conducting regular accessibility audits can help identify missing labels and other accessibility issues.
• User Testing: Conducting user testing with diverse user personas can help identify missing labels and other usability issues.
• Code Review: Reviewing code regularly can help identify missing labels and other technical issues.

Fixing Missing Labels

To fix missing labels, developers can take the following steps:

• Add Accessibility Attributes: Add accessibility attributes, such as android:contentDescription or aria-label, to provide a text description of each element.
• Use Clear and Concise Language: Use clear and concise language to provide a text description of each element, avoiding jargon and technical terms.
• Test with Diverse User Personas: Test the app with diverse user personas, including users with disabilities, elderly users, and users with limited technical expertise.
• Code-Level Guidance: For example, in Android, developers can add the android:contentDescription attribute to a TextView like this: .
• Example Fix for Login and Registration Forms: Add a android:contentDescription attribute to the username and password fields, like this: and .

Prevention: Catching Missing Labels Before Release

To catch missing labels before release, developers can take the following steps:

• Integrate Accessibility Testing into CI/CD Pipelines: Integrate accessibility testing into CI/CD pipelines using tools like GitHub Actions or JUnit XML.
• Use Automated Testing Tools: Use automated testing tools like SUSA (SUSATest) to automatically explore the app and identify missing labels.
• Conduct Regular Accessibility Audits: Conduct regular accessibility audits to identify missing labels and other accessibility issues.
• Test with Diverse User Personas: Test the app with diverse user personas, including users with disabilities, elderly users, and users with limited technical expertise.
• Code Review: Regularly review code to identify missing labels and other technical issues.

By following these steps, developers can catch missing labels before release and ensure that their banking app is accessible and usable for all users.