Skip to content

fix(accessibility): remove duplicate main landmark element - #622

Open
devogechukwu wants to merge 1 commit into
Pi-Defi-world:devfrom
devogechukwu:fix/landmark-accessibility
Open

fix(accessibility): remove duplicate main landmark element#622
devogechukwu wants to merge 1 commit into
Pi-Defi-world:devfrom
devogechukwu:fix/landmark-accessibility

Conversation

@devogechukwu

Copy link
Copy Markdown

this pr closes #514

This PR resolves an accessibility issue where screen reader landmark navigation was broken or misleading due to duplicate main landmark elements on the page.

Changes

  • Modified components/app-layout.tsx: Removed the duplicate <main> element wrapping {children} on line 34. The primary page content is already wrapped inside the <main> tag on line 23 which supports the PageTransition wrapper. Removing the duplicate tag fixes both the accessibility warning and avoids rendering the page children twice.

Verification

  • Verified that the duplicate <main> tag has been removed from the layout.
  • Verified that the document now contains exactly one <main> landmark element wrapping the page content.

@coderabbitai

coderabbitai Bot commented Jun 28, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@devogechukwu, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 56 minutes and 9 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

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 credits.

🚦 How do rate 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 see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: af50d9bf-d510-4b9b-b42d-e308ea8a13bc

📥 Commits

Reviewing files that changed from the base of the PR and between 65292d2 and e458277.

📒 Files selected for processing (1)
  • components/app-layout.tsx
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

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.

<main> landmark not wrapping primary page content

1 participant