Skip to content
https://polygon.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
58
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 FIX
D
Form Accessibility
Action
4 of 9 controls have issues
FIX
4 of 9 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="checkbox" id="expandMenuListDefault">; <input type="checkbox" id="showMoreToggle">
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="q">; <input type="text" name="q" id="js-search-input">
Info::
5 control(s) properly labeled
9 controls
5 labeled
2 placeholder only
2 unlabeled
ControlTypeLabelMethod
#side_menucheckboxMenufor/id
#navItems-GuidescheckboxGuides Submenufor/id
#navItems-GamescheckboxGames Submenufor/id
#navItems-EntertainmentcheckboxEntertainment Submenufor/id
#search-menucheckboxClosefor/id
qtext(Search Polygon)placeholder only
#js-search-inputtext(Search Polygon.com)placeholder only
#expandMenuListDefaultcheckbox(none)none
#showMoreTogglecheckbox(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<input type="checkbox" id="expandMenuListDefault">; <input type="checkbox" id="showMoreToggle">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

Placeholder text disappears on focus and is not a reliable label.

<input type="text" name="q">; <input type="text" name="q" id="js-search-input">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

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
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::
3 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 3 <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
Landmark Structure
7 landmarks
REVIEW
7 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Warning::
3 of 3 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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 ASIDE CONTENTINFO footer

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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
Heading Hierarchy
Action
56 headings, 1 skip(s)
REVIEW
56 headings, 1 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H3 Diablo 4: Lord of Hatred's much improved story gets in the way of its sweet, sweet grind
  • H3 Xbox Game Pass gets a price drop under new CEO, but there's a catch
  • H3 Double Fine's new competitive multiplayer game Kiln was designed to be the Cruis'n USA of pottery making
  • H2 Up next
  • H3 Please just put the entire Call of Duty series on Game Pass
  • H3 Sydney Sweeney's Gundam needs to be political to actually be faithful to the anime
  • H3 GTA 5 fans are starting riots in the silliest way possible
  • H2 Popular News
  • H3 Xbox Game Pass price drop shows that subscribers have limits
  • H3 Silo's first season 3 trailer unveils more of the pre-apocalyptic past
  • H3 Magic finally has a ninja Commander who doesn't stink thanks to Universes Beyond
  • H3 Incineroar is still the undisputed king in Pokémon Champions
  • H3 One Piece and Dragon Ball anime company Toei launches new games division
  • H3 Nintendo's single-player Splatoon spinoff splashes down on Switch 2 this summer
  • H3 Kick continues 2025's best soccer game trend
  • H3 Mass Effect fans waited 16 years for this Miranda statue
  • H3 This new horror game is basically The Terror with adorable penguins
  • H2 They said it
  • H3 The best line in Hades never gets old – here’s how Supergiant nailed it
  • H3 36 years later, The Secret of Monkey Island's combat is still unrivalled
  • H3 Leon S. Kennedy’s voice actor reveals his favorite Resident Evil one-liner
  • H2 Hack your way through Pragmata 🤖
  • H3 10 Pragmata beginner's tips to help you on your moon journey
  • H3 The best weapons and mods in Pragmata
  • H3 Mini Cabin figure locations in Pragmata
  • H3 All Solar Power Plant upgrade component locations in Pragmata
  • H3 Solar Power Plant 100% sector walkthrough in Pragmata
  • H3 How to beat the SectorGuard boss in Pragmata
  • H2 Reviews
  • H3 Dorohedoro season 2 is finally here and somehow wilder than ever
  • H3 You don’t need to be a Dropout fan to enjoy Izzy Roland's dark comedy about grief
  • H3 Tides of Tomorrow is the best anti-social social game you've ever played
  • H2 Latest
  • H5 Xbox Game Pass price drop shows that subscribers have limits skipped
  • H5 Silo's first season 3 trailer unveils more of the pre-apocalyptic past
  • H5 Magic finally has a ninja Commander who doesn't stink thanks to Universes Beyond
  • H5 Incineroar is still the undisputed king in Pokémon Champions
  • H5 One Piece and Dragon Ball anime company Toei launches new games division
  • H5 Nintendo's single-player Splatoon spinoff splashes down on Switch 2 this summer
  • H5 Kick continues 2025's best soccer game trend
  • H5 Mass Effect fans waited 16 years for this Miranda statue
  • H5 This new horror game is basically The Terror with adorable penguins
  • H5 Teenage Mutant Ninja Turtles Mutant Mayhem sequel director promises Shredder will be a 'spectacle'
  • H5 7 years later, Oscar Isaac is still mad about his worst Star Wars line
  • H5 Xbox Game Pass loses a much-loved Dragon Ball game next week
  • H5 Did Netflix drop the ball with JoJo: Steel Ball Run?
  • H5 Kit Connor's Elden Ring casting makes perfect sense if you've seen his underrated war movie
  • H5 Dragon Ball Xenoverse 3 should learn from Xenoverse 2’s biggest flaws
  • H5 The next X-Men crossover event could blur the line between Mutants and Avengers forever
  • H5 Elden Ring cast: Who's playing who in Alex Garland's live-action movie?
  • H5 Secrets of Strixhaven’s most underrated Commander deck is the only one still in stock
  • H5 ‘I don’t just want to make them a cameo’: How Dave the Diver’s dev has built a better Fortnite
  • H5 Cyberpunk’s Night City gets a massive new update set decades before 2077
  • H5 Game Changer returns next month and season 8 might be the most chaotic yet
  • H5 A bunch of great games are leaving Xbox Game Pass this month
  • H5 This Tomodachi Life tool will help you draw with pixel-perfect accuracy

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

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

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 Polygon.com Custom Styling Navigation Homepage Link Search Form
C
Favicon & Branding
Action
7 icon(s) detected
REVIEW
7 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::
Apple touch icon present
Info::
Multiple icon sizes detected
favicon.ico Missing
PNG Icons Present
Apple Touch Present
SVG Favicon Missing
Manifest Icons Missing
Multiple Sizes Present
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode Dark Mode Supported
color-scheme meta Not set Dark theme-color Not set CSS indicators Detected

