Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 3 REVIEW 6 FIX

404 Error Page

Action

HTTP 404, bare page

FIX

HTTP 404, bare page

Correct 404 status code returned

Got: HTTP 404

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

Status Code HTTP 404 ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

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

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://unpkg.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://unpkg.com/manifest.json

Manifest contains invalid JSON.

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 ✗

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.

Landmark Structure

3 landmarks

REVIEW

3 landmarks

<main> landmark present

1 <nav> landmark(s) found

No contentinfo (footer) 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

Link & Button Quality

4 issue(s) across 42 links and 0 buttons

REVIEW

4 issue(s) across 42 links and 0 buttons

4 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: #nobuild-apps; #metadata-api; #cache-performance; #about

38 link(s) with descriptive text

42 links

4 empty

0 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
#nobuild-apps	(empty)	empty	Add link text or aria-label
#metadata-api	(empty)	empty	Add link text or aria-label
#cache-performance	(empty)	empty	Add link text or aria-label
#about	(empty)	empty	Add link text or aria-label

38 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

#nobuild-apps; #metadata-api; #cache-performance; #about

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Lighthouse Accessibility Audits

Score 84/100 — 2 failing, 11 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
"my-package" `section#overview > div.mt-8 > div.p-4 > span.hljs-string`
"./dist/index.js" `section#overview > div.mt-8 > div.p-4 > span.hljs-string`
script `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-name`
"https://unpkg.com/my-package" `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-string`
script `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-name`
"my-package" `section#overview > div.mt-8 > div.p-4 > span.hljs-string`
"./dist/exp.js" `section#overview > div.mt-8 > div.p-4 > span.hljs-string`
script `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-name`
"https://unpkg.com/my-package/exp" `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-string`
script `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-name`
fetch `section#overview > div.mt-8 > div.p-4 > span.hljs-built_in`
"my-package" `section#overview > div.mt-8 > div.p-4 > span.hljs-string`
"./dist/index.unpkg.js" `section#overview > div.mt-8 > div.p-4 > span.hljs-string`
// This works `section#overview > div.mt-8 > div.p-4 > span.hljs-comment`
"./dist/index.unpkg.js" `section#overview > div.mt-8 > div.p-4 > span.hljs-string`
// This works, too `section#overview > div.mt-8 > div.p-4 > span.hljs-comment`
"./dist/index.js" `section#overview > div.mt-8 > div.p-4 > span.hljs-string`
<!doctype html> `section#nobuild-apps > div.mt-8 > div.p-4 > span.hljs-meta`
html `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-name`
"en" `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-string`
head `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-name`
meta `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-name`
"UTF-8" `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-string`
script `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-name`
"importmap" `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-string`
"imports" `div.mt-8 > div.p-4 > span.language-javascript > span.hljs-string`
"preact" `div.mt-8 > div.p-4 > span.language-javascript > span.hljs-string`
"https://unpkg.com/preact@10.25.4/dist/preact.module.js" `div.mt-8 > div.p-4 > span.language-javascript > span.hljs-string`
"preact/hooks" `div.mt-8 > div.p-4 > span.language-javascript > span.hljs-string`
"https://unpkg.com/preact@10.25.4/hooks/dist/hooks.module.js" `div.mt-8 > div.p-4 > span.language-javascript > span.hljs-string`
"htm" `div.mt-8 > div.p-4 > span.language-javascript > span.hljs-string`
"https://unpkg.com/htm@3.1.1/dist/htm.module.js" `div.mt-8 > div.p-4 > span.language-javascript > span.hljs-string`
script `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-name`
head `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-name`
body `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-name`
script `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-name`
"module" `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-string`
"preact" `div.mt-8 > div.p-4 > span.language-javascript > span.hljs-string`
"preact/hooks" `div.mt-8 > div.p-4 > span.language-javascript > span.hljs-string`
"htm" `div.mt-8 > div.p-4 > span.language-javascript > span.hljs-string`
bind `div.mt-8 > div.p-4 > span.language-javascript > span.hljs-title`
App `div.mt-8 > div.p-4 > span.language-javascript > span.hljs-title`
useState `div.mt-8 > div.p-4 > span.language-javascript > span.hljs-title`
div `span.language-javascript > span.language-xml > span.hljs-tag > span.hljs-name`
${count} `div.mt-8 > div.p-4 > span.language-javascript > span.hljs-subst`
button `span.language-javascript > span.language-xml > span.hljs-tag > span.hljs-name`
${() => setCount(count + 1)} `div.mt-8 > div.p-4 > span.language-javascript > span.hljs-subst`
button `span.language-javascript > span.language-xml > span.hljs-tag > span.hljs-name`
div `span.language-javascript > span.language-xml > span.hljs-tag > span.hljs-name`
render `div.mt-8 > div.p-4 > span.language-javascript > span.hljs-title`
${App} `div.mt-8 > div.p-4 > span.language-javascript > span.hljs-subst`
script `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-name`
body `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-name`
html `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-name`
"react-router" `section#metadata-api > div.mt-8 > div.p-4 > span.hljs-string`
"7.3.0" `section#metadata-api > div.mt-8 > div.p-4 > span.hljs-string`
"/dist/" `section#metadata-api > div.mt-8 > div.p-4 > span.hljs-string`
path `section#metadata-api > div.mt-8 > div.p-4 > span.hljs-selector-tag`
"/dist/development/dom-export.js" `section#metadata-api > div.mt-8 > div.p-4 > span.hljs-string`
"text/javascript" `section#metadata-api > div.mt-8 > div.p-4 > span.hljs-string`
"sha256-z5j8OHOsGkvfGAjBtW8sbj+M68LLmgLTSjDHk4A5uYA=" `section#metadata-api > div.mt-8 > div.p-4 > span.hljs-string`
path `section#metadata-api > div.mt-8 > div.p-4 > span.hljs-selector-tag`
"/dist/production/dom-export.js" `section#metadata-api > div.mt-8 > div.p-4 > span.hljs-string`
"text/javascript" `section#metadata-api > div.mt-8 > div.p-4 > span.hljs-string`
"sha256-Gh8wMHW9MO5IMaBq7fOc7szDMRemnO/7Qr8kTK4ebgY=" `section#metadata-api > div.mt-8 > div.p-4 > span.hljs-string`

