Skip to content
https://www.nytimes.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
70
GRADE
C
FIX
4
REVIEW
4
PASS
5
INFO
0
Checks
13
5 PASS 4 REVIEW 4 FIX
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
6 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 6 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Not Found - The New York Times ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
6 icon(s) detected
REVIEW
6 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
prefers-color-scheme CSS detected in inline styles
Info::
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 Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

C
Lighthouse Accessibility Audits
Action
Score 76/100 — 6 failing, 21 passed
REVIEW
76

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.

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
timeline div._container_gk23c_16 > div._scrubber_19d53_1 > div._track_19d53_28

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
seek div._container_gk23c_16 > div._scrubber_19d53_1 > div._track_19d53_28 > div._ariaPlaceholder_19d53_152

When an input field 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 more about input field labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div._container_gk23c_16 > div._scrubber_19d53_1 > div._track_19d53_28 > div._progressHandle_19d53_80 div._container_gk23c_16 > div._scrubber_19d53_1 > div._track_19d53_28 > div._progressHandle_19d53_80

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.

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
img._poster_13tnt_20 img._poster_13tnt_20
img._poster_13tnt_20 img._poster_13tnt_20
img._poster_13tnt_20 img._poster_13tnt_20
img._poster_13tnt_20 img._poster_13tnt_20
img._poster_13tnt_20 img._poster_13tnt_20
img._poster_13tnt_20 img._poster_13tnt_20

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
ol.carousel-ol > li.kyt-SgEEq > figure > a.kyt-tdFHR ol.carousel-ol > li.kyt-SgEEq > figure > a.kyt-tdFHR
ol.carousel-ol > li.kyt-SgEEq > figure > a.kyt-tdFHR ol.carousel-ol > li.kyt-SgEEq > figure > a.kyt-tdFHR
ol.carousel-ol > li.kyt-SgEEq > figure > a.kyt-tdFHR ol.carousel-ol > li.kyt-SgEEq > figure > a.kyt-tdFHR
ol.carousel-ol > li.kyt-SgEEq > figure > a.kyt-tdFHR ol.carousel-ol > li.kyt-SgEEq > figure > a.kyt-tdFHR
ol.carousel-ol > li.kyt-SgEEq > figure > a.kyt-tdFHR ol.carousel-ol > li.kyt-SgEEq > figure > a.kyt-tdFHR
ol.carousel-ol > li.kyt-SgEEq > figure > a.kyt-tdFHR ol.carousel-ol > li.kyt-SgEEq > figure > a.kyt-tdFHR
ol.carousel-ol > li.kyt-SgEEq > figure > a.kyt-tdFHR ol.carousel-ol > li.kyt-SgEEq > figure > a.kyt-tdFHR
ol.carousel-ol > li.kyt-SgEEq > figure > a.kyt-tdFHR ol.carousel-ol > li.kyt-SgEEq > figure > a.kyt-tdFHR
ol.carousel-ol > li.kyt-SgEEq > figure > a.kyt-tdFHR ol.carousel-ol > li.kyt-SgEEq > figure > a.kyt-tdFHR
ol.carousel-ol > li.kyt-SgEEq > figure > a.kyt-tdFHR ol.carousel-ol > li.kyt-SgEEq > figure > a.kyt-tdFHR
ol.carousel-ol > li.kyt-SgEEq > figure > a.kyt-tdFHR ol.carousel-ol > li.kyt-SgEEq > figure > a.kyt-tdFHR
ol.carousel-ol > li.kyt-SgEEq > figure > a.kyt-tdFHR ol.carousel-ol > li.kyt-SgEEq > figure > a.kyt-tdFHR

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
NYTCo nav#footer > ul.css-t8x4fj > li.css-a7htku > a.css-jq1cx6
Contact Us nav#footer > ul.css-t8x4fj > li.css-a7htku > a.css-jq1cx6
Accessibility nav#footer > ul.css-t8x4fj > li.css-a7htku > a.css-jq1cx6
Work with us nav#footer > ul.css-t8x4fj > li.css-a7htku > a.css-jq1cx6
Advertise nav#footer > ul.css-t8x4fj > li.css-a7htku > a.css-jq1cx6
T Brand Studio nav#footer > ul.css-t8x4fj > li.css-a7htku > a.css-jq1cx6
Privacy Policy nav#footer > ul.css-t8x4fj > li.css-a7htku > a.css-jq1cx6
Cookie Policy nav#footer > ul.css-t8x4fj > li.css-a7htku > a.css-jq1cx6
Terms of Service nav#footer > ul.css-t8x4fj > li.css-a7htku > a.css-jq1cx6

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[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]` 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.
●ARIA attributes are used as specified for the element's role
●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
●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
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○`[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
○`<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
○Links are distinguishable without relying on color.
○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
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○Elements with visible text labels have matching accessible names.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
A
Landmark Structure
11 landmarks
PASS
11 landmarks
Info::
<main> landmark present
Info::
6 <nav> landmark(s) found
Warning::
2 of 6 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "styln-trump-administration-hp-hp-menu" MAIN CONTENTINFO footer

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

Why this matters

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

Learn more ▾

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

Source: WAI-ARIA Authoring Practices

A+
Heading Hierarchy
10 headings
PASS
10 headings
Info::
Single H1 present
  • H1 New York Times - Top Stories
  • H2 What to Watch and Read
  • H2 Our Best Advice
  • H2 The AthleticSports coverage
  • H2 Well
  • H2 AudioPodcasts and narrated articles
  • H2 WirecutterProduct advice
  • H2 GamesDaily puzzles
  • H2 Site Index
  • H2 Site Information Navigation
A+
Alt Text Quality
All 21 images OK
PASS
All 21 images OK
Info::
2 image(s) with alt text over 125 characters
Info::
9 decorative image(s) correctly marked
Info::
10 image(s) with good alt text
21 images 10 good alt text 9 decorative
IssueCount
too long2 image(s)
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
querytextSearch the new york timesaria-label
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 New York Times - Top…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Site Index21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Site Information Nav…21.00:13.0:1
#000000
#FFFFFF
Pass
title The New York Times -…21.00:14.5:1
#000000
#FFFFFF
Pass
a Skip to content20.47:14.5:1
#000000
#FCFCFC
Pass
a Skip to site index19.60:14.5:1
#000000
#F7F7F7
Pass
a SKIP ADVERTISEMENT20.47:14.5:1
#000000
#FCFCFC
Pass
span Search & Section Nav…21.00:14.5:1
#000000
#FFFFFF
Pass
span Search21.00:14.5:1
#000000
#FFFFFF
Pass
a U.S.21.00:14.5:1
#000000
#FFFFFF
Pass
a International21.00:14.5:1
#000000
#FFFFFF
Pass
a Canada21.00:14.5:1
#000000
#FFFFFF
Pass
a Español21.00:14.5:1
#000000
#FFFFFF
Pass
a 中文21.00:14.5:1
#000000
#FFFFFF
Pass
span Subscribe for $0.50/…21.00:14.5:1
#000000
#FFFFFF
Pass
span Log in21.00:14.5:1
#000000
#FFFFFF
Pass
span Saturday, April 4, 2…21.00:14.5:1
#000000
#FFFFFF
Pass
a Today’s Paper21.00:14.5:1
#000000
#FFFFFF
Pass
span Subscribe for $0.50/…21.00:14.5:1
#000000
#FFFFFF
Pass
span LIVE21.00:14.5:1
#000000
#FFFFFF
Pass

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

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

Send Feedback