Menu
CRO lens — are real users excluded from converting by contrast, target size, focus, or semantics? Surveyed by the Analyst.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
CRO lens — does the wording lead with the visitor's value, specifically and concretely? Surveyed by the Analyst.
CRO lens — is the primary action obvious, singular, and labeled with a value-bearing verb? Surveyed by the Analyst.
CRO lens — what steps, fields, or hesitation points stand between intent and completion? Surveyed by the Analyst.
CRO lens — is slowness (LCP/CLS/INP) the thing suppressing conversion? Surveyed by the Analyst.
CRO lens — does the block show that others already chose this, at the moment of decision? Surveyed by the Analyst.
CRO lens — is there an honest reason to act now rather than later? Surveyed by the Analyst.
| name | cro-accessibility-as-conversion |
| description | CRO lens — are real users excluded from converting by contrast, target size, focus, or semantics? Surveyed by the Analyst. |
| license | Apache-2.0 |
| metadata | {"version":"1.1.0"} |
Lens question: Is anyone being prevented from completing the action — low contrast, tiny tap targets, keyboard traps, missing labels — such that fixing access is a conversion lift, not just compliance?
Signal of the gap (DOM/RUM):
a.button), target < 44px, action
reachable only by mouse, unlabeled controls, broken heading hierarchy in the
block's decorated DOM, images missing alt text — the same items the EDS
code-review checklist flags.Variant kind it implies: CSS-only for contrast, target size, focus-visible styling. Mixed if semantics/ARIA need repair inside the block's decorate path. This lens is also a guardrail — a variant from another lens must never regress it (the block manifest carries an accessibility guardrail the Validator enforces).