Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

3 PASS 4 REVIEW 6 FIX

Alt Text Quality

Action

2 of 117 images have issues

FIX

2 of 117 images have issues

2 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

2 image-in-link without alt text

An image inside a link with no alt creates an empty link.

115 image(s) with good alt text

117 images 115 good alt text 2 missing

Issue	Count
missing	2 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-1pq8o4

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://jezebel.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://jezebel.com/manifest.json

Manifest contains invalid JSON.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 1 <nav> element(s)

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.

Link & Button Quality

3 issue(s) across 283 links and 0 buttons

REVIEW

3 issue(s) across 283 links and 0 buttons

2 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: https://www.jezebel.com/membership-account; https://www.jezebel.com/membership-account

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: https://www.jezebel.com/latest ("More")

280 link(s) with descriptive text

283 links

2 empty

1 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.jezebel.com/	<img class="js-logo" src="http…	img no alt	Add alt attribute to the image
https://www.jezebel.com/membership-accou…	(empty)	empty	Add link text or aria-label
https://www.jezebel.com/search	<img class="search-small no-la…	img no alt	Add alt attribute to the image
https://www.jezebel.com/membership-accou…	(empty)	empty	Add link text or aria-label
https://www.jezebel.com/latest	More	generic text	Replace with descriptive text
Before: More Suggested: Latest

280 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

https://www.jezebel.com/membership-account; https://www.jezebel.com/membership-account

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Generic link text like 'click here' doesn't describe the destination.

https://www.jezebel.com/latest ("More")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

Favicon & Branding

10 icon(s) detected

REVIEW

10 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 1 fail WCAG AA

REVIEW

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

19 pass 1 fail WCAG AA

title Home

3.77:1

#000000

#686868

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
title Home	3.77:1	4.5:1	#000000	#686868	Fail
a Skip to the content	16.98:1	4.5:1	#000000	#E7E7E7	Pass
a Paste	16.98:1	4.5:1	#000000	#E7E7E7	Pass
a A.V. Club	16.98:1	4.5:1	#000000	#E7E7E7	Pass
a Jezebel	8.77:1	4.5:1	#000000	#CD9AA6	Pass
a Splinter	16.98:1	4.5:1	#000000	#E7E7E7	Pass
a Daytrotter	16.98:1	4.5:1	#000000	#E7E7E7	Pass
a Latest	16.98:1	4.5:1	#000000	#E7E7E7	Pass
a Politics	20.53:1	4.5:1	#000000	#FAFDFD	Pass
a Entertainment	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Celebrities	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a In Depth	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Dirt Bag	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Spooky Stories	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Splinter	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Newsletter	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a TikTok	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Bluesky	19.26:1	4.5:1	#000000	#F5F5F5	Pass
a Instagram	16.98:1	4.5:1	#000000	#E7E7E7	Pass
a Twitter	16.98:1	4.5:1	#000000	#E7E7E7	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.

Lighthouse Accessibility Audits

Score 84/100 — 4 failing, 24 passed

REVIEW

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
Accept all `div.cmpboxbtns > span#cmpwelcomebtnyes > a.cmpboxbtn > span#cmpbntyestxt`
Settings `div.cmpboxbtns > span#cmpwelcomebtncustom > a.cmpboxbtn > span#cmpbntcustomtxt`
Privacy notice `div.cmpboxinner > div.cmpboxbtns > div.cmpmore > a.cmpmorelink`

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.title-bar > h1.large-1 > a > img.js-logo `div.title-bar > h1.large-1 > a > img.js-logo`
div.top-bar-container > div.bottom-link-row > a > img.search-small `div.top-bar-container > div.bottom-link-row > a > img.search-small`

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
div.top-bar-container > div.title-bar > h1.large-1 > a `div.top-bar-container > div.title-bar > h1.large-1 > a`
header#master-header > div.top-bar-container > div.bottom-link-row > a `header#master-header > div.top-bar-container > div.bottom-link-row > a`
header#master-header > div.top-bar-container > div.bottom-link-row > a#mobile-account-icon-link `header#master-header > div.top-bar-container > div.bottom-link-row > a#mobile-account-icon-link`

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.

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
Paste \| A.V. Club \| Jezebel \| Splinter \| Daytrotter `div.grid-container > header#master-header > div#site-bar > ul`

These are opportunities to improve the experience of reading tabular or list data using 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

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●`[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

●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.

●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

●All heading elements contain content.

○`[accesskey]` values are unique

○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

○Buttons have an accessible name

○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

○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>`.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

○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.

Landmark Structure

5 landmarks

PASS

5 landmarks

<main> landmark present

1 <nav> landmark(s) found

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

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

1 headings

PASS

1 headings

Single H1 present

H1 <img class="js-logo" src="https://www.jezebel.com/wp-content/themes/pastemagazine/img/js-logo.svg" data-eio="l" />

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#master-search	text	Search	aria-label

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