Skip to content
https://razer.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
52
GRADE
F
FIX
7
REVIEW
1
PASS
5
INFO
0
Checks
13
5 PASS 1 REVIEW 7 FIX
F
404 Error Page
Action
HTTP 403, custom page
FIX
HTTP 403, custom page
Warning::
Unexpected status code: HTTP 403
Expected HTTP 404 but received 403. This may confuse search engine crawlers.
Got: HTTP 403
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 403 ✗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
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
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h1 Razer
1.02:1
#000000
on
#030303
needs 3.0:1 (large text)
32px · bottom of viewport
h2 GET US$10 OFF YOUR NEXT ORDER
1.02:1
#000000
on
#030303
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Sign up for our Razer newsletter to unlo…
1.02:1
#000000
on
#030303
needs 3.0:1 (large text)
19px · bottom of viewport
title Razer United States | For Gamers. By Gam…
1.32:1
#000000
on
#222222
needs 4.5:1 (normal text)
16px · top of page (header area)
button Skip to Header
1.32:1
#000000
on
#222222
needs 4.5:1 (normal text)
16px · top of page (header area)
button Skip to Main Content
1.32:1
#000000
on
#222222
needs 4.5:1 (normal text)
16px · top of page (header area)
button Skip to Footer
1.32:1
#000000
on
#222222
needs 4.5:1 (normal text)
16px · top of page (header area)
div You are currently on the
1.32:1
#000000
on
#222222
needs 4.5:1 (normal text)
16px · above the fold
span United States
1.32:1
#000000
on
#222222
needs 4.5:1 (normal text)
16px · above the fold
div site.
1.32:1
#000000
on
#222222
needs 4.5:1 (normal text)
16px · above the fold
div Select a location to view location-speci…
1.09:1
#000000
on
#0E0E0E
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
button Switch to
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
span Spain (España)
2.82:1
#000000
on
#555555
needs 4.5:1 (normal text)
16px · above the fold
a Select another location
2.82:1
#000000
on
#555555
needs 4.5:1 (normal text)
16px · above the fold
label Search razer.com
1.35:1
#000000
on
#242424
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
div Begin typing to search, navigate below f…
1.02:1
#000000
on
#030303
needs 4.5:1 (normal text)
16px · above the fold
span results found
1.02:1
#000000
on
#030303
needs 4.5:1 (normal text)
16px · mid-page
div TOP SUGGESTIONS
1.02:1
#000000
on
#030303
needs 4.5:1 (normal text)
16px · mid-page
div Sorry! No matches were found.
1.02:1
#000000
on
#040404
needs 4.5:1 (normal text)
16px · mid-page
div Don't give up! Check the spelling or try…
1.04:1
#000000
on
#060606
needs 4.5:1 (normal text)
16px · mid-page

2 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)
ElementRatioRequiredFGBGResult
h1 Razer1.02:13.0:1
#000000
#030303
Fail
h2 GET US$10 OFF YOUR N…1.02:13.0:1
#000000
#030303
Fail
h3 Sign up for our Raze…1.02:13.0:1
#000000
#030303
Fail
title Razer United States …1.32:14.5:1
#000000
#222222
Fail
button Skip to Header1.32:14.5:1
#000000
#222222
Fail
button Skip to Main Content1.32:14.5:1
#000000
#222222
Fail
button Skip to Footer1.32:14.5:1
#000000
#222222
Fail
div You are currently on…1.32:14.5:1
#000000
#222222
Fail
span United States1.32:14.5:1
#000000
#222222
Fail
div site.1.32:14.5:1
#000000
#222222
Fail
div Select a location to…1.09:14.5:1
#000000
#0E0E0E
Fail
button Switch to1.00:14.5:1
#000000
#000000
Fail
span Spain (España)2.82:14.5:1
#000000
#555555
Fail
a Select another locat…2.82:14.5:1
#000000
#555555
Fail
label Search razer.com1.35:14.5:1
#000000
#242424
Fail
div Begin typing to sear…1.02:14.5:1
#000000
#030303
Fail
span results found1.02:14.5:1
#000000
#030303
Fail
div TOP SUGGESTIONS1.02:14.5:1
#000000
#030303
Fail
div Sorry! No matches we…1.02:14.5:1
#000000
#040404
Fail
div Don't give up! Check…1.04:14.5:1
#000000
#060606
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
13 landmarks
PASS
13 landmarks
Info::
<main> landmark present
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 "global" MAIN CONTENTINFO footer

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+
Heading Hierarchy
9 headings
PASS
9 headings
Info::
Single H1 present
  • H1 Razer
  • H2 RAZER ATLAS PRO
  • H3 SKATING ON THIN GLASS
  • H2 RAZER VIPER V4 PRO
  • H3 FOR THE PRO
  • H2 RAZER HAMMERHEAD V3 HYPERSPEED
  • H3 ULTRA-LOW LATENCY. ULTIMATE IMMERSION.
  • H2 GET US$10 OFF YOUR NEXT ORDER
  • H3 Sign up for our Razer newsletter to unlock a special discount code for Razer gear and be the first to know about our latest specials and product releases.
A+
Alt Text Quality
All 13 images OK
PASS
All 13 images OK
Info::
10 decorative image(s) correctly marked
Info::
3 image(s) with good alt text
13 images 3 good alt text 10 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 3 controls have issues
PASS
1 of 3 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input>
Info::
2 control(s) properly labeled
3 controls
2 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#main-nav-search-inputtextSearch razer.comaria-label
#newsletter_inputemailEmail Addressfor/id
inputinput(none)none

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

<input>

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

A+
Lighthouse Accessibility Audits
Score 96/100 — 1 failing, 32 passed
PASS
96

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

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.user-logged > input body.user-logged > input

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
●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.
●`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 are distinguishable without relying on color.
●Links have a discernible name
●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.
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●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
○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.
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○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