Skip to content
https://blizzard.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
59
GRADE
D
FIX
6
REVIEW
3
PASS
4
INFO
0
Checks
13
4 PASS 3 REVIEW 6 FIX
F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 404 ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
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 Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✗ 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: #000b3a
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::
Hamburger menu detected (responsive design)
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)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
4 landmarks
REVIEW
4 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
No contentinfo (footer) landmark
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 CONTENTINFO (missing!)

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

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 18 fail WCAG AA
REVIEW

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

2 pass 18 fail WCAG AA 1 pass AA only
h1 Reign of Talon: Season 2 now live
1.88:1
#000000
on
#343D3E
needs 3.0:1 (large text)
32px · above the fold
h1 Support Habitat for Humanity
2.00:1
#000000
on
#374142
needs 3.0:1 (large text)
32px · mid-page
h1 The Taking is live
1.63:1
#000000
on
#19334F
needs 3.0:1 (large text)
32px · mid-page
h1 CATACLYSM CALLS now live!
1.40:1
#000000
on
#17273E
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Wield forbidden magic as the Warlock
1.40:1
#000000
on
#17273E
needs 3.0:1 (large text)
32px · bottom of viewport
h1 The reckoning arrives April 28
1.40:1
#000000
on
#17273E
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Wield forbidden magic as the Warlock
1.40:1
#000000
on
#17273E
needs 3.0:1 (large text)
32px · bottom of viewport
h1 The reckoning arrives April 28
1.40:1
#000000
on
#17273E
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Reign of Talon: Season 2 now live
1.40:1
#000000
on
#17273E
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Support Habitat for Humanity
1.40:1
#000000
on
#17273E
needs 3.0:1 (large text)
32px · bottom of viewport
h1 The Taking is live
1.40:1
#000000
on
#17273E
needs 3.0:1 (large text)
32px · bottom of viewport
h1 CATACLYSM CALLS now live!
1.40:1
#000000
on
#17273E
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Wield forbidden magic as the Warlock
1.40:1
#000000
on
#17273E
needs 3.0:1 (large text)
32px · bottom of viewport
h1 The reckoning arrives April 28
1.40:1
#000000
on
#17273E
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Download Battle.net
1.40:1
#000000
on
#17273E
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Download Battle.net
1.40:1
#000000
on
#17273E
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Featured Games
1.40:1
#000000
on
#17273E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 World of Warcraft: Midnight
1.40:1
#000000
on
#17273E
needs 3.0:1 (large text)
24px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Wield forbidden magi…5.40:13.0:1
#000000
#BA6D53
Pass
h1 The reckoning arrive…3.35:13.0:1
#000000
#7D5563
Pass
h1 Reign of Talon: Seas…1.88:13.0:1
#000000
#343D3E
Fail
h1 Support Habitat for …2.00:13.0:1
#000000
#374142
Fail
h1 The Taking is live1.63:13.0:1
#000000
#19334F
Fail
h1 CATACLYSM CALLS now…1.40:13.0:1
#000000
#17273E
Fail
h1 Wield forbidden magi…1.40:13.0:1
#000000
#17273E
Fail
h1 The reckoning arrive…1.40:13.0:1
#000000
#17273E
Fail
h1 Wield forbidden magi…1.40:13.0:1
#000000
#17273E
Fail
h1 The reckoning arrive…1.40:13.0:1
#000000
#17273E
Fail
h1 Reign of Talon: Seas…1.40:13.0:1
#000000
#17273E
Fail
h1 Support Habitat for …1.40:13.0:1
#000000
#17273E
Fail
h1 The Taking is live1.40:13.0:1
#000000
#17273E
Fail
h1 CATACLYSM CALLS now…1.40:13.0:1
#000000
#17273E
Fail
h1 Wield forbidden magi…1.40:13.0:1
#000000
#17273E
Fail
h1 The reckoning arrive…1.40:13.0:1
#000000
#17273E
Fail
h1 Download Battle.net1.40:13.0:1
#000000
#17273E
Fail
h1 Download Battle.net1.40:13.0:1
#000000
#17273E
Fail
h2 Featured Games1.40:13.0:1
#000000
#17273E
Fail
h2 World of Warcraft: M…1.40:13.0:1
#000000
#17273E
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.

