Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

3 PASS 7 REVIEW 3 FIX

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.

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 ✗

Heading Hierarchy

No headings

REVIEW

No headings

No headings found

Headings (H1-H6) create the document outline for screen reader navigation.

No headings found

Headings create the document outline for screen reader navigation.

Headings (H1-H6) create the document outline for screen reader navigation.

Why this matters

A page with zero headings is unnavigable by assistive tech and reads as one undifferentiated wall of text.

Learn more ▾

Screen reader users navigate by jumping between H1-H6 elements. A page with no headings has no skip targets — users have to read every word linearly. Adding a heading hierarchy (one H1, then H2 sections, optional H3 subsections) makes the page skimmable for both AT and human readers.

Source: WCAG 1.3.1 / W3C WAI

Alt Text Quality

Action

1 of 42 images have issues

REVIEW

1 of 42 images have issues

1 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

1 image-in-link without alt text

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

3 image(s) with alt text over 125 characters

38 image(s) with good alt text

42 images 38 good alt text 1 missing

Issue	Count
missing	1 image(s)
too long	3 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

Link & Button Quality

Action

32 issue(s) across 274 links and 4 buttons

REVIEW

32 issue(s) across 274 links and 4 buttons

32 link(s) with no accessible text

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

Got: /breaking-news; /breaking-news; /breaking-news; /breaking-news; /breaking-news; /politics; /climate; /politics; /politics; /politics (+22 more)

1 image-only link(s) without alt text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

Got: a[href="/article/202507/said-it-border-czar-tom-homan-bill-the-butcher-cutting"]

241 link(s) with descriptive text

274 links

32 empty

0 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/breaking-news	(empty)	empty	Add link text or aria-label
/breaking-news	(empty)	empty	Add link text or aria-label
/breaking-news	(empty)	empty	Add link text or aria-label
/breaking-news	(empty)	empty	Add link text or aria-label
/breaking-news	(empty)	empty	Add link text or aria-label
/politics	(empty)	empty	Add link text or aria-label
/climate	(empty)	empty	Add link text or aria-label
/politics	(empty)	empty	Add link text or aria-label
/politics	(empty)	empty	Add link text or aria-label
/politics	(empty)	empty	Add link text or aria-label
/politics	(empty)	empty	Add link text or aria-label
/politics	(empty)	empty	Add link text or aria-label
/politics	(empty)	empty	Add link text or aria-label
/politics	(empty)	empty	Add link text or aria-label
/politics	(empty)	empty	Add link text or aria-label
/culture	(empty)	empty	Add link text or aria-label
/culture	(empty)	empty	Add link text or aria-label
/climate	(empty)	empty	Add link text or aria-label
/climate	(empty)	empty	Add link text or aria-label
/climate	(empty)	empty	Add link text or aria-label
/climate	(empty)	empty	Add link text or aria-label
/climate	(empty)	empty	Add link text or aria-label
/climate	(empty)	empty	Add link text or aria-label
/article/202507/said-it-border-czar-tom-…	Who Said It: Border Czar Tom H…	img no alt	Add alt attribute to the image
https://www.facebook.com/newrepublic/	(empty)	empty	Add link text or aria-label
https://www.instagram.com/newrepublic/	(empty)	empty	Add link text or aria-label
https://www.x.com/newrepublic/	(empty)	empty	Add link text or aria-label
https://bsky.app/profile/newrepublic.com	(empty)	empty	Add link text or aria-label
https://flipboard.com/@thenewrepublic	(empty)	empty	Add link text or aria-label
https://open.spotify.com/show/39bB7ap727…	(empty)	empty	Add link text or aria-label
https://podcasts.apple.com/us/podcast/th…	(empty)	empty	Add link text or aria-label
https://www.youtube.com/user/NewRepublic…	(empty)	empty	Add link text or aria-label
https://www.linkedin.com/company/newrepu…	(empty)	empty	Add link text or aria-label

245 links and buttons have descriptive text

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

/breaking-news; /breaking-news; /breaking-news; /breaking-news; /breaking-news; /politics; /climate; /politics; /politics; /politics (+22 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

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

a[href="/article/202507/said-it-border-czar-tom-homan-bill-the-butcher-cutting"]

Why this matters

Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.

Source: WCAG 2.1 SC 2.4.4

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 The New Republic ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

16 icon(s) detected

REVIEW

16 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

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

Detection limited to meta tags and inline styles.

Lighthouse Accessibility Audits

Score 87/100 — 3 failing, 23 passed

REVIEW

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

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
a.ContainerImg > div.LedeImgContainer > picture > img.LedeImg `a.ContainerImg > div.LedeImgContainer > picture > img.LedeImg`

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
nav.HomePageNav > span.HomePageNav_siteNav > span.mobileTopRowCTA > a `nav.HomePageNav > span.HomePageNav_siteNav > span.mobileTopRowCTA > a`
div.StoryMedium > div.StoryMedium_text > div.Byline > a.ContainerArticleBadge_link `div.StoryMedium > div.StoryMedium_text > div.Byline > a.ContainerArticleBadge_link`
div.StoryMedium > div.StoryMedium_text > div.Byline > a.ContainerArticleBadge_link `div.StoryMedium > div.StoryMedium_text > div.Byline > a.ContainerArticleBadge_link`
div.StoryFeature > div.StoryFeature_text > div.Byline > a.ContainerArticleBadge_link `div.StoryFeature > div.StoryFeature_text > div.Byline > a.ContainerArticleBadge_link`
div.StoryMedium > div.StoryMedium_text > div.Byline > a.ContainerArticleBadge_link `div.StoryMedium > div.StoryMedium_text > div.Byline > a.ContainerArticleBadge_link`
div.StoryMedium > div.StoryMedium_text > div.Byline > a.ContainerArticleBadge_link `div.StoryMedium > div.StoryMedium_text > div.Byline > a.ContainerArticleBadge_link`
div.Container > div.Box1_text > div.Byline > a.ContainerArticleBadge_link `div.Container > div.Box1_text > div.Byline > a.ContainerArticleBadge_link`
div.StoryFeatureSquare > div.StorySmall > div.Byline > a.ContainerArticleBadge_link `div.StoryFeatureSquare > div.StorySmall > div.Byline > a.ContainerArticleBadge_link`
div.storyLarge > div.storyLarge_text > div.Byline > a.ContainerArticleBadge_link `div.storyLarge > div.storyLarge_text > div.Byline > a.ContainerArticleBadge_link`
div.StoryFeatureSquare > div.StorySmall > div.Byline > a.ContainerArticleBadge_link `div.StoryFeatureSquare > div.StorySmall > div.Byline > a.ContainerArticleBadge_link`
div.Container > div.Box1_text > div.Byline > a.ContainerArticleBadge_link `div.Container > div.Box1_text > div.Byline > a.ContainerArticleBadge_link`

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

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Subscribe `nav.HomePageNav > span.HomePageNav_siteNav > span.mobileTopRowCTA > button.mobileTopRowCTA__subscribeButton`

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-*]` attributes match their 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

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

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

●ARIA attributes are used as specified for the element's role

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

●Elements use only permitted ARIA attributes

●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

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with 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

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

○Heading elements appear in a sequentially-descending order

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○No element has a `[tabindex]` value greater than 0

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

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Landmark Structure

4 landmarks

PASS

4 landmarks

<main> landmark present

2 <nav> landmark(s) found

2 of 2 <nav> elements are unlabeled

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

No banner (header) landmark

Skip navigation link present

Page Structure — as a screen reader sees it

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

Why this matters

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

Learn more ▾

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

Source: WAI-ARIA Authoring Practices

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

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

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
title The New Republic	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Skip Navigation	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div The New Republic	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a LATEST	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a BREAKING NEWS	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a POLITICS	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a CLIMATE	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a CULTURE	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a MAGAZINE	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a NEWSLETTERS	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a PODCASTS	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a VIDEO	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div The New Republic	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div The New Republic	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a LATEST	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a BREAKING NEWS	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a POLITICS	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a CLIMATE	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a CULTURE	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a MAGAZINE	21.00:1	4.5:1	#000000	#FFFFFF	Pass

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.