Nextra is a Next.js-based documentation framework with 12K+ GitHub stars — MDX content, built-in full-text search, automatic sidebar, dark mode, and deep Next.js App Router integration — but as a static site framework it has no built-in WCAG accessibility audit, no Core Web Vitals scoring, and no post-deployment health monitoring. PageGuard audits the live deployed URL of any Nextra documentation site externally — free, no source code needed, results in 30 seconds.
ADA Title II Deadline: April 24, 2026
State and local government websites must meet WCAG 2.1 AA by April 24, 2026. Government agencies, universities, public libraries, and nonprofits frequently use Nextra to build documentation and policy guides on the Next.js platform. Nextra theme updates and Next.js major version upgrades can silently introduce accessibility regressions — common issues include the full-text search modal lacking proper ARIA combobox roles and focus trapping, Tabs and Steps components missing keyboard navigation, code block themes with insufficient color contrast, and custom React components embedded in MDX pages lacking ARIA labels. These issues only appear in the deployed, browser-rendered output and require external runtime validation. PageGuard provides continuous post-deployment accessibility monitoring without modifying your MDX pages or Next.js configuration.
| Feature | PageGuard | Nextra |
|---|---|---|
| What is it? | External website health monitor — scans any URL for performance, accessibility, SEO, and best practices | Next.js-based documentation framework created by Shuding (Vercel engineer) — turns a Next.js app into a documentation site using MDX, built-in full-text search, automatic sidebar from directory structure, dark/light mode, i18n, and code syntax highlighting; Nextra 2 uses Next.js 13+ App Router; 12K+ GitHub stars; powers SWR docs, Turbo docs, shadcn/ui docs, and hundreds of developer tool documentation sites |
| Free tier | ✓ Yes — unlimited one-off scans, no signup required | Free and open source (MIT license); no SaaS pricing — install via npm, create a Next.js project, add Nextra as a plugin, write MDX pages, run next build, and deploy the static or server-rendered output to Vercel, Netlify, or any Node.js host; Vercel provides free hosting for open source Nextra projects |
| Accessibility audit (WCAG / ADA) | ✓ Yes — WCAG 2.1 AA scored 0–100 with specific issue list | No — Nextra generates documentation from MDX and Next.js React components but has no built-in WCAG or ADA accessibility auditing; accessibility quality is entirely determined by the chosen Nextra theme (Docs or Blog), any custom React components embedded in .mdx files, and the interactive elements of the built-in search modal and navigation system |
| Technical SEO audit | ✓ Yes — meta tags, headings, canonical, structured data | No — Nextra uses Next.js Metadata API to generate title, meta description, Open Graph, and canonical URLs from page frontmatter; auto-generates sitemap via next-sitemap; but provides no SEO audit scores, heading hierarchy validation, or structured data completeness checking for the rendered documentation output |
| Performance audit (Core Web Vitals) | ✓ Yes — LCP, CLS, FCP scored 0–100 per scan | No — Nextra benefits from Next.js optimizations (image optimization, font optimization, React Server Components, partial prerendering) but Core Web Vitals depend on the theme CSS bundles, custom MDX components, embedded media, and search JavaScript; no built-in CWV measurement or scoring for deployed documentation sites |
| Next.js documentation framework | No — PageGuard is a monitoring tool, not a documentation framework | ✓ Yes — Nextra integrates deeply with Next.js: use React Server Components and Client Components in MDX, leverage Next.js image optimization and font loading in documentation pages, deploy to Vercel with zero configuration, use Next.js middleware for authentication-gated private documentation, and benefit from incremental static regeneration for large documentation sites with thousands of pages |
| MDX + React component integration | No — PageGuard is a standalone monitoring service | ✓ Yes — Nextra uses next-mdx-remote to process MDX with full React component support; embed interactive demos, live code sandboxes, API explorers, and custom callout components directly in documentation pages; the Docs theme provides built-in Card, Steps, Tabs, Callout, FileTree, and Table components; custom components via _meta.json configuration |
| Automated website monitoring | ✓ Yes — weekly or daily scans with email alerts on score drop | No — Nextra is a documentation framework; it has no post-deployment health monitoring, accessibility regression alerts, Core Web Vitals tracking, or uptime checking for the documentation sites it generates |
| AI-generated plain-English report | ✓ Yes — explains issues in non-technical language | No — no AI health report for sites built with Nextra |
| ADA Title II compliance monitoring | ✓ Yes — WCAG audit + alert on accessibility regression | No — Nextra does not audit or alert on WCAG compliance; common accessibility issues in Nextra documentation sites include: the built-in full-text search modal lacking proper focus trapping and ARIA combobox role, custom MDX component blocks (Tabs, Steps, Callout) missing keyboard navigation support, code block syntax highlighting with insufficient color contrast in the default theme, and the mobile navigation drawer not managing focus when opened or closed — all requiring external runtime validation on the deployed site |
| Works on any platform | ✓ Yes — scans any URL on any front-end or platform | No — Nextra builds your own documentation site only; it does not audit sites built by others or sites using different frameworks |
| Independent external audit | ✓ Yes — third-party scan, shareable URL for clients/stakeholders | No — no built-in tool to generate a shareable external health report for a Nextra-generated documentation site |
| Instant on-demand scan | ✓ Yes — results in 30 seconds, no code changes needed | No — no on-demand health scan; external auditing of Nextra sites requires separate tools like Lighthouse or axe after deployment |
| Multi-site dashboard | ✓ Yes — 1–50 sites depending on plan | Nextra generates individual documentation sites; there is no health monitoring dashboard showing accessibility, SEO, and performance scores across multiple Nextra deployments |
| Pricing for health monitoring | ✓ Free + from $9/mo for automated monitoring | Health monitoring not available — Nextra is a Next.js documentation framework, not a website health monitoring tool |
Get the WCAG accessibility score and Core Web Vitals for your deployed Nextra documentation site. Results in 30 seconds. No Next.js installation, MDX source code, or Vercel account required.
Results in ~30 seconds. 4 scores: Performance, Accessibility, SEO, Best Practices.
Yes — PageGuard scans the live deployed URL of any Nextra documentation site hosted on Vercel, Netlify, or a self-managed Node.js server. Enter the public URL and receive a full health report in ~30 seconds covering Core Web Vitals, WCAG 2.1 AA accessibility, technical SEO, and best practices. No Next.js installation, Nextra configuration, or MDX source code is required.
No — Nextra generates documentation from MDX and Next.js React components with no WCAG compliance checking. Common issues include the built-in search modal lacking ARIA combobox roles and focus trapping, Tabs and Steps components missing keyboard navigation, code block syntax highlighting with insufficient color contrast, and custom React components in MDX pages lacking ARIA labels. PageGuard audits your live Nextra site and provides a WCAG 2.1 AA score with specific issues to fix.
Nextra is used by developer tools companies, open source projects, and organizations whose documentation may be subject to ADA Title II requirements by April 24, 2026. Nextra theme updates, Next.js major version upgrades, and new MDX component integrations can silently introduce accessibility regressions in interactive elements like the search modal, Tabs navigation, collapsible sections, and custom React components. PageGuard provides continuous post-deployment monitoring without requiring changes to your MDX content or Next.js configuration.
No — they serve completely different purposes. Nextra is a Next.js documentation framework converting MDX files into fast documentation sites with built-in search, automatic sidebar, dark mode, and deep App Router integration. PageGuard is an external quality monitoring tool for the deployed output of those documentation sites. Organizations running Nextra documentation should use PageGuard to continuously monitor and improve accessibility, SEO, and performance without modifying their existing Next.js or MDX setup.