B
Lighthouse Accessibility Audits
Score 80/100 — 4 failing, 24 passed
REVIEW
80

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

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ul ul
main.main-content > div#promotions-carousel > blz-carousel-beta.carousel > blz-tab-controls main.main-content > div#promotions-carousel > blz-carousel-beta.carousel > blz-tab-controls

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#toggler-container > blz-footer-link.locale-toggle div#toggler-container > blz-footer-link.locale-toggle

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

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.wrapper > div.image-container > picture > img div.wrapper > div.image-container > picture > img
div.wrapper > div.image-container > picture > img div.wrapper > div.image-container > picture > img
div.wrapper > div.image-container > picture > img div.wrapper > div.image-container > picture > img
div.wrapper > div.image-container > picture > img div.wrapper > div.image-container > picture > img
div.wrapper > div.image-container > picture > img div.wrapper > div.image-container > picture > img
div.wrapper > div.image-container > picture > img div.wrapper > div.image-container > picture > img
div.wrapper > div.image-container > picture > img div.wrapper > div.image-container > picture > img
div.wrapper > div.image-container > picture > img div.wrapper > div.image-container > picture > img
div.wrapper > div.image-container > picture > img div.wrapper > div.image-container > picture > img
div.wrapper > div.image-container > picture > img div.wrapper > div.image-container > picture > img
div.wrapper > div.image-container > picture > img div.wrapper > div.image-container > picture > img
div.wrapper > div.image-container > picture > img div.wrapper > div.image-container > picture > img
div.wrapper > div.image-container > picture > img div.wrapper > div.image-container > picture > img
div.wrapper > div.image-container > picture > img div.wrapper > div.image-container > picture > img
div.wrapper > div.image-container > picture > img div.wrapper > div.image-container > picture > img
div.wrapper > div.image-container > picture > img div.wrapper > div.image-container > picture > img
div.wrapper > div.image-container > picture > img div.wrapper > div.image-container > picture > img
div.wrapper > div.image-container > picture > img div.wrapper > div.image-container > picture > img
div.wrapper > div.image-container > picture > img div.wrapper > div.image-container > picture > img
div.wrapper > div.image-container > picture > img div.wrapper > div.image-container > picture > img
div.wrapper > div.image-container > picture > img div.wrapper > div.image-container > picture > img
div.wrapper > div.image-container > picture > img div.wrapper > div.image-container > picture > img
div.wrapper > div.image-container > picture > img div.wrapper > div.image-container > picture > img
div.wrapper > div.image-container > picture > img div.wrapper > div.image-container > picture > img
div.wrapper > div.image-container > picture > img div.wrapper > div.image-container > picture > img
div.wrapper > div.image-container > picture > img div.wrapper > div.image-container > picture > img
div.wrapper > div.image-container > picture > img div.wrapper > div.image-container > picture > img
div.wrapper > div.image-container > picture > img div.wrapper > div.image-container > picture > img

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

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
●Buttons have an accessible name
●Form elements have associated labels
●`button`, `link`, and `menuitem` elements have accessible names
●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
●Links have a discernible name
●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.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○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
○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.
A
Heading Hierarchy
90 headings
PASS
90 headings
Warning::
Multiple H1 headings (18 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 Wield forbidden magic as the Warlock
  • H1 The reckoning arrives April 28 duplicate H1
  • H1 Reign of Talon: Season 2 now live duplicate H1
  • H1 Support Habitat for Humanity duplicate H1
  • H1 The Taking is live duplicate H1
  • H1 CATACLYSM CALLS now live! duplicate H1
  • H1 Wield forbidden magic as the Warlock duplicate H1
  • H1 The reckoning arrives April 28 duplicate H1
  • H1 Wield forbidden magic as the Warlock duplicate H1
  • H1 The reckoning arrives April 28 duplicate H1
  • H1 Reign of Talon: Season 2 now live duplicate H1
  • H1 Support Habitat for Humanity duplicate H1
  • H1 The Taking is live duplicate H1
  • H1 CATACLYSM CALLS now live! duplicate H1
  • H1 Wield forbidden magic as the Warlock duplicate H1
  • H1 The reckoning arrives April 28 duplicate H1
  • H2 Featured Games
  • H2 World of Warcraft: Midnight
  • H2 World of Warcraft: Mists of Pandaria Classic
  • H2 Diablo IV: Lord of Hatred
  • H2 Overwatch
  • H2 Hearthstone
  • H2 Diablo Immortal
  • H2 Diablo II: Resurrected
  • H2 Diablo III
  • H2 Warcraft III: Reforged
  • H2 Warcraft II: Remastered
  • H2 World of Warcraft: Midnight
  • H2 Diablo IV: Lord of Hatred
  • H2 World of Warcraft: Mists of Pandaria Classic
  • H2 Overwatch
  • H2 Hearthstone
  • H2 Diablo II: Resurrected
  • H2 Diablo Immortal
  • H2 Diablo III
  • H2 Warcraft III: Reforged
  • H2 Warcraft II: Remastered
  • H2 World of Warcraft: Midnight
  • H2 Diablo IV: Lord of Hatred
  • H2 Diablo II: Resurrected
  • H2 World of Warcraft: Mists of Pandaria Classic
  • H2 Warcraft I: Remastered
  • H2 Warcraft II: Remastered
  • H2 Warcraft III: Reforged
  • H2 Diablo IV
  • H2 World of Warcraft
  • H2 Overwatch
  • H2 Hearthstone
  • H2 Diablo Immortal
  • H2 World of Warcraft: Midnight
  • H2 Diablo II: Resurrected
  • H2 Diablo IV: Lord of Hatred
  • H2 World of Warcraft: Mists of Pandaria Classic
  • H2 Warcraft I: Remastered
  • H2 Warcraft III: Reforged
  • H2 Warcraft II: Remastered
  • H2 Diablo IV
  • H2 World of Warcraft
  • H2 Overwatch
  • H2 Hearthstone
  • H2 Diablo IV: Vessel of Hatred
  • H2 Diablo IV
  • H2 Overwatch
  • H2 Diablo II: Resurrected
  • H2 Diablo IV: Vessel of Hatred
  • H2 Diablo IV
  • H2 Overwatch
  • H2 Diablo II: Resurrected
  • H2 Hearthstone
  • H2 Diablo Immortal
  • H2 Warcraft Rumble
  • H2 Hearthstone
  • H2 Diablo Immortal
  • H2 Warcraft Rumble
  • H1 Download Battle.net duplicate H1
  • H1 Download Battle.net duplicate H1
  • H2 Privacy Preference Center
  • H3 Your Privacy
  • H3 Required Cookies
  • H3 Performance Cookies
  • H3 Functional Cookies
  • H3 Blizzard & Affiliate Marketing Cookies
  • H3 Social Media Cookies
  • H4 Your Privacy
  • H4 Required Cookies
  • H4 Performance Cookies
  • H4 Functional Cookies
  • H4 Blizzard & Affiliate Marketing Cookies
  • H4 Social Media 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

A+
Alt Text Quality
All 2 images OK
PASS
All 2 images OK
Info::
2 image(s) with good alt text
2 images 2 good alt text
All images have appropriate alt text.
A+
Form Accessibility
All 9 controls labeled
PASS
All 9 controls labeled
Info::
9 control(s) properly labeled
9 controls
9 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#ot-group-id-2checkboxPerformance Cookiesfor/id
#ot-group-id-3checkboxFunctional Cookiesfor/id
#ot-group-id-4checkboxBlizzard & Affiliate Marketing Cookiesfor/id
#ot-group-id-8checkboxSocial Media Cookiesfor/id
#vendor-search-handlertextCookie list searcharia-label
#select-all-hosts-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-leg-handlercheckboxcheckbox labelfor/id
#chkbox-idcheckboxcheckbox labelfor/id
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback