Accessibility

F

Heading Hierarchy

Action

84 headings, 24 skip(s)

FIX

84 headings, 24 skip(s)

Multiple H1 headings (37 found)

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

Heading level skipped: H1 → H3 (missing H2)

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

Heading level skipped: H1 → H3 (missing H2)

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

Heading level skipped: H1 → H3 (missing H2)

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

Heading level skipped: H1 → H3 (missing H2)

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

Heading level skipped: H1 → H3 (missing H2)

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

Heading level skipped: H1 → H3 (missing H2)

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

Heading level skipped: H1 → H3 (missing H2)

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

Heading level skipped: H1 → H3 (missing H2)

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

Heading level skipped: H1 → H3 (missing H2)

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

Heading level skipped: H1 → H3 (missing H2)

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

Heading level skipped: H1 → H3 (missing H2)

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

Heading level skipped: H1 → H3 (missing H2)

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

Heading level skipped: H1 → H3 (missing H2)

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

Heading level skipped: H1 → H3 (missing H2)

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

Heading level skipped: H1 → H3 (missing H2)

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

Heading level skipped: H1 → H3 (missing H2)

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

Heading level skipped: H1 → H3 (missing H2)

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

Heading level skipped: H1 → H3 (missing H2)

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

Heading level skipped: H1 → H3 (missing H2)

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

Heading level skipped: H1 → H3 (missing H2)

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

Heading level skipped: H1 → H3 (missing H2)

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

Heading level skipped: H1 → H3 (missing H2)

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

Heading level skipped: H1 → H3 (missing H2)

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

Heading level skipped: H1 → H3 (missing H2)

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

24 empty heading(s)

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

H1 Jacobin
H2 Set Up or Reset Your Password
H2 Log in with Password
H2 Log In with Sign-In Code
H2 Verify Account
H2 Log in with Google Account
H2 Log in via institution
H2 Claire Valdez’s Bold Program for Labor in Congress
H3 Washington Wants Its Military Base Back
H3 Yakov Kronrod’s Plan for Economic Democracy in the USSR
H3 Trump Officials Built an AI Tool to Turbocharge Deregulation
H3 The Jewish Labor Bund Stood Against Zionism
H1 (empty)
H3 Anti-Imperialism and Its Fault Lines skipped
H1 (empty)
H3 Big Tech Quietly Demanded Immunity for Working With TikTok skipped
H1 (empty)
H3 Socialists Are Cornering Hochul on Taxing the Rich skipped
H1 (empty)
H3 Victor Serge Was One of the Great Revolutionary Writers skipped
H1 (empty)
H3 LA Socialists’ Debates Reflect the Left’s Growing Strength skipped
H1 (empty)
H3 Dockworkers Against Russia’s and Israel’s Wars skipped
H1 (empty)
H3 Dance Marathons Were the Forerunners of Today’s Reality TV skipped
H1 (empty)
H3 Zohran Mamdani and the Left Made Kathy Hochul Tax the Rich skipped
H2 Teen Jacobin
H1 Subscribe duplicate H1
H1 Follow Us duplicate H1
H2 How Work Got So Bad
H3 Jean-Paul Marat Was the Prophet of the French Revolution
H3 The Vatican vs. Mar-a-Lago
H3 The War in Iran Has Triggered a Helium Crisis
H3 John Roberts’s About-Face on Supreme Court Activism
H1 (empty)
H3 No, Western Marxism Wasn’t a CIA Plot skipped
H1 (empty)
H3 The Hollow Crown of ChatGPT’s Head Honcho skipped
H1 (empty)
H3 Outcome Is Jonah Hill’s Inept Hollywood Satire skipped
H1 (empty)
H3 What Viktor Orbán’s Downfall Hasn’t Settled skipped
H1 (empty)
H3 Why the Rich Should Get Free Public Childcare Too skipped
H1 (empty)
H3 Will More Warehouses Burn? skipped
H1 (empty)
H3 Mexico Is Going All In for Universal Health Care skipped
H1 (empty)
H3 It’s Okay to Like Geese skipped
H2 Power, Not Economic Theory, Created Neoliberalism
H3 The AI Revolution Could Usher In a New Age of Stagnation
H3 “I’m Running Because It Shouldn’t Be So Hard to Live Here”
H3 Communists Helped Build the Mighty New York Hotel Union
H3 Ibrahim Traoré Would Like to Be Thomas Sankara’s Heir
H1 (empty)
H3 The Landless Workers’ Movement, 30 Years After a Massacre skipped
H1 (empty)
H3 Hungary After Orbán skipped
H1 (empty)
H3 How Flint Sit-Down Strikers Built Their Confidence skipped
H1 (empty)
H3 Decarbonizing Housing Means Fighting Landlords skipped
H1 (empty)
H3 The Left Needs an Alternative Cosmopolitanism skipped
H1 (empty)
H3 Make Lower Manhattan Socialist Again skipped
H1 (empty)
H3 Dwight Macdonald After the Death of Liberalism skipped
H1 (empty)
H3 Japan Is Building a War Machine in the East China Sea skipped
H1 Catalyst duplicate H1
H2 Vol. 6 No. 1
H1 Editors’ Note duplicate H1
H1 Yemen in Purgatory duplicate H1
H1 Lean Production Is Not a Solution duplicate H1
H1 India’s Ethnic Democracy duplicate H1
H1 Foucault’s Bad Trip duplicate H1
H1 Chile’s Resurgent Left duplicate H1
H1 Black Reconstruction as Class War duplicate H1
H1 Subscribe duplicate H1
H1 Sign up for our mailing list duplicate H1

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

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

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

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

F

Alt Text Quality

Action

13 of 14 images have issues

FIX

13 of 14 images have issues

13 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

13 image-in-link without alt text

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

1 image(s) with good alt text

14 images 1 good alt text 13 missing

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

2 icon(s) detected

FIX

2 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

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.

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

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)

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

B

Form Accessibility

2 of 11 controls have issues

REVIEW

2 of 11 controls have issues

1 control(s) without accessible label

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

Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response">

1 control(s) rely on placeholder only

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

Got: <input name="email">

9 control(s) properly labeled

11 controls

9 labeled

1 placeholder only

1 unlabeled

Control	Type	Label	Method
input	input	Email	none
#login-email	input	Email	none
#login-password	password	Password	none
input	input	Email	none
input	input	Verification Code	none
#cookiescript_category_strict	checkbox	Strictly necessary	for/id
#cookiescript_category_performance	checkbox	Performance	for/id
#cookiescript_category_targeting	checkbox	Targeting	for/id
#cookiescript_category_functionality	checkbox	Functionality	for/id
email	input	(Email Address Here)	placeholder only
#g-recaptcha-response	textarea	(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

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

C

Link & Button Quality

Action

17 issue(s) across 121 links and 7 buttons

REVIEW

17 issue(s) across 121 links and 7 buttons

17 link(s) with no accessible text

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

Got: /2026/04/valdez-labor-left-congress-campaign; /2026/04/colombia-election-cepeda-military-bases; /2026/04/kronrod-soviet-union-socialism-democracy; /2026/04/trump-deregulation-artificial-intelligence-musk; /2026/04/jewish-labor-bund-crabapple-review; issue/teen-jacobin; /2026/03/work-deskilling-labor-capitalism-technology; /2026/04/marat-legacy-violence-jacobins-robespierre; /2026/04/vatican-leo-trump-iran-war; /2026/04/iran-war-us-helium-crisis (+7 more)

13 link(s) open in new tab without warning

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

Got: https://www.facebook.com/jacobinmag/; https://twitter.com/jacobin; https://shows.acast.com/jacobin-radio; /cookies; https://cookie-script.com/privacy-policy.html; https://stripe.com/privacy; https://policies.google.com/privacy; https://www.facebook.com/policy.php; https://policies.google.com/privacy; https://stripe.com/privacy (+3 more)

