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 6 REVIEW 2 FIX

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

Action

5 landmarks

REVIEW

5 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

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

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

Heading Hierarchy

4 headings

REVIEW

4 headings

No H1 heading found

Every page should have one H1 that describes the page content.

H3 The app for independent voices
H4 You made it, you own it
H4 Great discussions
H4 Cookie Policy

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

Link & Button Quality

Action

1 issue(s) across 33 links and 58 buttons

REVIEW

1 issue(s) across 33 links and 58 buttons

3 image-only link(s) without alt text

2 link(s) open in new tab without warning

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

Got: https://www.natesilver.net/; https://bookshop.org/p/books/dress-your-baby-in-sage-and-taupe-a-handbook-for-the-sad-beige-parent-hayley-deroche/529fe6a86cd31163?ean=9781324112044&next=t&next=t&affiliate=115083

1 button(s) with no accessible text

28 link(s) with descriptive text

33 links

0 empty

0 generic text

2 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
/home/post/p-193434872?source=queue	Juno NewsOP-ED: Kamloops India…	img no alt	Add alt attribute to the image
/home/post/p-193342283?source=queue	Malone NewsTHE MOLECULE YOUR B…	img no alt	Add alt attribute to the image
https://www.natesilver.net/	Silver Bulletin	new tab	Add '(opens in new tab)' to text
https://bookshop.org/p/books/dress-your-…	bookshop.org/p/books/dr…	new tab	Add '(opens in new tab)' to text
https://5calls.org/	5calls.org5 CallsSpend 5 minut…	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label

85 links and buttons have descriptive text

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

https://www.natesilver.net/; https://bookshop.org/p/books/dress-your-baby-in-sage-and-taupe-a-handbook-for-the-sad-beige-parent-hayley-deroche/529fe6a86cd31163?ean=9781324112044&next=t&next=t&affiliate=115083

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

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

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

Dark-specific theme-color detected

A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.

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 #ffffff ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

Lighthouse Accessibility Audits

Action

Score 70/100 — 9 failing, 17 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.

ARIA

When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.reader-nav-root > div.pencraft > div.pencraft > a.pencraft `div.reader-nav-root > div.pencraft > div.pencraft > a.pencraft`
div.reader-nav-root > div.pencraft > div.pencraft > a.pencraft `div.reader-nav-root > div.pencraft > div.pencraft > a.pencraft`
div.reader-nav-root > div.pencraft > div.pencraft > a.pencraft `div.reader-nav-root > div.pencraft > div.pencraft > a.pencraft`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#entry > div.reader-nav-root > div.app-banner > button.reader2-button-reset `div#entry > div.reader-nav-root > div.app-banner > button.reader2-button-reset`

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.pencraft > div.pencraft > div.pencraft > a.pencraft `div.pencraft > div.pencraft > div.pencraft > a.pencraft`

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.

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
Get the app `div.pencraft > div.pencraft > div.pencraft > button.pencraft`
Get the app `div.pencraft > div.pencraft > div.pencraft > button.pencraft`
For you `div.pencraft > div.pencraft > div.pencraft > button.pencraft`
Mar 27 `div.pencraft > span.pencraft > a.pencraft > span.pencraft`
Subscribe `div.pencraft > div.pencraft > div.pencraft > button.pencraft`
Mar 29 `div.pencraft > span.pencraft > a.pencraft > span.pencraft`
Subscribe `div.pencraft > div.pencraft > div.pencraft > button.pencraft`
4h `div.pencraft > span.pencraft > a.pencraft > span.pencraft`
Subscribe `div.pencraft > div.pencraft > div.pencraft > button.pencraft`
You always own your intellectual property, mailing list, and subscriber payment… `div.pencraft > div.pencraft > div.pencraft > p.pencraft`
Get started `div.pencraft > div.pencraft > div.pencraft > button.pencraft`
3h `div.pencraft > span.pencraft > a.pencraft > span.pencraft`
Subscribe `div.pencraft > div.pencraft > div.pencraft > button.pencraft`
3h `div.pencraft > span.pencraft > a.pencraft > span.pencraft`
Subscribe `div.pencraft > div.pencraft > div.pencraft > button.pencraft`
bookshop.org/p/books/dr… `div.pencraft > div.ProseMirror > p > a.pencraft`
Mar 12 `span.pencraft > span.pencraft > a.pencraft > span.pencraft`
Join the most interesting and insightful discussions. `div.pencraft > div.pencraft > div.pencraft > p.pencraft`
Get started `div.pencraft > div.pencraft > div.pencraft > button.pencraft`
1h `div.pencraft > span.pencraft > a.pencraft > span.pencraft`
Subscribe `div.pencraft > div.pencraft > div.pencraft > button.pencraft`
5calls.org `div.pencraft > a.pencraft > div.pencraft > p.pencraft`
Spend 5 minutes. Make 5 calls. Make your voice heard. `div.pencraft > a.pencraft > div.pencraft > p.pencraft`
Get app `div.reader-nav-root > div.app-banner > a.app-banner-cta > div.pencraft`
privacy policy `div.pencraft > div.pencraft > div.pencraft > a.pencraft`

These are opportunities to improve the legibility of your content.

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
The app for independent voices `div.pencraft > div.pencraft > div.pencraft > h4.pencraft`

These are opportunities to improve keyboard navigation in your application.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Hayley DeRoche's avatar `div.pencraft > a.pencraft > div.pencraft > a.pencraft`
Hayley DeRoche `div.pencraft > span > span.pencraft > a.pencraft`
Mar 12 `div.pencraft > span.pencraft > span.pencraft > a.pencraft`

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
22.2K `div.pencraft > div.pencraft > div.pencraft > button.pencraft`
1.2K `div.pencraft > div.pencraft > div.pencraft > button.pencraft`
565 `div.pencraft > div.pencraft > div.pencraft > button.pencraft`
6.5K `div.pencraft > div.pencraft > div.pencraft > button.pencraft`
59 `div.pencraft > div.pencraft > div.pencraft > button.pencraft`
1K `div.pencraft > div.pencraft > div.pencraft > button.pencraft`
129 `div.pencraft > div.pencraft > div.pencraft > button.pencraft`
6 `div.pencraft > div.pencraft > div.pencraft > button.pencraft`
1.3K `div.pencraft > div.pencraft > div.pencraft > button.pencraft`
156 `div.pencraft > div.pencraft > div.pencraft > button.pencraft`
341 `div.pencraft > div.pencraft > div.pencraft > button.pencraft`
20 `div.pencraft > div.pencraft > div.pencraft > button.pencraft`
1 `div.pencraft > div.pencraft > div.pencraft > button.pencraft`
27 `div.pencraft > div.pencraft > div.pencraft > button.pencraft`
3 `div.pencraft > div.pencraft > div.pencraft > button.pencraft`
7 `div.pencraft > div.pencraft > div.pencraft > button.pencraft`

○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

●Image elements have `[alt]` attributes

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

●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 are distinguishable without relying on color.

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

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

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

○Form elements have associated labels

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

A+

Alt Text Quality

All 17 images OK

PASS

All 17 images OK

9 decorative image(s) correctly marked

8 image(s) with good alt text

17 images 8 good alt text 9 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.

Favicon & Branding

10 icon(s) detected

PASS

10 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✓ Manifest Icons Present

✓ Multiple Sizes Present

A+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: Substack

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name Substack ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓

Name Substack Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 6 icon(s)

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
h3 The app for independ…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Substack	21.00:1	4.5:1	#000000	#FFFFFF	Pass
button Sign in	21.00:1	4.5:1	#000000	#FFFFFF	Pass
button Create account	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Juno News	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div OP-ED: Kamloops Indi…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div 5m read	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Malone News	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div THE MOLECULE YOUR BO…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div 18m read	21.00:1	4.5:1	#000000	#FFFFFF	Pass
button Get started	21.00:1	4.5:1	#000000	#FFFFFF	Pass
button Learn more	21.00:1	4.5:1	#000000	#FFFFFF	Pass
button For you	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Aaron Parnas	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Mar 27	21.00:1	4.5:1	#000000	#FFFFFF	Pass
button Subscribe	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p First 24 hours done,…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p Wouldn’t trade it …	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p Thank you to all of …	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div 22.2K	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.