Skip to content
https://pbskids.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
63
GRADE
D
FIX
5
REVIEW
4
PASS
4
INFO
0
Checks
13
4 PASS 4 REVIEW 5 FIX
D
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::
Apple touch icon present
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ 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
Theme color only
FIX
Theme color only
Info::
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: #2638c4
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 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.

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::
1 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 1 <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.
B
Heading Hierarchy
2 headings
REVIEW
2 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 Site Menu
  • H2 Video Picks of the Week

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

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title PBS Kids Home! ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 10 fail WCAG AA
REVIEW

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

10 pass 10 fail WCAG AA
span minutes.
3.81:1
#000000
on
#A220DF
needs 4.5:1 (normal text)
16px · above the fold
span Full Episode
3.81:1
#000000
on
#A220DF
needs 4.5:1 (normal text)
16px · above the fold
span New
3.81:1
#000000
on
#A220DF
needs 4.5:1 (normal text)
16px · mid-page
p Cyberchase
3.81:1
#000000
on
#A220DF
needs 4.5:1 (normal text)
16px · mid-page
p Fix It Time!
3.81:1
#000000
on
#A220DF
needs 4.5:1 (normal text)
16px · mid-page
span minutes.
3.81:1
#000000
on
#A220DF
needs 4.5:1 (normal text)
16px · mid-page
span Full Episode
3.81:1
#000000
on
#A220DF
needs 4.5:1 (normal text)
16px · mid-page
p Daniel Tiger's Neighborhood
3.81:1
#000000
on
#A220DF
needs 4.5:1 (normal text)
16px · mid-page
p The Neighborhood Wedding (ASL)
3.81:1
#000000
on
#A220DF
needs 4.5:1 (normal text)
16px · mid-page
a Grown-Ups
3.81:1
#000000
on
#A220DF
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Site Menu9.86:13.0:1
#000000
#2FC0EB
Pass
h2 Video Picks of the W…16.31:13.0:1
#000000
#F9E464
Pass
title PBS KIDS9.86:14.5:1
#000000
#2FC0EB
Pass
span Games7.70:14.5:1
#000000
#819BE0
Pass
span Videos16.31:14.5:1
#000000
#F9E464
Pass
span minutes.18.89:14.5:1
#000000
#FDF4C1
Pass
span Full Episode11.67:14.5:1
#000000
#6CD1D0
Pass
span New11.67:14.5:1
#000000
#6CD1D0
Pass
p Wild Kratts21.00:14.5:1
#000000
#FFFFFF
Pass
p Butternut Tree21.00:14.5:1
#000000
#FFFFFF
Pass
span minutes.3.81:14.5:1
#000000
#A220DF
Fail
span Full Episode3.81:14.5:1
#000000
#A220DF
Fail
span New3.81:14.5:1
#000000
#A220DF
Fail
p Cyberchase3.81:14.5:1
#000000
#A220DF
Fail
p Fix It Time!3.81:14.5:1
#000000
#A220DF
Fail
span minutes.3.81:14.5:1
#000000
#A220DF
Fail
span Full Episode3.81:14.5:1
#000000
#A220DF
Fail
p Daniel Tiger's Neigh…3.81:14.5:1
#000000
#A220DF
Fail
p The Neighborhood Wed…3.81:14.5:1
#000000
#A220DF
Fail
a Grown-Ups3.81:14.5:1
#000000
#A220DF
Fail

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
Landmark Structure
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
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 "site-nav-title" MAIN CONTENTINFO footer

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

A+
Alt Text Quality
All 70 images OK
PASS
All 70 images OK
Info::
35 decorative image(s) correctly marked
Info::
35 image(s) with good alt text
70 images 35 good alt text 35 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.
A+
Lighthouse Accessibility Audits
Score 96/100 — 1 failing, 24 passed
PASS
96

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
NEW li.MediaItem_mediaItem__qeyda > article.MediaItem_videoCard__2gS6g > div.MediaItem_newBadgeWrapper__8pB5Y > span.MediaBadge_mediaBadgeNew__p0WAl
NEW li.MediaItem_mediaItem__qeyda > article.MediaItem_videoCard__2gS6g > div.MediaItem_newBadgeWrapper__8pB5Y > span.MediaBadge_mediaBadgeNew__p0WAl

These are opportunities to improve the legibility of your content.

○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
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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
●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
○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
○`<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
○Links are distinguishable without relying on color.
○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.

Send Feedback