Base body text ~20px, smallest 13px.
content · Aug 9, 2026
30/100 Sparse
Scores above 18% of 1,252 multi-step funnels we have measured. Among the 63 content funnels in that group, above 42%.
Coverage is detection coverage, not a verdict — it counts the conversion tactics we could prove are present, out of the 5 that apply to a content funnel.
Measured by Roentgen 1.20.1, one of our versioned rulesets. A capture is read once and its measurements freeze there, so the stamp says which ruleset read this one.
Walk 5 links seen, 4 walkable, 3 matched, and we walked 4 pages.
see their whole funnel without clicking through it. scored step by step
measuredextracted directly from the live page. a fact, not an opinionthe entry page’s own title, headline, buttons and prices — quoted, never paraphrased
measuredextracted directly from the live page. a fact, not an opinionFree Planning Poker App & Scrum Poker Online | Planning Poker by TeamRetro
Free Planning Poker app for agile teams — run scrum poker story-point estimation in your browser, in real time, with no account and nothing to install. Vote, reveal, and align with TeamRetro.
Free Planning Poker Online for Agile Teams
How to run a planning poker session online
Scrum poker built for agile estimation
Planning Poker FAQ
Keep learning
Create a room
Invite your team
Vote and reveal
Built for remote teams+2 more, not shown
expand_more
Learn expand_more
support
question_mark
DISCUSS ESTIMATE REVIEW
DISCUSS
ESTIMATE
REVIEW
Try the demo
Create a room
conversion tactics we could prove are present, with the on-page text that evidences each
measuredextracted directly from the live page. a fact, not an opinionIs Planning Poker free? What is Planning Poker? Do I need an account to use Planning Poker
applicable tactics we checked for and did not see on any step we reached
measuredextracted directly from the live page. a fact, not an opinionAbsence is a measurement, not a recommendation: we do not know why a tactic is missing, whether it belongs here, or whether adding it would change anything. Where a walk stopped early, a tactic living deeper would also read as not detected.
contrast, mobile, typography, accessibility, weight — each with what would fix it
measuredextracted directly from the live page. a fact, not an opinion36% of measurable text passes WCAG AA. 4+ runs fail. 19% of text was unmeasurable (over images/gradients). not counted either way.
worst: “Estimate” at 1:1 (14px, #ffffff on #ffffff). needs 4.5:1
fix Raise text/background contrast to ≥4.5:1 (≥3:1 for large text), especially on CTAs and body copy.
Responsive viewport meta is present.
Base body text ~20px, smallest 13px.
2 paragraphs run past ~95 characters per line.
fix Cap measure at ~60-75ch for comfortable reading.
html[lang] is set for screen readers.
All 67 content images carry alt text.
3 form fields rely on placeholder text as the only label.
fix Back placeholders with a real <label>. placeholder text vanishes on input.
52 buttons/links have no accessible name (icon-only, no aria-label).
fix Add aria-label to icon-only buttons and links.
No same-page “skip to content” link was found. Keyboard users tab through the whole nav on every page.
fix Add a first-in-DOM <a href="#main"> that is visible on focus.
5 controls have an aria-label that does not contain its visible text, so voice-control users cannot activate it by saying what they see.
fix Make the accessible name start with the visible label text.
The page scrolls ~48px horizontally at 1440px wide. content spills past the viewport.
fix Find the overflowing element (fixed widths, unwrapped rows) and constrain it to 100%.
At least 0.6 MB across 22 measurable resources, but 120 cross-origin resources did not expose a size. The true weight cannot be determined from the page.
67 images are shipped at more than 2x the width shown.
“PlanningPoker.svg” is 855px wide, displayed at 192px
fix Serve responsive sizes (srcset/sizes) matching the rendered width.
No <main> or <footer> landmark. screen-reader users cannot jump between regions.
fix Wrap the page in <header>, <main> and <footer> (or matching ARIA roles).
35 elements look clickable but cannot be reached by keyboard.
“User authentication system with so”, “User authentication system with so”, “Shopping cart functionality with p”
fix Use <button>/<a>, or add role + tabindex="0" and a key handler.
palette by on-page usage · type rendered live
measuredextracted directly from the live page. a fact, not an opinionBody copy in their text role, on a surface card.
Body copy set at their measured paragraph size. This is how their product reads to a first-time visitor. same family, same scale, same weight.
We also looked for Sections, Elements and Playbook match, and found none on this funnel.