Skip to content
https://www.ruby-lang.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
65
GRADE
D
FIX
4
REVIEW
6
PASS
3
INFO
0
Checks
13
3 PASS 6 REVIEW 4 FIX
D
Landmark Structure
Action
5 landmarks
FIX
5 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
3 <nav> landmark(s) found
Warning::
3 of 3 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Warning::
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
BANNER header NAV MAIN (missing!) CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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

D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
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 ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
3 navigation landmark(s) detected
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 3 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Heading Hierarchy
18 headings
REVIEW
18 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 Why Ruby?
  • H3 Ecosystem
  • H3 Simple
  • H3 Productivity
  • H3 Community
  • H2 Join the Community
  • H2 News
  • H3 Ruby 3.2.11 Released
  • H3 Ruby 3.3.11 Released
  • H3 Ruby 4.0.2 Released
  • H3 Ruby 3.4.9 Released
  • H2 Security
  • H3 CVE-2026-27820: Buffer overflow vulnerability in Zlib::GzipReader
  • H3 CVE-2025-61594: URI Credential Leakage Bypass previous fixes
  • H3 CVE-2025-58767: DoS vulnerability in REXML
  • H3 CVE-2025-24294: Possible Denial of Service in resolv gem
  • H3 CVE-2025-43857: DoS vulnerability in net-imap
  • H3 Security advisories: CVE-2025-27219, CVE-2025-27220 and CVE-2025-27221

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404: Not Found | Ruby ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

B
Lighthouse Accessibility Audits
Score 88/100 — 3 failing, 20 passed
REVIEW
88

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.container > div.flex > div.flex > button#mobile-menu-toggle div.container > div.flex > div.flex > button#mobile-menu-toggle

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

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
DOWNLOAD div.absolute > div.absolute > div.flex > a.mt-4
# Output "I love Ruby" figure.highlight > pre > code.language-ruby > span.c1
puts figure.highlight > pre > code.language-ruby > span.nb
# Output "I *LOVE* RUBY" figure.highlight > pre > code.language-ruby > span.c1
puts figure.highlight > pre > code.language-ruby > span.nb
# Output "I *love* Ruby" figure.highlight > pre > code.language-ruby > span.c1
# five times figure.highlight > pre > code.language-ruby > span.c1
puts figure.highlight > pre > code.language-ruby > span.nb
# Ruby knows what you figure.highlight > pre > code.language-ruby > span.c1
# mean, even if you figure.highlight > pre > code.language-ruby > span.c1
# want to do math on figure.highlight > pre > code.language-ruby > span.c1
# an entire Array figure.highlight > pre > code.language-ruby > span.c1
puts figure.highlight > pre > code.language-ruby > span.nb
# The Greeter class figure.highlight > pre > code.language-ruby > span.c1
name figure.highlight > pre > code.language-ruby > span.nb
name figure.highlight > pre > code.language-ruby > span.nb
puts figure.highlight > pre > code.language-ruby > span.nb
# Create a new object figure.highlight > pre > code.language-ruby > span.c1
# Output "Hello World!" figure.highlight > pre > code.language-ruby > span.c1
Try Ruby div.container > div.text-center > p.text-stone-700 > a.text-semantic-text-link
Ecosystem div.why-ruby-card > div.relative > div.relative > h3.text-5xl
Creator of Ruby div.relative > div.flex-shrink-0 > div.text-left > p.text-xs
Simple div.why-ruby-card > div.relative > div.relative > h3.text-5xl
Creator of Ruby on Rails div.relative > div.flex-shrink-0 > div.text-left > p.text-xs
Productivity div.why-ruby-card > div.relative > div.relative > h3.text-5xl
Author of "The Pragmatic Programmer" div.relative > div.flex-shrink-0 > div.text-left > p.text-xs
Community div.why-ruby-card > div.relative > div.relative > h3.text-5xl
Executive Director of Rails Foundation div.relative > div.flex-shrink-0 > div.text-left > p.text-xs
The universal motto is "MINASWAN" — Matz is nice and so we are nice section.community-section > div.container > div.text-center > p.text-lg
MINASWAN div.container > div.text-center > p.text-lg > span.font-bold
Matz is nice and so we are nice div.container > div.text-center > p.text-lg > span.italic
Continue Reading... div.space-y-6 > article.pb-6 > p.mt-1 > a.text-xs
Continue Reading... div.space-y-6 > article.pb-6 > p.mt-1 > a.text-xs
Continue Reading... div.space-y-6 > article.pb-6 > p.mt-1 > a.text-xs
Continue Reading... div.space-y-6 > article.pb-6 > p.mt-1 > a.text-xs
Read more news div.grid > div.lg:col-span-2 > p.mt-4 > a.text-sm
Read more security div.grid > div > p.mt-4 > a.text-sm

These are opportunities to improve the legibility of your content.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.fonts-loaded html.fonts-loaded

These items highlight common accessibility best practices.

○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
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
○`[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
○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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○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
○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.
A+
Alt Text Quality
All 94 images OK
PASS
All 94 images OK
Info::
40 decorative image(s) correctly marked
Info::
54 image(s) with good alt text
94 images 54 good alt text 40 decorative
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
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)
ElementRatioRequiredFGBGResult
h2 Why Ruby?18.09:13.0:1
#000000
#F1EEE4
Pass
h3 Ecosystem18.09:13.0:1
#000000
#F1EEE4
Pass
h3 Simple18.09:13.0:1
#000000
#F1EEE4
Pass
h3 Productivity18.09:13.0:1
#000000
#F1EEE4
Pass
h3 Community18.09:13.0:1
#000000
#F1EEE4
Pass
title Ruby Programming Lan…21.00:14.5:1
#000000
#FFFFFF
Pass
span Ruby21.00:14.5:1
#000000
#FFFFFF
Pass
a Install19.76:14.5:1
#000000
#F9F8F4
Pass
a Docs18.09:14.5:1
#000000
#F1EEE4
Pass
a Libraries18.09:14.5:1
#000000
#F1EEE4
Pass
a Contribution15.25:14.5:1
#000000
#E6DBBF
Pass
a Community18.09:14.5:1
#000000
#F1EEE4
Pass
a News18.09:14.5:1
#000000
#F1EEE4
Pass
span English17.78:14.5:1
#000000
#F0ECE0
Pass
span Български17.48:14.5:1
#000000
#EFEADD
Pass
span Deutsch17.30:14.5:1
#000000
#EEE9DA
Pass
span English18.09:14.5:1
#000000
#F1EEE4
Pass
span Español18.09:14.5:1
#000000
#F1EEE4
Pass
span Français18.09:14.5:1
#000000
#F1EEE4
Pass
span Indonesia18.09:14.5:1
#000000
#F1EEE4
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.

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

Send Feedback