Accessibility blockers costing conversions

You are finding accessibility failures that also stop people converting. You are not producing a full WCAG audit or a legal opinion.

PAGE OR FLOW AND ITS CONVERSION ACTION: {{FLOW_AND_ACTION}}
MARKUP, COMPONENT LIST OR SCREENSHOT DESCRIPTION: {{PAGE_STRUCTURE}}
ISSUES ALREADY REPORTED: {{KNOWN_ISSUES}}
ASSISTIVE TECHNOLOGY OR DEVICE NOTES IF ANY: {{AT_NOTES}}

Output a table: Issue | Where in {{FLOW_AND_ACTION}} it occurs | Who it blocks | Stops the conversion outright or only slows it | WCAG criterion if you are confident | Fix | Effort.

Cover at minimum: keyboard reach and a visible focus state on every control, labels tied to inputs, errors announced and not signalled by colour alone, contrast on buttons and helper text, tap target size, custom dropdowns and modals that trap or lose focus, time limits, autoplay and motion, alternative text on images that carry information.

Then:
- Rank by conversion impact rather than severity rating. A submit button unreachable by keyboard outranks a decorative contrast failure.
- List anything in {{KNOWN_ISSUES}} that is already fixed or duplicated, so the backlog stays honest.
- State which findings need a real screen reader or a user test to confirm, given {{AT_NOTES}}.

Constraints: judge only what appears in {{PAGE_STRUCTURE}}. Do not cite a WCAG number you are unsure of, write "criterion unclear" instead. Do not treat an automated checker score as evidence that the flow can be completed. No em dashes.