Skip to content
https://marvel.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
52
GRADE
F
FIX
6
REVIEW
5
PASS
2
INFO
0
Checks
13
2 PASS 5 REVIEW 6 FIX
D
Landmark Structure
Action
10 landmarks
FIX
10 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
6 <nav> landmark(s) found
Warning::
1 of 6 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No banner (header) 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 (missing!) NAV MAIN (missing!) CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

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::
6 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 6 <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.
C
Heading Hierarchy
Action
43 headings, 1 skip(s)
REVIEW
43 headings, 1 skip(s)
Warning::
Multiple H1 headings (5 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
3 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 (empty)
  • H1 (empty)
  • H1 (empty)
  • H1 This Week's New Comics duplicate H1
  • H1 It's Jeff/Aquaman Infinity Comic duplicate H1
  • H2 Available NowNew on Marvel Unlimited
  • H2 The Latest
  • H2 Watch Now
  • H2 On Sale 4/22New Comics This Week
  • H4 Marvel Unlimited skipped
  • H4 Send a Gift
  • H4 Follow Marvel
  • H2 Your Privacy Settings
  • H3 We and our partners process data to:
  • H2 Privacy Preference Center
  • H3 Manage Consent Preferences
  • H4 Essential Cookies
  • H4 Performance & Analytics Cookies
  • H4 Functionality Cookies
  • H4 Targeting & Advertising Cookies
  • H4 Store and/or access information on a device 813 partners can use this purpose
  • H4 Precise geolocation data, and identification through device scanning 373 partners can use this purpose
  • H5 Use precise geolocation data 291 partners can use this special feature
  • H5 Actively scan device characteristics for identification 159 partners can use this special feature
  • H4 Personalised advertising and content, advertising and content measurement, audience research and services development 966 partners can use this purpose
  • H5 Use limited data to select advertising 762 partners can use this purpose
  • H5 Create profiles for personalised advertising 619 partners can use this purpose
  • H5 Use profiles to select personalised advertising 621 partners can use this purpose
  • H5 Create profiles to personalise content 263 partners can use this purpose
  • H5 Use profiles to select personalised content 237 partners can use this purpose
  • H5 Measure advertising performance 883 partners can use this purpose
  • H5 Measure content performance 405 partners can use this purpose
  • H5 Understand audiences through statistics or combinations of data from different sources 560 partners can use this purpose
  • H5 Develop and improve services 661 partners can use this purpose
  • H5 Use limited data to select content 178 partners can use this purpose
  • H4 Special purposes & features 908 partners can use this purpose
  • H5 Ensure security, prevent and detect fraud, and fix errors 628 partners can use this special purpose
  • H5 Deliver and present advertising and content 621 partners can use this special purpose
  • H5 Match and combine data from other data sources 444 partners can use this feature
  • H5 Link different devices 372 partners can use this feature
  • H5 Identify devices based on information transmitted automatically 578 partners can use this feature
  • H5 Save and communicate privacy choices 478 partners can use this special purpose
  • H3 Cookie List

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

C
Form Accessibility
Action
9 of 41 controls have issues
REVIEW
9 of 41 controls have issues
Critical::
9 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select>; <select>; <select>; <select>; <select>; <select>; <select>; <select>; <select>
Info::
32 control(s) properly labeled
41 controls
32 labeled
0 placeholder only
9 unlabeled
ControlTypeLabelMethod
#caption-settings-foreground-vjs_video_3selectForegroundfor/id
#caption-settings-foreground-opacity-vjs_video_3selectOpacityfor/id
#caption-settings-background-vjs_video_3selectBackgroundfor/id
#caption-settings-background-opacity-vjs_video_3selectOpacityfor/id
#caption-settings-window-vjs_video_3selectWindowfor/id
#caption-settings-window-opacity-vjs_video_3selectOpacityfor/id
#caption-settings-fontSize-vjs_video_3selectFont Sizefor/id
#caption-settings-textEdgeStyle-vjs_video_3selectText Edge Stylefor/id
#caption-settings-fontFamily-vjs_video_3selectFont Familyfor/id
#ot-group-id-C0002checkboxPerformance & Analytics Cookiesfor/id
#ot-group-id-C0003checkboxFunctionality Cookiesfor/id
#ot-group-id-C0004checkboxTargeting & Advertising Cookiesfor/id
#ot-group-id-IAB2V2_1checkboxStore and/or access information on a devicefor/id
#ot-group-id-V2STACK1checkboxPrecise geolocation data, and identification through device scanningfor/id
#ot-sub-group-id-ISF2V2_1checkboxUse precise geolocation dataaria-label
#ot-sub-group-id-ISF2V2_2checkboxActively scan device characteristics for identificationaria-label
#ot-group-id-V2STACK42checkboxPersonalised advertising and content, advertising and content measurement, audience research and services developmentfor/id
#ot-sub-group-id-IAB2V2_2checkboxUse limited data to select advertisingaria-label
#ot-sub-group-id-IAB2V2_3checkboxCreate profiles for personalised advertisingaria-label
#ot-sub-group-id-IAB2V2_4checkboxUse profiles to select personalised advertisingaria-label
#ot-sub-group-id-IAB2V2_5checkboxCreate profiles to personalise contentaria-label
#ot-sub-group-id-IAB2V2_6checkboxUse profiles to select personalised contentaria-label
#ot-sub-group-id-IAB2V2_7checkboxMeasure advertising performancearia-label
#ot-sub-group-id-IAB2V2_8checkboxMeasure content performancearia-label
#ot-sub-group-id-IAB2V2_9checkboxUnderstand audiences through statistics or combinations of data from different sourcesaria-label
#ot-sub-group-id-IAB2V2_10checkboxDevelop and improve servicesaria-label
#ot-sub-group-id-IAB2V2_11checkboxUse limited data to select contentaria-label
#vendor-search-handlertextCookie list searcharia-label
#chkbox-idcheckboxcheckbox labelfor/id
#select-all-hosts-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-leg-handlercheckboxcheckbox labelfor/id
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none

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

<select>; <select>; <select>; <select>; <select>; <select>; <select>; <select>; <select>

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

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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Marvel.com | The Official Site for Marvel Movies, Characters, Comics, TV ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
B
Favicon & Branding
19 icon(s) detected
REVIEW
19 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
C
Lighthouse Accessibility Audits
Action
Score 74/100 — 7 failing, 21 passed
REVIEW
74

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.Slider > div.Slider__Root > div.Slider__Viewport > button.Slider__Next div.Slider > div.Slider__Root > div.Slider__Viewport > button.Slider__Next
div.Slider > div.Slider__Root > div.Slider__Viewport > button.Slider__Next div.Slider > div.Slider__Root > div.Slider__Viewport > button.Slider__Next

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
ul.Navigation__List > div.Navigation__Left > li.mobile > a.Navigation__Menu ul.Navigation__List > div.Navigation__Left > li.mobile > a.Navigation__Menu
ul.Navigation__List > div.Navigation__Right > li > a ul.Navigation__List > div.Navigation__Right > li > a
  div.Slider__Slide > div.Card > div.SliderMastheadCard > a.SliderMastheadCard__Click_Overlay
div.GeneralContainer__Wrapper > div.SliderMastheadCard__Info > div.SliderMastheadCard__Info_Wrapper > a.SliderMastheadCard__Hyperlink div.GeneralContainer__Wrapper > div.SliderMastheadCard__Info > div.SliderMastheadCard__Info_Wrapper > a.SliderMastheadCard__Hyperlink
  div.Slider__Slide > div.Card > div.SliderMastheadCard > a.SliderMastheadCard__Click_Overlay
div.GeneralContainer__Wrapper > div.SliderMastheadCard__Info > div.SliderMastheadCard__Info_Wrapper > a.SliderMastheadCard__Hyperlink div.GeneralContainer__Wrapper > div.SliderMastheadCard__Info > div.SliderMastheadCard__Info_Wrapper > a.SliderMastheadCard__Hyperlink
  div.Slider__Slide > div.Card > div.SliderMastheadCard > a.SliderMastheadCard__Click_Overlay
div.GeneralContainer__Wrapper > div.SliderMastheadCard__Info > div.SliderMastheadCard__Info_Wrapper > a.SliderMastheadCard__Hyperlink div.GeneralContainer__Wrapper > div.SliderMastheadCard__Info > div.SliderMastheadCard__Info_Wrapper > a.SliderMastheadCard__Hyperlink
  div.Slider__Slide > div.Card > div.SliderMastheadCard > a.SliderMastheadCard__Click_Overlay
  div.Slider__Slide > div.Card > div.SliderMastheadCard > a.SliderMastheadCard__Click_Overlay
div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image
div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image
div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image
div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image
div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image
div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image
div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image
div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image
div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image
div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image
div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image
div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image
div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image
div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image
div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image
div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image
div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image
div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image
div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image
div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image
div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image
div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image
div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image
div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image
div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image
div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image
div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image
div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image div.Slider__Slide > div.Card > div.ComicCard > a.ComicCard__Image
footer.MainFooter > div.MainFooter__Content > div.MainFooter__Links > a.MainFooter__Logo footer.MainFooter > div.MainFooter__Content > div.MainFooter__Links > a.MainFooter__Logo

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.

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
Movies div.Card > div.FeedCard > div.FeedCard__Meta > p.FeedCard__Meta__Category
TV Shows div.Card > div.FeedCard > div.FeedCard__Meta > p.FeedCard__Meta__Category
TV Shows div.Card > div.FeedCard > div.FeedCard__Meta > p.FeedCard__Meta__Category
Movies div.Card > div.FeedCard > div.FeedCard__Meta > p.FeedCard__Meta__Category
Comics div.Card > div.FeedCard > div.FeedCard__Meta > p.FeedCard__Meta__Category
Access Over 30,000+ Digital Comics a > span.MainFooter__Promotion_Link > div.MainFooter__Promotion_Info > p.MainFooter__Promotion_Description
Terms of Use footer.MainFooter > nav.MainFooter__Legal > span.MainFooter__Legal_Text > a
Privacy Policy footer.MainFooter > nav.MainFooter__Legal > span.MainFooter__Legal_Text > a
Interest-Based Ads footer.MainFooter > nav.MainFooter__Legal > span.MainFooter__Legal_Text > a
EU Privacy Rights footer.MainFooter > nav.MainFooter__Legal > span.MainFooter__Legal_Text > a
Cookie Policy footer.MainFooter > nav.MainFooter__Legal > span.MainFooter__Legal_Text > a
License Agreement footer.MainFooter > nav.MainFooter__Legal > span.MainFooter__Legal_Text > a
Manage Privacy Preferences footer.MainFooter > nav.MainFooter__Legal > span.MainFooter__Legal_Text > a
©2026 MARVEL div#themeProvider > footer.MainFooter > nav.MainFooter__Legal > span.MainFooter__Legal_CopyWrite

These are opportunities to improve the legibility of your content.

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
MARVEL UNLIMITED a > span.MainFooter__Promotion_Link > div.MainFooter__Promotion_Info > h4.MainFooter__Promotion_Title

These are opportunities to improve keyboard navigation in your application.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#themeProvider > nav.Marvel__Navigation > div.Navigation__Top__Wrapper > ul.Navigation__List div#themeProvider > nav.Marvel__Navigation > div.Navigation__Top__Wrapper > ul.Navigation__List

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.Navigation__Top__Wrapper > ul.Navigation__List > div.Navigation__Left > li.mobile div.Navigation__Top__Wrapper > ul.Navigation__List > div.Navigation__Left > li.mobile
div.Navigation__Top__Wrapper > ul.Navigation__List > div.Navigation__Right > li div.Navigation__Top__Wrapper > ul.Navigation__List > div.Navigation__Right > li

These are opportunities to improve the experience of reading tabular or list data using 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
ABOUT MARVEL nav.MainFooter__PrimaryLinks > ul > li.MainFooter__Link > a
ADVERTISING nav.MainFooter__SecondaryLinks > ul > li.MainFooter__Link > a

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
●`[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
●`[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
●No element has a `[tabindex]` value greater than 0
●`[lang]` attributes have a valid value
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●All heading elements contain content.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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 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
○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.
○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.
○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.
A
Alt Text Quality
All 115 images OK
PASS
All 115 images OK
Info::
3 image(s) with alt text over 125 characters
Info::
88 decorative image(s) correctly marked
Info::
24 image(s) with good alt text
115 images 24 good alt text 88 decorative
IssueCount
too long3 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
h1 This Week's New Comi…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 It's Jeff/Aquaman In…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Your Privacy Setting…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Privacy Preference C…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 We and our partners …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Manage Consent Prefe…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Cookie List21.00:13.0:1
#000000
#FFFFFF
Pass
title Marvel.com | The Off…21.00:14.5:1
#000000
#FFFFFF
Pass
a Skip Menu21.00:14.5:1
#000000
#FFFFFF
Pass
p MARVEL UNLIMITED21.00:14.5:1
#000000
#FFFFFF
Pass
span SUBSCRIBE21.00:14.5:1
#000000
#FFFFFF
Pass
a News21.00:14.5:1
#000000
#FFFFFF
Pass
a Comics21.00:14.5:1
#000000
#FFFFFF
Pass
a Characters21.00:14.5:1
#000000
#FFFFFF
Pass
a Games21.00:14.5:1
#000000
#FFFFFF
Pass
a Movies21.00:14.5:1
#000000
#FFFFFF
Pass
a TV Shows21.00:14.5:1
#000000
#FFFFFF
Pass
a Videos21.00:14.5:1
#000000
#FFFFFF
Pass
a News21.00:14.5:1
#000000
#FFFFFF
Pass
a Comics21.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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback