Accessibility

D

Tabindex Anti-Patterns

Action

0 positive, 26 -1-on-focusable

FIX

0 positive, 26 -1-on-focusable

tabindex="-1" on naturally-focusable <button id="fides-tab-features">

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button id="fides-tab-vendors">

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button id="fidesActiveMenuItem">

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button id="fidesActiveMenuItem">

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

D

Iframe Accessibility

Action

6/6 iframe(s) missing title; 0 placeholder(s)

FIX

6/6 iframe(s) missing title; 0 placeholder(s)

WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

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

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

7 navigation landmark(s) detected

Hamburger menu detected (responsive design)

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Search

Skip Link

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

10 landmarks

REVIEW

10 landmarks

<main> landmark present

7 <nav> landmark(s) found

2 of 7 <nav> elements are unlabeled

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

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

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

C

Link & Button Quality

Action

19 issue(s) across 429 links and 78 buttons

REVIEW

19 issue(s) across 429 links and 78 buttons

19 link(s) with no accessible text

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

Got: https://www.nytimes.com/news-event/2026-midterm-elections; https://www.nytimes.com/2026/05/08/opinion/ezra-klein-podcast-julia-belluz.html; a.tpl-lbl (#2728 on page); a.tpl-lbl (#2737 on page); a.tpl-lbl (#2746 on page); a.tpl-lbl (#2756 on page); a.tpl-lbl (#2765 on page); a.tpl-lbl (#2774 on page); a.tpl-lbl (#2784 on page); a.tpl-lbl (#2793 on page) (+9 more)

20 link(s) open in new tab without warning

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

Got: https://6sense.com/privacy-policy/; https://6sense.com/privacy-policy/; https://veepee-ad.com/politique-confidentialit%C3%A9-activit%C3%A9-publicitaire; https://veepee-ad.com/politique-confidentialit%C3%A9-activit%C3%A9-publicitaire; https://www.abcsinsights.com/privacy/ad-measurement; https://www.adventori.com/fr/rgpd/; https://www.adventori.com/fr/rgpd/; https://corp.aarki.com/privacy; https://corp.aarki.com/privacy; https://privacy.acuityads.com/corporate-privacy-policy.html (+10 more)

390 link(s) with descriptive text

429 links

19 empty

0 generic text

20 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://6sense.com/privacy-policy/	Privacy policy	new tab	Add '(opens in new tab)' to text
https://6sense.com/privacy-policy/	Legitimate interest disclosure	new tab	Add '(opens in new tab)' to text
https://veepee-ad.com/politique-confiden…	Privacy policy	new tab	Add '(opens in new tab)' to text
https://veepee-ad.com/politique-confiden…	Legitimate interest disclosure	new tab	Add '(opens in new tab)' to text
https://www.abcsinsights.com/privacy/ad-…	Privacy policy	new tab	Add '(opens in new tab)' to text
https://www.adventori.com/fr/rgpd/	Privacy policy	new tab	Add '(opens in new tab)' to text
https://www.adventori.com/fr/rgpd/	Legitimate interest disclosure	new tab	Add '(opens in new tab)' to text
https://corp.aarki.com/privacy	Privacy policy	new tab	Add '(opens in new tab)' to text
https://corp.aarki.com/privacy	Legitimate interest disclosure	new tab	Add '(opens in new tab)' to text
https://privacy.acuityads.com/corporate-…	Privacy policy	new tab	Add '(opens in new tab)' to text
https://privacy.acuityads.com/corporate-…	Legitimate interest disclosure	new tab	Add '(opens in new tab)' to text
http://adelement.com/privacy-policy.html	Privacy policy	new tab	Add '(opens in new tab)' to text
https://adelement.com/privacy-policy.htm…	Legitimate interest disclosure	new tab	Add '(opens in new tab)' to text
https://policy.samsungrs.com/consent/eu/…	Privacy policy	new tab	Add '(opens in new tab)' to text
https://policy.samsungrs.com/consent/eu/…	Legitimate interest disclosure	new tab	Add '(opens in new tab)' to text
https://adkernel.com/privacy-policy/	Privacy policy	new tab	Add '(opens in new tab)' to text
https://adkernel.com/privacy-policy/	Legitimate interest disclosure	new tab	Add '(opens in new tab)' to text
https://help.adspirit.de/privacy.php?lan…	Privacy policy	new tab	Add '(opens in new tab)' to text
https://help.adspirit.de/privacy.php?lan…	Legitimate interest disclosure	new tab	Add '(opens in new tab)' to text
https://www.nytimes.com/2026/05/08/us/po…	Allison Robbert for The New Yo…	img no alt	Add alt attribute to the image
https://www.nytimes.com/news-event/2026-…	(empty)	empty	Add link text or aria-label
https://www.nytimes.com/2026/05/09/world…	Haiyun Jiang/The New York Time…	img no alt	Add alt attribute to the image
https://www.nytimes.com/2026/05/08/nyreg…	Purported Epstein Suicide Note…	img no alt	Add alt attribute to the image
https://www.nytimes.com/athletic/7261263…	Jeffrey Brown/Icon Sportswire,…	img no alt	Add alt attribute to the image
https://www.nytimes.com/2026/05/08/opini…	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
https://www.nytimes.com/athletic/connect…	Play Connections: Sports Editi…	img no alt	Add alt attribute to the image
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
https://www.nytimes.com/games/wordle/ind…	WordleGuess the 5-letter word …	img no alt	Add alt attribute to the image
https://www.nytimes.com/games/connection…	ConnectionsGroup words that sh…	img no alt	Add alt attribute to the image
https://www.nytimes.com/puzzles/spelling…	Spelling BeeHow many words can…	img no alt	Add alt attribute to the image
https://www.nytimes.com/crosswords/game/…	The Mini CrosswordSolve this b…	img no alt	Add alt attribute to the image
https://www.nytimes.com/crosswords/game/…	The Midi CrosswordCan you solv…	img no alt	Add alt attribute to the image
https://www.nytimes.com/crosswords/game/…	The CrosswordGet clued in with…	img no alt	Add alt attribute to the image
/privacy/manage-settings	Manage Privacy Preferences	new tab	Add '(opens in new tab)' to text

