Skip to content

docs(evidence): re-verify tap-target finding 64e2fc0b10 against current main and live (2026-08-15) - #231

Merged
nish3451 merged 1 commit into
mainfrom
fix/tap-targets-rereverify-2026-08-15
Aug 15, 2026
Merged

docs(evidence): re-verify tap-target finding 64e2fc0b10 against current main and live (2026-08-15)#231
nish3451 merged 1 commit into
mainfrom
fix/tap-targets-rereverify-2026-08-15

Conversation

@nish3451

Copy link
Copy Markdown
Collaborator

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

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 report

Closes the item as re-verified against current main (cdfa877) and live.

…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>
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@greptile-apps greptile-apps Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Your trial has ended. Reactivate Greptile to resume code reviews.

@coderabbitai

coderabbitai Bot commented Aug 15, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@nish3451, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 18 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: defaults

Review profile: CHILL

Plan: Free

Run ID: 45240567-3fc3-4b0f-9004-39ccd395c69d

📥 Commits

Reviewing files that changed from the base of the PR and between cdfa877 and 99a3f10.

📒 Files selected for processing (2)
  • .lane/reports/tap-targets-rereverify-2026-08-15.md
  • docs/evidence/tap-targets-2026-08-09.md

Note

🎁 Summarized by CodeRabbit Free

Your 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 @coderabbitai help to get the list of available commands.

@nish3451
nish3451 merged commit c62211c into main Aug 15, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant