Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

1 PASS 7 REVIEW 5 FIX

Link & Button Quality

Action

16 issue(s) across 152 links and 28 buttons

FIX

16 issue(s) across 152 links and 28 buttons

14 link(s) with no accessible text

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

Got: https://geni.us/oQY0y?utm_content=spotlight_knowledge; https://giving.ted.com/page/tedmember?utm_medium=website&utm_source=spotlight…; /talks?sort=newest&topics%5B0%5D=undefined; https://www.ted.com/about?utm_medium=website&utm_source=homepage-spotlight_da…; /talks?sort=newest&topics%5B0%5D=undefined; /talks?sort=newest&topics%5B0%5D=undefined; /talks?sort=newest&topics%5B0%5D=undefined; https://www.linkedin.com/company/ted-conferences/; https://twitter.com/tedtalks; https://instagram.com/ted (+4 more)

2 image-only link(s) without alt text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

Got: a[href="/talks/undefined"]; a[href="https://www.ted.com/"]

3 link(s) open in new tab without warning

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

Got: https://www.ted.com/about/our-organization/our-policies-terms/privacy-policy; https://www.ted.com/about?utm_medium=website&utm_source=homepage-spotlight_da…; https://www.ted.com/about?utm_medium=website&utm_source=homepage-spotlight_da…

2 button(s) with no accessible text

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