91 link(s) with descriptive text

121 links

17 empty

0 generic text

13 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/2026/04/valdez-labor-left-congress-camp…	(empty)	empty	Add link text or aria-label
/2026/04/colombia-election-cepeda-milita…	(empty)	empty	Add link text or aria-label
/2026/04/kronrod-soviet-union-socialism-…	(empty)	empty	Add link text or aria-label
/2026/04/trump-deregulation-artificial-i…	(empty)	empty	Add link text or aria-label
/2026/04/jewish-labor-bund-crabapple-rev…	(empty)	empty	Add link text or aria-label
issue/teen-jacobin	(empty)	empty	Add link text or aria-label
https://www.facebook.com/jacobinmag/	Facebook IconFacebook	new tab	Add '(opens in new tab)' to text
https://twitter.com/jacobin	Twitter IconTwitter	new tab	Add '(opens in new tab)' to text
https://shows.acast.com/jacobin-radio	Podcasts	new tab	Add '(opens in new tab)' to text
/2026/03/work-deskilling-labor-capitalis…	(empty)	empty	Add link text or aria-label
/2026/04/marat-legacy-violence-jacobins-…	(empty)	empty	Add link text or aria-label
/2026/04/vatican-leo-trump-iran-war	(empty)	empty	Add link text or aria-label
/2026/04/iran-war-us-helium-crisis	(empty)	empty	Add link text or aria-label
/2026/04/roberts-supreme-court-activism-…	(empty)	empty	Add link text or aria-label
/2025/12/neoliberalism-keynes-friedman-h…	(empty)	empty	Add link text or aria-label
/2026/04/ai-stagnation-services-producti…	(empty)	empty	Add link text or aria-label
/2026/04/city-council-dc-raj-election	(empty)	empty	Add link text or aria-label
/2026/04/communists-hotel-union-obermeie…	(empty)	empty	Add link text or aria-label
/2026/04/traore-reform-military-repressi…	(empty)	empty	Add link text or aria-label
https://catalyst-journal.com/	(empty)	empty	Add link text or aria-label
/cookies	Read more, opens a new window	new tab	Add '(opens in new tab)' to text
https://cookie-script.com/privacy-policy…	CookieScript	new tab	Add '(opens in new tab)' to text
https://stripe.com/privacy	Stripe	new tab	Add '(opens in new tab)' to text
https://policies.google.com/privacy	Google LLC	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/policy.php	Meta Platform Inc.	new tab	Add '(opens in new tab)' to text
https://policies.google.com/privacy	Google LLC	new tab	Add '(opens in new tab)' to text
https://stripe.com/privacy	Stripe Inc.	new tab	Add '(opens in new tab)' to text
https://stripe.com/privacy	Stripe Inc.	new tab	Add '(opens in new tab)' to text
https://cookie-script.com/cookie-report?…	report, opens a new window	new tab	Add '(opens in new tab)' to text
https://cookie-script.com	CookieScript Consent Managemen…	new tab	Add '(opens in new tab)' to text

98 links and buttons have descriptive text

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

/2026/04/valdez-labor-left-congress-campaign; /2026/04/colombia-election-cepeda-military-bases; /2026/04/kronrod-soviet-union-socialism-democracy; /2026/04/trump-deregulation-artificial-intelligence-musk; /2026/04/jewish-labor-bund-crabapple-review; issue/teen-jacobin; /2026/03/work-deskilling-labor-capitalism-technology; /2026/04/marat-legacy-violence-jacobins-robespierre; /2026/04/vatican-leo-trump-iran-war; /2026/04/iran-war-us-helium-crisis (+7 more)

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

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

https://www.facebook.com/jacobinmag/; https://twitter.com/jacobin; https://shows.acast.com/jacobin-radio; /cookies; https://cookie-script.com/privacy-policy.html; https://stripe.com/privacy; https://policies.google.com/privacy; https://www.facebook.com/policy.php; https://policies.google.com/privacy; https://stripe.com/privacy (+3 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

