Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

6 PASS 3 REVIEW 4 FIX

Web Manifest

Action

Not found

FIX

Not found

No web manifest found

No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark ModeNo Dark Mode Detected

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

Print Stylesheet

Action

No print styles

FIX

No print styles

No print-specific styles detected

When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.

Print Stylesheet No Print Styles

Print stylesheet Not found ✗Inline @media print Not detected ✗

Landmark Structure

2 landmarks

REVIEW

2 landmarks

<main> landmark present

No <nav> landmark found

No banner (header) landmark

Skip navigation link is missing (WCAG 2.4.1)

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Page Structure — as a screen reader sees it

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found - Read the Docs Community ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

6 icon(s) detected

REVIEW

6 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

A+

Heading Hierarchy

18 headings

PASS

18 headings

Single H1 present

H1 Docs as Code for everyone
H2 Automatic deploy previews
H2 Ideal developer experience
H2 Work privately or publicly
H3 Trusted by businesses worldwide since 2010
H3 Features
H3 Supports any doc tool
H3 Integrated search
H3 Pull request previews
H3 Versioned docs
H3 Private repository support Paid plan feature
H3 Single-Sign On Paid plan feature
H2 Upgrade your documentation with Read the Docs
H3 Join thousands of happy users
H4 Stay updated
H4 Learn more
H4 Product
H4 Company

A+

Alt Text Quality

All 11 images OK

PASS

All 11 images OK

11 image(s) with good alt text

11 images 11 good alt text

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Link & Button Quality

64 links, 0 buttons — all OK

PASS

64 links, 0 buttons — all OK

10 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: http://status.readthedocs.com; https://docs.readthedocs.io/page/support.html; https://docs.readthedocs.io; https://docs.readthedocs.io/page/tutorial/; http://status.readthedocs.com; https://docs.readthedocs.io/page/support.html; https://docs.readthedocs.io; https://docs.readthedocs.io/page/tutorial/; https://docs.godotengine.org/; https://jupytergis.readthedocs.io/

54 link(s) with descriptive text

64 links

0 empty

0 generic text

10 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
http://status.readthedocs.com	Status	new tab	Add '(opens in new tab)' to text
https://docs.readthedocs.io/page/support…	Support	new tab	Add '(opens in new tab)' to text
https://docs.readthedocs.io	Documentation	new tab	Add '(opens in new tab)' to text
https://docs.readthedocs.io/page/tutoria…	Tutorial	new tab	Add '(opens in new tab)' to text
http://status.readthedocs.com	Status	new tab	Add '(opens in new tab)' to text
https://docs.readthedocs.io/page/support…	Support	new tab	Add '(opens in new tab)' to text
https://docs.readthedocs.io	Documentation	new tab	Add '(opens in new tab)' to text
https://docs.readthedocs.io/page/tutoria…	Tutorial	new tab	Add '(opens in new tab)' to text
https://docs.godotengine.org/	Max Hilbrunner …	new tab	Add '(opens in new tab)' to text
https://jupytergis.readthedocs.io/	Matt Fisher …	new tab	Add '(opens in new tab)' to text

54 links and buttons have descriptive text

Add '(opens in new tab)' to link text or aria-label.

http://status.readthedocs.com; https://docs.readthedocs.io/page/support.html; https://docs.readthedocs.io; https://docs.readthedocs.io/page/tutorial/; http://status.readthedocs.com; https://docs.readthedocs.io/page/support.html; https://docs.readthedocs.io; https://docs.readthedocs.io/page/tutorial/; https://docs.godotengine.org/; https://jupytergis.readthedocs.io/

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

A+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Docs as Code for eve…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Automatic deploy pre…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Ideal developer expe…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Work privately or pu…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Upgrade your documen…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Trusted by businesse…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Features	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Supports any doc too…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Integrated search	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Pull request preview…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Versioned docs	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Private repository s…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Single-Sign On	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Full featured docume…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Log in	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Read the Docs Commun…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
code https://readthedocs.…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Read the Docs Busine…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
code https://readthedocs.…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Sign up	21.00:1	4.5:1	#000000	#FFFFFF	Pass

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

A+

Lighthouse Accessibility Audits

Score 95/100 — 1 failing, 18 passed

PASS

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Get started for free `div.row > div.seven > div.ui > a.ui`
# nodejs: "16" `div.highlight > pre > code > span.c1`
Web Framework `div.ui > a.card > div.content > div.meta`
Data Science Environment `div.ui > a.card > div.content > div.meta`
Game Engine `div.ui > a.card > div.content > div.meta`
Godot Engine `div.ui > a.item > div.content > div.extra`
UC Berkeley Eric and Wendy Schmidt Center for Data Science and Environment `div.ui > a.item > div.content > div.extra`
Create an account `div.column > div.ui > p > a.ui`

These are opportunities to improve the legibility of your content.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Image elements have `[alt]` attributes

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●ARIA attributes are used as specified for the element's role

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●Links have a discernible name

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Deprecated ARIA roles were not used

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○`[role]`s have all required `[aria-*]` attributes

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○`[role]` values are valid

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○Buttons have an accessible name

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.