Detection limited to meta tags and inline styles.

A+
Alt Text Quality
All 54 images OK
PASS
All 54 images OK
Info::
2 image(s) with alt text over 125 characters
Info::
52 image(s) with good alt text
54 images 52 good alt text
IssueCount
too long2 image(s)
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Up next21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Popular News21.00:13.0:1
#000000
#FFFFFF
Pass
h2 They said it21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Hack your way throug…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Reviews21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Latest21.00:13.0:1
#000000
#FFFFFF
Pass
title Polygon: Gaming and …20.82:14.5:1
#000000
#FEFEFE
Pass
span Menu21.00:14.5:1
#000000
#FFFFFF
Pass
span Sign in now21.00:14.5:1
#000000
#FFFFFF
Pass
div Guides21.00:14.5:1
#000000
#FFFFFF
Pass
div Gaming21.00:14.5:1
#000000
#FFFFFF
Pass
div Entertainment21.00:14.5:1
#000000
#FFFFFF
Pass
span Close21.00:14.5:1
#000000
#FFFFFF
Pass
span What To Play21.00:14.5:1
#000000
#FFFFFF
Pass
span What to Watch21.00:14.5:1
#000000
#FFFFFF
Pass
span Guides21.00:14.5:1
#000000
#FFFFFF
Pass
span Submenu21.00:14.5:1
#000000
#FFFFFF
Pass
span All Guides21.00:14.5:1
#000000
#FFFFFF
Pass
span All Maps21.00:14.5:1
#000000
#FFFFFF
Pass
span Pragmata21.00:14.5:1
#000000
#FFFFFF
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
Lighthouse Accessibility Audits
Score 91/100 — 3 failing, 22 passed
PASS
91

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.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Xbox Game Pass price drop shows that subscribers have limits div.sentinel-home-list > div.display-card > div.w-display-card-content > h5.display-card-title

These are opportunities to improve keyboard navigation in your application.

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.w-side-navigation-social > ul#menu-follow > li.social-elements > a.social-links div.w-side-navigation-social > ul#menu-follow > li.social-elements > a.social-links
div.w-side-navigation-social > ul#menu-follow > li.social-elements > a.social-links div.w-side-navigation-social > ul#menu-follow > li.social-elements > a.social-links
div.w-side-navigation-social > ul#menu-follow > li.social-elements > a.social-links div.w-side-navigation-social > ul#menu-follow > li.social-elements > a.social-links
div.w-side-navigation-social > ul#menu-follow > li.social-elements > a.social-links div.w-side-navigation-social > ul#menu-follow > li.social-elements > a.social-links
div.w-side-navigation-social > ul#menu-follow > li.social-elements > a.social-links div.w-side-navigation-social > ul#menu-follow > li.social-elements > a.social-links
div.w-display-card-content > div.w-display-card-details > div.w-display-card-extra > a.total-info-number div.w-display-card-content > div.w-display-card-details > div.w-display-card-extra > a.total-info-number
div.footer-content-el > ul.social-media > li.social-elements > a.text div.footer-content-el > ul.social-media > li.social-elements > a.text
div.footer-content-el > ul.social-media > li.social-elements > a.text div.footer-content-el > ul.social-media > li.social-elements > a.text
div.footer-content-el > ul.social-media > li.social-elements > a.text div.footer-content-el > ul.social-media > li.social-elements > a.text
div.footer-content-el > ul.social-media > li.social-elements > a.text div.footer-content-el > ul.social-media > li.social-elements > a.text
div.footer-content-el > ul.social-media > li.social-elements > a.text div.footer-content-el > ul.social-media > li.social-elements > a.text
div.footer-content-el > ul.social-media > li.social-elements > a.text div.footer-content-el > ul.social-media > li.social-elements > a.text

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

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
RYAN EPPS div.w-display-card-details > div.w-display-card-meta > div.w-author > a.meta_txt
ANIME div.display-card > div.w-display-card-content > div.w-display-card-category > a.dc-tag-label
Join Our Team div.footer-content-el > ul > li > a.text
About Us div.footer-content-el > ul > li > a.text
Press & Events div.footer-content-el > ul > li > a.text
Editorial Ethics and Guidelines div.footer-content-el > ul > li > a.text
Community Guidelines div.footer-content-el > ul > li > a.text
Media Coverage div.footer-content-el > ul > li > a.text
Contact Us div.footer-content-el > ul > li > a.text
Advertising div.footer-content-el > ul.align-right > li > a.text
Careers div.footer-content-el > ul.align-right > li > a.text
Terms div.footer-content-el > ul.align-right > li > a.text
Privacy div.footer-content-el > ul.align-right > li > a.text
Policies div.footer-content-el > ul.align-right > li > a.text

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
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.
ARIA attributes are used as specified for the element's role
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
Elements use only permitted ARIA attributes
Background and foreground colors have a sufficient contrast ratio
Document has a `<title>` element
`<frame>` or `<iframe>` elements have a title
`<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
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
`[aria-hidden="true"]` elements do not contain focusable descendents
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
Buttons have an accessible name
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
`<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.
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
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>`.
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