These are opportunities to improve the legibility of your content.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div > section#nobuild-apps > h2.mt-16 > a.outline-none `div > section#nobuild-apps > h2.mt-16 > a.outline-none`
div > section#metadata-api > h2.mt-16 > a.outline-none `div > section#metadata-api > h2.mt-16 > a.outline-none`
div > section#cache-performance > h2.mt-16 > a.outline-none `div > section#cache-performance > h2.mt-16 > a.outline-none`
div > section#about > h2.mt-16 > a.outline-none `div > section#about > h2.mt-16 > a.outline-none`

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

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

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

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

○Image elements have `[alt]` attributes

○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

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

A+

Heading Hierarchy

5 headings

PASS

5 headings

Single H1 present

H1 UNPKG
H2 Nobuild Apps
H2 Metadata API
H2 Cache Performance
H2 About

A+

Alt Text Quality

No images

PASS

No images

No images on this page

No images on this page.

A+

Form Accessibility

No form controls

PASS

No form controls

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)

Element	Ratio	Required	FG	BG	Result
h1 UNPKG	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Nobuild Apps	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Metadata API	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Cache Performance	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 About	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title UNPKG	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p UNPKG is a fast, glo…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a npm	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p . Use it to quickly …	21.00:1	4.5:1	#000000	#FFFFFF	Pass
code unpkg.com/:pkg@:ver/…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
code https://unpkg.com/:p…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
code :pkg	21.00:1	4.5:1	#000000	#FFFFFF	Pass
code :package	21.00:1	4.5:1	#000000	#FFFFFF	Pass
li is the name of the p…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
code :ver	21.00:1	4.5:1	#000000	#FFFFFF	Pass
code :version	21.00:1	4.5:1	#000000	#FFFFFF	Pass
li is the version of th…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
code :file	21.00:1	4.5:1	#000000	#FFFFFF	Pass
li is the path to a fil…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p For example:	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.

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