Skip to content
https://www.hashnode.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
63
GRADE
D
FIX
4
REVIEW
4
PASS
5
INFO
0
Checks
13
5 PASS 4 REVIEW 4 FIX
F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-z6zbxy
404 Page Quality Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

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
No navigation patterns
FIX
No navigation patterns
Info::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
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.
B
Landmark Structure
9 landmarks
REVIEW
9 landmarks
Info::
<main> landmark present
Warning::
Multiple <main> landmarks (3 found)
A page should have only one <main> landmark.
Info::
1 <nav> landmark(s) found
Info::
No contentinfo (footer) landmark
Warning::
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
BANNER header NAV "Resources" MAIN ASIDE CONTENTINFO (missing!)

A page should have only one <main> landmark.

Why this matters

Multiple <main> elements violate the spec — there must be exactly one per page.

Learn more

HTML5 spec: 'authors must not include more than one main element' visible to AT at the same time. Multiple <main>s confuse AT and break the 'jump to main content' shortcut. Refactor to a single <main> with nested <section>/<article>.

Source: HTML5 spec

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

B
Heading Hierarchy
30 headings, 1 skip(s)
REVIEW
30 headings, 1 skip(s)
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
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 Popular posts
  • H1 Write to think.Publish to connect. duplicate H1
  • H3 A complete beginner’s guide to understanding Networking and getting started skipped
  • H3 The Enemy in Your Terminal: Why OpenClaw was the Perfect Trojan Horse
  • H3 Learn JavaScript, HTML, CSS and React in 2026
  • H3 From “97% Accuracy” to Production Chaos: Why You Need NIST AI RMF
  • H3 Why Side Projects Compound 🏗️
  • H3 Power Up #4: My AI Workflow
  • H3 Engineering with AI - The Hidden Tax
  • H3 Frontend Is Not UI Anymore.
  • H2 People are talking about
  • H3 Want to build a prediction market platform
  • H3 7 Practical Tips for Building Your MVP
  • H3 Authors worth following
  • H3 Trending tags this week
  • H3 Trending series
  • H3 From our blog
  • H3 4 Lessons from Dissecting Production Systems at Scale — Architecture Dojo 2025
  • H3 I Built Telegram Inside My Terminal Using Python
  • H3 Why (and How) I Built a Go AI SDK
  • H3 Legacy Migration Starts with Understanding, not Inventory
  • H3 @platformatic/kafka Now Supports Confluent Schema Registry
  • H3 Migrating from Next.js to SolidStart: An Opinionated Guide
  • H3 Model Context Protocol (MCP) -- Overview & Performance Benchmarks
  • H3 Recent comments
  • H3 Authors worth following
  • H3 Trending tags this week
  • H3 Trending series
  • H3 From our blog
  • H2 Search Hashnode

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

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

B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: Hashnode
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name Hashnode 192×192 icon 512×512 icon Start URL Display Mode standalone
Name Hashnode Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
prefers-color-scheme CSS detected in inline styles
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 Not set Dark theme-color Not set CSS indicators Detected

Detection limited to meta tags and inline styles.

A+
Alt Text Quality
All 138 images OK
PASS
All 138 images OK
Info::
105 decorative image(s) correctly marked
Info::
33 image(s) with good alt text
138 images 33 good alt text 105 decorative
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A
Favicon & Branding
7 icon(s) detected
PASS
7 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
favicon.ico Present
PNG Icons Present
Apple Touch Present
SVG Favicon Present
Manifest Icons Present
Multiple Sizes Present
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)
ElementRatioRequiredFGBGResult
h1 Popular posts20.10:13.0:1
#000000
#F9FAFB
Pass
h1 Write to think.20.10:13.0:1
#000000
#F9FAFB
Pass
h2 People are talking a…20.10:13.0:1
#000000
#F9FAFB
Pass
h2 Search Hashnode20.10:13.0:1
#000000
#F9FAFB
Pass
h3 A complete beginner…20.10:13.0:1
#000000
#F9FAFB
Pass
h3 The Enemy in Your Te…20.10:13.0:1
#000000
#F9FAFB
Pass
h3 Learn JavaScript, HT…20.10:13.0:1
#000000
#F9FAFB
Pass
h3 From “97% Accuracy…20.10:13.0:1
#000000
#F9FAFB
Pass
h3 Why Side Projects Co…20.10:13.0:1
#000000
#F9FAFB
Pass
h3 Power Up #4: My AI W…20.10:13.0:1
#000000
#F9FAFB
Pass
h3 Engineering with AI …20.10:13.0:1
#000000
#F9FAFB
Pass
h3 Frontend Is Not UI A…20.10:13.0:1
#000000
#F9FAFB
Pass
h3 Want to build a pred…20.10:13.0:1
#000000
#F9FAFB
Pass
h3 7 Practical Tips for…20.10:13.0:1
#000000
#F9FAFB
Pass
h3 Authors worth follow…20.10:13.0:1
#000000
#F9FAFB
Pass
h3 Trending tags this w…20.10:13.0:1
#000000
#F9FAFB
Pass
h3 Trending series20.10:13.0:1
#000000
#F9FAFB
Pass
h3 From our blog20.10:13.0:1
#000000
#F9FAFB
Pass
h3 4 Lessons from Disse…20.10:13.0:1
#000000
#F9FAFB
Pass
h3 I Built Telegram Ins…20.10:13.0:1
#000000
#F9FAFB
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 91/100 — 3 failing, 23 passed
PASS
91

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
Last 24h: div.mx-auto > div.ml-auto > div.flex > span.text-muted-foreground
641 articles div.ml-auto > div.flex > span.flex > span
372 writers div.ml-auto > div.flex > span.flex > span
NEW & POPULAR section.mx-auto > div.flex > div.flex > span.text-sm
Kubernetes Over Koffee article.group > div.flex > div.flex > a.truncate
1d ago article.group > div.flex > div.flex > span.text-sm
62 min article.group > div.flex > div.flex > span.text-sm
Syed Ahmer Shah article.group > div.flex > div.flex > a.truncate
23h ago article.group > div.flex > div.flex > span.text-sm
5 min article.group > div.flex > div.flex > span.text-sm
Shubham Jha article.group > div.flex > div.flex > a.truncate
1d ago article.group > div.flex > div.flex > span.text-sm
7 min article.group > div.flex > div.flex > span.text-sm

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
A complete beginner’s guide to understanding Networking and getting started article.group > div.flex > a.hover:no-underline > h3.text-base

