Dashboard Accessibility Issues
This file tracks the dashboard accessibility findings that are currently known, without forcing visual regressions just to satisfy the audit mechanically.
Confirmed Current Issue
- Confirmed by
ClueSolverUITests.testDashboardPassAccessibilityAudit on March 15, 2026.
- The current layout in
ClueSolver/Views/Game/CardListView.swift clips around the THE ENVELOPE header row on iPhone 16 Pro.
- This is a real accessibility issue, but the previous layout-only fix materially worsened the visual presentation.
2. Summary metrics also clip in contradiction/dashboard states
- Confirmed by the contradiction-banner accessibility audit on March 15, 2026.
- Strings like
3 eliminated clip inside the compact summary row in ClueSolver/Views/Game/CardListView.swift.
- This means the clipping issue is broader than the envelope header; the trailing category-summary treatment also needs redesign.
3. Category summary line is fragile at smaller widths
- The summary row combines:
N possible
N eliminated
- optional envelope-card text
- In the current design this is compressed into a single trailing line, which is likely to clip or truncate on smaller devices, larger text sizes, or long card names.
4. Envelope slot height is tight for long card names
EnvelopeSlot uses a compact, fixed-height presentation.
- This is visually strong, but long room or themed-edition card names may not fit comfortably without truncation or cramped scaling.
5. Secondary summary text may need a contrast pass
- Some summary/status text still relies on low-opacity steel/ivory styling.
- This was not the active failing audit after the revert, but it remains a likely accessibility/design follow-up item.
Resolved Non-Visual Issue Kept In Place
6. Raw SF Symbol labels were being exposed to accessibility
- Earlier, card rows could expose labels like
person.fill through the default accessibility tree.
- This has been addressed with explicit row-level accessibility labeling in
ClueSolver/Views/Game/CardListView.swift.
- This change is non-visual and worth keeping.
Better Resolution Directions
Instead of forcing the dashboard into a visibly worse adaptive layout, the likely better options are:
- Redesign the envelope header as a stronger two-line composition that still feels intentional.
- Turn the category summary row into a richer stacked metric block instead of a cramped one-line status string.
- Introduce edition-aware truncation or abbreviated labels for long envelope-card names.
- Run a focused typography/spacing pass for accessibility sizes rather than ad hoc
ViewThatFits fallbacks.
Testing Policy For Now
- Home-screen accessibility audit remains CI-gated.
- Dashboard and contradiction-dashboard accessibility issues are currently tracked here and covered by smoke tests until the visual redesign is agreed.