Got: button.group (#376 on page); button.group (#380 on page)

133 link(s) with descriptive text

152 links

14 empty

0 generic text

3 new tab

2 empty buttons

Element	Text	Issue	Suggested Fix
https://www.ted.com/about/our-organizati…	Privacy Policy	new tab	Add '(opens in new tab)' to text
https://geni.us/oQY0y?utm_content=spotli…	(empty)	empty	Add link text or aria-label
https://giving.ted.com/page/tedmember?ut…	(empty)	empty	Add link text or aria-label
/talks/undefined	NaN min	img no alt	Add alt attribute to the image
/talks?sort=newest&topics%5B0%5D=undefin…	(empty)	empty	Add link text or aria-label
https://www.ted.com/	Test sponsored by	img no alt	Add alt attribute to the image
https://www.ted.com/about?utm_medium=web…	Ideas change everything.	new tab	Add '(opens in new tab)' to text
https://www.ted.com/about?utm_medium=web…	Learn more about TED	new tab	Add '(opens in new tab)' to text
https://www.ted.com/about?utm_medium=web…	(empty)	empty	Add link text or aria-label
/talks?sort=newest&topics%5B0%5D=undefin…	(empty)	empty	Add link text or aria-label
/talks?sort=newest&topics%5B0%5D=undefin…	(empty)	empty	Add link text or aria-label
/talks?sort=newest&topics%5B0%5D=undefin…	(empty)	empty	Add link text or aria-label
https://www.linkedin.com/company/ted-con…	(empty)	empty	Add link text or aria-label
https://twitter.com/tedtalks	(empty)	empty	Add link text or aria-label
https://instagram.com/ted	(empty)	empty	Add link text or aria-label
https://www.youtube.com/ted	(empty)	empty	Add link text or aria-label
https://www.facebook.com/TED	(empty)	empty	Add link text or aria-label
https://play.google.com/store/apps/detai…	(empty)	empty	Add link text or aria-label
https://play.google.com/store/apps/detai…	(empty)	empty	Add link text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

159 links and buttons have descriptive text

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

https://geni.us/oQY0y?utm_content=spotlight_knowledge; https://giving.ted.com/page/tedmember?utm_medium=website&utm_source=spotlight…; /talks?sort=newest&topics%5B0%5D=undefined; https://www.ted.com/about?utm_medium=website&utm_source=homepage-spotlight_da…; /talks?sort=newest&topics%5B0%5D=undefined; /talks?sort=newest&topics%5B0%5D=undefined; /talks?sort=newest&topics%5B0%5D=undefined; https://www.linkedin.com/company/ted-conferences/; https://twitter.com/tedtalks; https://instagram.com/ted (+4 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

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

a[href="/talks/undefined"]; a[href="https://www.ted.com/"]

Why this matters

Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.

Source: WCAG 2.1 SC 2.4.4

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

https://www.ted.com/about/our-organization/our-policies-terms/privacy-policy; https://www.ted.com/about?utm_medium=website&utm_source=homepage-spotlight_da…; https://www.ted.com/about?utm_medium=website&utm_source=homepage-spotlight_da…

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.group (#376 on page); button.group (#380 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

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

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #eb0028

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 ModePartial Dark Mode

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

3 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

Skip Link

Labeled Navigation 3 <nav> element(s)

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.

Landmark Structure

8 landmarks

REVIEW

8 landmarks

<main> landmark present

3 <nav> landmark(s) found

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

Heading Hierarchy

2 headings

REVIEW

2 headings

No H1 heading found

Every page should have one H1 that describes the page content.

H3 Newsletters
H3 Newsletters

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

Alt Text Quality

1 of 27 images have issues

REVIEW

1 of 27 images have issues

1 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

1 image-in-link without alt text

An image inside a link with no alt creates an empty link.

4 decorative image(s) correctly marked

22 image(s) with good alt text

27 images 22 good alt text 4 decorative 1 missing

Issue	Count
missing	1 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

Form Accessibility

2 of 7 controls have issues

REVIEW

2 of 7 controls have issues

1 control(s) without accessible label

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

Got: <input name="email">

1 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input type="email" id="newsletter-email">

5 control(s) properly labeled

7 controls

5 labeled

1 placeholder only

1 unlabeled

Control	Type	Label	Method
#osano-cm-dialog-toggle--category_STORAGE	checkbox		none
#osano-cm-dialog-toggle--category_MARKETING	checkbox		none
#osano-cm-dialog-toggle--category_PERSONALIZATION	checkbox		none
#osano-cm-dialog-toggle--category_ANALYTICS	checkbox		none
#navigation-search	search	Type to search	aria-label
#newsletter-email	email	(What's your email?)	placeholder only
email	input	(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

Placeholder text disappears on focus and is not a reliable label.

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title TED | 404: Not Found ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✓

Favicon & Branding

Action

5 icon(s) detected

REVIEW

5 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

SVG favicon detected — scales perfectly to any size

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Lighthouse Accessibility Audits

Action

Score 76/100 — 6 failing, 24 passed

REVIEW

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

ARIA

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
A challenge for your brain Daily word, logic, and strategy games that push your… `body.antialiased > section#sailthru-overlay-container`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#hero-slider-images > div.cloned-standard-hero-slider-nav-prev > div.absolute > button.group `div#hero-slider-images > div.cloned-standard-hero-slider-nav-prev > div.absolute > button.group`
div#hero-slider-images > div.cloned-standard-hero-slider-nav-next > div.absolute > button.group `div#hero-slider-images > div.cloned-standard-hero-slider-nav-next > div.absolute > button.group`
div.gencl:absolute > div.gencl:absolute > div.gencl:flex > button.gencl:inline-flex `div.gencl:absolute > div.gencl:absolute > div.gencl:flex > button.gencl:inline-flex`
div.gencl:absolute > div.gencl:absolute > div.gencl:flex > button.gencl:inline-flex `div.gencl:absolute > div.gencl:absolute > div.gencl:flex > button.gencl:inline-flex`
div.gencl:absolute > div.gencl:absolute > div.gencl:flex > button.gencl:inline-flex `div.gencl:absolute > div.gencl:absolute > div.gencl:flex > button.gencl:inline-flex`
body.antialiased > section#sailthru-overlay-container > div.sailthru-overlay > button.sailthru-overlay-close `body.antialiased > section#sailthru-overlay-container > div.sailthru-overlay > button.sailthru-overlay-close`

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.flex > div.mb-8 > div.relative > input.newsletter-input `div.flex > div.mb-8 > div.relative > input.newsletter-input`

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.mx-auto > div.flex > div.h-100 > a `div.mx-auto > div.flex > div.h-100 > a`
div.mx-auto > div.flex > div.h-100 > a `div.mx-auto > div.flex > div.h-100 > a`
div.w-full > div > div.mb-2 > a.relative `div.w-full > div > div.mb-2 > a.relative`
div.w-full > div > div.mb-2 > a.relative `div.w-full > div > div.mb-2 > a.relative`
div.w-full > div > div.mb-2 > a.relative `div.w-full > div > div.mb-2 > a.relative`

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

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

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
Storage Preferences `div#befbc0e5-ee15-4e14-8ba1-c77e210294a9 > div.osano-cm-dialog__content > p.osano-cm-content__drawer-links > a.osano-cm-drawer-links__link`
Third Parties `div#befbc0e5-ee15-4e14-8ba1-c77e210294a9 > div.osano-cm-dialog__content > p.osano-cm-content__drawer-links > a.osano-cm-drawer-links__link`
LOVE `div.flex > div.flex > div.flex > a.relative`
SCIENCE `div.flex > div.flex > div.flex > a.relative`
BUSINESS `div.flex > div.flex > div.flex > a.relative`
TECHNOLOGY `div.flex > div.flex > div.flex > a.relative`
RELATIONSHIPS `div.flex > div.flex > div.flex > a.relative`
RELATIONSHIPS `div.flex > div.flex > div.flex > a.relative`
HEALTH `div.flex > div.grid > div.flex > a.relative`
WAR `div.flex > div.grid > div.flex > a.relative`
SCIENCE `div.flex > div.grid > div.flex > a.relative`
TECHNOLOGY `div.flex > div.grid > div.flex > a.relative`
GLOBAL ISSUES `div.flex > div.grid > div.flex > a.relative`
TECHNOLOGY `div.flex > div.grid > div.flex > a.relative`

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

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Image elements have `[alt]` attributes

●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

●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

●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

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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●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

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

○Elements with visible text labels have matching accessible names.

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

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

A+

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
h3 Newsletters	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Newsletters	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title TED: Ideas change ev…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Opens in a new windo…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Opens an external we…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Opens an external we…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span We and our 19 IAB TC…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Personal data may be…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Our third party IAB …	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span You may change your …	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span You may close this b…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Privacy Policy	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Storage Preferences	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Third Parties	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Storage	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Targeted Advertising	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Personalization	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Analytics	21.00:1	4.5:1	#000000	#FFFFFF	Pass
button Save	21.00:1	4.5:1	#000000	#FFFFFF	Pass
button Accept All	21.00:1	4.5:1	#000000	#FFFFFF	Pass

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

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