468 links and buttons have descriptive text

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

https://www.nytimes.com/news-event/2026-midterm-elections; https://www.nytimes.com/2026/05/08/opinion/ezra-klein-podcast-julia-belluz.html; a.tpl-lbl (#2728 on page); a.tpl-lbl (#2737 on page); a.tpl-lbl (#2746 on page); a.tpl-lbl (#2756 on page); a.tpl-lbl (#2765 on page); a.tpl-lbl (#2774 on page); a.tpl-lbl (#2784 on page); a.tpl-lbl (#2793 on page) (+9 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://6sense.com/privacy-policy/; https://6sense.com/privacy-policy/; https://veepee-ad.com/politique-confidentialit%C3%A9-activit%C3%A9-publicitaire; https://veepee-ad.com/politique-confidentialit%C3%A9-activit%C3%A9-publicitaire; https://www.abcsinsights.com/privacy/ad-measurement; https://www.adventori.com/fr/rgpd/; https://www.adventori.com/fr/rgpd/; https://corp.aarki.com/privacy; https://corp.aarki.com/privacy; https://privacy.acuityads.com/corporate-privacy-policy.html (+10 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

Tap Target Adequacy

Action

9 tap target(s) too small or too close together

REVIEW

9 tap target(s) too small or too close together

9 tap target(s) too small or too close to neighbors

WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.

B

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 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

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

B

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

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 Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

A

Heading Hierarchy

54 headings

PASS

54 headings

Single H1 present

2 empty heading(s)

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

H2 We and our partners process data for the following purposes
H1 New York Times - Top Stories
H2 What to Watch and Read
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
H3 SECTIONS
H3 TOP STORIES
H3 NEWSLETTERS
H3 PODCASTS
H3 SECTIONS
H3 TOP STORIES
H3 NEWSLETTERS
H3 (empty)
H3 SECTIONS
H3 TOP STORIES
H3 NEWSLETTERS
H3 PODCASTS
H3 SECTIONS
H3 RECOMMENDATIONS
H3 NEWSLETTERS
H3 PODCASTS
H3 SECTIONS
H3 COLUMNS
H3 NEWSLETTERS
H3 PODCASTS
H3 SECTIONS
H3 TOPICS
H3 COLUMNISTS
H3 PODCASTS
H3 Playlists
H3 Listen
H3 Featured
H3 Newsletters
H3 Play
H3 Community
H3 Newsletters
H3 Recipes
H3 Editors' Picks
H3 Newsletters
H3 (empty)
H3 Reviews
H3 The Best...
H3 Newsletters
H3 LEAGUES
H3 TOP STORIES
H3 NEWSLETTERS
H3 PLAY

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

A+

Alt Text Quality

All 22 images OK

PASS

All 22 images OK

2 image(s) with alt text over 125 characters

11 decorative image(s) correctly marked

9 image(s) with good alt text

22 images 9 good alt text 11 decorative

Issue	Count
too long	2 image(s)

A+

Form Accessibility

All 20 controls labeled

PASS

All 20 controls labeled

20 control(s) properly labeled

20 controls

20 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
1	checkbox	Store and/or access information on a device	aria-label
2	checkbox	Use limited data to select advertising	aria-label
3	checkbox	Create profiles for personalised advertising	aria-label
4	checkbox	Use profiles to select personalised advertising	aria-label
7	checkbox	Measure advertising performance	aria-label
9	checkbox	Understand audiences through statistics or combinations of data from different sources	aria-label
10	checkbox	Develop and improve services	aria-label
1	checkbox	Use precise geolocation data	aria-label
2	checkbox	Actively scan device characteristics for identification	aria-label
gvl.740	checkbox	6sense	aria-label
gvl.272	checkbox	A.Mob	aria-label
gvl.1271	checkbox	ABCS INSIGHTS	aria-label
gvl.27	checkbox	ADventori	aria-label
gvl.806	checkbox	Aarki	aria-label
gvl.231	checkbox	AcuityAds	aria-label
gvl.196	checkbox	AdElement Media Solutions	aria-label
gvl.790	checkbox	AdGear	aria-label
gvl.14	checkbox	AdKernel	aria-label
gvl.6	checkbox	AdSpirit AdServer	aria-label
query	text	Search the new york times	aria-label

A+

Form Input Types

1 input(s) using type=text where a specific type would help

PASS

1 input(s) using type=text where a specific type would help

Input "query" should use type="search" (currently type="text")

Field name "query" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

A+

Form Input Quality

20 form control(s) checked, no input-semantic issues

PASS

20 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

<html lang="en"> is set and valid

Got: en

A+

Mobile-Readable Font Sizes

Font-size measurement not available for this scan

PASS

Font-size measurement not available for this scan

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

A

Lighthouse Accessibility Audits

Score 92/100 — 2 failing, 30 passed

PASS

92

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