Accessibility

D

Landmark Structure

Action

No landmarks

FIX

No landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

No <nav> landmark found

No banner (header) landmark

No contentinfo (footer) landmark

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.

No landmarks detected

Screen reader users have no way to navigate by region.

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

F

Heading Hierarchy

Action

22 headings, 4 skip(s)

FIX

22 headings, 4 skip(s)

Multiple H1 headings (4 found)

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

Heading level skipped: H1 → H6 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H1 → H6 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H1 → H6 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H1 → H6 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H1 Another Day Has Come
H6 Monday, 20 April 2026 skipped
H2 Monday, 20 April 2026
H2 Sunday, 19 April 2026
H1 ‘A Reading Room on Wheels, a Lover’s Lane, and, After 11 PM, a Flophouse’ duplicate H1
H6 Saturday, 18 April 2026 skipped
H2 Saturday, 18 April 2026
H2 Friday, 17 April 2026
H2 Thursday, 16 April 2026
H2 Wednesday, 15 April 2026
H1 David Pierce Tried a Bunch of Android Phones and Then Bought an iPhone Again duplicate H1
H6 Wednesday, 15 April 2026 skipped
H2 Wednesday, 15 April 2026
H2 Tuesday, 14 April 2026
H2 Monday, 13 April 2026
H2 Sunday, 12 April 2026
H1 Let Us Learn to Show Our Friendship for a Man When He Is Alive and Not After He Is Dead duplicate H1
H6 Friday, 10 April 2026 skipped
H2 1.
H2 2.
H2 3.
H2 4.

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

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

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

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

D

Web Manifest

Action

Not found

FIX

Not found

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

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

F

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

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

Back to Top

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

C

Alt Text Quality

Action

5 of 10 images have issues

REVIEW

5 of 10 images have issues

5 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

5 image(s) with good alt text

10 images 5 good alt text 5 missing

Issue	Count
missing	5 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

B

Form Accessibility

2 of 2 controls have issues

REVIEW

2 of 2 controls have issues

2 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="submit">

2 controls

0 labeled

0 placeholder only

2 unlabeled

Control	Type	Label	Method
q	text	(none)	none
input	submit	(none)	none

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

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

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Daring Fireball: Error: Page Not Found ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

C

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

C

Color Contrast (Screenshot)

Action

20 text elements analyzed, 19 fail WCAG AA

REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

1 pass 19 fail WCAG AA 1 pass AA only

h2 Monday, 20 April 2026

2.65:1

#000000

on

#4A525A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Sunday, 19 April 2026

2.65:1

#000000

on

#4A525A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Saturday, 18 April 2026

2.65:1

#000000

on

#4A525A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Friday, 17 April 2026

2.65:1

#000000

on

#4A525A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Thursday, 16 April 2026

2.65:1

#000000

on

#4A525A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Wednesday, 15 April 2026

2.65:1

#000000

on

#4A525A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Wednesday, 15 April 2026

2.65:1

#000000

on

#4A525A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Tuesday, 14 April 2026

2.65:1

#000000

on

#4A525A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Monday, 13 April 2026

2.65:1

#000000

on

#4A525A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Sunday, 12 April 2026

2.65:1

#000000

on

#4A525A

needs 3.0:1 (large text)

24px · bottom of viewport

title Daring Fireball

2.65:1

#000000

on

#4A525A

needs 4.5:1 (normal text)

16px · top of page (header area)

strong John Gruber

2.65:1

#000000

on

#4A525A

needs 3.0:1 (large text)

16px · top of page (header area)

a Archive

2.65:1

#000000

on

#4A525A

needs 4.5:1 (normal text)

16px · top of page (header area)

a The Talk Show

2.65:1

#000000

on

#4A525A

needs 4.5:1 (normal text)

16px · top of page (header area)

a Dithering

2.65:1

#000000

on

#4A525A

needs 4.5:1 (normal text)

16px · above the fold

a Projects

2.65:1

#000000

on

#4A525A

needs 4.5:1 (normal text)

16px · above the fold

a Colophon

3.77:1

#000000

on

#626970

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a Feeds / Social

2.65:1

#000000

on

#4A525A

needs 4.5:1 (normal text)

16px · above the fold

a Sponsorship

2.65:1

#000000

on

#4A525A

needs 4.5:1 (normal text)

