Skip to content
https://warnerbros.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
61
GRADE
D
FIX
5
REVIEW
3
PASS
5
INFO
0
Checks
13
5 PASS 3 REVIEW 5 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-68pkw0
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
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://warnerbros.com/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://warnerbros.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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
4 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 4 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
B
Favicon & Branding
5 icon(s) detected
REVIEW
5 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 19 fail WCAG AA
REVIEW

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

1 pass 19 fail WCAG AA
h1 Now Playing & Coming Soon
1.13:1
#000000
on
#060B42
needs 3.0:1 (large text)
32px · mid-page
title WarnerBros.com | Home of WB Movies, TV, …
1.04:1
#000000
on
#060607
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to content
1.04:1
#000000
on
#070607
needs 4.5:1 (normal text)
16px · top of page (header area)
span Movies
1.07:1
#000000
on
#02003B
needs 4.5:1 (normal text)
16px · top of page (header area)
span TV Shows
1.07:1
#000000
on
#02003C
needs 4.5:1 (normal text)
16px · top of page (header area)
span Games & Apps
1.07:1
#000000
on
#03003D
needs 4.5:1 (normal text)
16px · above the fold
span Brands
1.08:1
#000000
on
#06013E
needs 4.5:1 (normal text)
16px · above the fold
span Collections
1.07:1
#000000
on
#03003E
needs 4.5:1 (normal text)
16px · above the fold
span Press Releases
1.07:1
#000000
on
#02003C
needs 4.5:1 (normal text)
16px · above the fold
span Experiences
1.06:1
#000000
on
#01003B
needs 4.5:1 (normal text)
16px · above the fold
span Shop
1.06:1
#000000
on
#010039
needs 4.5:1 (normal text)
16px · above the fold
div No Results Found
1.05:1
#000000
on
#010036
needs 4.5:1 (normal text)
16px · above the fold
p Follow
1.05:1
#000000
on
#010035
needs 4.5:1 (normal text)
16px · above the fold
p @WarnerBros
1.06:1
#000000
on
#020137
needs 4.5:1 (normal text)
16px · above the fold
p Follow
1.08:1
#000000
on
#030339
needs 4.5:1 (normal text)
16px · mid-page
p @WarnerBrosComedy
1.08:1
#000000
on
#030339
needs 4.5:1 (normal text)
16px · mid-page
p Follow
1.08:1
#000000
on
#040338
needs 4.5:1 (normal text)
16px · mid-page
p @WarnerBrosHorror
1.07:1
#000000
on
#030237
needs 4.5:1 (normal text)
16px · mid-page
p Follow
1.05:1
#000000
on
#010036
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Now Playing & Coming…1.13:13.0:1
#000000
#060B42
Fail
h1 Movie & TV Favorites5.24:13.0:1
#000000
#7F7F7F
Pass
title WarnerBros.com | Hom…1.04:14.5:1
#000000
#060607
Fail
a Skip to content1.04:14.5:1
#000000
#070607
Fail
span Movies1.07:14.5:1
#000000
#02003B
Fail
span TV Shows1.07:14.5:1
#000000
#02003C
Fail
span Games & Apps1.07:14.5:1
#000000
#03003D
Fail
span Brands1.08:14.5:1
#000000
#06013E
Fail
span Collections1.07:14.5:1
#000000
#03003E
Fail
span Press Releases1.07:14.5:1
#000000
#02003C
Fail
span Experiences1.06:14.5:1
#000000
#01003B
Fail
span Shop1.06:14.5:1
#000000
#010039
Fail
div No Results Found1.05:14.5:1
#000000
#010036
Fail
p Follow1.05:14.5:1
#000000
#010035
Fail
p @WarnerBros1.06:14.5:1
#000000
#020137
Fail
p Follow1.08:14.5:1
#000000
#030339
Fail
p @WarnerBrosComedy1.08:14.5:1
#000000
#030339
Fail
p Follow1.08:14.5:1
#000000
#040338
Fail
p @WarnerBrosHorror1.07:14.5:1
#000000
#030237
Fail
p Follow1.05:14.5:1
#000000
#010036
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
63 landmarks
PASS
63 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
No contentinfo (footer) landmark
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Main navigation" MAIN CONTENTINFO (missing!)
A
Heading Hierarchy
2 headings
PASS
2 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 Now Playing & Coming Soon
  • H1 Movie & TV Favorites duplicate H1

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

A+
Alt Text Quality
1 of 13 images have issues
PASS
1 of 13 images have issues
Warning::
1 image(s) with generic alt text
Info::
12 image(s) with good alt text
13 images 12 good alt text 1 generic
IssueCount
generic1 image(s)
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 97/100 — 1 failing, 30 passed
PASS
97

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.sc-kAzzGY > nav.sc-chPdSV > div.sc-kgAjT > a div.sc-kAzzGY > nav.sc-chPdSV > div.sc-kgAjT > a

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
●Form elements have associated labels
●`[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
●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
●`<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
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○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