C

Color Contrast (Screenshot)

Action

20 text elements analyzed, 1 fail WCAG AA

REVIEW

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

19 pass 1 fail WCAG AA 1 pass AA only

h2 Log in with Password

1.58:1

#000000

on

#2B312F

needs 3.0:1 (large text)

24px · mid-page · over background image/gradient

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
h1 Jacobin	5.25:1	3.0:1	#000000	#FF0000	Pass
h1 Follow Us	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Catalyst	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Sign up for our mail…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Set Up or Reset Your…	11.33:1	3.0:1	#000000	#CCBBB4	Pass
h2 Log in with Password	1.58:1	3.0:1	#000000	#2B312F	Fail
h2 Log In with Sign-In …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Verify Account	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Log in with Google A…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Log in via instituti…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Vol. 6 No. 1	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Jacobin	5.25:1	4.5:1	#000000	#FF0000	Pass
a Subscribe	9.53:1	4.5:1	#000000	#FE8F8E	Pass
a Magazine	18.95:1	4.5:1	#000000	#FFF0EE	Pass
a Donate	18.95:1	4.5:1	#000000	#FFF0EE	Pass
a Catalyst	18.95:1	4.5:1	#000000	#FFF0EE	Pass
p Login	18.95:1	4.5:1	#000000	#FFF0EE	Pass
span Password Login	18.95:1	4.5:1	#000000	#FFF0EE	Pass
span Email Code	18.95:1	4.5:1	#000000	#FFF0EE	Pass
span Google Account	18.95:1	4.5:1	#000000	#FFF0EE	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.

C

Lighthouse Accessibility Audits

Action

Score 78/100 — 7 failing, 29 passed

REVIEW

78

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

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
COOKIE DECLARATION `div#cookiescript_bottompart > div#cookiescript_cookietablewrap > div#cookiescript_maintabs > div#cookiescript_declaration`

When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.si-hr__container > ul#site-nav > li.si-hr-nv__item > div.si-hr-nv__toggle `div.si-hr__container > ul#site-nav > li.si-hr-nv__item > div.si-hr-nv__toggle`

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.

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
OUR SPECIAL SPRING ISSUE IS OUT NOW. GET A DISCOUNTED SUBSCRIPTION TO OUR PRINT… `section.bn-at > div.bn-at__container > p > a`
JACOBIN‘S SPECIAL SPRING ISSUE, “TEEN JACOBIN,” IS OUT NOW. FOLLOW THIS LINK TO… `main.hm > aside.hm-cp > div.hm-cp__container > p`
JACOBIN `aside.hm-cp > div.hm-cp__container > p > i`
FOLLOW THIS LINK TO GET A DISCOUNTED SUBSCRIPTION TO OUR BEAUTIFUL PRINT QUARTE… `aside.hm-cp > div.hm-cp__container > p > a`
Helen Lackner `div.hm-xc__container > section.hm-xc__content > article.hm-xc__article > p.hm-xc__author`
Herman Rosenfeld `div.hm-xc__container > section.hm-xc__content > article.hm-xc__article > p.hm-xc__author`
Achin Vanaik `div.hm-xc__container > section.hm-xc__content > article.hm-xc__article > p.hm-xc__author`
Bryan D. Palmer `div.hm-xc__container > section.hm-xc__content > article.hm-xc__article > p.hm-xc__author`
René Rojas `div.hm-xc__container > section.hm-xc__content > article.hm-xc__article > p.hm-xc__author`
Jeff Goodwin `div.hm-xc__container > section.hm-xc__content > article.hm-xc__article > p.hm-xc__author`
section#mailing-list-signup > form.si-fr-ml__form > div.si-fr-ml__formbox > input.si-fr-ml__field `section#mailing-list-signup > form.si-fr-ml__form > div.si-fr-ml__formbox > input.si-fr-ml__field`
SUBMIT `section#mailing-list-signup > form.si-fr-ml__form > button.si-fr-ml__submit > span`
Catalyst `footer.si-fr > ul.si-fr-mu > li.si-fr-mu__item > a.si-fr-mu__link`
About Us `footer.si-fr > ul.si-fr-mu > li.si-fr-mu__item > a.si-fr-mu__link`
Contact Us `footer.si-fr > ul.si-fr-mu > li.si-fr-mu__item > a.si-fr-mu__link`
Advertise `footer.si-fr > ul.si-fr-mu > li.si-fr-mu__item > a.si-fr-mu__link`
Privacy Policy `footer.si-fr > ul.si-fr-mu > li.si-fr-mu__item > a.si-fr-mu__link`

