docs(evidence): re-verify tap-target finding 64e2fc0b10 against current main and live (2026-08-15) - #231
Conversation
…nt main and live (2026-08-15) The 44px tap-target fix (PR #48, extended by #70) still holds on the current head: npm run check passes with the tap-target guard pinning the >=44px rules in all five stylesheets, and the full test suite passes (242 tests, 0 failures), including the narrow-viewport Chromium regressions from #174 and #176. Since the 2026-08-14 receipt (base 7ad776a), three commits touched the surface: #176 and #174 (index.css/shared.css layout-only changes that did not move any tap-target rule) and #202/#193 (llms.txt/offer.md text and URLs only). Fresh headless-Chromium full-element sweeps at 390x844 on a local static copy of public/ and on the live deployment show every standalone interactive element on all seven served pages is >=44px in height and width (logo 50, nav links 45, nav CTA 47, lead CTA 44, footer links 44-45, .back 45, in-content CTAs 46, Agent Desk controls 44-65.2); the only sub-44px elements are inline text links inside sentences (.xa1/.xi19/.xp1), exempt under the WCAG 2.5.8/2.5.5 Inline exception and intentionally excluded. All seven live pages serve 200 and match main element-for-element. The finding stays closed with no code change. Co-authored-by: nish3451 <nish3451@users.noreply.github.com> Co-authored-by: CommandCodeBot <noreply@commandcode.ai>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
|
Warning Review limit reached
Next review available in: 18 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Free Run ID: 📒 Files selected for processing (2)
Note 🎁 Summarized by CodeRabbit FreeYour organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/login. Comment |
What
Re-verification lane for review item
64e2fc0b10: "Mobile tap targets fall under WCAG sizes on every page: primary CTAs are 42px tall and nav links ~15px".Verdict: the finding stays closed — no code change required.
Evidence
npm run checkpasses — the tap-target guard pins the ≥44px rules inshared.css,index.css,audit.css,brief-requested.css,styles.css.npm testsuite passes: 242 tests, 0 failures (incl. narrow-viewport Chromium regressions from fix(public): wrap the /agents hero h1 at 280px #174/fix(home): keep the hero mock and its flags inside the viewport below 320px #176).a, button, input, select, textarea, summary), on a local static copy ofpublic/AND the live deployment:.back45px, in-content.cta46px, Agent Desk controls 44–65.2px — all ≥44px on all seven pages, main and live identical..xa1/.xi19/.xp1) — WCAG-exempt under the 2.5.8/2.5.5 "Inline" exception, intentionally excluded.Files
docs/evidence/tap-targets-2026-08-09.md— appended 2026-08-15 re-verification receipt.lane/reports/tap-targets-rereverify-2026-08-15.md— lane reportCloses the item as re-verified against current main (
cdfa877) and live.