chore: accessibility audit — WCAG 2.1 + ND-specific UX review #4

New issue

Open

opened 2026-07-05 11:02:35 -07:00 by pyr0ball · 0 comments

pyr0ball commented

2026-07-05 11:02:35 -07:00

Collaborator

Context

Focus Flow is purpose-built for ADHD/executive dysfunction users. CF has a dedicated
accessibility practice (cf-a11y agent, WCAG 2.1/2.2 + ND-informed UX standards).

An early audit catches issues before the UI is deeply built rather than retrofitting.

Scope

WCAG 2.1 technical compliance

Color contrast ratios on timeline items, task type indicators, staleness colors
(green/blue/purple backlog) — check against 4.5:1 (normal) / 3:1 (large)
Touch target sizes (Flutter desktop → also mobile paths in future)
Screen reader / TalkBack / VoiceOver label coverage on interactive elements
Focus order on timeline interactions

ND-specific UX review

Areas specific to ADHD/executive dysfunction not covered by WCAG:

Error and warning messages — tone check (no guilt/shame language)
Empty states — safe, non-anxiety-inducing copy
Push/defer UI — confirm it doesn't create micro-decisions or cognitive load
Backlog staleness indicators — ensure these inform without nagging
Task failure states (missed, cancelled) — trauma-informed framing
Time displays — support for time blindness (relative + absolute, configurable)

Demand avoidance considerations

Are any actions framed as obligations rather than choices?
Can all core flows be completed without reading instructional text?
Is there any shame language in default copy, placeholder text, or status labels?

Output

Issues filed per finding. Severity: WCAG-fail (must fix), ND-UX (should fix),
suggestion (nice to have).

CF contributor

CF's cf-a11y agent will run this audit against the Flutter UI in
apps/focus_flow_flutter. Ashley to review and prioritize findings.

## Context Focus Flow is purpose-built for ADHD/executive dysfunction users. CF has a dedicated accessibility practice (cf-a11y agent, WCAG 2.1/2.2 + ND-informed UX standards). An early audit catches issues before the UI is deeply built rather than retrofitting. ## Scope ### WCAG 2.1 technical compliance - Color contrast ratios on timeline items, task type indicators, staleness colors (green/blue/purple backlog) — check against 4.5:1 (normal) / 3:1 (large) - Touch target sizes (Flutter desktop → also mobile paths in future) - Screen reader / TalkBack / VoiceOver label coverage on interactive elements - Focus order on timeline interactions ### ND-specific UX review Areas specific to ADHD/executive dysfunction not covered by WCAG: - Error and warning messages — tone check (no guilt/shame language) - Empty states — safe, non-anxiety-inducing copy - Push/defer UI — confirm it doesn't create micro-decisions or cognitive load - Backlog staleness indicators — ensure these inform without nagging - Task failure states (missed, cancelled) — trauma-informed framing - Time displays — support for time blindness (relative + absolute, configurable) ### Demand avoidance considerations - Are any actions framed as obligations rather than choices? - Can all core flows be completed without reading instructional text? - Is there any shame language in default copy, placeholder text, or status labels? ## Output Issues filed per finding. Severity: WCAG-fail (must fix), ND-UX (should fix), suggestion (nice to have). ## CF contributor CF's cf-a11y agent will run this audit against the Flutter UI in `apps/focus_flow_flutter`. Ashley to review and prioritize findings.