Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

7 PASS 1 REVIEW 5 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

favicon.ico present at site root

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 Present

✗ PNG Icons Missing

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

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 ✗

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

prefers-color-scheme CSS detected in inline styles

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.

Landmark Structure

8 landmarks

PASS

8 landmarks

<main> landmark present

3 <nav> landmark(s) found

3 of 3 <nav> elements are unlabeled

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

Skip navigation link present

Page Structure — as a screen reader sees it

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

A+

Heading Hierarchy

31 headings

PASS

31 headings

Single H1 present

H1 One short link for everything you share.
H2 Everything that should already be included.
H3 Short Links
H3 Analytics
H3 Auto QR Codes
H3 Code Snippets
H3 Folders & Tags
H3 Team Workspaces
H3 Version History
H2 Share links from a workspace that stays organized.
H2 Create it once. Use it everywhere.
H3 Add what you want to share
H3 Share the short link or QR code
H3 Track what happens next
H3 Add what you want to share
H3 Share the short link or QR code
H3 Track what happens next
H2 Free to start. More powerful as you grow.
H3 Pro
H3 Team
H3 Organization
H3 Questions worth asking before you pay.
H3 Do files and images count as links?
H3 Can I undo a destination change?
H3 What happens when I reach the Free plan limit?
H3 Can I use a domain I already own?
H3 Can I upgrade or downgrade whenever I want?
H3 What am I committing to with annual billing?
H3 How does a workspace work for teams?
H3 Is there a trial before I pay?
H3 What if I change my mind after paying?

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+

Link & Button Quality

21 links, 18 buttons — all OK

PASS

21 links, 18 buttons — all OK

21 link(s) with descriptive text

21 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

39 links and buttons have descriptive text

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 One short link for e…	20.82:1	3.0:1	#000000	#FEFEFE	Pass
h2 Everything that shou…	20.26:1	3.0:1	#000000	#FAFBFB	Pass
h2 Share links from a w…	20.26:1	3.0:1	#000000	#FAFBFB	Pass
h2 Create it once. Use …	20.26:1	3.0:1	#000000	#FAFBFB	Pass
h2 Free to start. More …	20.26:1	3.0:1	#000000	#FAFBFB	Pass
h3 Short Links	20.26:1	3.0:1	#000000	#FAFBFB	Pass
h3 Analytics	20.26:1	3.0:1	#000000	#FAFBFB	Pass
h3 Auto QR Codes	20.26:1	3.0:1	#000000	#FAFBFB	Pass
h3 Code Snippets	20.26:1	3.0:1	#000000	#FAFBFB	Pass
h3 Folders & Tags	20.26:1	3.0:1	#000000	#FAFBFB	Pass
h3 Team Workspaces	20.26:1	3.0:1	#000000	#FAFBFB	Pass
h3 Version History	20.26:1	3.0:1	#000000	#FAFBFB	Pass
h3 Add what you want to…	20.26:1	3.0:1	#000000	#FAFBFB	Pass
h3 Share the short link…	20.26:1	3.0:1	#000000	#FAFBFB	Pass
h3 Track what happens n…	20.26:1	3.0:1	#000000	#FAFBFB	Pass
h3 Add what you want to…	20.26:1	3.0:1	#000000	#FAFBFB	Pass
h3 Share the short link…	20.26:1	3.0:1	#000000	#FAFBFB	Pass
h3 Track what happens n…	20.26:1	3.0:1	#000000	#FAFBFB	Pass
h3 Pro	20.26:1	3.0:1	#000000	#FAFBFB	Pass
h3 Team	20.26:1	3.0:1	#000000	#FAFBFB	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 96/100 — 1 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.

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
Redirects, PDFs, media, and snippets in one feed `div.border-b > div.flex > div > span.text-[11px]`
wren-api-v2.pdf · 5 days ago `div.divide-y > div.flex > div.min-w-0 > p.mt-0.5`
deploy.sh · 3 files · 1 week ago `div.divide-y > div.flex > div.min-w-0 > p.mt-0.5`
stripe.com/checkout · 1 week ago `div.divide-y > div.flex > div.min-w-0 > p.mt-0.5`
spring-launch-cover.png · 2 weeks ago `div.divide-y > div.flex > div.min-w-0 > p.mt-0.5`
github.com/acme/v2-launch `div.relative > div.absolute > div.flex > span.font-mono`
14,204 clicks `div.relative > div.absolute > div.flex > span.font-mono`
2 days ago `div.relative > div.absolute > div.flex > span.text-[10px]`
linksh.re/r/launch-week `div.feat-card > div.h-32 > div.flex > span.text-[10px]`
Live `div.feat-card > div.h-32 > div.flex > span.flex`
clicks `div.h-32 > div.flex-1 > div.shrink-0 > div.text-[10px]`
Chrome 58% `div.h-32 > div.flex-1 > div.space-y-1 > div.text-[10px]`
Safari 31% `div.h-32 > div.flex-1 > div.space-y-1 > div.text-[10px]`
linksh.re/code/abc123 `div.feat-card > div.relative > div.flex > span.text-[10px]`
32 `div.feat-card > div.h-32 > div.org-item > div.ml-auto`
47 `div.feat-card > div.h-32 > div.org-item > div.ml-auto`
12 `div.feat-card > div.h-32 > div.org-item > div.ml-auto`
ML `div.flex > div.flex > div.w-7 > span.text-[9px]`
4 members `div.absolute > div.flex > div > p.text-[10px]`
linksh.re/r/launch-week `div.feat-card > div.h-32 > div.flex > span.text-[10px]`
3 versions `div.feat-card > div.h-32 > div.flex > span.text-[10px]`
acme.com/v3-launch `div.flex-1 > div.flex > div.flex-1 > span.text-[9px]`
2 min ago `div.flex-1 > div.flex > div.flex > span.text-[9px]`
acme.com/v2-launch `div.flex-1 > div.flex > div.flex-1 > span.text-[9px]`
3 days ago `div.flex-1 > div.flex > div.flex > span.text-[9px]`
Current `div.flex > div.flex-1 > div.flex > span.text-[8px]`
acme.com/v1-launch `div.flex-1 > div.flex > div.flex-1 > span.text-[9px]`
12 days ago `div.flex-1 > div.flex > div.flex > span.text-[9px]`

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

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

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

●Skip links are focusable.

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

○Image elements have `[alt]` attributes

○Input buttons have discernible text.

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

○Form elements have associated labels

○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

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

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