Skip to content
https://wnyc.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
48
GRADE
F
FIX
7
REVIEW
4
PASS
2
INFO
0
Checks
13
2 PASS 4 REVIEW 7 FIX
D
Landmark Structure
Action
7 landmarks
FIX
7 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
5 <nav> landmark(s) found
Warning::
5 of 5 <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 MAIN (missing!) CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

F
Heading Hierarchy
Action
61 headings, 15 skip(s)
FIX
61 headings, 15 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 WNYC Navigation
  • H2 All Things Considered
  • H4 Top Stories skipped
  • H2 Mayor Mamdani's Lessons From Mayor La Guardia
  • H4 The Brian Lehrer Show skipped
  • H2 Celebrating Library Workers
  • H4 The Brian Lehrer Show skipped
  • H2 How a Brooklyn musician uses her Norwegian fiddle to make a sound all her own
  • H4 Latest from WNYC skipped
  • H2 The LES is the city's new vintage district. With prices high and supply low, can it last?
  • H2 A Genocide Scholar Asks “What Went Wrong” in Israel
  • H4 The New Yorker Radio Hour skipped
  • H2 Influencers Usher in a New Era for #MeToo
  • H4 On the Media skipped
  • H2 Fast-Tracking Psychedelics Research
  • H4 The Brian Lehrer Show skipped
  • H2 Send us your poems for National Poetry Month on WNYC
  • H4 Go Deeper with WNYC skipped
  • H2 NYC NOW
  • H2 Sign up for WNYC's Weekly newsletter
  • H2 Ask Governor Sherrill
  • H2 Let’s talk democracy at the laundromat!
  • H4 From The WNYC Archives skipped
  • H2 One of the Country's Earliest African-American Radio Programs on WNYC 1929-1930
  • H2 Breaking the Glass Ceiling: Lilian Supove Blake
  • H2 Take A Dive into the WNYC Archives
  • H4 Culture skipped
  • H2 Broadway on the Radio: 'Ragtime' at WNYC
  • H4 All Of It with Alison Stewart skipped
  • H2 A Wonder Is What It Is: Nick Offerman Reads 'A Vision,' by Wendell Berry
  • H4 All Of It with Alison Stewart skipped
  • H2 David Hyde Pierce on Classical Music Happy Hour
  • H2 The 2026 Public Song Project
  • H2 April 'Get Lit' Preview: Cynthia D'Aprix Sweeney on 'Lake Effect'
  • H4 All Of It with Alison Stewart skipped
  • H4 Popular Stories
  • H2 Trump Administration Dismantling Climate Goals; Earth Day from Space; Will the US or Iran Blink First?; Advice for Finding Your Life's Work
  • H2 Lessons from La Guardia; Psychedelics Research; A Brownsville Novel; Celebrating Library Workers
  • H2 Monday Morning Politics: Looking Ahead to Midterms; New Jersey Budget Update; Investing Pension Funds In Affordable Housing; Jazz Legacies
  • H2 Making a Meaningful Earth Day; Brooklyn's Greenest Block; New Doc About A Gym Run By Formerly Incarcerated People; Pete Ohs & Jeremy O. Harris on 'Erupcja'
  • H2 Byrne & O'Hara in 'Fallen Angels'; Luke Tennie; Art of NYC's Sanitation Department; "Ceija Stojka: Making Visible"; "Art Fair of the Global Majority"
  • H2 Trump Administration Dismantling Climate Goals; Earth Day from Space; Will the US or Iran Blink First?; Advice for Finding Your Life's Work
  • H2 Lessons from La Guardia; Psychedelics Research; A Brownsville Novel; Celebrating Library Workers
  • H2 Making a Meaningful Earth Day; Brooklyn's Greenest Block; New Doc About A Gym Run By Formerly Incarcerated People; Pete Ohs & Jeremy O. Harris on 'Erupcja'
  • H2 Byrne & O'Hara in 'Fallen Angels'; Luke Tennie; Art of NYC's Sanitation Department; "Ceija Stojka: Making Visible"; "Art Fair of the Global Majority"
  • H2 Monday Morning Politics: Looking Ahead to Midterms; New Jersey Budget Update; Investing Pension Funds In Affordable Housing; Jazz Legacies
  • H2 Photo Gallery: WQXR Celebrates Earth Day With Your Photo Submissions
  • H2 Saturday at 1pm: Kaija Saariaho’s Innocence
  • H2 New Book Explores Men & Masculinity; Xochitl Gonzalez's Latest Novel; 4/20 Legal Cannabis News Roundup; The Versatile Chocolate Chip Cookie
  • H2 Byrne & O'Hara in 'Fallen Angels'; Luke Tennie; Art of NYC's Sanitation Department; "Ceija Stojka: Making Visible"; "Art Fair of the Global Majority"
  • H2 #3644: Another World Music Edition
  • H4 EVENTS AND INFORMATION skipped
  • H2 Poetry Together: A Night of Collaboration and Community
  • H2 Get Lit April Book Club: Cynthia D'Aprix Sweeney
  • H2 Broadway on the Radio: CATS: The Jellicle Ball
  • H2 Diversity, Equity, Inclusion, Accessibility & Belonging
  • H5 Document Footer skipped
  • H2 About WNYC
  • H2 Inside WNYC
  • H2 Social
  • H2 Legal Nav

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

F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
favicon.ico Present
PNG Icons Present
Apple Touch Missing
SVG Favicon Missing
Manifest Icons Missing
Multiple Sizes Missing
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
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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
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::
5 navigation landmark(s) detected
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 5 <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.
C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality Custom 404 Page
Status Code HTTP 404 Page Title WNYC | New York Public Radio, Podcasts, Live Streaming Radio, News Custom Styling Navigation Homepage Link Search Form
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 5 fail WCAG AA
REVIEW

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

15 pass 5 fail WCAG AA
title WNYC | New York Public Radio, Podcasts, …
1.66:1
#000000
on
#333333
needs 4.5:1 (normal text)
16px · top of page (header area)
span A list of our sites
2.71:1
#000000
on
#9A2639
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
a NYPR Network
4.36:1
#000000
on
#DE1E3D
needs 4.5:1 (normal text)
16px · top of page (header area)
span NYPR Network
3.44:1
#000000
on
#BE1F38
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
span WNYC Navigation
2.41:1
#000000
on
#8E2131
needs 4.5:1 (normal text)
16px · above the fold

2 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)
ElementRatioRequiredFGBGResult
h2 Inside WNYC18.59:13.0:1
#000000
#F1F1F1
Pass
h2 Social18.59:13.0:1
#000000
#F1F1F1
Pass
h2 Legal Nav18.59:13.0:1
#000000
#F1F1F1
Pass
title WNYC | New York Publ…1.66:14.5:1
#000000
#333333
Fail
span A list of our sites2.71:14.5:1
#000000
#9A2639
Fail
a NYPR Network4.36:14.5:1
#000000
#DE1E3D
Fail
span NYPR Network3.44:14.5:1
#000000
#BE1F38
Fail
span WNYC Navigation2.41:14.5:1
#000000
#8E2131
Fail
a Donate18.59:14.5:1
#000000
#F1F1F1
Pass
a Member Center18.59:14.5:1
#000000
#F1F1F1
Pass
a Radio18.59:14.5:1
#000000
#F1F1F1
Pass
a All Streams18.59:14.5:1
#000000
#F1F1F1
Pass
a Schedule18.59:14.5:1
#000000
#F1F1F1
Pass
a 100 Years18.59:14.5:1
#000000
#F1F1F1
Pass
a Shows18.59:14.5:1
#000000
#F1F1F1
Pass
a Topics18.59:14.5:1
#000000
#F1F1F1
Pass
a Discover18.59:14.5:1
#000000
#F1F1F1
Pass
a Support Us18.59:14.5:1
#000000
#F1F1F1
Pass
a Search18.59:14.5:1
#000000
#F1F1F1
Pass
span WNYC 93.9 FM18.59:14.5:1
#000000
#F1F1F1
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.