These are opportunities to improve keyboard navigation in your application.

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
article.group > div.relative > div.absolute > a.absolute article.group > div.relative > div.absolute > a.absolute
article.group > div.relative > div.absolute > a.absolute article.group > div.relative > div.absolute > a.absolute
article.group > div.relative > div.absolute > a.absolute article.group > div.relative > div.absolute > a.absolute
article.group > div.relative > div.absolute > a.absolute article.group > div.relative > div.absolute > a.absolute
article.group > div.relative > div.absolute > a.absolute article.group > div.relative > div.absolute > a.absolute
article.group > div.relative > div.absolute > a.absolute article.group > div.relative > div.absolute > a.absolute
div.grid > div.flex > div.grid > a.shrink-0 div.grid > div.flex > div.grid > a.shrink-0
div.grid > div.flex > div.grid > a.shrink-0 div.grid > div.flex > div.grid > a.shrink-0
div.grid > div.flex > div.grid > a.shrink-0 div.grid > div.flex > div.grid > a.shrink-0
li.flex > span.flex > span.flex > a.relative li.flex > span.flex > span.flex > a.relative
li.flex > span.flex > span.flex > a.relative li.flex > span.flex > span.flex > a.relative
li.flex > span.flex > span.flex > a.relative li.flex > span.flex > span.flex > a.relative
li.flex > span.flex > span.flex > a.relative li.flex > span.flex > span.flex > a.relative
li.flex > span.flex > span.flex > a.relative li.flex > span.flex > span.flex > a.relative
li.flex > span.flex > span.flex > a.relative li.flex > span.flex > span.flex > a.relative
li.flex > span.flex > span.flex > a.relative li.flex > span.flex > span.flex > a.relative
li.flex > span.flex > span.flex > a.relative li.flex > span.flex > span.flex > a.relative
li.flex > span.flex > span.flex > a.relative li.flex > span.flex > span.flex > a.relative
li.flex > span.flex > span.flex > a.relative li.flex > span.flex > span.flex > a.relative
li.flex > span.flex > span.flex > a.relative li.flex > span.flex > span.flex > a.relative
li.flex > span.flex > span.flex > a.relative li.flex > span.flex > span.flex > a.relative
li.flex > span.flex > span.flex > a.relative li.flex > span.flex > span.flex > a.relative
li.flex > span.flex > span.flex > a.relative li.flex > span.flex > span.flex > a.relative
li.flex > span.flex > span.flex > a.relative li.flex > span.flex > span.flex > a.relative
li.flex > span.flex > span.flex > a.relative li.flex > span.flex > span.flex > a.relative
li.flex > span.flex > span.flex > a.relative li.flex > span.flex > span.flex > a.relative
li.flex > span.flex > span.flex > a.relative li.flex > span.flex > span.flex > a.relative
li.flex > span.flex > span.flex > a.relative li.flex > span.flex > span.flex > a.relative
li.flex > span.flex > span.flex > a.relative li.flex > span.flex > span.flex > a.relative
li.flex > span.flex > span.flex > a.relative li.flex > span.flex > span.flex > a.relative
li.flex > span.flex > span.flex > a.relative li.flex > span.flex > span.flex > a.relative
li.flex > span.flex > span.flex > a.relative li.flex > span.flex > span.flex > a.relative
li.flex > span.flex > span.flex > a.relative li.flex > span.flex > span.flex > a.relative
li.flex > span.flex > span.flex > a.relative li.flex > span.flex > span.flex > a.relative
li.flex > span.flex > span.flex > a.relative li.flex > span.flex > span.flex > a.relative
li.flex > span.flex > span.flex > a.relative li.flex > span.flex > span.flex > a.relative
li.flex > span.flex > span.flex > a.relative li.flex > span.flex > span.flex > a.relative
li.flex > span.flex > span.flex > a.relative li.flex > span.flex > span.flex > a.relative
li.flex > span.flex > span.flex > a.relative li.flex > span.flex > span.flex > a.relative
li.flex > span.flex > span.flex > a.relative li.flex > span.flex > span.flex > a.relative
li.flex > span.flex > span.flex > a.relative li.flex > span.flex > span.flex > a.relative
li.flex > span.flex > span.flex > a.relative li.flex > span.flex > span.flex > a.relative
li.flex > span.flex > span.flex > a.relative li.flex > span.flex > span.flex > a.relative
li.flex > span.flex > span.flex > a.relative li.flex > span.flex > span.flex > a.relative
li.flex > span.flex > span.flex > a.relative li.flex > span.flex > span.flex > a.relative
li.flex > span.flex > span.flex > a.relative li.flex > span.flex > span.flex > a.relative
li.flex > span.flex > span.flex > a.relative li.flex > span.flex > span.flex > a.relative
li.flex > span.flex > span.flex > a.relative li.flex > span.flex > span.flex > a.relative
div.grid > div.flex > div.grid > a.shrink-0 div.grid > div.flex > div.grid > a.shrink-0
div.grid > div.flex > div.grid > a.shrink-0 div.grid > div.flex > div.grid > a.shrink-0
div.grid > div.flex > div.grid > a.shrink-0 div.grid > div.flex > div.grid > a.shrink-0
div.grid > div.flex > div.grid > a.shrink-0 div.grid > div.flex > div.grid > a.shrink-0
div.grid > div.flex > div.grid > a.shrink-0 div.grid > div.flex > div.grid > a.shrink-0
div.grid > div.flex > div.grid > a.shrink-0 div.grid > div.flex > div.grid > a.shrink-0

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-*]` 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
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
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
Document has a main landmark.
Deprecated ARIA roles were not used
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
`[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.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Form elements have associated labels
Links are distinguishable without relying on color.
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
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.

Send Feedback