Skip to content
https://hashnode.dev

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
61
GRADE
D
FIX
5
REVIEW
3
PASS
5
INFO
0
Checks
13
5 PASS 3 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 ✗
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
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
Favicon & Branding
5 icon(s) detected
REVIEW
5 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 Missing
✓ Multiple Sizes Present
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
Heading Hierarchy
31 headings
PASS
31 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 Popular posts
  • H1 Write to think.Publish to connect. duplicate H1
  • H2 Breaking Apps Hackathon
  • H3 Why Your Binance Order Book Should Not Live Inside Your Bot
  • H3 APEX - the state of things - April 2026
  • H3 How I Stopped Resisting AI and Started Teaching It
  • H3 🧱 I built a tiny (in size, not in power) full-stack framework for the AI era, I call it webjs.
  • H3 Mastering File Uploads in Node.js: Multer + Cloudinary Strategy
  • H3 Building Production-Ready Mongoose Models: Hooks, JWT & Bcrypt
  • H3 Full Account Takeover on an MCP OAuth Proxy: Why PKCE Can't Save You
  • H3 Leaking a Google OAuth 2.0 Access Token Through Misconfigured Error Handling
  • H2 People are talking about
  • H3 Is AI actually solving UX problems, or just shifting the friction?
  • H3 The "Everything is a File" Tour of Linux
  • H3 Authors worth following
  • H3 Trending tags this week
  • H3 Trending series
  • H3 From our blog
  • H3 Introducing Azure RBAC Role Matching SKILL.md: A Practical Path to Least-Privilege Access
  • H3 Type 2 - Energy System
  • H3 Velero on OCI OKE: Complete Kubernetes Backup, Restore & Scheduled Backup Guide (Production Ready)
  • H3 Email validity checker using Google's JSON API for DNS over HTTPS (DoH) in Google Sheets
  • H3 Mastering File Uploads in Node.js: Multer + Cloudinary Strategy
  • H3 Over-Engineer vs Sustainable Architecture
  • H3 How to Build an Automatic Knowledge Graph for Your Blog with PHP and JSON-LD
  • 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

A+
Alt Text Quality
All 146 images OK
PASS
All 146 images OK
Info::
104 decorative image(s) correctly marked
Info::
42 image(s) with good alt text
146 images 42 good alt text 104 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+
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 Breaking Apps Hackat…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 Why Your Binance Ord…20.10:13.0:1
#000000
#F9FAFB
Pass
h3 APEX - the state of …20.10:13.0:1
#000000
#F9FAFB
Pass
h3 How I Stopped Resist…20.10:13.0:1
#000000
#F9FAFB
Pass
h3 🧱 I built a tiny …20.10:13.0:1
#000000
#F9FAFB
Pass
h3 Mastering File Uploa…20.10:13.0:1
#000000
#F9FAFB
Pass
h3 Building Production-…20.10:13.0:1
#000000
#F9FAFB
Pass
h3 Full Account Takeove…20.10:13.0:1
#000000
#F9FAFB
Pass
h3 Leaking a Google OAu…20.10:13.0:1
#000000
#F9FAFB
Pass
h3 Is AI actually solvi…20.10:13.0:1
#000000
#F9FAFB
Pass
h3 The "Everything is a…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 Introducing Azure RB…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 96/100 — 1 failing, 25 passed
PASS
96

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
676 articles div.ml-auto > div.flex > span.flex > span
376 writers div.ml-auto > div.flex > span.flex > span
NEW & POPULAR section.mx-auto > div.flex > div.flex > span.text-sm
Live now · 19d 6h a.group/hk > div.flex > div.flex > span.inline-flex
· 19d 6h div.flex > div.flex > span.inline-flex > span.tabular-nums

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
●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
●Links have a discernible name
●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.
●Heading elements appear in a sequentially-descending order
●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