These are opportunities to improve the legibility of your content.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Jacobin `header#site-header > div.si-hr__container > div.si-hr-lo > a.si-hr-lo__container`
div.si-hr__container > ul#site-nav > li.si-hr-nv__item > div.si-hr-nv__toggle `div.si-hr__container > ul#site-nav > li.si-hr-nv__item > div.si-hr-nv__toggle`
div.si-hr__container > ul#site-nav > li.si-hr-nv__item > div.si-hr-nv__toggle `div.si-hr__container > ul#site-nav > li.si-hr-nv__item > div.si-hr-nv__toggle`
div.si-hr__container > ul#site-nav > li.si-hr-nv__item > div.si-hr-nv__toggle `div.si-hr__container > ul#site-nav > li.si-hr-nv__item > div.si-hr-nv__toggle`

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
Anti-Imperialism and Its Fault Lines `section.hm-sd > aside.hm-sd-ty > article.hm-dg__article > h3.hm-dg__title`
Big Tech Quietly Demanded Immunity for Working With TikTok `section.hm-sd > aside.hm-sd-ty > article.hm-dg__article > h3.hm-dg__title`
Socialists Are Cornering Hochul on Taxing the Rich `section.hm-sd > aside.hm-sd-ty > article.hm-dg__article > h3.hm-dg__title`
Victor Serge Was One of the Great Revolutionary Writers `section.hm-sd > aside.hm-sd-ty > article.hm-dg__article > h3.hm-dg__title`
LA Socialists’ Debates Reflect the Left’s Growing Strength `section.hm-sd > aside.hm-sd-ty > article.hm-dg__article > h3.hm-dg__title`
Dockworkers Against Russia’s and Israel’s Wars `section.hm-sd > aside.hm-sd-ty > article.hm-dg__article > h3.hm-dg__title`
Dance Marathons Were the Forerunners of Today’s Reality TV `section.hm-sd > aside.hm-sd-ty > article.hm-dg__article > h3.hm-dg__title`
Zohran Mamdani and the Left Made Kathy Hochul Tax the Rich `section.hm-sd > aside.hm-sd-ty > article.hm-dg__article > h3.hm-dg__title`
No, Western Marxism Wasn’t a CIA Plot `section.hm-sd > aside.hm-sd-ty > article.hm-dg__article > h3.hm-dg__title`
The Hollow Crown of ChatGPT’s Head Honcho `section.hm-sd > aside.hm-sd-ty > article.hm-dg__article > h3.hm-dg__title`
Outcome Is Jonah Hill’s Inept Hollywood Satire `section.hm-sd > aside.hm-sd-ty > article.hm-dg__article > h3.hm-dg__title`
What Viktor Orbán’s Downfall Hasn’t Settled `section.hm-sd > aside.hm-sd-ty > article.hm-dg__article > h3.hm-dg__title`
Why the Rich Should Get Free Public Childcare Too `section.hm-sd > aside.hm-sd-ty > article.hm-dg__article > h3.hm-dg__title`
Will More Warehouses Burn? `section.hm-sd > aside.hm-sd-ty > article.hm-dg__article > h3.hm-dg__title`
Mexico Is Going All In for Universal Health Care `section.hm-sd > aside.hm-sd-ty > article.hm-dg__article > h3.hm-dg__title`
It’s Okay to Like Geese `section.hm-sd > aside.hm-sd-ty > article.hm-dg__article > h3.hm-dg__title`
The Landless Workers’ Movement, 30 Years After a Massacre `section.hm-sd > aside.hm-sd-ty > article.hm-dg__article > h3.hm-dg__title`
Hungary After Orbán `section.hm-sd > aside.hm-sd-ty > article.hm-dg__article > h3.hm-dg__title`
How Flint Sit-Down Strikers Built Their Confidence `section.hm-sd > aside.hm-sd-ty > article.hm-dg__article > h3.hm-dg__title`
Decarbonizing Housing Means Fighting Landlords `section.hm-sd > aside.hm-sd-ty > article.hm-dg__article > h3.hm-dg__title`
The Left Needs an Alternative Cosmopolitanism `section.hm-sd > aside.hm-sd-ty > article.hm-dg__article > h3.hm-dg__title`
Make Lower Manhattan Socialist Again `section.hm-sd > aside.hm-sd-ty > article.hm-dg__article > h3.hm-dg__title`
Dwight Macdonald After the Death of Liberalism `section.hm-sd > aside.hm-sd-ty > article.hm-dg__article > h3.hm-dg__title`
Japan Is Building a War Machine in the East China Sea `section.hm-sd > aside.hm-sd-ty > article.hm-dg__article > h3.hm-dg__title`

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.hm-sd-b__container > article.hm-dg__article > a.hm-dg__frame > img.hm-dg__image `div.hm-sd-b__container > article.hm-dg__article > a.hm-dg__frame > img.hm-dg__image`
div.hm-sd-b__container > article.hm-dg__article > a.hm-dg__frame > img.hm-dg__image `div.hm-sd-b__container > article.hm-dg__article > a.hm-dg__frame > img.hm-dg__image`
div.hm-sd-b__container > article.hm-dg__article > a.hm-dg__frame > img.hm-dg__image `div.hm-sd-b__container > article.hm-dg__article > a.hm-dg__frame > img.hm-dg__image`
div.hm-sd-b__container > article.hm-dg__article > a.hm-dg__frame > img.hm-dg__image `div.hm-sd-b__container > article.hm-dg__article > a.hm-dg__frame > img.hm-dg__image`
div.hm-xj__cover > div.hm-xj__container > a.hm-xj__frame > img.hm-xj__image `div.hm-xj__cover > div.hm-xj__container > a.hm-xj__frame > img.hm-xj__image`
div.hm-sd-sy > article.hm-dg__article > a.hm-dg__frame > img.hm-dg__image `div.hm-sd-sy > article.hm-dg__article > a.hm-dg__frame > img.hm-dg__image`
div.hm-sd-sy > article.hm-dg__article > a.hm-dg__frame > img.hm-dg__image `div.hm-sd-sy > article.hm-dg__article > a.hm-dg__frame > img.hm-dg__image`
div.hm-sd-sy > article.hm-dg__article > a.hm-dg__frame > img.hm-dg__image `div.hm-sd-sy > article.hm-dg__article > a.hm-dg__frame > img.hm-dg__image`
div.hm-sd-sy > article.hm-dg__article > a.hm-dg__frame > img.hm-dg__image `div.hm-sd-sy > article.hm-dg__article > a.hm-dg__frame > img.hm-dg__image`
div.hm-sd-sy > article.hm-dg__article > a.hm-dg__frame > img.hm-dg__image `div.hm-sd-sy > article.hm-dg__article > a.hm-dg__frame > img.hm-dg__image`
div.hm-sd-sy > article.hm-dg__article > a.hm-dg__frame > img.hm-dg__image `div.hm-sd-sy > article.hm-dg__article > a.hm-dg__frame > img.hm-dg__image`
div.hm-sd-sy > article.hm-dg__article > a.hm-dg__frame > img.hm-dg__image `div.hm-sd-sy > article.hm-dg__article > a.hm-dg__frame > img.hm-dg__image`
div.hm-sd-sy > article.hm-dg__article > a.hm-dg__frame > img.hm-dg__image `div.hm-sd-sy > article.hm-dg__article > a.hm-dg__frame > img.hm-dg__image`

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
section.hm-sd > div.hm-sd-b__container > article.hm-dg__article > a.hm-dg__frame `section.hm-sd > div.hm-sd-b__container > article.hm-dg__article > a.hm-dg__frame`
section.hm-sd > div.hm-sd-b__container > article.hm-dg__article > a.hm-dg__frame `section.hm-sd > div.hm-sd-b__container > article.hm-dg__article > a.hm-dg__frame`
section.hm-sd > div.hm-sd-b__container > article.hm-dg__article > a.hm-dg__frame `section.hm-sd > div.hm-sd-b__container > article.hm-dg__article > a.hm-dg__frame`
section.hm-sd > div.hm-sd-b__container > article.hm-dg__article > a.hm-dg__frame `section.hm-sd > div.hm-sd-b__container > article.hm-dg__article > a.hm-dg__frame`
section.hm-sd > div.hm-sd-b__container > article.hm-dg__article > a.hm-dg__frame `section.hm-sd > div.hm-sd-b__container > article.hm-dg__article > a.hm-dg__frame`
section.hm-xj > div.hm-xj__cover > div.hm-xj__container > a.hm-xj__frame `section.hm-xj > div.hm-xj__cover > div.hm-xj__container > a.hm-xj__frame`
section.hm-sd > div.hm-sd-py > article.hm-dg__article > a.hm-dg__frame `section.hm-sd > div.hm-sd-py > article.hm-dg__article > a.hm-dg__frame`
section.hm-sd > div.hm-sd-sy > article.hm-dg__article > a.hm-dg__frame `section.hm-sd > div.hm-sd-sy > article.hm-dg__article > a.hm-dg__frame`
section.hm-sd > div.hm-sd-sy > article.hm-dg__article > a.hm-dg__frame `section.hm-sd > div.hm-sd-sy > article.hm-dg__article > a.hm-dg__frame`
section.hm-sd > div.hm-sd-sy > article.hm-dg__article > a.hm-dg__frame `section.hm-sd > div.hm-sd-sy > article.hm-dg__article > a.hm-dg__frame`
section.hm-sd > div.hm-sd-sy > article.hm-dg__article > a.hm-dg__frame `section.hm-sd > div.hm-sd-sy > article.hm-dg__article > a.hm-dg__frame`
section.hm-sd > div.hm-sd-py > article.hm-dg__article > a.hm-dg__frame `section.hm-sd > div.hm-sd-py > article.hm-dg__article > a.hm-dg__frame`
section.hm-sd > div.hm-sd-sy > article.hm-dg__article > a.hm-dg__frame `section.hm-sd > div.hm-sd-sy > article.hm-dg__article > a.hm-dg__frame`
section.hm-sd > div.hm-sd-sy > article.hm-dg__article > a.hm-dg__frame `section.hm-sd > div.hm-sd-sy > article.hm-dg__article > a.hm-dg__frame`
section.hm-sd > div.hm-sd-sy > article.hm-dg__article > a.hm-dg__frame `section.hm-sd > div.hm-sd-sy > article.hm-dg__article > a.hm-dg__frame`
section.hm-sd > div.hm-sd-sy > article.hm-dg__article > a.hm-dg__frame `section.hm-sd > div.hm-sd-sy > article.hm-dg__article > a.hm-dg__frame`
section.hm-xc > div.hm-xc__container > footer.hm-xc__issue > a.hm-xc__icon `section.hm-xc > div.hm-xc__container > footer.hm-xc__issue > a.hm-xc__icon`

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

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

●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

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

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

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

●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●All heading elements contain content.

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

○`[accesskey]` values are unique

○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

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

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

A

Landmark Structure

23 landmarks

PASS

23 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

404 Error Page

HTTP 404, custom page

PASS

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

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Jacobin Logo ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