Skip to content
https://towardsliberty.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
80
GRADE
B
FIX
5
REVIEW
5
PASS
14
INFO
0
Checks
24
14 PASS 5 REVIEW 5 FIX
F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
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 ✗
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
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 ✗
F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
1 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 1 <nav> element(s)
Back to Top
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.
C
Tap Target Adequacy
Action
5 tap target(s) too small or too close together
REVIEW
5 tap target(s) too small or too close together
Warning::
5 tap target(s) too small or too close to neighbors
WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
color-scheme meta tag present
The site declares support for light and dark color schemes via <meta name='color-scheme'>.
Got: dark
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #000000
Info::
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 dark ✓Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

C
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 Max
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
32px · above the fold
h3 Send Zap
1.06:1
#000000
on
#0A0A0A
needs 3.0:1 (large text)
19px · bottom of viewport
title Towards Liberty
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to content
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
a Towards Liberty
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
a Full search and filters
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
button Retry full text
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
span ₿
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
a Notes
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
a Articles
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
a Media
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
a Library
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
a By Max
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
div Praxeologist ~ Cryptoanarchist ~ Cypherp…
1.02:1
#000000
on
#040404
needs 4.5:1 (normal text)
16px · mid-page
div Message me on
1.06:1
#000000
on
#0A0A0A
needs 4.5:1 (normal text)
16px · mid-page
span @White Noise
1.06:1
#000000
on
#0A0A0A
needs 4.5:1 (normal text)
16px · mid-page
code max@towardsliberty.com
1.06:1
#000000
on
#0A0A0A
needs 4.5:1 (normal text)
16px · mid-page
div Would love some feedback on my new book …
1.06:1
#000000
on
#0A0A0A
needs 4.5:1 (normal text)
16px · mid-page
div towardsliberty.com/library
1.06:1
#000000
on
#0A0A0A
needs 4.5:1 (normal text)
16px · mid-page
div Got any improvements to the ux and list …
1.06:1
#000000
on
#0A0A0A
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Max1.00:13.0:1
#000000
#000000
Fail
h3 Send Zap1.06:13.0:1
#000000
#0A0A0A
Fail
title Towards Liberty1.00:14.5:1
#000000
#000000
Fail
a Skip to content1.00:14.5:1
#000000
#000000
Fail
a Towards Liberty1.00:14.5:1
#000000
#000000
Fail
a Full search and filt…1.00:14.5:1
#000000
#000000
Fail
button Retry full text1.00:14.5:1
#000000
#000000
Fail
span ₿1.00:14.5:1
#000000
#000000
Fail
a Notes1.00:14.5:1
#000000
#000000
Fail
a Articles1.00:14.5:1
#000000
#000000
Fail
a Media1.00:14.5:1
#000000
#000000
Fail
a Library1.00:14.5:1
#000000
#000000
Fail
a By Max1.00:14.5:1
#000000
#000000
Fail
div Praxeologist ~ Crypt…1.02:14.5:1
#000000
#040404
Fail
div Message me on1.06:14.5:1
#000000
#0A0A0A
Fail
span @White Noise1.06:14.5:1
#000000
#0A0A0A
Fail
code max@towardsliberty.c…1.06:14.5:1
#000000
#0A0A0A
Fail
div Would love some feed…1.06:14.5:1
#000000
#0A0A0A
Fail
div towardsliberty.com/l…1.06:14.5:1
#000000
#0A0A0A
Fail
div Got any improvements…1.06:14.5:1
#000000
#0A0A0A
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.

