Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 4 REVIEW 4 FIX

Web Manifest

Action

Valid manifest

FIX

Valid manifest

No name or short_name

Add a name field to identify the app.

192x192 icon present

512x512 icon present

PWA Install Criteria Not Installable

Name ✗192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode ✗

Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)

Dark Mode Support

Action

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #ffffff

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 ModePartial Dark Mode

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 1 <nav> element(s)

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.

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 - Rust Programming Language ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

6 icon(s) detected

REVIEW

6 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✓ Manifest Icons Present

✓ Multiple Sizes Present

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

REVIEW

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

20 pass 19 pass AA only

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Rust	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 A language empowerin…	3.59:1	3.0:1	#000000	#0B7261	Pass
h2 to build reliable an…	3.59:1	3.0:1	#000000	#0B7261	Pass
h2 Why Rust?	3.59:1	3.0:1	#000000	#0B7261	Pass
h2 Build it in Rust	3.59:1	3.0:1	#000000	#0B7261	Pass
h2 Rust in production	3.59:1	3.0:1	#000000	#0B7261	Pass
h2 Get involved	3.59:1	3.0:1	#000000	#0B7261	Pass
h2 Thanks	3.59:1	3.0:1	#000000	#0B7261	Pass
h3 Performance	3.59:1	3.0:1	#000000	#0B7261	Pass
h3 Reliability	3.59:1	3.0:1	#000000	#0B7261	Pass
h3 Productivity	3.59:1	3.0:1	#000000	#0B7261	Pass
h3 Command Line	3.59:1	3.0:1	#000000	#0B7261	Pass
h3 WebAssembly	3.59:1	3.0:1	#000000	#0B7261	Pass
h3 Networking	3.59:1	3.0:1	#000000	#0B7261	Pass
h3 Embedded	3.59:1	3.0:1	#000000	#0B7261	Pass
h3 Read Rust	3.59:1	3.0:1	#000000	#0B7261	Pass
h3 Watch Rust	3.59:1	3.0:1	#000000	#0B7261	Pass
h3 Contribute code	3.59:1	3.0:1	#000000	#0B7261	Pass
h3 Individuals	3.59:1	3.0:1	#000000	#0B7261	Pass
h3 Corporate sponsors	3.59:1	3.0:1	#000000	#0B7261	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.

Lighthouse Accessibility Audits

Score 87/100 — 2 failing, 13 passed

REVIEW

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
Version 1.94.1 `div.flex > div.w-30-l > p.tc > a.download-link`

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
File an issue! `div.w-100 > div.attribution > p > a`
previous website `div.w-100 > div.attribution > p > a`

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-hidden="true"]` is not present on the document `<body>`

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

●Select elements have associated label elements.

●Document has a `<title>` element

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

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

●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

●Document has a main landmark.

○`[accesskey]` values are unique

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

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

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

○Deprecated ARIA roles were not used

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

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted ARIA attributes

○`[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

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

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

○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

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

○`<object>` elements have alternate text

○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

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

Landmark Structure

9 landmarks

PASS

9 landmarks

<main> landmark present

1 <nav> landmark(s) found

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

A+

Heading Hierarchy

22 headings

PASS

22 headings

Single H1 present

H1 Rust
H2 A language empowering everyone to build reliable and efficient software.
H2 Why Rust?
H3 Performance
H3 Reliability
H3 Productivity
H2 Build it in Rust
H3 Command Line
H3 WebAssembly
H3 Networking
H3 Embedded
H2 Rust in production
H2 Get involved
H3 Read Rust
H3 Watch Rust
H3 Contribute code
H2 Thanks
H3 Individuals
H3 Corporate sponsors
H4 Get help!
H4 Terms and policies
H4 Social

A+

Alt Text Quality

All 9 images OK

PASS

All 9 images OK

9 image(s) with good alt text

9 images 9 good alt text

All images have appropriate alt text.

A+

Form Accessibility

All 2 controls labeled

PASS

All 2 controls labeled

2 control(s) properly labeled

2 controls

2 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#language-nav	select	Language	for/id
#language-footer	select	Language	for/id

Link & Button Quality

35 links, 0 buttons — all OK

PASS

35 links, 0 buttons — all OK

5 link(s) open in new tab without warning

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

Got: https://social.rust-lang.org/@rust; https://bsky.app/profile/rust-lang.org; https://www.youtube.com/channel/UCaYhcUwRBNscFNUKTjgPFiA; https://github.com/rust-lang; https://github.com/rust-lang/www.rust-lang.org/issues/new/choose

30 link(s) with descriptive text

35 links

0 empty

0 generic text

5 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://social.rust-lang.org/@rust	Mastodon	new tab	Add '(opens in new tab)' to text
https://bsky.app/profile/rust-lang.org	Bluesky	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/channel/UCaYhcUw…	youtube logo	new tab	Add '(opens in new tab)' to text
https://github.com/rust-lang	github logo	new tab	Add '(opens in new tab)' to text
https://github.com/rust-lang/www.rust-la…	File an issue!	new tab	Add '(opens in new tab)' to text

30 links and buttons have descriptive text

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

https://social.rust-lang.org/@rust; https://bsky.app/profile/rust-lang.org; https://www.youtube.com/channel/UCaYhcUwRBNscFNUKTjgPFiA; https://github.com/rust-lang; https://github.com/rust-lang/www.rust-lang.org/issues/new/choose

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

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