Skip to content
https://nytimes.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
65
GRADE
D
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
No navigation patterns
FIX
No navigation patterns
Info::
8 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
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 8 <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.
B
Landmark Structure
11 landmarks
REVIEW
11 landmarks
Info::
<main> landmark present
Info::
8 <nav> landmark(s) found
Warning::
2 of 8 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Warning::
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
BANNER header NAV "hp-live-band-container-heading" 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

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

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

A+
Heading Hierarchy
13 headings
PASS
13 headings
Info::
Single H1 present
  • H2 We and our partners process data for the following purposes
  • H1 New York Times - Top Stories
  • H2 Live
  • H2 Top Stories
  • H2 More News
  • H2 The AthleticSports coverage
  • H2 Well
  • H2 Culture and Lifestyle
  • H2 AudioPodcasts and narrated articles
  • H2 WirecutterProduct advice
  • H2 GamesDaily puzzles
  • H2 Site Index
  • H2 Site Information Navigation
A+
Alt Text Quality
All 25 images OK
PASS
All 25 images OK
Info::
2 image(s) with alt text over 125 characters
Info::
9 decorative image(s) correctly marked
Info::
14 image(s) with good alt text
25 images 14 good alt text 9 decorative
IssueCount
too long2 image(s)
A+
Form Accessibility
All 20 controls labeled
PASS
All 20 controls labeled
Info::
20 control(s) properly labeled
20 controls
20 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
1checkboxStore and/or access information on a devicearia-label
2checkboxUse limited data to select advertisingaria-label
3checkboxCreate profiles for personalised advertisingaria-label
4checkboxUse profiles to select personalised advertisingaria-label
7checkboxMeasure advertising performancearia-label
9checkboxUnderstand audiences through statistics or combinations of data from different sourcesaria-label
10checkboxDevelop and improve servicesaria-label
1checkboxUse precise geolocation dataaria-label
2checkboxActively scan device characteristics for identificationaria-label
gvl.740checkbox6sensearia-label
gvl.272checkboxA.Mobaria-label
gvl.1271checkboxABCS INSIGHTSaria-label
gvl.27checkboxADventoriaria-label
gvl.806checkboxAarkiaria-label
gvl.231checkboxAcuityAdsaria-label
gvl.196checkboxAdElement Media Solutionsaria-label
gvl.790checkboxAdGeararia-label
gvl.14checkboxAdKernelaria-label
gvl.6checkboxAdSpirit AdServeraria-label
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 We and our partners …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Live21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Top Stories21.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 -…11.42:14.5:1
#000000
#BFBFBF
Pass
div Manage Privacy Prefe…11.18:14.5:1
#000000
#BDBDBD
Pass
span We and our vendors u…10.70:14.5:1
#000000
#B9B9B9
Pass
button Purposes11.18:14.5:1
#000000
#BDBDBD
Pass
button Features11.30:14.5:1
#000000
#BEBEBE
Pass
button Vendors21.00:14.5:1
#000000
#FFFFFF
Pass
div Below, you will find…21.00:14.5:1
#000000
#FFFFFF
Pass
button Consent21.00:14.5:1
#000000
#FFFFFF
Pass
button Legitimate interest21.00:14.5:1
#000000
#FFFFFF
Pass
div Purposes21.00:14.5:1
#000000
#FFFFFF
Pass
span Store and/or access …21.00:14.5:1
#000000
#FFFFFF
Pass
span Off21.00:14.5:1
#000000
#FFFFFF
Pass
span IAB TCF21.00:14.5:1
#000000
#FFFFFF
Pass
p Cookies, device or s…21.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.

A
Lighthouse Accessibility Audits
Score 92/100 — 2 failing, 30 passed
PASS
92

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

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-*]` attributes match their 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]`s are contained by their required parent element
●`[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 with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[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.
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●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
●ARIA IDs are unique
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●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
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○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
○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
○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.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback