Android QA Audit — Visa App Validation, Localization & UX

I reviewed UK ETA Office on Android, combining functional flow checks with form-validation and usability observations. The audit documented four issues or improvement opportunities: one high, two medium, and one low.

Role: Manual QA Tester & UX Reviewer Device: Samsung Galaxy S25 Ultra Platform: Android; the source report does not specify the OS version Duration: More than 30 minutes Report date: 27 February 2026

The review covered Home, Eligibility, Application, Submission, Tracking, FAQs, and Support. I checked onboarding, document capture, local file uploads, form entry, and Arabic right-to-left layout behaviour.

In the tested flows, the report recorded responsive transitions, functioning capture and upload flows, working support links, and a correctly presented Arabic RTL layout. The findings focused on strengthening data consistency and reducing avoidable entry friction rather than presenting every observation as a crash or failure.

High — Missing cross-field consistency checks. The report described a nationality selection that could conflict with the uploaded passport's country information without being flagged. The recommendation was to validate relevant fields together and make discrepancies visible for review.

Medium — Weak passport-number validation. The field accepted lowercase entries and inconsistent string lengths. Follow-up validation should use the application's requirements and the relevant issuing-country rules; a single universal passport format should not be assumed.

Medium — Age capture relied on a Yes/No toggle. The original report questioned whether this captured enough detail for the intended workflow. This is a product/data-quality observation, not a finding that the service violated an immigration requirement.

Low — Inconsistent placeholder capitalization. The Employment Information placeholder differed from the title-case style elsewhere in the form.

This reformatted extract summarizes the environment, tested flows, positive observations, and all four findings from the original report. Follow-up guidance is clarified for product requirements. No passport images or personal applicant records are included.

I recommended stronger consistency checks and OCR-assisted entry to reduce repeated manual typing after document upload. Those recommendations are intended to guide product improvements and further testing; the portfolio does not claim they were implemented or that error rates subsequently fell.

The deliverable was a structured QA report connecting functional observations to validation and UX recommendations. This was software testing, not a compliance certification or endorsement of the service.

Need QA for a form-heavy website or app? Send the priority flows, supported languages, test-access details, and deadline through Contra.