Skip to content
https://zimbio.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
55
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 FIX
F
404 Error Page
Action
HTTP 403, custom page
FIX
HTTP 403, custom page
Warning::
Unexpected status code: HTTP 403
Expected HTTP 404 but received 403. This may confuse search engine crawlers.
Got: HTTP 403
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 403 ✗Page Title 403 Forbidden ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
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
Heading Hierarchy
38 headings
REVIEW
38 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 Latest Stories
  • H3 The Amika Hair Quiz – Your Shortcut to Finally Loving Your Hair Again
  • H3 Aaron Nesmith Points Last 5 Games and His Recent Performance
  • H3 Cartoon Characters We All Lowkey Relate to as Adults
  • H3 Classic TV Series Millennials Grew Up With
  • H3 The Complete Guide to Hair Extensions – Transforming Your Look with Style and Confidence
  • H3 Mustache Cartoon Characters and Their Iconic Screen Flair
  • H3 Characters That Start with K in Pop Culture and Myths
  • H3 Cartoon Characters That Start with H For Classic Laughs
  • H3 Duck Cartoon Characters And Why They Feel Familiar
  • H3 Cartoon Characters That Start with E and Why They Stay
  • H3 5 of the Best YouTube Fashion Influencers
  • H3 Black Hair Cartoon Characters Boy in Classic and New Animation
  • H3 Characters that Start with L and Why L Stays Memorable
  • H3 Random Spongebob Characters That Steal Background Moments
  • H3 Cartoon Rat Characters That Charm Animated Worlds
  • H3 Cartoon Characters that Start with N for Quick Smiles
  • H3 Grey Cartoon Characters That Shape Quiet Animation Worlds
  • H3 Thestripesblog.com Entertainment and Today’s Pop Culture Buzz
  • H3 Girl Cartoon Characters That Shaped Pop Culture for Decades
  • H3 Funny Looking Cartoon Characters Male with Odd Charm
  • H2 Celebrities
  • H2 Biography
  • H2 Net Worth
  • H2 Pop Culture
  • H2 Fashion
  • H2 Lifestyle
  • H2 Quiz
  • H3 MORE LATEST
  • H3 Random Genshin Character Generator for Fun Team Picks
  • H3 Brown Cartoon Character Charm Across Modern Animation
  • H3 White Boy Cartoon Characters in Pop Culture Chats
  • H3 Cartoon Characters with Pink Hair That Pop on Screen
  • H3 Personajes Con Orejas Grandes En Pop Culture Lore
  • H3 Cartoon with Blue Hair and Its Curious Pop-Culture Pull
  • H3 Purple and Green Characters in Pop Culture Spotlight
  • H3 Characters that Start with A Across Stories and Screens
  • H4 Zimbio-Entertainment news, the largest celebrity photo collection, movies, TV, music & polls for the pop culture obsessed

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
Alt Text Quality
1 of 66 images have issues
REVIEW
1 of 66 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
1 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
4 decorative image(s) correctly marked
Info::
61 image(s) with good alt text
66 images 61 good alt text 4 decorative 1 missing
IssueCount
missing1 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

C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 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
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 3 fail WCAG AA
REVIEW

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

17 pass 3 fail WCAG AA
title Zimbio - Entertainment News, Celebrity N…
1.06:1
#000000
on
#000038
needs 4.5:1 (normal text)
16px · top of page (header area)
span 28K
1.06:1
#000000
on
#000038
needs 4.5:1 (normal text)
16px · top of page (header area)
span 1.7M
1.06:1
#000000
on
#000038
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Latest Stories21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Celebrities21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Biography21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Net Worth21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Pop Culture21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Fashion21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Lifestyle21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Quiz21.00:13.0:1
#000000
#FFFFFF
Pass
h3 MORE LATEST21.00:13.0:1
#000000
#FFFFFF
Pass
title Zimbio - Entertainme…1.06:14.5:1
#000000
#000038
Fail
span 28K1.06:14.5:1
#000000
#000038
Fail
span 1.7M1.06:14.5:1
#000000
#000038
Fail
span 922K21.00:14.5:1
#000000
#FFFFFF
Pass
span 73K21.00:14.5:1
#000000
#FFFFFF
Pass
span 7.7K21.00:14.5:1
#000000
#FFFFFF
Pass
button ☰21.00:14.5:1
#000000
#FFFFFF
Pass
a NEWS21.00:14.5:1
#000000
#FFFFFF
Pass
a CELEBRITIES21.00:14.5:1
#000000
#FFFFFF
Pass
a BIOGRAPHY21.00:14.5:1
#000000
#FFFFFF
Pass
a NET WORTH21.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
Landmark Structure
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
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 footer

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
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" name="s">
1 controls
0 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
ssearch(Search...)placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input type="search" name="s">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

A
Lighthouse Accessibility Audits
Score 93/100 — 2 failing, 24 passed
PASS
93

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

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.col-lg-12 > div.threeposts-sec > div.single-post > a div.col-lg-12 > div.threeposts-sec > div.single-post > a
div.col-lg-12 > div.threeposts-sec > div.single-post > a div.col-lg-12 > div.threeposts-sec > div.single-post > a
div.col-lg-12 > div.threeposts-sec > div.single-post > a div.col-lg-12 > div.threeposts-sec > div.single-post > a
div.col-lg-12 > div.threeposts-sec > div.single-post > a div.col-lg-12 > div.threeposts-sec > div.single-post > a

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.

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
Go to slide 1 div.col-lg-12 > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 2 div.col-lg-12 > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 3 div.col-lg-12 > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 4 div.col-lg-12 > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 5 div.col-lg-12 > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 6 div.col-lg-12 > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 7 div.col-lg-12 > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 8 div.col-lg-12 > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet

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
●Buttons have an accessible name
●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.
●`button`, `link`, and `menuitem` elements have accessible names
●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
●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
●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
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○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.
○`[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.
○Identical links have the same purpose.
○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