16px · above the fold

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Monday, 20 April 202…	2.65:1	3.0:1	#000000	#4A525A	Fail
h2 Sunday, 19 April 202…	2.65:1	3.0:1	#000000	#4A525A	Fail
h2 Saturday, 18 April 2…	2.65:1	3.0:1	#000000	#4A525A	Fail
h2 Friday, 17 April 202…	2.65:1	3.0:1	#000000	#4A525A	Fail
h2 Thursday, 16 April 2…	2.65:1	3.0:1	#000000	#4A525A	Fail
h2 Wednesday, 15 April …	2.65:1	3.0:1	#000000	#4A525A	Fail
h2 Wednesday, 15 April …	2.65:1	3.0:1	#000000	#4A525A	Fail
h2 Tuesday, 14 April 20…	2.65:1	3.0:1	#000000	#4A525A	Fail
h2 Monday, 13 April 202…	2.65:1	3.0:1	#000000	#4A525A	Fail
h2 Sunday, 12 April 202…	2.65:1	3.0:1	#000000	#4A525A	Fail
title Daring Fireball	2.65:1	4.5:1	#000000	#4A525A	Fail
strong John Gruber	2.65:1	3.0:1	#000000	#4A525A	Fail
a Archive	2.65:1	4.5:1	#000000	#4A525A	Fail
a The Talk Show	2.65:1	4.5:1	#000000	#4A525A	Fail
a Dithering	2.65:1	4.5:1	#000000	#4A525A	Fail
a Projects	2.65:1	4.5:1	#000000	#4A525A	Fail
a Contact	5.05:1	4.5:1	#000000	#787D82	Pass
a Colophon	3.77:1	4.5:1	#000000	#626970	Fail
a Feeds / Social	2.65:1	4.5:1	#000000	#4A525A	Fail
a Sponsorship	2.65:1	4.5:1	#000000	#4A525A	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, 13 passed

REVIEW

81

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
Monday, 20 April 2026 `div#Box > div#Main > div.article > h6.dateline`
MONDAY, 20 APRIL 2026 `body.daringfireball-net > div#Box > div#Main > h2.dateline`
SUNDAY, 19 APRIL 2026 `body.daringfireball-net > div#Box > div#Main > h2.dateline`
Saturday, 18 April 2026 `div#Box > div#Main > div.article > h6.dateline`
SATURDAY, 18 APRIL 2026 `body.daringfireball-net > div#Box > div#Main > h2.dateline`
FRIDAY, 17 APRIL 2026 `body.daringfireball-net > div#Box > div#Main > h2.dateline`
RequestReviewAction `blockquote > p > a > code`
THURSDAY, 16 APRIL 2026 `body.daringfireball-net > div#Box > div#Main > h2.dateline`
WEDNESDAY, 15 APRIL 2026 `body.daringfireball-net > div#Box > div#Main > h2.dateline`
Wednesday, 15 April 2026 `div#Box > div#Main > div.article > h6.dateline`
WEDNESDAY, 15 APRIL 2026 `body.daringfireball-net > div#Box > div#Main > h2.dateline`
TUESDAY, 14 APRIL 2026 `body.daringfireball-net > div#Box > div#Main > h2.dateline`
MONDAY, 13 APRIL 2026 `body.daringfireball-net > div#Box > div#Main > h2.dateline`
SUNDAY, 12 APRIL 2026 `body.daringfireball-net > div#Box > div#Main > h2.dateline`
Friday, 10 April 2026 `div#Box > div#Main > div.article > h6.dateline`
↩︎ `ol > li#fn1-2026-04-10 > p > a.footnoteBackLink`
↩︎︎ `ol > li#fn2-2026-04-10 > p > a.footnoteBackLink`
Display Preferences Copyright © 2002–2026 The Daring Fireball Company LLC. `div#Box > div#Main > div#Footer > p.smallprint`

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
Monday, 20 April 2026 `div#Box > div#Main > div.article > h6.dateline`
Saturday, 18 April 2026 `div#Box > div#Main > div.article > h6.dateline`
Wednesday, 15 April 2026 `div#Box > div#Main > div.article > h6.dateline`
Friday, 10 April 2026 `div#Box > div#Main > div.article > h6.dateline`

These are opportunities to improve keyboard navigation in your application.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#Footer > form#SiteSearch > div > input `div#Footer > form#SiteSearch > div > input`

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

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.daringfireball-net `html.daringfireball-net`

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-hidden="true"]` is not present on the document `<body>`

●Image elements have `[alt]` attributes

●Input buttons have discernible text.

●`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

●Definition list items are wrapped in `<dl>` elements

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●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

●Touch targets have sufficient size and spacing.

○`[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

○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 type="image">` elements have `[alt]` text

○The document does not use `<meta http-equiv="refresh">`

○`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

○`<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.

○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+

Link & Button Quality

290 links, 1 buttons — all OK

PASS

290 links, 1 buttons — all OK

290 link(s) with descriptive text

290 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

291 links and buttons have descriptive text

A+

Print Stylesheet

Print styles detected

PASS

Print styles detected

External print stylesheet detected

Got: /css/fireball_print.css?v01

Print Stylesheet ✓ Print Optimized

Print stylesheet /css/fireball_print.css?v01 ✓Inline @media print Not detected ✗