LoyaltyCards is committed to ensuring digital accessibility for all users, including those with disabilities. We strive to continually improve the user experience for everyone and apply relevant accessibility standards.
🟡 Partial Compliance. LoyaltyCards is partially conformant with WCAG 2.1 Level AA — some parts of the application do not yet fully conform.
Basic support via iOS defaults — button labels, navigation changes, and text fields are read. Gaps: custom widgets may lack semantic labels, QR scanner status isn't clearly announced, stamp counts may be read as separate numbers, and business logos may be described as "image" rather than by business name.
Body text scales with system settings; some headings use fixed sizes; QR code size doesn't scale (functional limitation); card layout may break at extreme text sizes (200%+).
The app follows the device's system light/dark appearance (both apps' main.dart wire up real, distinct light/dark ColorScheme objects, defaulting to system mode), but there is no in-app toggle to choose Light/Dark/System independent of the device setting. Verified July 20, 2026: every text-color usage most likely to cause an illegible-text bug in dark mode (21 instances across both apps) was checked against its background — all of them pair fixed text with a fixed background (branded info/success/warning badges), so none go illegible in dark mode. This is a deliberate, pre-existing pattern, not an oversight. The visible effect is that these badges keep a fixed light background regardless of theme, so in dark mode they can look like a light-colored card on an otherwise dark screen — a style inconsistency, not a legibility problem.
Users with visual impairments cannot scan QR codes independently, and there's currently no non-visual alternative. Workaround: request assistance from business staff, or have the business scan the customer's QR code and verbally confirm details. Voice-guided scanning and manual code entry are potential future enhancements, not currently scheduled. NFC as a non-visual alternative would require architecture changes and is not on the current product roadmap.
Cards use color and layout to convey information, which can be harder for color-blind or screen-reader users. Business name and stamp count are always present as text, mitigating this partially.
VoiceOver support relies on iOS defaults rather than custom optimization; navigation flow may not be fully optimal for screen reader users. All buttons have text labels and navigation is linear and predictable as a baseline mitigation.
See "Dark Mode" above — branded callout badges keep a fixed light background regardless of theme (verified as a style issue, not a legibility one), and users cannot force a light/dark mode independent of their device setting.
Manual testing has covered basic VoiceOver navigation, Dynamic Type at system sizes, Reduce Motion, manual WCAG contrast checks, and touch target measurement. No automated accessibility testing or CI/CD checks are in place yet, and no formal audit or testing with users who have disabilities has been performed yet.
| Level | Status |
|---|---|
| A | Partially Conformant |
| AA | Partially Conformant |
| AAA | Not Conformant |
Evaluation Method: self-assessment (manual testing + targeted code review). Last Evaluation: April 18, 2026 (general); dark-mode legibility risk specifically re-checked July 20, 2026. Next Evaluation: before the final pre-submission build, covering the remaining open roadmap items.
Relevant standards we track: Americans with Disabilities Act (ADA) Title III and Section 508 in the US; WCAG 2.1 and EN 301 549 internationally; Apple's iOS Human Interface Guidelines and App Store Review Guideline 2.5.18 (Accessibility). We are actively working toward full WCAG 2.1 Level AA compliance.
Email: ian.hamlet@dotconnected.com — subject line "Accessibility Issue - [App Name]". Please include which app, device/iOS version, assistive technology used (if any), and a description of the barrier. We aim to respond within 48 hours.