Read the Docs is the leading documentation hosting platform used by Python, Django, and thousands of open-source projects — but as a hosting platform it has no WCAG accessibility audit, no Core Web Vitals scoring, and no front-end health monitoring for documentation it serves. PageGuard audits any Read the Docs documentation URL externally — free, no Git repository access 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, nonprofits, and educational institutions publishing documentation on Read the Docs face this compliance deadline. Read the Docs automatically builds and deploys documentation on every Git push, but has no accessibility quality gate before serving new documentation builds — Sphinx theme updates, MkDocs plugin upgrades, and new documentation content (images without alt text, tables without headers, complex nested navigation) can introduce WCAG violations that reach live documentation instantly. Common accessibility issues in Read the Docs documentation include insufficient color contrast in code syntax highlighting, missing ARIA labels on search modals and navigation sidebars, and keyboard navigation gaps in tabbed documentation sections. PageGuard provides continuous front-end accessibility monitoring without requiring Read the Docs account access or documentation source changes.
| Feature | PageGuard | Read the Docs |
|---|---|---|
| What is it? | External website health monitor — scans any URL for performance, accessibility, SEO, and best practices | Documentation hosting platform that builds and hosts technical documentation from Sphinx, MkDocs, and Jupyter Book source files stored in Git repositories; serves documentation at readthedocs.io or custom domains; supports versioned documentation, PDF/ePub generation, pull request previews, automated builds triggered by Git push hooks, full-text search via Elasticsearch, analytics dashboards, and advertising-supported free tier for open-source projects; used by Python, Django, Kubernetes, NumPy, Pandas, and thousands of open-source projects worldwide; commercial Read the Docs for Business from $150/month for private documentation without ads |
| Free tier | ✓ Yes — unlimited one-off scans, no signup required | Read the Docs Community (readthedocs.org) is free for open-source projects supported by advertising and sponsored by Cloudflare, Mozilla, and the Python Software Foundation; Read the Docs for Business starts from $150/month for private documentation, custom domains, password protection, and ad-free hosting; no credit card required for community tier; free tier includes unlimited builds, versioned docs, PR previews, PDF export, and Elasticsearch search |
| Accessibility audit (WCAG / ADA) | ✓ Yes — WCAG 2.1 AA scored 0–100 with specific issue list | No — Read the Docs is a documentation hosting platform that builds and serves documentation HTML generated by Sphinx, MkDocs, and Jupyter Book; it provides no built-in WCAG or ADA accessibility auditing for rendered documentation pages; front-end accessibility quality of Read the Docs-hosted documentation is entirely determined by the Sphinx or MkDocs theme selected (sphinx_rtd_theme, Furo, Material for MkDocs, etc.) and the reStructuredText or Markdown content that generates headings, code blocks, images, tables, and navigation; Read the Docs itself has no ARIA audit, color contrast checker, or keyboard navigation testing for the generated HTML output; themes from the Sphinx or MkDocs ecosystem may include components created before WCAG 2.1 was published |
| Technical SEO audit | ✓ Yes — meta tags, headings, canonical, structured data | No — Read the Docs generates documentation with basic SEO meta tags derived from page titles, but provides no SEO audit scores, heading hierarchy analysis, canonical URL validation, structured data verification, or meta description quality checking; documentation search rankings depend on the documentation structure and content quality; Read the Docs adds a canonical tag to point to the latest stable version of documentation, but this is automated configuration rather than an interactive SEO audit tool |
| Performance audit (Core Web Vitals) | ✓ Yes — LCP, CLS, FCP scored 0–100 per scan | No — Read the Docs does not measure Core Web Vitals (LCP, CLS, FCP, INP) for documentation pages it hosts; documentation page performance depends on the theme's CSS and JavaScript bundle size, embedded images from documentation content, CDN configuration, and the complexity of theme JavaScript features like navigation sidebars, search modals, and syntax highlighting; Read the Docs provides traffic analytics (page views, search queries) but no browser-side rendering performance metrics |
| Documentation hosting (Sphinx / MkDocs) | No — PageGuard is a front-end quality monitoring tool | ✓ Yes — Read the Docs' core capability: automated documentation builds triggered by Git webhooks; supports Sphinx (rst, MyST Markdown), MkDocs (Markdown, YAML config), and Jupyter Book; versioned documentation with stable, latest, and tagged release branches; pull request preview builds; PDF and ePub generation; full-text Elasticsearch search with autocomplete; custom domain with SSL; internationalization (i18n) support for multi-language documentation; flyout widget for version/language switching; extensive ecosystem of themes including sphinx_rtd_theme (50K+ repositories), Furo, PyData Sphinx Theme, and Material for MkDocs |
| Versioned documentation builds | No — PageGuard is a front-end quality monitoring tool | ✓ Yes — Read the Docs automatically builds and hosts multiple versions of documentation simultaneously; each Git tag, branch, or release can be served as a separate documentation version accessible at /en/stable/, /en/latest/, /en/v1.x/; documentation consumers can switch between versions using the flyout widget; version management is automated through the Read the Docs dashboard; deprecation warnings can be added to older versions; this versioning system is a core differentiator versus self-hosted documentation on Netlify or Vercel where versioning requires custom implementation |
| Automated website monitoring | ✓ Yes — weekly or daily scans with email alerts on score drop | No — Read the Docs monitors documentation build status (build success/failure, build time, deploy status) and provides traffic analytics (page views, search queries, referrers); it does not perform automated front-end quality monitoring for WCAG compliance, Core Web Vitals regressions, SEO quality, or best practices for the rendered documentation HTML |
| AI-generated plain-English report | ✓ Yes — explains issues in non-technical language | No — no AI-generated accessibility analysis or plain-English quality report for documentation hosted on Read the Docs; documentation authors see build logs, build warnings (broken references, missing images, deprecated directives), and traffic analytics, but no health report explaining WCAG issues or SEO improvements in plain language |
| ADA Title II compliance monitoring | ✓ Yes — WCAG audit + alert on accessibility regression | No — Read the Docs does not audit or alert on WCAG compliance for documentation it hosts; government agencies, nonprofits, and educational institutions using Read the Docs for public-facing technical documentation face ADA Title II compliance requirements with an April 24, 2026 deadline; Sphinx and MkDocs themes may have unresolved accessibility issues including insufficient color contrast in code syntax highlighting, missing ARIA labels on navigation sidebars, keyboard navigation gaps in search modals, and inaccessible tabbed content in documentation; Sphinx extension upgrades, theme version updates, and content additions (tables without headers, images without alt text, complex nested navigation) can introduce WCAG regressions with each documentation build; Read the Docs has no front-end quality gate that validates accessibility before serving a new build |
| Works on any platform | ✓ Yes — scans any URL on any front-end or platform | Read the Docs hosts documentation from Git repositories; it does not monitor or audit documentation or websites hosted on other platforms |
| Independent external audit | ✓ Yes — third-party scan, shareable URL for clients/stakeholders | No — no built-in tool to generate a shareable external accessibility or performance health report for documentation hosted on Read the Docs; documentation maintainers who need to demonstrate WCAG compliance to government procurement teams or grant reviewers must use a separate tool |
| Instant on-demand scan | ✓ Yes — results in 30 seconds, no code changes needed | No — no on-demand front-end health scan for documentation hosted on Read the Docs; auditing WCAG compliance and Core Web Vitals for Read the Docs-hosted documentation requires separate tools like Lighthouse, axe-core, or Pa11y run against the live documentation URL |
| Multi-site dashboard | ✓ Yes — 1–50 sites depending on plan | Read the Docs provides a project dashboard for managing multiple documentation projects, build history, version management, and analytics across all projects in an organization; there is no cross-project front-end health monitoring showing WCAG accessibility, SEO, and Core Web Vitals scores across multiple documentation sites |
| Pricing for health monitoring | ✓ Free + from $9/mo for automated monitoring | Health monitoring not available — Read the Docs Community: free for open source (ad-supported); Business: from $150/month (private docs, custom domains, no ads); Enterprise: custom pricing; no front-end quality monitoring included at any tier |
Get WCAG accessibility scores and Core Web Vitals for any documentation hosted on Read the Docs. Results in 30 seconds. No Git repository access, API tokens, or Read the Docs account required.
Results in ~30 seconds. 4 scores: Performance, Accessibility, SEO, Best Practices.
Yes — PageGuard scans the live URL of any documentation site hosted on Read the Docs. Enter your documentation 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 Read the Docs account, Git repository access, or source changes are required.
No — Read the Docs is a documentation hosting platform with no built-in WCAG compliance checking. Read the Docs builds and serves HTML generated by Sphinx or MkDocs themes but has no awareness of WCAG requirements. Common issues include insufficient color contrast in syntax highlighting, missing ARIA labels on search modals and navigation sidebars, keyboard gaps in tabbed sections, and images without alt text. Each build can introduce accessibility regressions. PageGuard audits the live documentation URL and provides a WCAG 2.1 AA score with specific issues to fix.
Read the Docs deploys new documentation on every Git push, but front-end accessibility quality depends entirely on the theme, extensions, and content — not the hosting platform. Government agencies, nonprofits, and universities publishing on Read the Docs face ADA Title II requirements with an April 24, 2026 deadline. Theme updates, extension upgrades, and new content can all introduce WCAG regressions automatically. PageGuard provides continuous post-build accessibility monitoring with email alerts when WCAG scores drop.
No — they serve completely different purposes. Read the Docs is a documentation hosting platform that builds Sphinx and MkDocs documentation from Git repositories and serves versioned docs with full-text search, PR previews, and PDF export. PageGuard is an external quality monitoring tool for the rendered front-end output of documentation pages — including those hosted on Read the Docs. Documentation teams should add PageGuard to continuously verify WCAG compliance, Core Web Vitals, and SEO quality, especially for publicly accessible government or educational documentation.