Skip to content
https://inverse.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
62
GRADE
D
FIX
5
REVIEW
4
PASS
4
INFO
0
Checks
13
4 PASS 4 REVIEW 5 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
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::
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
3 landmarks
REVIEW
3 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

B
Form Accessibility
2 of 14 controls have issues
REVIEW
2 of 14 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="navCheckbox">; <input type="checkbox" id="searchCheckbox">
Info::
12 control(s) properly labeled
14 controls
12 labeled
0 placeholder only
2 unlabeled
ControlTypeLabelMethod
#radio-0-190355629radioMoviesfor/id
#radio-1-190355629radioTVfor/id
#radio-2-190355629radioGamesfor/id
#radio-3-190355629radioGearfor/id
emailemailEmail addressaria-label
qsearchSearch Inversearia-label
#subv_resetresetHide subverticalsaria-label
#subv_entertainmentradioShow subverticalsaria-label
#subv_gamingradioShow subverticalsaria-label
#subv_gearradioShow subverticalsaria-label
#subv_innovationradioShow subverticalsaria-label
#subv_mind-bodyradioShow subverticalsaria-label
#searchCheckboxcheckbox(none)none
#navCheckboxcheckbox(none)none

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

<input type="checkbox" id="navCheckbox">; <input type="checkbox" id="searchCheckbox">

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

C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 8 fail WCAG AA
REVIEW

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

12 pass 8 fail WCAG AA
title Inverse
3.06:1
#000000
on
#555B63
needs 4.5:1 (normal text)
16px · top of page (header area)
span We value your privacy
3.06:1
#000000
on
#555B63
needs 4.5:1 (normal text)
16px · top of page (header area)
a View Privacy Policy
3.06:1
#000000
on
#555B63
needs 4.5:1 (normal text)
16px · top of page (header area)
span We and our 770
3.06:1
#000000
on
#555B63
needs 4.5:1 (normal text)
16px · top of page (header area)
a partners
3.06:1
#000000
on
#555B63
needs 4.5:1 (normal text)
16px · above the fold
span store and access information on your dev…
3.06:1
#000000
on
#555B63
needs 4.5:1 (normal text)
16px · above the fold
div Please note that this website/app uses o…
3.06:1
#000000
on
#555B63
needs 4.5:1 (normal text)
16px · above the fold
span MORE OPTIONS
3.06:1
#000000
on
#555B63
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Inverse21.00:13.0:1
#000000
#FFFFFF
Pass
h2 The State of Hollywo…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Cool Stuff21.00:13.0:1
#000000
#FFFFFF
Pass
title Inverse3.06:14.5:1
#000000
#555B63
Fail
span We value your privac…3.06:14.5:1
#000000
#555B63
Fail
a View Privacy Policy3.06:14.5:1
#000000
#555B63
Fail
span We and our 7703.06:14.5:1
#000000
#555B63
Fail
a partners3.06:14.5:1
#000000
#555B63
Fail
span store and access inf…3.06:14.5:1
#000000
#555B63
Fail
div Please note that thi…3.06:14.5:1
#000000
#555B63
Fail
span MORE OPTIONS3.06:14.5:1
#000000
#555B63
Fail
span AGREE21.00:14.5:1
#000000
#FFFFFF
Pass
span Menu21.00:14.5:1
#000000
#FFFFFF
Pass
span Rewind21.00:14.5:1
#000000
#FFFFFF
Pass
span 'Silent Hill' Was Th…21.00:14.5:1
#000000
#FFFFFF
Pass
p For better and worse…21.00:14.5:1
#000000
#FFFFFF
Pass
div By Chrishaun Baker21.00:14.5:1
#000000
#FFFFFF
Pass
span Bat-Origins21.00:14.5:1
#000000
#FFFFFF
Pass
span 'The Batman 2' Might…21.00:14.5:1
#000000
#FFFFFF
Pass
span Cheatsheet21.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+
Heading Hierarchy
3 headings
PASS
3 headings
Info::
Single H1 present
  • H1 Inverse
  • H2 The State of Hollywood Tech
  • H2 Cool Stuff
A+
Alt Text Quality
All 16 images OK
PASS
All 16 images OK
Info::
2 decorative image(s) correctly marked
Info::
14 image(s) with good alt text
16 images 14 good alt text 2 decorative
All images have appropriate alt text.
A
404 Error Page
HTTP 404, custom page
PASS
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
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 Not Found ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
A+
Lighthouse Accessibility Audits
Score 96/100 — 1 failing, 26 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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
'For All Mankind' Just Revealed A Secret Character And A Killer Cameo div.wml > div.DGg > div.Mkc > p.hvk
BY RYAN BRITT div.wml > div.DGg > div.Mkc > div.lFD
The legacy of the previous seasons isn't going away anytime soon. div.wml > div.DGg > div.Mkc > p.EJZ

These are opportunities to improve the legibility of your content.

○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
●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
●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
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●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
○`<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
○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
○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