B
Lighthouse Accessibility Audits
Score 81/100 — 4 failing, 18 passed
REVIEW
81

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
@White Noise div.profile-info > div.profile-bio > a.profile-mention > span.profile-mention-name
https://github.com/marmot-protocol/marmot-ts div.note-wrapper > article.note > div.note-content > a
@White Noise article.note > div.note-content > a.profile-mention > span.profile-mention-name
https://www.whitenoise.chat/docs div.note-wrapper > article.note > div.note-content > a
@marmot article.note > div.note-content > a.profile-mention > span.profile-mention-name
https://github.com/marmot-protocol/awesome-marmot div.note-wrapper > article.note > div.note-content > a
https://dts.podtrac.com/redirect.mp3/cdn.mises.org/2025-02/06_Rothbard_Shaping-… div.note-wrapper > article.note > div.note-content > a
http://mises.org/podcasts/individual-lectures/anarchism-colonies div.note-wrapper > article.note > div.note-content > a
https://dts.podtrac.com/redirect.mp3/cdn.mises.org/2025-02/Rothbard_Columbia_19… div.note-wrapper > article.note > div.note-content > a
http://mises.org/podcasts/individual-lectures/strategies-achieving-liberty div.note-wrapper > article.note > div.note-content > a
@White Noise article.note > div.note-content > a.profile-mention > span.profile-mention-name
@White Noise article.note > div.note-content > a.profile-mention > span.profile-mention-name
@Amethyst article.note > div.note-content > a.profile-mention > span.profile-mention-name
@White Noise article.note > div.note-content > a.profile-mention > span.profile-mention-name
@GrapheneOS article.note > div.note-content > a.profile-mention > span.profile-mention-name
@Offline Speech to Text article.note > div.note-content > a.profile-mention > span.profile-mention-name
https://github.com/DavidVentura/offline-translator div.note-wrapper > article.note > div.note-content > a
@White Noise article.note > div.note-content > a.profile-mention > span.profile-mention-name
@Max div.note-content > a.note-preview > span.note-preview-header > span.note-preview-author
@White Noise article.note > div.note-content > a.profile-mention > span.profile-mention-name
@Zapstore article.note > div.note-content > a.profile-mention > span.profile-mention-name
https://towardsliberty.com/library div.note-wrapper > article.note > div.note-content > a
https://dts.podtrac.com/redirect.mp3/cdn.mises.org/rothbard_19791204.mp3 div.note-wrapper > article.note > div.note-content > a
http://mises.org/podcasts/individual-lectures/libertarian-paradigms-american-hi… div.note-wrapper > article.note > div.note-content > a
https://dts.podtrac.com/redirect.mp3/cdn.mises.org/rothbard_19800923.mp3 div.note-wrapper > article.note > div.note-content > a
http://mises.org/podcasts/individual-lectures/crisis-american-foreign-policy div.note-wrapper > article.note > div.note-content > a
@White Noise article.note > div.note-content > a.profile-mention > span.profile-mention-name
@Juraj🏴💛🌘 article.note > div.note-content > a.profile-mention > span.profile-mention-name
https://towardsliberty.com/pop/sk/ div.note-wrapper > article.note > div.note-content > a
https://github.com/fr34aky/reticulum-fips-bridge div.note-wrapper > article.note > div.note-content > a
@White Noise article.note > div.note-content > a.profile-mention > span.profile-mention-name
@Nicolas Dorier article.note > div.note-content > a.profile-mention > span.profile-mention-name
#6 div.note-wrapper > article.note > div.note-content > a.hashtag
@Max div.note-content > a.note-preview > span.note-preview-header > span.note-preview-author
@LightningPiggy article.note > div.note-content > a.profile-mention > span.profile-mention-name
@White Noise article.note > div.note-content > a.profile-mention > span.profile-mention-name
@Block Open Source article.note > div.note-content > a.profile-mention > span.profile-mention-name
@White Noise article.note > div.note-content > a.profile-mention > span.profile-mention-name
https://github.com/marmot-protocol/mdk/tree/master/integrations/goose/marmot div.note-wrapper > article.note > div.note-content > a
@Max div.note-content > a.note-preview > span.note-preview-header > span.note-preview-author
https://gitworkshop.dev/cyberguy.fyi/relay.ngit.dev/mdk-odin div.note-wrapper > article.note > div.note-content > a
https://mises.org/podcasts/history-struggle-liberty div.note-wrapper > article.note > div.note-content > a
Like this knowledge? Zap the author! main#main > div.zap-footer > button.zap-footer-btn > span

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Nostr body > footer.site-footer > p > a

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.note-wrapper > article.note > div.note-images > a.note-image-link div.note-wrapper > article.note > div.note-images > a.note-image-link

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.

Best practices

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
https://github.com/marmot-protocol/marmot-ts div.note-wrapper > article.note > div.note-content > a
https://www.whitenoise.chat/docs div.note-wrapper > article.note > div.note-content > a
https://towardsliberty.com/pop/sk/ div.note-wrapper > article.note > div.note-content > a
https://github.com/fr34aky/reticulum-fips-bridge div.note-wrapper > article.note > div.note-content > a
https://mises.org/podcasts/history-struggle-liberty div.note-wrapper > article.note > div.note-content > a

These items highlight common accessibility best practices.

○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>`
●`[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
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●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
○Deprecated ARIA roles were not used
○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
○`[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
○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
○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.
○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.
○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+
Landmark Structure
5 landmarks
PASS
5 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Main navigation" MAIN CONTENTINFO footer
A
Heading Hierarchy
2 headings, 1 skip(s)
PASS
2 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Max
  • H3 Send Zap skipped

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

A+
Heading Text Quality
All 2 heading(s) have substantive, well-formed text
PASS
All 2 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 26 images OK
PASS
All 26 images OK
Info::
24 decorative image(s) correctly marked
Info::
2 image(s) with good alt text
26 images 2 good alt text 24 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 2 controls have issues
PASS
1 of 2 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="number" id="zap-custom-input">
Info::
1 control(s) properly labeled
2 controls
1 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
inputtextSearch all contentaria-label
#zap-custom-inputnumber(Enter sats)placeholder only

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

<input type="number" id="zap-custom-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

A+
Form Input Types
1 input(s) using type=text where a specific type would help
PASS
1 input(s) using type=text where a specific type would help
Info::
Input "Search all content" should use type="search" (currently type="text")
Field name "Search all content" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
A+
Form Input Quality
2 form control(s) checked, no input-semantic issues
PASS
2 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "en"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
A+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A+
Mobile-Readable Font Sizes
All 169 visible text node(s) render at >= 12 CSS pixels
PASS
All 169 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
Browser-chrome `theme-color` meta tag present
The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback