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 3 REVIEW 5 FIX

Favicon & Branding

Action

1 icon(s) detected

FIX

1 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

No apple-touch-icon detected

iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

✗ favicon.ico Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

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 ✗

Alt Text Quality

Action

6 of 8 images have issues

REVIEW

6 of 8 images have issues

6 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

2 image(s) with good alt text

8 images 2 good alt text 6 missing

Issue	Count
missing	6 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 18 fail WCAG AA

REVIEW

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

2 pass 18 fail WCAG AA

h1 Safe, stable,

1.31:1

#000000

#231B44

needs 3.0:1 (large text)

32px · mid-page · over background image/gradient

h1 reproducible projects

1.58:1

#000000

#3F2450

needs 3.0:1 (large text)

32px · mid-page

h3 Workspaces

1.08:1

#000000

#090B1F

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Stability

1.08:1

#000000

#090B1F

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Documentation

1.08:1

#000000

#090B1F

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Plugins

1.08:1

#000000

#090B1F

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Innovation

1.08:1

#000000

#090B1F

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Openness

1.08:1

#000000

#090B1F

needs 3.0:1 (large text)

19px · bottom of viewport

b Yarn

1.42:1

#000000

#362038

needs 3.0:1 (large text)

16px · top of page (header area)

a Get Started

1.39:1

#000000

#341F35

needs 4.5:1 (normal text)

16px · top of page (header area)

a Features

1.36:1

#000000

#321D33

needs 4.5:1 (normal text)

16px · above the fold

a CLI

1.32:1

#000000

#2F1B30

needs 4.5:1 (normal text)

16px · above the fold

a Configuration

1.30:1

#000000

#2D1A2D

needs 4.5:1 (normal text)

16px · above the fold

a Advanced

1.28:1

#000000

#2B192A

needs 4.5:1 (normal text)

16px · above the fold

a Blog

1.25:1

#000000

#291728

needs 4.5:1 (normal text)

16px · above the fold

a API

1.23:1

#000000

#271625

needs 4.5:1 (normal text)

16px · above the fold

a master (4.14.1-dev)

1.20:1

#000000

#241423

needs 4.5:1 (normal text)

16px · above the fold

a master (4.14.1-dev)

1.18:1

#000000

#221320

needs 4.5:1 (normal text)

16px · above the fold

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Safe, stable,	1.31:1	3.0:1	#000000	#231B44	Fail
h1 reproducible project…	1.58:1	3.0:1	#000000	#3F2450	Fail
h3 Workspaces	1.08:1	3.0:1	#000000	#090B1F	Fail
h3 Stability	1.08:1	3.0:1	#000000	#090B1F	Fail
h3 Documentation	1.08:1	3.0:1	#000000	#090B1F	Fail
h3 Plugins	1.08:1	3.0:1	#000000	#090B1F	Fail
h3 Innovation	1.08:1	3.0:1	#000000	#090B1F	Fail
h3 Openness	1.08:1	3.0:1	#000000	#090B1F	Fail
title Home page \| Yarn	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Skip to main content	21.00:1	4.5:1	#000000	#FFFFFF	Pass
b Yarn	1.42:1	3.0:1	#000000	#362038	Fail
a Get Started	1.39:1	4.5:1	#000000	#341F35	Fail
a Features	1.36:1	4.5:1	#000000	#321D33	Fail
a CLI	1.32:1	4.5:1	#000000	#2F1B30	Fail
a Configuration	1.30:1	4.5:1	#000000	#2D1A2D	Fail
a Advanced	1.28:1	4.5:1	#000000	#2B192A	Fail
a Blog	1.25:1	4.5:1	#000000	#291728	Fail
a API	1.23:1	4.5:1	#000000	#271625	Fail
a master (4.14.1-dev)	1.20:1	4.5:1	#000000	#241423	Fail
a master (4.14.1-dev)	1.18:1	4.5:1	#000000	#221320	Fail

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+

Landmark Structure

4 landmarks

PASS

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

No banner (header) landmark

Skip navigation link present

Page Structure — as a screen reader sees it

Heading Hierarchy

7 headings, 1 skip(s)

PASS

7 headings, 1 skip(s)

Single H1 present

Heading level skipped: H1 → H3 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H1 Safe, stable,reproducible projectsstable... canary...
H3 Workspaces skipped
H3 Stability
H3 Documentation
H3 Plugins
H3 Innovation
H3 Openness

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Form Accessibility

1 of 1 controls have issues

PASS

1 of 1 controls have issues

1 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input>

1 controls

0 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
input	input	(Search packages (e.g. babel, webpack, react, ...))	placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input>

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

Link & Button Quality

16 links, 2 buttons — all OK

PASS

16 links, 2 buttons — all OK

4 link(s) open in new tab without warning

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

Got: https://v3.yarnpkg.com; https://classic.yarnpkg.com/en/docs; https://discord.gg/yarnpkg; https://github.com/yarnpkg/berry

12 link(s) with descriptive text

16 links

0 empty

0 generic text

4 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://v3.yarnpkg.com	3.8.7	new tab	Add '(opens in new tab)' to text
https://classic.yarnpkg.com/en/docs	1.22.22	new tab	Add '(opens in new tab)' to text
https://discord.gg/yarnpkg	Discord	new tab	Add '(opens in new tab)' to text
https://github.com/yarnpkg/berry	GitHub	new tab	Add '(opens in new tab)' to text

14 links and buttons have descriptive text

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

https://v3.yarnpkg.com; https://classic.yarnpkg.com/en/docs; https://discord.gg/yarnpkg; https://github.com/yarnpkg/berry

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

Lighthouse Accessibility Audits

Score 93/100 — 2 failing, 21 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.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Workspaces `div.row > div.col > div.text--center > h3`

These are opportunities to improve keyboard navigation in your application.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.row > div.col > div.text--center > img.icon_cRwW `div.row > div.col > div.text--center > img.icon_cRwW`
div.row > div.col > div.text--center > img.icon_cRwW `div.row > div.col > div.text--center > img.icon_cRwW`
div.row > div.col > div.text--center > img.icon_cRwW `div.row > div.col > div.text--center > img.icon_cRwW`
div.row > div.col > div.text--center > img.icon_cRwW `div.row > div.col > div.text--center > img.icon_cRwW`
div.row > div.col > div.text--center > img.icon_cRwW `div.row > div.col > div.text--center > img.icon_cRwW`
div.row > div.col > div.text--center > img.icon_cRwW `div.row > div.col > div.text--center > img.icon_cRwW`

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.

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

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

●`[role]` values are valid

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

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

●Buttons have an accessible name

●Form elements have associated labels

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

●Background and foreground colors have a sufficient contrast ratio

●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

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

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

○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

○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

○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

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

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

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