B
Lighthouse Accessibility Audits
Score 87/100 — 6 failing, 23 passed
REVIEW
87

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.

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
The Brian Lehrer Show div.story-wrapper > div.text > a.gtm__click-tracking > h4.show-name
The Brian Lehrer Show div.story-wrapper > div.text > a.gtm__click-tracking > h4.show-name
SPONSORED div#top-stories-wrapper > div.sideblock > p > span.admessage
The New Yorker Radio Hour div.story-wrapper > div.text > a.gtm__click-tracking > h4.show-name
On the Media div.story-wrapper > div.text > a.gtm__click-tracking > h4.show-name
The Brian Lehrer Show div.story-wrapper > div.text > a.gtm__click-tracking > h4.show-name
All Of It with Alison Stewart div.story-wrapper > div.text > a.gtm__click-tracking > h4.show-name
All Of It with Alison Stewart div.story-wrapper > div.text > a.gtm__click-tracking > h4.show-name
All Of It with Alison Stewart div.story-wrapper > div.text > a.gtm__click-tracking > h4.show-name
ON AIR SCHEDULE div.l-flex1of2 > ul.list > li.list-item > a.link--capbold
DAILY NEWSLETTER div.l-flex1of2 > ul.list > li.list-item > a.link--capbold
EVENTS div.l-flex1of2 > ul.list > li.list-item > a.link--capbold
PARTNER EVENTS div.l-flex1of2 > ul.list > li.list-item > a.link--capbold
COMMUNITY div.l-flex1of2 > ul.list > li.list-item > a.link--capbold
GIVEAWAYS div.l-flex1of2 > ul.list > li.list-item > a.link--capbold
WEATHER div.l-flex1of2 > ul.list > li.list-item > a.link--capbold
DOWNLOAD OUR APPS div.l-flex1of2 > ul.list > li.list-item > a.link--capbold
PODCASTS div.l-flex1of2 > ul.list > li.list-item > a.link--capbold
ARCHIVED SHOWS div.l-flex1of2 > ul.list > li.list-item > a.link--capbold
AUDIO ARCHIVES div.l-flex1of2 > ul.list > li.list-item > a.link--capbold
AUDIO HELP div.l-flex1of2 > ul.list > li.list-item > a.link--capbold
SUPPORT US div.l-flex1of2 > ul.list > li.list-item > a.link--capbold
ABOUT US div.align--mq-centertoleft > ul.list > li.list-item > a.link--capbold
CONTACT US / FEEDBACK div.align--mq-centertoleft > ul.list > li.list-item > a.link--capbold
ONLINE MEMBER CENTER div.align--mq-centertoleft > ul.list > li.list-item > a.link--capbold
BECOME A SPONSOR div.align--mq-centertoleft > ul.list > li.list-item > a.link--capbold
DONORS div.align--mq-centertoleft > ul.list > li.list-item > a.link--capbold
CAREERS div.align--mq-centertoleft > ul.list > li.list-item > a.link--capbold
DIVERSITY (DEI) div.align--mq-centertoleft > ul.list > li.list-item > a.link--capbold
PRESS div.align--mq-centertoleft > ul.list > li.list-item > a.link--capbold
© 2026 NEW YORK PUBLIC RADIO nav.align--mq-centertoleft > ul.list > li.list-item > a.link--capbold
TERMS OF USE nav.align--mq-centertoleft > ul.list > li.list-item > a.link--capbold
PRIVACY POLICY nav.align--mq-centertoleft > ul.list > li.list-item > a.link--capbold
ACCESSIBILITY nav.align--mq-centertoleft > ul.list > li.list-item > a.link--capbold
CORRECTIONS nav.align--mq-centertoleft > ul.list > li.list-item > a.link--capbold
GIVEAWAY RULES nav.align--mq-centertoleft > ul.list > li.list-item > a.link--capbold
WNYC-FM FCC PUBLIC FILE nav.align--mq-centertoleft > ul.list > li.list-item > a.link--capbold
EEO REPORT nav.align--mq-centertoleft > ul.list > li.list-item > a.link--capbold
WNYC-AM FCC PUBLIC FILE nav.align--mq-centertoleft > ul.list > li.list-item > a.link--capbold

These are opportunities to improve the legibility of your content.

Navigation

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
TOP STORIES div#wnyc_home > div#top-stories-wrapper > div.top-stories > h4.bucket-title
The Brian Lehrer Show div.story-wrapper > div.text > a.gtm__click-tracking > h4.show-name
The Brian Lehrer Show div.story-wrapper > div.text > a.gtm__click-tracking > h4.show-name
LATEST FROM WNYC div#main > div#wnyc_home > div.shelf > h4.bucket-title
The New Yorker Radio Hour div.story-wrapper > div.text > a.gtm__click-tracking > h4.show-name
On the Media div.story-wrapper > div.text > a.gtm__click-tracking > h4.show-name
The Brian Lehrer Show div.story-wrapper > div.text > a.gtm__click-tracking > h4.show-name
GO DEEPER WITH WNYC div#main > div#wnyc_home > div.shelf > h4.bucket-title
FROM THE WNYC ARCHIVES div#main > div#wnyc_home > div.shelf > h4.bucket-title
CULTURE div#main > div#wnyc_home > div.shelf > h4.bucket-title
All Of It with Alison Stewart div.story-wrapper > div.text > a.gtm__click-tracking > h4.show-name
All Of It with Alison Stewart div.story-wrapper > div.text > a.gtm__click-tracking > h4.show-name
All Of It with Alison Stewart div.story-wrapper > div.text > a.gtm__click-tracking > h4.show-name
EVENTS AND INFORMATION div#main > div#wnyc_home > div.shelf > h4.bucket-title
Document Footer div#site-chrome > footer#footer > div.for-screenreaders > h5

These are opportunities to improve keyboard navigation in your application.

Names and labels

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
div.story-wrapper > div.media-wrapper > div.media > a.gtm__click-tracking div.story-wrapper > div.media-wrapper > div.media > a.gtm__click-tracking
div.story-wrapper > div.media-wrapper > div.media > a.gtm__click-tracking div.story-wrapper > div.media-wrapper > div.media > a.gtm__click-tracking
div.story-wrapper > div.media-wrapper > div.media > a.gtm__click-tracking div.story-wrapper > div.media-wrapper > div.media > a.gtm__click-tracking
div.story-wrapper > div.media-wrapper > div.media > a.gtm__click-tracking div.story-wrapper > div.media-wrapper > div.media > a.gtm__click-tracking
div.story-wrapper > div.media-wrapper > div.media > a.gtm__click-tracking div.story-wrapper > div.media-wrapper > div.media > a.gtm__click-tracking
div.story-wrapper > div.media-wrapper > div.media > a.gtm__click-tracking div.story-wrapper > div.media-wrapper > div.media > a.gtm__click-tracking
div.story-wrapper > div.media-wrapper > div.media > a.gtm__click-tracking div.story-wrapper > div.media-wrapper > div.media > a.gtm__click-tracking
div.story-wrapper > div.media-wrapper > div.media > a.gtm__click-tracking div.story-wrapper > div.media-wrapper > div.media > a.gtm__click-tracking
div.story-wrapper > div.media-wrapper > div.media > a.gtm__click-tracking div.story-wrapper > div.media-wrapper > div.media > a.gtm__click-tracking
div.story-wrapper > div.media-wrapper > div.media > a.gtm__click-tracking div.story-wrapper > div.media-wrapper > div.media > a.gtm__click-tracking
div.story-wrapper > div.media-wrapper > div.media > a.gtm__click-tracking div.story-wrapper > div.media-wrapper > div.media > a.gtm__click-tracking
div.story-wrapper > div.media-wrapper > div.media > a.gtm__click-tracking div.story-wrapper > div.media-wrapper > div.media > a.gtm__click-tracking
div.story-wrapper > div.media-wrapper > div.media > a.gtm__click-tracking div.story-wrapper > div.media-wrapper > div.media > a.gtm__click-tracking
div.story-wrapper > div.media-wrapper > div.media > a.gtm__click-tracking div.story-wrapper > div.media-wrapper > div.media > a.gtm__click-tracking
div.story-wrapper > div.media-wrapper > div.media > a.gtm__click-tracking div.story-wrapper > div.media-wrapper > div.media > a.gtm__click-tracking
div.story-wrapper > div.media-wrapper > div.media > a.gtm__click-tracking div.story-wrapper > div.media-wrapper > div.media > a.gtm__click-tracking
li > div.story-wrapper > div.media > a.gtm__click-tracking li > div.story-wrapper > div.media > a.gtm__click-tracking
li > div.story-wrapper > div.media > a.gtm__click-tracking li > div.story-wrapper > div.media > a.gtm__click-tracking
li > div.story-wrapper > div.media > a.gtm__click-tracking li > div.story-wrapper > div.media > a.gtm__click-tracking
li > div.story-wrapper > div.media > a.gtm__click-tracking li > div.story-wrapper > div.media > a.gtm__click-tracking
li.last > div.story-wrapper > div.media > a.gtm__click-tracking li.last > div.story-wrapper > div.media > a.gtm__click-tracking
div.story-wrapper > div.media-wrapper > div.media > a.gtm__click-tracking div.story-wrapper > div.media-wrapper > div.media > a.gtm__click-tracking

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Radio All Streams Schedule 100 Years Shows Topics Discover Suppo… nav.l-page-nav > div.scrollable-body > div > ul.list

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.touchevents html.touchevents

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Listen Live div.stream-banner-card > div > div#ember1170 > button#ember1171
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
Image elements have `[alt]` attributes
`[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
Document has a `<title>` element
`<frame>` or `<iframe>` elements have a title
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links are distinguishable without relying on color.
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
Deprecated ARIA roles were not used
All heading elements contain content.
`[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
`<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
`<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.
Identical links have the same purpose.
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+
Alt Text Quality
All 38 images OK
PASS
All 38 images OK
Info::
31 decorative image(s) correctly marked
Info::
7 image(s) with good alt text
38 images 7 good alt text 31 decorative
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback