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 2 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 ✓Page Title Page Not Found - beehiiv — The newsletter platform built for growth | beehiiv ✓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

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

3 navigation landmark(s) detected

Hamburger menu detected (responsive design)

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 3 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Landmark Structure

5 landmarks

REVIEW

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

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

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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 20 fail WCAG AA

REVIEW

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

0 pass 20 fail WCAG AA

h1 POWERING THE INTERNET'S BEST

1.03:1

#000000

#050318

needs 3.0:1 (large text)

32px · bottom of viewport

h2 THE ONE PLATFORM FOR EVERY CREATOR

1.03:1

#000000

#050318

needs 3.0:1 (large text)

24px · bottom of viewport

h2 CONNECT YOUR NEWSLETTER

1.03:1

#000000

#050318

needs 3.0:1 (large text)

24px · bottom of viewport

h2 WITH THE TOOLS YOU LOVE

1.03:1

#000000

#050318

needs 3.0:1 (large text)

24px · bottom of viewport

h2 GOT QUESTIONS?

1.03:1

#000000

#050318

needs 3.0:1 (large text)

24px · bottom of viewport

h2 WE'VE GOT ANSWERS.

1.03:1

#000000

#050318

needs 3.0:1 (large text)

24px · bottom of viewport

h2 READY TO Build?

1.03:1

#000000

#050318

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Take a tour of beehiiv

1.03:1

#000000

#050318

needs 3.0:1 (large text)

19px · bottom of viewport

h3 State of Newsletters

1.03:1

#000000

#050318

needs 3.0:1 (large text)

19px · bottom of viewport

title beehiiv — The newsletter platform buil…

1.04:1

#000000

#060419

needs 4.5:1 (normal text)

16px · top of page (header area)

a Login

1.04:1

#000000

#060419

needs 4.5:1 (normal text)

16px · top of page (header area)

a Sign up

1.04:1

#000000

#060419

needs 4.5:1 (normal text)

16px · top of page (header area)

div Platform

1.04:1

#000000

#060419

needs 4.5:1 (normal text)

16px · top of page (header area)

span Newsletters

1.04:1

#000000

#060419

needs 4.5:1 (normal text)

16px · above the fold

p Make a statement in the inbox.

1.04:1

#000000

#060419

needs 4.5:1 (normal text)

16px · above the fold

span Web Builder

1.04:1

#000000

#060419

needs 4.5:1 (normal text)

16px · above the fold

p Build your digital home base.

1.04:1

#000000

#060419

needs 4.5:1 (normal text)

16px · above the fold

span Podcasts

1.04:1

#000000

#060419

needs 4.5:1 (normal text)

16px · above the fold

p Turn listeners into a loyal audience.

1.04:1

#000000

#060419

needs 4.5:1 (normal text)

16px · above the fold

span Ad Network

1.04:1

#000000

#060419

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 POWERING THE INTERNE…	1.03:1	3.0:1	#000000	#050318	Fail
h2 THE ONE PLATFORM FOR…	1.03:1	3.0:1	#000000	#050318	Fail
h2 CONNECT YOUR NEWSLET…	1.03:1	3.0:1	#000000	#050318	Fail
h2 WITH THE TOOLS YOU L…	1.03:1	3.0:1	#000000	#050318	Fail
h2 GOT QUESTIONS?	1.03:1	3.0:1	#000000	#050318	Fail
h2 WE'VE GOT ANSWERS.	1.03:1	3.0:1	#000000	#050318	Fail
h2 READY TO Build?	1.03:1	3.0:1	#000000	#050318	Fail
h3 Take a tour of beehi…	1.03:1	3.0:1	#000000	#050318	Fail
h3 State of Newsletters	1.03:1	3.0:1	#000000	#050318	Fail
title beehiiv — The news…	1.04:1	4.5:1	#000000	#060419	Fail
a Login	1.04:1	4.5:1	#000000	#060419	Fail
a Sign up	1.04:1	4.5:1	#000000	#060419	Fail
div Platform	1.04:1	4.5:1	#000000	#060419	Fail
span Newsletters	1.04:1	4.5:1	#000000	#060419	Fail
p Make a statement in …	1.04:1	4.5:1	#000000	#060419	Fail
span Web Builder	1.04:1	4.5:1	#000000	#060419	Fail
p Build your digital h…	1.04:1	4.5:1	#000000	#060419	Fail
span Podcasts	1.04:1	4.5:1	#000000	#060419	Fail
p Turn listeners into …	1.04:1	4.5:1	#000000	#060419	Fail
span Ad Network	1.04:1	4.5:1	#000000	#060419	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+

Heading Hierarchy

7 headings

PASS

7 headings

Single H1 present

H3 Take a tour of beehiiv
H3 State of Newsletters
H1 POWERING THE INTERNET'S BEST NEWSLETTERS
H2 THE ONE PLATFORM FOR EVERY CREATOR
H2 CONNECT YOUR NEWSLETTERWITH THE TOOLS YOU LOVE
H2 GOT QUESTIONS? WE'VE GOT ANSWERS.
H2 READY TO Build?

A+

Alt Text Quality

All 65 images OK

PASS

All 65 images OK

4 decorative image(s) correctly marked

61 image(s) with good alt text

65 images 61 good alt text 4 decorative

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Link & Button Quality

181 links, 11 buttons — all OK

PASS

181 links, 11 buttons — all OK

11 link(s) open in new tab without warning

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

Got: https://app.beehiiv.com/login; https://blog.beehiiv.com; https://product.beehiiv.com; https://developers.beehiiv.com; https://www.creatorspotlight.com/; https://beehiiv.com/support; https://app.beehiiv.com/login; https://www.beehiiv.com/migration; https://beehiiv.com/support; https://security.beehiiv.com/ (+1 more)

170 link(s) with descriptive text

181 links

0 empty

0 generic text

11 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://app.beehiiv.com/login	Login	new tab	Add '(opens in new tab)' to text
https://blog.beehiiv.com	BlogBest practices for scaling…	new tab	Add '(opens in new tab)' to text
https://product.beehiiv.com	ProductRegularly released prod…	new tab	Add '(opens in new tab)' to text
https://developers.beehiiv.com	DevelopersAPI docs and other d…	new tab	Add '(opens in new tab)' to text
https://www.creatorspotlight.com/	Creator SpotlightStories from …	new tab	Add '(opens in new tab)' to text
https://beehiiv.com/support	SupportProduct support and doc…	new tab	Add '(opens in new tab)' to text
https://app.beehiiv.com/login	Login	new tab	Add '(opens in new tab)' to text
https://www.beehiiv.com/migration	migration resources here	new tab	Add '(opens in new tab)' to text
https://beehiiv.com/support	Support	new tab	Add '(opens in new tab)' to text
https://security.beehiiv.com/	Security	new tab	Add '(opens in new tab)' to text
/sitemap	Sitemap	new tab	Add '(opens in new tab)' to text

181 links and buttons have descriptive text

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

https://app.beehiiv.com/login; https://blog.beehiiv.com; https://product.beehiiv.com; https://developers.beehiiv.com; https://www.creatorspotlight.com/; https://beehiiv.com/support; https://app.beehiiv.com/login; https://www.beehiiv.com/migration; https://beehiiv.com/support; https://security.beehiiv.com/ (+1 more)

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

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 28 passed

PASS

100

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.

○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

●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

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

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

●Buttons have an accessible name

●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

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<frame>` or `<iframe>` elements have a title

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

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

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

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

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

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

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