Accessibility

F

Heading Hierarchy

Action

31 headings, 12 skip(s)

FIX

31 headings, 12 skip(s)

No H1 heading found

Every page should have one H1 that describes the page content.

Heading level skipped: H4 → H6 (missing H5)

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

Heading level skipped: H4 → H6 (missing H5)

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

Heading level skipped: H4 → H6 (missing H5)

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

Heading level skipped: H4 → H6 (missing H5)

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

Heading level skipped: H4 → H6 (missing H5)

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

Heading level skipped: H4 → H6 (missing H5)

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

Heading level skipped: H4 → H6 (missing H5)

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

Heading level skipped: H4 → H6 (missing H5)

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

Heading level skipped: H4 → H6 (missing H5)

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

Heading level skipped: H4 → H6 (missing H5)

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

Heading level skipped: H4 → H6 (missing H5)

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

Heading level skipped: H4 → H6 (missing H5)

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

H6 Account
H6 Navigation
H6 Follow us
H6 News
H4 Trump Wants to Double Production of New Nuclear Weapon Cores
H6 Support our reporting. Subscribe. skipped
H6 News
H4 Trump Wants to Double Production of New Nuclear Weapon Cores
H6 AI skipped
H4 Startups Brag They Spend More Money on AI Than Human Employees
H6 Podcast skipped
H4 Podcast: How Algorithms Make Us Feel Bad and Weird
H6 podcasts skipped
H4 EMERGENCY BREAKING NEWS PODCAST: Tim, Cooked
H6 News skipped
H4 This AI Tool Rips Off Open Source Software Without Violating Copyright
H6 The Abstract skipped
H4 Scientists Gave a Bunch of Salmon Cocaine. This Is What Happened Next
H6 News skipped
H4 Forbes Prediction Market Gamifies Story About Mass Shooting of 8 Children
H6 Podcast skipped
H4 Why Journalists Are Going Indie (with Maddy Myers)
H6 The Abstract skipped
H4 Babies Born from Dead Parents Will Increase with New Tech. Are We Ready?
H6 News skipped
H4 FAA Scraps Civil and Criminal Penalties for Flying Drones Near ICE Vehicles
H6 The Abstract skipped
H4 The Destroyed Remnants of a Lost World Are Falling to Earth, Scientists Discover
H6 Behind The Blog skipped
H4 Behind the Blog: Jazz and Journalism
H3 Unparalleled access to hidden worlds both online and IRL.

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

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

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

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

Print Stylesheet

Action

No print styles

FIX

No print styles

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

1 navigation landmark(s) detected

Hamburger menu detected (responsive design)

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.

C

Link & Button Quality

Action

3 issue(s) across 110 links and 4 buttons

REVIEW

3 issue(s) across 110 links and 4 buttons

2 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: a#menu-close; https://www.404media.co

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: /about ("here")

14 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://x.com/404mediaco; https://bsky.app/profile/404media.co; https://mastodon.social/@404mediaco; https://instagram.com/404mediaco; https://tiktok.com/@404.media; https://www.facebook.com/404mediaco; /rss; https://x.com/404mediaco; https://bsky.app/profile/404media.co; https://mastodon.social/@404mediaco (+4 more)

93 link(s) with descriptive text

110 links

2 empty

1 generic text

14 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
	(empty)	empty	Add link text or aria-label
https://x.com/404mediaco	Twitter	new tab	Add '(opens in new tab)' to text
https://bsky.app/profile/404media.co	Bluesky	new tab	Add '(opens in new tab)' to text
https://mastodon.social/@404mediaco	Mastodon	new tab	Add '(opens in new tab)' to text
https://instagram.com/404mediaco	Instagram	new tab	Add '(opens in new tab)' to text
https://tiktok.com/@404.media	TikTok	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/404mediaco	Facebook	new tab	Add '(opens in new tab)' to text
/rss	RSS	new tab	Add '(opens in new tab)' to text
https://www.404media.co	(empty)	empty	Add link text or aria-label
/about	here	generic text	Replace with descriptive text
Before: here Suggested: About
https://x.com/404mediaco	Twitter	new tab	Add '(opens in new tab)' to text
https://bsky.app/profile/404media.co	Bluesky	new tab	Add '(opens in new tab)' to text
https://mastodon.social/@404mediaco	Mastodon	new tab	Add '(opens in new tab)' to text
https://instagram.com/404mediaco	Instagram	new tab	Add '(opens in new tab)' to text
https://tiktok.com/@404.media	TikTok	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/404mediaco	Facebook	new tab	Add '(opens in new tab)' to text
/rss	RSS	new tab	Add '(opens in new tab)' to text

97 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

a#menu-close; https://www.404media.co

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Generic link text like 'click here' doesn't describe the destination.

/about ("here")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

Add '(opens in new tab)' to link text or aria-label.

https://x.com/404mediaco; https://bsky.app/profile/404media.co; https://mastodon.social/@404mediaco; https://instagram.com/404mediaco; https://tiktok.com/@404.media; https://www.facebook.com/404mediaco; /rss; https://x.com/404mediaco; https://bsky.app/profile/404media.co; https://mastodon.social/@404mediaco (+4 more)

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

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 404 Media ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

C

Favicon & Branding

Action

5 icon(s) detected

REVIEW

5 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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'>.

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

B

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

Dark-specific theme-color detected

A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.

prefers-color-scheme CSS detected in inline styles

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 #000000 ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

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

title 404 Media

1.00:1

#000000

on

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

span Listen to the

1.00:1

#000000

on

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

span 404 Media Podcast

1.00:1

#000000

on

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

a Log in

1.00:1

#000000

on

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

a Subscribe

1.00:1

#000000

on

#000000

