Skip to content
https://scholastic.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
45
GRADE
F
FIX
7
REVIEW
3
PASS
3
INFO
0
Checks
13
3 PASS 3 REVIEW 7 FIX
F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-ogepa0
404 Page Quality ✗ Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
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 Missing
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://scholastic.com/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://scholastic.com/manifest.json

Manifest contains invalid JSON.

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::
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.
C
Landmark Structure
Action
4 landmarks
REVIEW
4 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
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 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

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

B
Heading Hierarchy
34 headings
REVIEW
34 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 Spring into New Stories
  • H2 Teachers, Raise Funds and Unlock Exclusive Offers
  • H2 Discover Scholastic TV Now
  • H2 Watch Free Shows and Movies for the Entire Family
  • H2 Summer Learning
  • H3 My Books Summer | Take-Home Book Packs
  • H3 LitCamp | Summer Literacy Program
  • H3 MathCamp | Summer Math Program
  • H3 Phonics Booster Kits
  • H3 Summer Workbooks
  • H3 Scholar Zone Summer
  • H3 Summer PreK
  • H3 School Readiness Kits
  • H3 School Success Kits
  • H2 Book Sets Under $30
  • H3 Mister Shivers Value Pack (#1-4)
  • H3 Continue the Series: Unicorn and Yeti #2-5
  • H3 Cat on the Run Trilogy Value Pack
  • H3 Raise a Reader Set: Magical Reads
  • H3 Disaster Squad Value Pack #1-4
  • H3 Raise a Reader Set: Graphix Thrills
  • H3 Let's Sing Board Books Value Pack
  • H3 Kwame's Magic Quest Value Pack #1-4
  • H3 Raise a Reader Set: Pre-K Reads
  • H3 Heartwarming Board Books (Pack of 3)
  • H2 Don't Miss Out
  • H3 Books about Feelings & Kindness
  • H3 See What's New!
  • H3 Summer Take-Home Book Packs
  • H2 Footer
  • H2 Educators
  • H2 Parents
  • H2 Our Sites
  • H2 About Us

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
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
REVIEW

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

20 pass 4 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Summer Learning20.65:13.0:1
#000000
#FDFDFD
Pass
h2 Book Sets Under $3020.65:13.0:1
#000000
#FDFDFD
Pass
h2 Don't Miss Out20.65:13.0:1
#000000
#FDFDFD
Pass
h2 Footer20.65:13.0:1
#000000
#FDFDFD
Pass
h2 Educators20.65:13.0:1
#000000
#FDFDFD
Pass
h2 Parents20.65:13.0:1
#000000
#FDFDFD
Pass
h2 Our Sites20.65:13.0:1
#000000
#FDFDFD
Pass
h2 About Us20.65:13.0:1
#000000
#FDFDFD
Pass
h3 Books about Feelings…20.65:13.0:1
#000000
#FDFDFD
Pass
h3 See What's New!20.65:13.0:1
#000000
#FDFDFD
Pass
h3 Summer Take-Home Boo…20.65:13.0:1
#000000
#FDFDFD
Pass
title Scholastic | Books f…4.52:14.5:1
#000000
#E81111
Pass
p Don't forget to upgr…6.66:14.5:1
#000000
#E66C5B
Pass
p This browser is not …11.80:14.5:1
#000000
#C2C785
Pass
p Download the latest …5.31:14.5:1
#000000
#917A82
Pass
p Chrome8.56:14.5:1
#000000
#D5949E
Pass
p Safari8.24:14.5:1
#000000
#E087AD
Pass
p Firefox6.10:14.5:1
#000000
#C96C9A
Pass
p Shop8.37:14.5:1
#000000
#E089AF
Pass
p Scholastic Book Club…11.40:14.5:1
#000000
#E4B2BD
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+
Alt Text Quality
All 108 images OK
PASS
All 108 images OK
Info::
61 decorative image(s) correctly marked
Info::
47 image(s) with good alt text
108 images 47 good alt text 61 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 95/100 — 3 failing, 23 passed
PASS
95

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.responsivegrid > div.aem-Grid > div.responsivegrid > a.cmp-title__link div.responsivegrid > div.aem-Grid > div.responsivegrid > a.cmp-title__link
div.aem-Grid > div.responsivegrid > div.aem-Grid > a.cmp-title__link div.aem-Grid > div.responsivegrid > div.aem-Grid > a.cmp-title__link
div.responsivegrid > div.aem-Grid > div.image > a.cmp-title__link div.responsivegrid > div.aem-Grid > div.image > a.cmp-title__link
div.aem-Grid > div.image > div.cmp-image > a.cmp-title__link div.aem-Grid > div.image > div.cmp-image > a.cmp-title__link
div.responsivegrid > div.aem-Grid > div.responsivegrid > a.cmp-title__link div.responsivegrid > div.aem-Grid > div.responsivegrid > a.cmp-title__link
div.aem-Grid > div.responsivegrid > div.aem-Grid > a.cmp-title__link div.aem-Grid > div.responsivegrid > div.aem-Grid > a.cmp-title__link
div.responsivegrid > div.aem-Grid > div.image > a.cmp-title__link div.responsivegrid > div.aem-Grid > div.image > a.cmp-title__link
div.aem-Grid > div.image > div.cmp-image > a.cmp-title__link div.aem-Grid > div.image > div.cmp-image > a.cmp-title__link

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

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 html

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
LEARN MORE div.aem-Grid > div.button > div.cmp-title > a.cmp-title__link
STREAM NOW div.aem-Grid > div.button > div.cmp-title > a.cmp-title__link
○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
●`[role]`s are contained by their required parent element
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●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
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●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 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.
○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.
○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