WCAG-focused review
Structure, interaction, source, responsive behavior, and assistive-technology considerations.
Illustrative workflow Ready for review
XA-TFM-003Task friction
The primary action is difficult to distinguish
Three equally prominent paths appear before the first useful step, increasing choice load and obscuring the intended task.
Why it matters
People scanning quickly or managing attention and working-memory demands may pause, choose a detour, or leave without beginning.
Proposed change
− Three equal-weight actions+ One primary action, two quiet alternativesPreviewed. No files changed.
Traceable to findingUndo fixRevert session
01 Standards-aware
02 Task-aware
03 Code-aware
04 Developer-controlled
One controlled process
Evidence becomes action without becoming a black box.
WCAG-focused review and Xezom’s Task Friction Mapping converge on one finding ledger. Reasoning, proposed code, approval, validation, and recovery remain connected throughout.
Task Friction Mapping
Where someone may lose the thread while orienting, starting, acting, recovering, or resuming.
Finding ledger
- 01
Review
Gather concrete evidence around a real task.
- 02
Reason
Explain the barrier, impact, and certainty.
- 03
Preview
Connect an eligible code change to its finding.
- 04
Approve
Keep implementation behind explicit developer control.
- 05
Validate
Verify the result and retain undo or full reversion.
- Stable finding IDs
- Evidence-linked reasoning
- Preview before change
- Per-finding undo
- Full-session revert
A Xezom framework
Accessibility includes the effort it takes to complete a task.
Task Friction Mapping gives developers a consistent way to examine cognitive and interaction demands that conventional scanners may overlook. It supplements WCAG; it is not a medical assessment or a replacement for standards-based review.
- 01
Orient
Purpose, place, and the next meaningful action are clear.
- 02
Start
The first useful step is apparent without unnecessary decisions.
- 03
Act
Context remains visible while competing signals stay quiet.
- 04
Recover
Errors explain what happened and preserve completed work.
- 05
Resume
A return path restores intent, position, and the next step.
Built for developer control
Automation you can inspect, approve, and reverse.
Every finding explains the task impact, evidence, and recommended direction.
Proposed code remains visible and unchanged until the developer approves it.
Undo one finding without disturbing the others, or revert the complete session.
Early developer testing
Bring us a real task. Keep your keys.
The core review, reasoning, code-remediation, validation, undo, and reversion capabilities are functional and have passed initial controlled tests. Select participants will receive funded API access, with no model key or analysis charges required.