needs 4.5:1 (normal text)

16px · above the fold

a Home

1.00:1

#000000

on

#000000

needs 4.5:1 (normal text)

16px · above the fold

a About

1.00:1

#000000

on

#000000

needs 4.5:1 (normal text)

16px · above the fold

a RSS

1.00:1

#000000

on

#000000

needs 4.5:1 (normal text)

16px · above the fold

a Support/FAQ

1.00:1

#000000

on

#000000

needs 4.5:1 (normal text)

16px · above the fold

a Podcast

1.00:1

#000000

on

#000000

needs 4.5:1 (normal text)

16px · above the fold

a FOIA Forum Archive

1.00:1

#000000

on

#000000

needs 4.5:1 (normal text)

16px · above the fold

a Merch

1.00:1

#000000

on

#000000

needs 4.5:1 (normal text)

16px · above the fold

a Advertise

1.00:1

#000000

on

#000000

needs 4.5:1 (normal text)

16px · mid-page

a Thanks

1.00:1

#000000

on

#000000

needs 4.5:1 (normal text)

16px · mid-page

a Privacy

1.00:1

#000000

on

#000000

needs 4.5:1 (normal text)

16px · mid-page

a Twitter

1.00:1

#000000

on

#000000

needs 4.5:1 (normal text)

16px · mid-page

a Bluesky

1.00:1

#000000

on

#000000

needs 4.5:1 (normal text)

16px · mid-page

a Mastodon

1.00:1

#000000

on

#000000

needs 4.5:1 (normal text)

16px · mid-page

a Instagram

1.00:1

#000000

on

#000000

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h3 Unparalleled access …	3.55:1	3.0:1	#000000	#646464	Pass
title 404 Media	1.00:1	4.5:1	#000000	#000000	Fail
span Listen to the	1.00:1	4.5:1	#000000	#000000	Fail
span 404 Media Podcast	1.00:1	4.5:1	#000000	#000000	Fail
a Log in	1.00:1	4.5:1	#000000	#000000	Fail
a Subscribe	1.00:1	4.5:1	#000000	#000000	Fail
a Home	1.00:1	4.5:1	#000000	#000000	Fail
a About	1.00:1	4.5:1	#000000	#000000	Fail
a RSS	1.00:1	4.5:1	#000000	#000000	Fail
a Support/FAQ	1.00:1	4.5:1	#000000	#000000	Fail
a Podcast	1.00:1	4.5:1	#000000	#000000	Fail
a FOIA Forum Archive	1.00:1	4.5:1	#000000	#000000	Fail
a Merch	1.00:1	4.5:1	#000000	#000000	Fail
a Advertise	1.00:1	4.5:1	#000000	#000000	Fail
a Thanks	1.00:1	4.5:1	#000000	#000000	Fail
a Privacy	1.00:1	4.5:1	#000000	#000000	Fail
a Twitter	1.00:1	4.5:1	#000000	#000000	Fail
a Bluesky	1.00:1	4.5:1	#000000	#000000	Fail
a Mastodon	1.00:1	4.5:1	#000000	#000000	Fail
a Instagram	1.00:1	4.5:1	#000000	#000000	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 85/100 — 4 failing, 22 passed

REVIEW

85

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.

ARIA

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Search `div.row > div.col-xs-3 > div.header__search > a.header__search--open`
Light Theme `div.row > div.col-xs-3 > div.header__theme > a#theme-light`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
SUPPORT OUR REPORTING. SUBSCRIBE. `main.main > div.promo-unit > div.promo-unit__content > h6.promo-unit__cta`
AI `div.col-xs-12 > div.post-card > div.post-card__content > h6`
PODCAST `div.col-xs-12 > div.post-card > div.post-card__content > h6`
PODCASTS `div.col-xs-12 > div.post-card > div.post-card__content > h6`
NEWS `div.col-xs-12 > div.post-card > div.post-card__content > h6`
THE ABSTRACT `div.col-xs-12 > div.post-card > div.post-card__content > h6`
NEWS `div.col-xs-12 > div.post-card > div.post-card__content > h6`
PODCAST `div.col-xs-12 > div.post-card > div.post-card__content > h6`
THE ABSTRACT `div.col-xs-12 > div.post-card > div.post-card__content > h6`
NEWS `div.col-xs-12 > div.post-card > div.post-card__content > h6`
THE ABSTRACT `div.col-xs-12 > div.post-card > div.post-card__content > h6`
BEHIND THE BLOG `div.col-xs-12 > div.post-card > div.post-card__content > h6`

These are opportunities to improve keyboard navigation in your application.

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
div#bsa-zone_1694817838459-1_123456 > div#standard > a.native-banner > img.native-img `div#bsa-zone_1694817838459-1_123456 > div#standard > a.native-banner > img.native-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.row > div.col-xs-6 > div.header__brand > a.header__logo `div.row > div.col-xs-6 > div.header__brand > a.header__logo`

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

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Form elements have associated labels

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

●Background and foreground colors have a sufficient contrast ratio

●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.

●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.

●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.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Deprecated ARIA roles were not used

○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

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

○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

○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

○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

4 landmarks

PASS

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

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

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

A+

Alt Text Quality

All 28 images OK

PASS

All 28 images OK

28 image(s) with good alt text

28 images 28 good alt text

All images have appropriate alt text.

A

Form Accessibility

1 of 1 controls have issues

PASS

1 of 1 controls have issues

1 control(s) rely on placeholder only

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

Got: <input type="email">

1 controls

0 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
input	email	(Your email)	placeholder only

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

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

A+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: 404 Media

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name 404 Media ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓

Name 404 Media Display Mode standalone Theme Color #e50b4f Background Color #ffffff Icons 3 icon(s)