Skip to content
https://martinfowler.com

Accessibility

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

F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✓ favicon.ico Present
✗ PNG Icons Missing
✗ Apple Touch Missing
✗ 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
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
No navigation patterns
FIX
No navigation patterns
Info::
5 navigation landmark(s) detected
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 5 <nav> element(s)
Back to Top
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.
D
Lighthouse Accessibility Audits
Action
Score 60/100 — 4 failing, 8 passed
FIX
60

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
Thoughtworks section.row > section.intro > p > a.highlight
photo: Christopher Ferguson main > section.row > section.photo > p.credit
agile software development section.center-main > section#AWebsiteOnBuildingSoftwareEffectively > p > a.highlight
architecture section.center-main > section#AWebsiteOnBuildingSoftwareEffectively > p > a.highlight
microservices section.center-main > section#AWebsiteOnBuildingSoftwareEffectively > p > a.highlight
Refactoring section.center-main > section#AWebsiteOnBuildingSoftwareEffectively > p > a.highlight
Continuous Delivery section.center-main > section#AWebsiteOnBuildingSoftwareEffectively > p > a.highlight
Testing section.center-main > section#AWebsiteOnBuildingSoftwareEffectively > p > a.highlight
data management section.card-box > section#DataManagement > p > a.highlight
Domain-Specific Languages section.card-box > section#Domain-specificLanguages > p > a.highlight
Tue 21 Apr 2026 16:34 CEST section.feed > section.entries > article.feed-entry > p.datetime
Tue 14 Apr 2026 09:16 section.feed > section.entries > article.feed-entry > p.datetime
Sat 11 Apr 2026 09:01 section.feed > section.entries > article.feed-entry > p.datetime
Wed 08 Apr 2026 09:28 section.feed > section.entries > article.feed-entry > p.datetime
Tue 07 Apr 2026 09:39 section.feed > section.entries > article.feed-entry > p.datetime
Thu 02 Apr 2026 09:10 section.feed > section.entries > article.feed-entry > p.datetime
Tue 31 Mar 2026 11:20 section.feed > section.entries > article.feed-entry > p.datetime
Tue 24 Mar 2026 09:50 section.feed > section.entries > article.feed-entry > p.datetime

These are opportunities to improve the legibility of your content.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

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
header#banner > div.name-logo > a > img header#banner > div.name-logo > a > img
section#Photostream > p.img-link > a > img section#Photostream > p.img-link > a > img
section#ConferenceTalks > section.picture > p.img-link > img section#ConferenceTalks > section.picture > p.img-link > img
section#BoardGames > section.picture > p.img-link > img section#BoardGames > section.picture > p.img-link > img
article.feed-entry > div.img-link > a > img article.feed-entry > div.img-link > a > img
article.feed-entry > div.img-link > a > img article.feed-entry > div.img-link > a > img
footer#page-footer > div.tw-logo > a > img footer#page-footer > div.tw-logo > 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
body > header#banner > div.name-logo > a body > header#banner > div.name-logo > a
body > header#banner > div.menu-button > a.icon body > header#banner > div.menu-button > a.icon
section.card-box > section#Photostream > p.img-link > a section.card-box > section#Photostream > p.img-link > a
section.entries > article.feed-entry > div.img-link > a section.entries > article.feed-entry > div.img-link > a
section.entries > article.feed-entry > div.img-link > a section.entries > article.feed-entry > div.img-link > a
body > footer#page-footer > div.tw-logo > a body > footer#page-footer > div.tw-logo > 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-hidden="true"]` is not present on the document `<body>`
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●Document has a `<title>` element
●Links are distinguishable without relying on color.
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○Deprecated ARIA roles were not used
○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 use only permitted ARIA attributes
○`[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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○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 a valid value for its `[lang]` attribute
○`<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.
○Skip links are focusable.
○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.
○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.
B
Landmark Structure
8 landmarks
REVIEW
8 landmarks
Info::
<main> landmark present
Info::
5 <nav> landmark(s) found
Warning::
5 of 5 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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 MAIN CONTENTINFO footer

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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

C
Form Accessibility
Action
3 of 3 controls have issues
REVIEW
3 of 3 controls have issues
Critical::
3 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" name="q">; <input type="text" name="q">; <input type="text" name="q">
3 controls
0 labeled
0 placeholder only
3 unlabeled
ControlTypeLabelMethod
qtext(none)none
qtext(none)none
qtext(none)none

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

<input type="text" name="q">; <input type="text" name="q">; <input type="text" name="q">

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

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::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title not found ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
A
Heading Hierarchy
27 headings
PASS
27 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H2 Topics
  • H2 about me
  • H2 content
  • H2 Thoughtworks
  • H2 follow
  • H1 A website on building software effectively
  • H2 Photostream
  • H2 Data Management
  • H2 Domain-Specific Languages
  • H2 Books
  • H2 Conference Talks
  • H2 Board Games
  • H2 Tags
  • H1 Recent Changes duplicate H1
  • H2 Fragments: April 21
  • H2 Fragments: April 14
  • H2 Alan Turing play in Cambridge MA
  • H2 Feedback Flywheel
  • H2 Principles of Mechanical Sympathy
  • H2 Harness engineering for coding agent users
  • H2 Encoding Team Standards
  • H2 Bliki: Architecture Decision Record
  • H2 Topics
  • H2 about me
  • H2 content
  • H2 Thoughtworks
  • H2 follow

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+
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 A website on buildin…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Topics21.00:13.0:1
#000000
#FFFFFF
Pass
h2 about me21.00:13.0:1
#000000
#FFFFFF
Pass
h2 content21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Thoughtworks21.00:13.0:1
#000000
#FFFFFF
Pass
h2 follow21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Photostream21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Data Management21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Domain-Specific Lang…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Books21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Conference Talks21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Board Games21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Tags21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Topics21.00:13.0:1
#000000
#FFFFFF
Pass
h2 about me21.00:13.0:1
#000000
#FFFFFF
Pass
h2 content21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Thoughtworks21.00:13.0:1
#000000
#FFFFFF
Pass
h2 follow21.00:13.0:1
#000000
#FFFFFF
Pass
title martinfowler.com21.00:14.5:1
#000000
#FFFFFF
Pass
a Refactoring21.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