Common Missing Labels in Flight Booking Apps: Causes and Fixes

Missing labels in flight booking apps can lead to a poor user experience, causing frustration and confusion for travelers. Technical root causes of missing labels include incomplete or incorrect imple

Introduction to Missing Labels in Flight Booking Apps

Missing labels in flight booking apps can lead to a poor user experience, causing frustration and confusion for travelers. Technical root causes of missing labels include incomplete or incorrect implementation of accessibility features, inadequate testing, and insufficient consideration of user personas, such as the accessibility persona used in SUSA (SUSATest) autonomous QA platform. For instance, when uploading an APK or web URL to SUSA, it can explore the app autonomously, identifying potential issues like missing labels without requiring scripts.

Real-World Impact of Missing Labels

The real-world impact of missing labels in flight booking apps can be significant. User complaints and negative reviews can lead to lower store ratings, resulting in reduced visibility and revenue loss. For example, a flight booking app with missing labels may receive complaints about inaccessible features, leading to a 1-star review and a subsequent decline in downloads. SUSA's 10 user personas, including the elderly and novice personas, can help identify such issues by simulating real-user interactions.

Examples of Missing Labels in Flight Booking Apps

Missing labels can manifest in various ways in flight booking apps, including:

• Flight search form: Missing labels for input fields, such as "Departure city" or "Return date", can make it difficult for users to understand what information is required.
• Seat selection: Unclear or missing labels for seat options, such as "Extra legroom" or "Emergency exit", can lead to confusion and incorrect seat selections.
• Payment options: Missing labels for payment methods, such as "Credit card" or "PayPal", can cause users to struggle with completing their booking.
• Booking summary: Inadequate or missing labels for booking details, such as "Flight number" or "Departure time", can make it hard for users to review and confirm their booking.
• Error messages: Missing or unclear labels for error messages, such as "Invalid password" or "Flight not available", can frustrate users and make it difficult for them to resolve issues.
• Accessibility features: Insufficient or missing labels for accessibility features, such as screen reader support or font size adjustment, can exclude users with disabilities from using the app.
• Multi-step processes: Missing labels for multi-step processes, such as login, registration, or checkout, can lead to UX friction and crashes, which SUSA can detect and report.

Detecting Missing Labels

To detect missing labels, developers can use various tools and techniques, such as:

• Automated testing tools, like SUSA, which can auto-generate Appium (Android) + Playwright (Web) regression test scripts and identify missing labels through WCAG 2.1 AA accessibility testing.
• Manual testing: Testers can manually review the app, paying attention to areas where labels are missing or unclear.
• User testing: Conducting user testing with real users can help identify areas where missing labels cause confusion or frustration.
• Code reviews: Regular code reviews can help identify areas where labels are missing or incomplete.

When detecting missing labels, developers should look for areas where:

• Input fields or buttons lack clear labels
• Error messages are unclear or missing
• Accessibility features are insufficient or missing
• Multi-step processes lack clear labels or instructions

Fixing Missing Labels

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

• Add clear and concise labels: Use simple and descriptive language to label input fields, buttons, and other interactive elements.
• Implement accessibility features: Ensure that the app includes accessibility features, such as screen reader support and font size adjustment, and provides clear labels for these features.
• Use ARIA attributes: Use ARIA attributes to provide additional context and labels for dynamic content and interactive elements.
• Test with real users: Conduct user testing to ensure that the app is accessible and usable for all users, including those with disabilities.

For example, to fix a missing label for a flight search form input field, a developer could add a clear and concise label using HTML and CSS:

<label for="departure-city">Departure city</label>
<input type="text" id="departure-city" />

SUSA's cross-session learning capability can help identify and report missing labels, enabling developers to fix issues and improve the overall user experience.

Preventing Missing Labels

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

• Conduct regular accessibility audits: Regularly review the app for accessibility issues, including missing labels.
• Use automated testing tools: Use tools like SUSA to identify and report missing labels and other accessibility issues.
• Implement a design system: Establish a design system that includes clear guidelines for labeling and accessibility.
• Test with real users: Conduct user testing to ensure that the app is accessible and usable for all users, including those with disabilities.
• Integrate with CI/CD pipelines: Integrate SUSA with CI/CD pipelines, such as GitHub Actions, to automate testing and catch missing labels before release.

By following these steps and using tools like SUSA, developers can ensure that their flight booking apps are accessible and usable for all users, reducing the risk of missing labels and improving the overall user experience. SUSA's coverage analytics can also help identify areas of the app that require additional testing, ensuring that all aspects of the app are thoroughly tested and validated.