Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 2 REVIEW 7 FIX

Link & Button Quality

Action

8 issue(s) across 27 links and 14 buttons

FIX

8 issue(s) across 27 links and 14 buttons

5 link(s) with no accessible text

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

Got: https://www.facebook.com/Wizards-of-the-Coast-540208589333239/; https://twitter.com/wizards; https://www.linkedin.com/company/wizards-of-the-coast; https://shop.hasbro.com; https://www.esrb.org/EPCConfirm/916/

4 link(s) open in new tab without warning

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

Got: https://www.exodusgame.com/en-US/; https://magic.wizards.com/en; https://magic.wizards.com/en/mtgarena-welcome; https://magic.wizards.com/en/mtgarena

3 button(s) with no accessible text

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

Got: button.css-2ryGO (#318 on page); button.css-2ryGO (#323 on page); button.css-2ryGO (#328 on page)

18 link(s) with descriptive text

27 links

5 empty

0 generic text

4 new tab

3 empty buttons

Element	Text	Issue	Suggested Fix
https://www.exodusgame.com/en-US/	Visit EXODUSGame.com	new tab	Add '(opens in new tab)' to text
https://magic.wizards.com/en	Visit Site	new tab	Add '(opens in new tab)' to text
https://magic.wizards.com/en/mtgarena-we…	I'm Brand New	new tab	Add '(opens in new tab)' to text
https://magic.wizards.com/en/mtgarena	I Play Magic	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/Wizards-of-the-…	(empty)	empty	Add link text or aria-label
https://twitter.com/wizards	(empty)	empty	Add link text or aria-label
https://www.linkedin.com/company/wizards…	(empty)	empty	Add link text or aria-label
https://shop.hasbro.com	(empty)	empty	Add link text or aria-label
https://www.esrb.org/EPCConfirm/916/	(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
<button>	(empty)	empty	Add button text or aria-label

29 links and buttons have descriptive text

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

https://www.facebook.com/Wizards-of-the-Coast-540208589333239/; https://twitter.com/wizards; https://www.linkedin.com/company/wizards-of-the-coast; https://shop.hasbro.com; https://www.esrb.org/EPCConfirm/916/

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

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

https://www.exodusgame.com/en-US/; https://magic.wizards.com/en; https://magic.wizards.com/en/mtgarena-welcome; https://magic.wizards.com/en/mtgarena

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.css-2ryGO (#318 on page); button.css-2ryGO (#323 on page); button.css-2ryGO (#328 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

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

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-gi4y84

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.

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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 Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://wizards.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://wizards.com/manifest.json

Manifest contains invalid JSON.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

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

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

1 navigation landmark(s) detected

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 1 <nav> element(s)

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.

Heading Hierarchy

2 headings

REVIEW

2 headings

No H1 heading found

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

H2 Our Company
H2 News from Wizards and beyond

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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 17 fail WCAG AA

REVIEW

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

3 pass 17 fail WCAG AA 2 pass AA only

h2 Our Company

2.11:1

#000000

#1B4856

needs 3.0:1 (large text)

24px · above the fold

h2 News from Wizards and beyond

1.75:1

#000000

#113C42

needs 3.0:1 (large text)

24px · mid-page

title Wizards of the Coast

1.01:1

#000000

#000104

needs 4.5:1 (normal text)

16px · top of page (header area)

div Fetching mountains...

1.01:1

#000000

#000103

needs 4.5:1 (normal text)

16px · top of page (header area)

b Introducing EXODUS: A new AAA science fi…

1.10:1

#000000

#021121

needs 3.0:1 (large text)

16px · top of page (header area)

a Visit EXODUSGame.com

1.09:1

#000000

#030F1F

needs 4.5:1 (normal text)

16px · top of page (header area)

strong Dare to enter the ever-changing plane of…

1.08:1

#000000

#030E1A

needs 3.0:1 (large text)

16px · above the fold

a Visit Site

1.13:1

#000000

#011426

needs 4.5:1 (normal text)

16px · above the fold

strong Crush your competition and command the b…

1.46:1

#000000

#0D2B48

needs 3.0:1 (large text)

16px · above the fold

a I'm Brand New

1.23:1

#000000

#061D35

needs 4.5:1 (normal text)

16px · above the fold

a I Play Magic

1.15:1

#000000

#061722

needs 4.5:1 (normal text)

16px · above the fold

span Our Games

1.82:1

#000000

#313B3A

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

p Wizards is a family of studios, we speci…

2.24:1

#000000

#244C55

needs 4.5:1 (normal text)

16px · above the fold

p Craft Our Next Game -

2.35:1

#000000

#314E54

needs 4.5:1 (normal text)

16px · above the fold

a Find a Job

2.32:1

#000000

#2C4E52

needs 4.5:1 (normal text)

16px · mid-page · over background image/gradient

span Latest

2.23:1

#000000

#404846

needs 4.5:1 (normal text)

16px · mid-page · over background image/gradient

span Magic: The Gathering

3.90:1

#000000

#925E40

needs 4.5:1 (normal text)

16px · mid-page

3 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Our Company	2.11:1	3.0:1	#000000	#1B4856	Fail
h2 News from Wizards an…	1.75:1	3.0:1	#000000	#113C42	Fail
title Wizards of the Coast	1.01:1	4.5:1	#000000	#000104	Fail
div Fetching mountains..…	1.01:1	4.5:1	#000000	#000103	Fail
b Introducing EXODUS: …	1.10:1	3.0:1	#000000	#021121	Fail
a Visit EXODUSGame.com	1.09:1	4.5:1	#000000	#030F1F	Fail
strong Dare to enter the ev…	1.08:1	3.0:1	#000000	#030E1A	Fail
a Visit Site	1.13:1	4.5:1	#000000	#011426	Fail
strong Crush your competiti…	1.46:1	3.0:1	#000000	#0D2B48	Fail
a I'm Brand New	1.23:1	4.5:1	#000000	#061D35	Fail
a I Play Magic	1.15:1	4.5:1	#000000	#061722	Fail
span Our Games	1.82:1	4.5:1	#000000	#313B3A	Fail
p Wizards is a family …	2.24:1	4.5:1	#000000	#244C55	Fail
p Craft Our Next Game …	2.35:1	4.5:1	#000000	#314E54	Fail
em Join Us	5.56:1	4.5:1	#000000	#8B836B	Pass
a Find a Job	2.32:1	4.5:1	#000000	#2C4E52	Fail
span Latest	2.23:1	4.5:1	#000000	#404846	Fail
span Magic: The Gathering	3.90:1	4.5:1	#000000	#925E40	Fail
span MTG Arena	5.81:1	4.5:1	#000000	#AC7D53	Pass
span Dungeons & Dragons	7.14:1	4.5:1	#000000	#AB9371	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.

Landmark Structure

10 landmarks

PASS

10 landmarks

<main> landmark present

1 <nav> landmark(s) found

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

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 9 images OK

PASS

All 9 images OK

8 decorative image(s) correctly marked

1 image(s) with good alt text

9 images 1 good alt text 8 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
language-selector	select	Choose your language	aria-label

Lighthouse Accessibility Audits

Score 91/100 — 2 failing, 26 passed

PASS

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

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.css-3um1i > div.css-3Wuiu > a > button.css-2ryGO `div.css-3um1i > div.css-3Wuiu > a > button.css-2ryGO`
div.css-3um1i > div.css-3Wuiu > a > button.css-2ryGO `div.css-3um1i > div.css-3Wuiu > a > button.css-2ryGO`
div.css-3um1i > div.css-3Wuiu > a > button.css-2ryGO `div.css-3um1i > div.css-3Wuiu > a > button.css-2ryGO`

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.css-2n4XB > div.css-3um1i > div.css-3Wuiu > a `div.css-2n4XB > div.css-3um1i > div.css-3Wuiu > a`
div.css-2n4XB > div.css-3um1i > div.css-3Wuiu > a `div.css-2n4XB > div.css-3um1i > div.css-3Wuiu > a`
div.css-2n4XB > div.css-3um1i > div.css-3Wuiu > a `div.css-2n4XB > div.css-3um1i > div.css-3Wuiu > a`
div.css-2CNF5 > div.css-3ER1c > div.css-31vhM > a.css-2LsKE `div.css-2CNF5 > div.css-3ER1c > div.css-31vhM > a.css-2LsKE`
div.css-2CNF5 > div.css-3ER1c > div.css-31vhM > a.css-2LsKE `div.css-2CNF5 > div.css-3ER1c > div.css-31vhM > a.css-2LsKE`

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

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

●Select elements have associated label elements.

●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

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●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

●All heading elements contain content.

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[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

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

○Skip links are focusable.

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

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

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