Skip to content
https://joelonsoftware.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
60
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 FIX
F
Alt Text Quality
Action
5 of 7 images have issues
FIX
5 of 7 images have issues
Critical::
5 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
3 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
1 decorative image(s) correctly marked
Info::
1 image(s) with good alt text
7 images 1 good alt text 1 decorative 5 missing
IssueCount
missing5 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

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
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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.

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.
B
Form Accessibility
2 of 2 controls have issues
REVIEW
2 of 2 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit" name="sa">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" name="q">
2 controls
0 labeled
1 placeholder only
1 unlabeled
ControlTypeLabelMethod
qsearch(Search …)placeholder only
sasubmit(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<input type="submit" name="sa">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

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

<input type="search" name="q">

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

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found – Joel on Software ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓
B
Favicon & Branding
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
B
Lighthouse Accessibility Audits
Score 83/100 — 4 failing, 21 passed
REVIEW
83

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
DECEMBER 19, 2022 div.entry-date > span.posted-on > a > time.entry-date
by article#post-4176 > header.entry-header > div.entry-date > span.byline
JOEL SPOLSKY header.entry-header > div.entry-date > span.author > a.url
JANUARY 27, 2022 div.entry-date > span.posted-on > a > time.entry-date
by article#post-3906 > header.entry-header > div.entry-date > span.byline
JOEL SPOLSKY header.entry-header > div.entry-date > span.author > a.url
JUNE 2, 2021 div.entry-date > span.posted-on > a > time.entry-date
by article#post-3810 > header.entry-header > div.entry-date > span.byline
JOEL SPOLSKY header.entry-header > div.entry-date > span.author > a.url
JUNE 18, 2020 div.entry-date > span.posted-on > a > time.entry-date
by article#post-3701 > header.entry-header > div.entry-date > span.byline
JOEL SPOLSKY header.entry-header > div.entry-date > span.author > a.url
TOP 10 main#main > div.editor-reading-lists > h3.editor-reading-list-title > a
STACK OVERFLOW main#main > div.editor-reading-lists > h3.editor-reading-list-title > a
NEW DEVELOPER main#main > div.editor-reading-lists > h3.editor-reading-list-title > a
ROCK STAR DEVELOPER main#main > div.editor-reading-lists > h3.editor-reading-list-title > a
TECH LEAD main#main > div.editor-reading-lists > h3.editor-reading-list-title > a
CEO main#main > div.editor-reading-lists > h3.editor-reading-list-title > a
STARTUP FOUNDER main#main > div.editor-reading-lists > h3.editor-reading-list-title > a
SOFTWARE DESIGNER main#main > div.editor-reading-lists > h3.editor-reading-list-title > a
PRODUCT MANAGER main#main > div.editor-reading-lists > h3.editor-reading-list-title > a
RECRUITER main#main > div.editor-reading-lists > h3.editor-reading-list-title > a
FOG CREEK SOFTWARE main#main > div.editor-reading-lists > h3.editor-reading-list-title > a

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
More about me aside#text-3 > div.textwidget > p > a
1114 articles div#primary > main#main > p.editor-reading-list-intro > a

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
aside#text-3 > div.textwidget > a > img aside#text-3 > div.textwidget > a > img

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#front-widgets > aside#text-3 > div.textwidget > a div#front-widgets > aside#text-3 > div.textwidget > a

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
●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
●`[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
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●All heading elements contain content.
○`[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
○Buttons have an accessible name
○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>`.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○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.
A+
Landmark Structure
17 landmarks
PASS
17 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 ASIDE CONTENTINFO footer
A+
Heading Hierarchy
22 headings
PASS
22 headings
Info::
Single H1 present
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 Joel on Software
  • H2 (empty)
  • H2 Your host
  • H2 Careers
  • H2 Twitter! Twitter!
  • H2 What’s new?
  • H2 Progress on the Block Protocol
  • H2 Making the web better. With blocks!
  • H2 Kinda a big announcement
  • H2 HASH: a free, online platform for modeling the world
  • H2 Reading lists
  • H3 Top 10
  • H3 Stack Overflow
  • H3 New developer
  • H3 Rock star developer
  • H3 Tech lead
  • H3 CEO
  • H3 Startup founder
  • H3 Software designer
  • H3 Product manager
  • H3 Recruiter
  • H3 Fog Creek Software

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

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
h2 Your host19.26:13.0:1
#000000
#F5F5F5
Pass
h2 Careers21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Twitter! Twitter!21.00:13.0:1
#000000
#FFFFFF
Pass
h2 What’s new?21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Reading lists21.00:13.0:1
#000000
#FFFFFF
Pass
title Joel on Software16.98:14.5:1
#000000
#E7E7E7
Pass
a Skip to content18.26:14.5:1
#000000
#EFEFEF
Pass
span View menu19.26:14.5:1
#000000
#F5F5F5
Pass
span View sidebar19.26:14.5:1
#000000
#F5F5F5
Pass
a Joel on Software19.26:14.5:1
#000000
#F5F5F5
Pass
p I’m Joel Spolsky, …19.26:14.5:1
#000000
#F5F5F5
Pass
a More about me19.26:14.5:1
#000000
#F5F5F5
Pass
span Search19.26:14.5:1
#000000
#F5F5F5
Pass
div Read the archives in…21.00:14.5:1
#000000
#FFFFFF
Pass
a four books21.00:14.5:1
#000000
#FFFFFF
Pass
div , available at your …21.00:14.5:1
#000000
#FFFFFF
Pass
p Ready to level up?21.00:14.5:1
#000000
#FFFFFF
Pass
a Stack Overflow Jobs21.00:14.5:1
#000000
#FFFFFF
Pass
p is the job site that…21.00:14.5:1
#000000
#FFFFFF
Pass
a let employers discov…21.00:14.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.

Send Feedback