Skip to content
https://vox.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
62
GRADE
D
FIX
5
REVIEW
3
PASS
5
INFO
0
Checks
13
5 PASS 3 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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
4 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 4 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
B
Heading Hierarchy
45 headings
REVIEW
45 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 Making sense of it all:
  • H2 The context you need, when you need it
  • H2 Top links
  • H2 Recommended For You
  • H2 Even Better
  • H2 Future Perfect
  • H2 Most Popular
  • H2 Listen
  • H2 Today, Explained
  • H2 Watch
  • H2 Explainers
  • H2 Politics
  • H2 Culture
  • H2 Advice
  • H2 More News
  • H2 Pagination
  • H2 Privacy Notice
  • H3 Ways we may use your data:
  • H2 Privacy Center
  • H3 Manage Consent Preferences
  • H4 Strictly Necessary Cookies 77 partners can use this purpose
  • H5 Ensure security, prevent and detect fraud, and fix errors 77 partners can use this special purpose
  • H4 Functional Cookies 104 partners can use this purpose
  • H5 Use limited data to select advertising 79 partners can use this purpose
  • H5 Use limited data to select content 19 partners can use this purpose
  • H5 Use profiles to select personalised content 21 partners can use this purpose
  • H5 Create profiles to personalise content 24 partners can use this purpose
  • H5 Deliver and present advertising and content 76 partners can use this special purpose
  • H5 Identify devices based on information transmitted automatically 59 partners can use this feature
  • H4 Performance Cookies 34 partners can use this purpose
  • H5 Link different devices 34 partners can use this feature
  • H4 Social Media & Embedded Content
  • H4 Targeting Cookies 64 partners can use this purpose
  • H5 Actively scan device characteristics for identification 15 partners can use this special feature
  • H5 Use precise geolocation data 34 partners can use this special feature
  • H5 Match and combine data from other data sources 48 partners can use this feature
  • H4 Measure content performance 36 partners can use this purpose
  • H4 Use profiles to select personalised advertising 60 partners can use this purpose
  • H5 Create profiles for personalised advertising 63 partners can use this purpose
  • H4 Understand audiences through statistics or combinations of data from different sources 63 partners can use this purpose
  • H5 Develop and improve services 77 partners can use this purpose
  • H5 Measure advertising performance 103 partners can use this purpose
  • H4 Store and/or access information on a device 89 partners can use this purpose
  • H4 Save and communicate privacy choices 67 partners can use this special purpose
  • H3 Vendors List

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

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 TikTok ✓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
A
Landmark Structure
7 landmarks
PASS
7 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Warning::
2 of 4 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No banner (header) landmark
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER (missing!) NAV "Top Navigation" MAIN 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 127 images OK
PASS
All 127 images OK
Info::
127 image(s) with good alt text
127 images 127 good alt text
All images have appropriate alt text.
A
Form Accessibility
1 of 25 controls have issues
PASS
1 of 25 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">
Info::
24 control(s) properly labeled
25 controls
24 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#:Rkqgr96:textSearchfor/id
#emailemailEmail (required)for/id
#ot-group-id-C0003checkboxFunctional Cookiesfor/id
#ot-sub-group-id-IAB2V2_2checkboxUse limited data to select advertisingaria-label
#ot-sub-group-id-IAB2V2_11checkboxUse limited data to select contentaria-label
#ot-sub-group-id-IAB2V2_6checkboxUse profiles to select personalised contentaria-label
#ot-sub-group-id-IAB2V2_5checkboxCreate profiles to personalise contentaria-label
#ot-group-id-C0002checkboxPerformance Cookiesfor/id
#ot-group-id-C0005checkboxSocial Media & Embedded Contentfor/id
#ot-group-id-C0004checkboxTargeting Cookiesfor/id
#ot-sub-group-id-ISF2V2_2checkboxActively scan device characteristics for identificationaria-label
#ot-sub-group-id-ISF2V2_1checkboxUse precise geolocation dataaria-label
#ot-group-id-IAB2V2_8checkboxMeasure content performancefor/id
#ot-group-id-IAB2V2_4checkboxUse profiles to select personalised advertisingfor/id
#ot-sub-group-id-IAB2V2_3checkboxCreate profiles for personalised advertisingaria-label
#ot-group-id-IAB2V2_9checkboxUnderstand audiences through statistics or combinations of data from different sourcesfor/id
#ot-sub-group-id-IAB2V2_10checkboxDevelop and improve servicesaria-label
#ot-sub-group-id-IAB2V2_7checkboxMeasure advertising performancearia-label
#ot-group-id-IAB2V2_1checkboxStore and/or access information on a devicefor/id
#vendor-search-handlertextVendor 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
#g-recaptcha-response-100000textarea(none)none

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

<textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

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+
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 Making sense of it a…17.95:13.0:1
#000000
#FFF200
Pass
h2 The context you need…17.95:13.0:1
#000000
#FFF200
Pass
h2 Top links17.95:13.0:1
#000000
#FFF200
Pass
h2 Recommended For You17.95:13.0:1
#000000
#FFF200
Pass
h2 Even Better17.95:13.0:1
#000000
#FFF200
Pass
h2 Future Perfect17.95:13.0:1
#000000
#FFF200
Pass
h2 Most Popular17.95:13.0:1
#000000
#FFF200
Pass
h2 Listen17.95:13.0:1
#000000
#FFF200
Pass
h2 Today, Explained17.95:13.0:1
#000000
#FFF200
Pass
h2 Watch17.95:13.0:1
#000000
#FFF200
Pass
h2 Explainers17.95:13.0:1
#000000
#FFF200
Pass
h2 Politics17.95:13.0:1
#000000
#FFF200
Pass
h2 Culture17.95:13.0:1
#000000
#FFF200
Pass
h2 Advice17.95:13.0:1
#000000
#FFF200
Pass
h2 More News17.95:13.0:1
#000000
#FFF200
Pass
h2 Pagination17.95:13.0:1
#000000
#FFF200
Pass
h2 Privacy Notice17.95:13.0:1
#000000
#FFF200
Pass
h2 Privacy Center17.95:13.0:1
#000000
#FFF200
Pass
h3 Ways we may use your…17.95:13.0:1
#000000
#FFF200
Pass
h3 Manage Consent Prefe…17.95:13.0:1
#000000
#FFF200
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 97/100 — 2 failing, 27 passed
PASS
97

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.

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
Privacy Notice div._1ujku670 > ul._1ujku671 > li._1ujku672 > a._1ujku673
Terms of Use div._1ujku670 > ul._1ujku671 > li._1ujku672 > a._1ujku673
Platform Status div._1ujku670 > ul._1ujku671 > li._1ujku672 > a._1ujku673
Careers div._1ujku670 > ul._1ujku671 > li._1ujku672 > a._1ujku673

These items highlight common accessibility best practices.

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
Cookie 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
●`<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
●Heading elements appear in a sequentially-descending order
●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
○`<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.
○`[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