Skip to content
https://rockpapershotgun.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
69
GRADE
D
FIX
3
REVIEW
5
PASS
5
INFO
0
Checks
13
5 PASS 5 REVIEW 3 FIX
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
10 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 10 <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
Heading Hierarchy
No headings
REVIEW
No headings
Warning::
No headings found
Headings (H1-H6) create the document outline for screen reader navigation.

No headings found

Headings create the document outline for screen reader navigation.

Headings (H1-H6) create the document outline for screen reader navigation.

Why this matters

A page with zero headings is unnavigable by assistive tech and reads as one undifferentiated wall of text.

Learn more ▾

Screen reader users navigate by jumping between H1-H6 elements. A page with no headings has no skip targets — users have to read every word linearly. Adding a heading hierarchy (one H1, then H2 sections, optional H3 subsections) makes the page skimmable for both AT and human readers.

Source: WCAG 1.3.1 / W3C WAI

C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 Page not found ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗
B
Favicon & Branding
6 icon(s) detected
REVIEW
6 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
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.

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

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

8 pass 12 fail WCAG AA 8 pass AA only
title Rock Paper Shotgun
4.22:1
#000000
on
#6E7071
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
a Hollow Knight Silksong walkthrough
3.50:1
#000000
on
#636363
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Tomawrow never dies
4.19:1
#000000
on
#6F6F72
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Latest
3.34:1
#000000
on
#5E6067
needs 4.5:1 (normal text)
16px · above the fold
a News
1.13:1
#000000
on
#101318
needs 4.5:1 (normal text)
16px · above the fold
a Reviews
2.65:1
#000000
on
#594F4E
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Hardware
1.09:1
#000000
on
#0B0F14
needs 4.5:1 (normal text)
16px · above the fold
a Features
1.13:1
#000000
on
#0D1419
needs 4.5:1 (normal text)
16px · mid-page
a Videos
1.16:1
#000000
on
#12171B
needs 4.5:1 (normal text)
16px · mid-page
a Guides
1.26:1
#000000
on
#1C1E20
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient
a Bestest Bests
2.56:1
#000000
on
#4E4F51
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient
a Deals
1.67:1
#000000
on
#353333
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient

7 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
title Rock Paper Shotgun4.22:14.5:1
#000000
#6E7071
Fail
a Skip to main content4.94:14.5:1
#000000
#797B7C
Pass
a Mouse: PI For Hire w…5.24:14.5:1
#000000
#7F7F7F
Pass
a Crimson Desert: What…5.24:14.5:1
#000000
#7F7F7F
Pass
a Best Minecraft seeds…5.24:14.5:1
#000000
#7F7F7F
Pass
a Hollow Knight Silkso…3.50:14.5:1
#000000
#636363
Fail
a Elden Ring boss loca…5.24:14.5:1
#000000
#7F7F7F
Pass
a Past Wordle answers5.03:14.5:1
#000000
#7C7C7C
Pass
a Tomawrow never dies4.19:14.5:1
#000000
#6F6F72
Fail
a Latest3.34:14.5:1
#000000
#5E6067
Fail
a News1.13:14.5:1
#000000
#101318
Fail
a Reviews2.65:14.5:1
#000000
#594F4E
Fail
a Hardware1.09:14.5:1
#000000
#0B0F14
Fail
a Features1.13:14.5:1
#000000
#0D1419
Fail
a Videos1.16:14.5:1
#000000
#12171B
Fail
a Guides1.26:14.5:1
#000000
#1C1E20
Fail
a Bestest Bests2.56:14.5:1
#000000
#4E4F51
Fail
a Free games4.96:14.5:1
#000000
#7B7B7B
Pass
a Discord5.17:14.5:1
#000000
#7E7E7E
Pass
a Deals1.67:14.5:1
#000000
#353333
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
16 landmarks
PASS
16 landmarks
Info::
<main> landmark present
Info::
10 <nav> landmark(s) found
Warning::
10 of 10 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
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

A
Alt Text Quality
All 67 images OK
PASS
All 67 images OK
Info::
14 image(s) with alt text over 125 characters
Info::
53 image(s) with good alt text
67 images 53 good alt text
IssueCount
too long14 image(s)
A+
Form Accessibility
All 4 controls labeled
PASS
All 4 controls labeled
Info::
4 control(s) properly labeled
4 controls
4 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
qsearchWhat are you looking for?aria-label
themeradioAutonone
themeradioLightnone
themeradioDarknone
A+
Lighthouse Accessibility Audits
Score 100/100 — 1 failing, 29 passed
PASS
100

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.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
9 div.wrapper > div.metadata > div.comments > a.comments__link
44 div.wrapper > div.metadata > div.comments > a.comments__link
23 div.wrapper > div.metadata > div.comments > a.comments__link
23 div.wrapper > div.metadata > div.comments > a.comments__link
16 div.wrapper > div.metadata > div.comments > a.comments__link
6 div.wrapper > div.metadata > div.comments > a.comments__link
6 div.wrapper > div.metadata > div.comments > a.comments__link
2 div.wrapper > div.metadata > div.comments > a.comments__link
23 div.wrapper > div.metadata > div.comments > a.comments__link
23 div.wrapper > div.metadata > div.comments > a.comments__link
6 div.wrapper > div.metadata > div.comments > a.comments__link
9 div.wrapper > div.metadata > div.comments > a.comments__link
6 div.wrapper > div.metadata > div.comments > a.comments__link
44 div.wrapper > div.metadata > div.comments > a.comments__link
2 div.wrapper > div.metadata > div.comments > a.comments__link
23 div.wrapper > div.metadata > div.comments > a.comments__link
our Privacy Policy div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link
○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.
●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
●`<frame>` or `<iframe>` elements have a title
●`<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.
●Skip links are focusable.
●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 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
○Heading elements appear in a sequentially-descending order
○`<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