Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 3 REVIEW 6 FIX

Link & Button Quality

Action

6 issue(s) across 133 links and 17 buttons

FIX

6 issue(s) across 133 links and 17 buttons

1 link(s) with no accessible text

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

Got: /search/

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: /radio/premium/ ("More")

20 link(s) open in new tab without warning

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

Got: https://itunes.apple.com/us/app/tunein-radio/id418987775?referrer=utm_medium%…; https://play.google.com/store/apps/details?id=tunein.player&hl=en&referrer=ut…; https://tunein.com/about/; https://tunein.com/contact/; https://tunein.com/careers/; https://tunein.com/press/; https://help.tunein.com; https://tunein.com/get-tunein/; https://tunein.com/business/; https://tunein.com/broadcasters/ (+10 more)

4 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button (#1124 on page); button (#1134 on page); button (#1148 on page); button (#1162 on page)

111 link(s) with descriptive text

133 links

1 empty

1 generic text

20 new tab

4 empty buttons

Element	Text	Issue	Suggested Fix
/search/	(empty)	empty	Add link text or aria-label
https://itunes.apple.com/us/app/tunein-r…	Download on the App Store	new tab	Add '(opens in new tab)' to text
https://play.google.com/store/apps/detai…	Get it on Google Play	new tab	Add '(opens in new tab)' to text
/radio/premium/	More	generic text	Replace with descriptive text
Before: More Suggested: Premium
https://tunein.com/about/	About Us	new tab	Add '(opens in new tab)' to text
https://tunein.com/contact/	Contact Us	new tab	Add '(opens in new tab)' to text
https://tunein.com/careers/	Careers	new tab	Add '(opens in new tab)' to text
https://tunein.com/press/	Press	new tab	Add '(opens in new tab)' to text
https://help.tunein.com	Support	new tab	Add '(opens in new tab)' to text
https://tunein.com/get-tunein/	Devices	new tab	Add '(opens in new tab)' to text
https://tunein.com/business/	Brands	new tab	Add '(opens in new tab)' to text
https://tunein.com/broadcasters/	Broadcasters	new tab	Add '(opens in new tab)' to text
https://tunein.com/podcasters/	Podcasters	new tab	Add '(opens in new tab)' to text
https://tunein.com/policies/privacy/	Privacy	new tab	Add '(opens in new tab)' to text
https://tunein.com/policies/	Terms	new tab	Add '(opens in new tab)' to text
https://tunein.com/sitemap/	Sitemap	new tab	Add '(opens in new tab)' to text
https://instagram.com/tunein	Instagram	new tab	Add '(opens in new tab)' to text
https://twitter.com/tunein	Twitter	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/tunein/	LinkedIn	new tab	Add '(opens in new tab)' to text
https://tunein.com/policies/privacy/	More information about your pr…	new tab	Add '(opens in new tab)' to text
https://privacy.tunein.com/policies/en/?…	More information about your pr…	new tab	Add '(opens in new tab)' to text
https://www.onetrust.com/products/cookie…	Powered by OneTrust Opens in a…	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

124 links and buttons have descriptive text

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

/search/

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

Generic link text like 'click here' doesn't describe the destination.

/radio/premium/ ("More")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

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

https://itunes.apple.com/us/app/tunein-radio/id418987775?referrer=utm_medium%…; https://play.google.com/store/apps/details?id=tunein.player&hl=en&referrer=ut…; https://tunein.com/about/; https://tunein.com/contact/; https://tunein.com/careers/; https://tunein.com/press/; https://help.tunein.com; https://tunein.com/get-tunein/; https://tunein.com/business/; https://tunein.com/broadcasters/ (+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

Icon-only buttons need an aria-label so screen readers can announce them.

button (#1124 on page); button (#1134 on page); button (#1148 on page); button (#1162 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

404 Error Page

Action

HTTP 404, custom page

FIX

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

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

Breadcrumbs

Skip Link

Labeled Navigation 1 <nav> element(s)

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.

Landmark Structure

Action

2 landmarks

REVIEW

2 landmarks

No <main> landmark found

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

1 <nav> landmark(s) found

No banner (header) landmark

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

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

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

Alt Text Quality

Action

35 of 57 images have issues

REVIEW

35 of 57 images have issues

2 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

33 image(s) with filename as alt text

22 image(s) with good alt text

57 images 22 good alt text 33 generic 2 missing

Issue	Count
missing	2 image(s)
filename	33 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Heading Hierarchy

14 headings

PASS

14 headings

Multiple H1 headings (6 found)

A page should have only one H1. Multiple H1s dilute the document outline.

H1 TuneIn brings together live sports, music, news, audiobooks, and podcasts — hear what matters most to you!
H1 BREAKING NEWS. duplicate H1
H1 LIVE SPORTS. duplicate H1
H1 NONSTOP MUSIC. duplicate H1
H1 UNLIMITED AUDIOBOOKS. duplicate H1
H1 ALL YOUR PODCASTS. duplicate H1
H2 We Care About Your Privacy
H2 About Your Privacy
H3 Manage Consent Preferences
H4 Strictly Necessary Cookies
H4 Targeting Cookies
H4 Performance Cookies
H4 Functional Cookies
H3 Cookie List

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

Form Accessibility

1 of 10 controls have issues

PASS

1 of 10 controls have issues

1 control(s) without accessible label

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

9 control(s) properly labeled

10 controls

9 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#searchField	text	searchField	for/id
#ot-group-id-C0004	checkbox	Targeting Cookies	for/id
#ot-group-id-C0002	checkbox	Performance Cookies	for/id
#ot-group-id-C0003	checkbox	Functional Cookies	for/id
#vendor-search-handler	text	Cookie list search	aria-label
#chkbox-id	checkbox	checkbox label	for/id
#select-all-hosts-groups-handler	checkbox	checkbox label	for/id
#select-all-vendor-groups-handler	checkbox	checkbox label	for/id
#select-all-vendor-leg-handler	checkbox	checkbox label	for/id
#g-recaptcha-response-100000	textarea	(none)	none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

A+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

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

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 TuneIn brings togeth…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 BREAKING NEWS.	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 LIVE SPORTS.	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 NONSTOP MUSIC.	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 UNLIMITED AUDIOBOOKS…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 ALL YOUR PODCASTS.	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 We Care About Your P…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 About Your Privacy	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Manage Consent Prefe…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Cookie List	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title TuneIn \| Free Intern…	13.08:1	4.5:1	#000000	#FEC25A	Pass
a Home	13.08:1	4.5:1	#000000	#FEC25A	Pass
a Search	13.08:1	4.5:1	#000000	#FEC25A	Pass
a Local Radio	13.08:1	4.5:1	#000000	#FEC25A	Pass
a Recents	13.08:1	4.5:1	#000000	#FEC25A	Pass
a Trending	13.08:1	4.5:1	#000000	#FEC25A	Pass
a Music	13.08:1	4.5:1	#000000	#FEC25A	Pass
a Sports	13.08:1	4.5:1	#000000	#FEC25A	Pass
a News & Talk	13.08:1	4.5:1	#000000	#FEC25A	Pass
a Podcasts	13.08:1	4.5:1	#000000	#FEC25A	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 96/100 — 1 failing, 24 passed

PASS

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

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#appRootScrollReset > div.header-module__header___zvH_Q > div.header-module__headerWrapper___FPkEz > a.header-module__searchToggleContainer___H0IaD `div#appRootScrollReset > div.header-module__header___zvH_Q > div.header-module__headerWrapper___FPkEz > a.header-module__searchToggleContainer___H0IaD`

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.

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

●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

●`<frame>` or `<iframe>` elements have a title

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

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

○Links are distinguishable without relying on color.

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

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

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

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

○Elements with visible text labels have matching accessible names.

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

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

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