Skip to content
https://knowyourmeme.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
51
GRADE
F
FIX
7
REVIEW
3
PASS
3
INFO
0
Checks
13
3 PASS 3 REVIEW 7 FIX
F
Alt Text Quality
Action
14 of 182 images have issues
FIX
14 of 182 images have issues
Critical::
14 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
6 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
13 image(s) with alt text over 125 characters
Info::
155 image(s) with good alt text
182 images 155 good alt text 14 missing
IssueCount
missing14 image(s)
too long13 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

D
Form Accessibility
Action
5 of 5 controls have issues
FIX
5 of 5 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="submit">; <input type="submit">
Warning::
3 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="email" name="email">; <input type="search" name="q" id="search_box">; <input type="email" name="email">
5 controls
0 labeled
3 placeholder only
2 unlabeled
ControlTypeLabelMethod
emailemail(Enter Your Email)placeholder only
#search_boxsearch(Search the world's largest internet culture authority...)placeholder only
emailemail(Enter Your Email)placeholder only
inputsubmit(none)none
inputsubmit(none)none

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

<input type="submit">; <input type="submit">

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

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

<input type="email" name="email">; <input type="search" name="q" id="search_box">; <input type="email" name="email">

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

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
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #ffffff
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 ModePartial Dark Mode
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
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 Page Not Found (404) - Know Your Meme ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
5 icon(s) detected
REVIEW
5 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
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
h2 Meme Encyclopedia
1.18:1
#000000
on
#11133B
needs 3.0:1 (large text)
24px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Know Your Meme21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Meme Encyclopedia1.18:13.0:1
#000000
#11133B
Fail
h2 Status21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Images21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Videos21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Try Yourself21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Editorials21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Episodes21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Popular right now21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Today In Internet Cu…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Today In Internet Cu…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Top Entries This Mon…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Fresh Entries21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Latest Explainers21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Latest Explainers21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Top Entries This Mon…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Latest Episodes21.00:13.0:1
#000000
#FFFFFF
Pass
h2 News & Editorials21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Latest21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Heart Butt Challenge21.00:13.0: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
6 landmarks
PASS
6 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 ASIDE 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+
Heading Hierarchy
85 headings
PASS
85 headings
Info::
Single H1 present
  • H2 Meme Encyclopedia
  • H2 Status
  • H3 Heart Butt Challenge
  • H3 March 2026
  • H2 Images
  • H2 Videos All Videos
  • H3 Google Dockey
  • H3 Mark Zuckerberg Spent $88 Billion on a World With No Legs
  • H3 Warp Zone - Wario Blast: Featuring Bomberman!
  • H2 Try Yourself
  • H2 Editorials All Editorials
  • H3 What Does The 'Straight Girls VS. Lesbians Hanging Out' Meme Mean? The Reaction Image And Cliché Explained
  • H3 The Weekly Meme Roundup: 7x7=49, Eggs After 11, Real Estate Fish Edits And More
  • H3 What Does 'You The Birthday' Mean? The Viral Gen Z Slang Term Inspired By Hunxho's 'Birthday Girl' Explained
  • H2 Episodes All Episodes
  • H3 How "LARP" Went From Foam Swords to the Internet's Favorite Insult
  • H3 Why Everyone Thinks This Math Equation Is Attractive
  • H3 How "These Nuggets Ain't Ready" Became a Meme
  • H1 Know Your Meme
  • H2 Popular right now
  • H3 Heart Butt Challenge
  • H3 7x7=49
  • H3 Thank You Chainsaw Man
  • H3 Incidental 49A / Real Estate Fish Stan Edits
  • H3 Goonmobile
  • H2 Today In Internet Culture
  • H3 The Weekly Meme Roundup: 7x7=49, Eggs After 11, Real Estate Fish Edits And More
  • H3 What Does The 'Straight Girls VS. Lesbians Hanging Out' Meme Mean? The Reaction Image And Cliché Explained
  • H3 What Does 'You The Birthday' Mean? The Viral Gen Z Slang Term Inspired By Hunxho's 'Birthday Girl' Explained
  • H2 Today In Internet Culture
  • H3 The Weekly Meme Roundup: 7x7=49, Eggs After 11, Real Estate Fish Edits And More
  • H3 What Does The 'Straight Girls VS. Lesbians Hanging Out' Meme Mean? The Reaction Image And Cliché Explained
  • H3 What Does 'You The Birthday' Mean? The Viral Gen Z Slang Term Inspired By Hunxho's 'Birthday Girl' Explained
  • H2 Top Entries This Month
  • H3 Thank You Chainsaw Man
  • H3 Goonmobile
  • H3 7x7=49
  • H3 March 2026
  • H2 Fresh Entries
  • H3 Heart Butt Challenge
  • H3 Geeked Patrick
  • H3 7x7=49
  • H3 Incidental 49A / Real Estate Fish Stan Edits
  • H3 These Nuggets Ain't Ready
  • H3 Thank You Chainsaw Man
  • H3 Trending Images
  • H2 Latest Explainers
  • H3 What Does The 'Straight Girls VS. Lesbians Hanging Out' Meme Mean? The Reaction Image And Cliché Explained
  • H3 The Weekly Meme Roundup: 7x7=49, Eggs After 11, Real Estate Fish Edits And More
  • H3 What Does 'You The Birthday' Mean? The Viral Gen Z Slang Term Inspired By Hunxho's 'Birthday Girl' Explained
  • H2 Latest Explainers
  • H3 What Does The 'Straight Girls VS. Lesbians Hanging Out' Meme Mean? The Reaction Image And Cliché Explained
  • H3 The Weekly Meme Roundup: 7x7=49, Eggs After 11, Real Estate Fish Edits And More
  • H2 Top Entries This Month
  • H3 Thank You Chainsaw Man
  • H3 Goonmobile
  • H3 7x7=49
  • H3 March 2026
  • H3 Trending Images
  • H3 Top 5 Memes
  • H4 ⭐from the last week⭐
  • H3 Heart Butt Challenge
  • H3 7x7=49
  • H3 Thank You Chainsaw Man
  • H3 Incidental 49A / Real Estate Fish Stan Edits
  • H3 Goonmobile
  • H2 Latest Episodes
  • H3 How "LARP" Went From Foam Swords to the Internet's Favorite Insult
  • H3 Why Everyone Thinks This Math Equation Is Attractive
  • H3 How "These Nuggets Ain't Ready" Became a Meme
  • H3 The 'Keep On Dreaming… Denji' Meme Explained
  • H3 What Is The 'Thank You, Chainsaw Man' Meme?
  • H2 News & Editorials
  • H3 Can You Find Every Hidden Detail in These 23 Brain-Teasing Images?
  • H3 What Does The 'Straight Girls VS. Lesbians Hanging Out' Meme Mean? The Reaction Image And Cliché Explained
  • H3 The Weekly Meme Roundup: 7x7=49, Eggs After 11, Real Estate Fish Edits And More
  • H3 What Does 'You The Birthday' Mean? The Viral Gen Z Slang Term Inspired By Hunxho's 'Birthday Girl' Explained
  • H3 25 Memes To End The Week On A Good Note
  • H3 25 Uncomfortable Images With No Real Explanation
  • H2 Latest
  • H3 25 Photos To Inspire A Weekend Getaway
  • H3 25 Odd Cars Spotted Ruling The Roads
  • H3 Nine Years Ago, Jughead Declared Himself 'Weird' On 'Riverdale,' Inspiring Internet-Wide Cringe
  • H3 30 Worn Down Items That Have Stood The Test Of Time
  • H3 18 Years Later, The Internet Is Still Begging People to Come to Brazil
A
Lighthouse Accessibility Audits
Score 91/100 — 3 failing, 25 passed
PASS
91

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

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
a > div.messageBox > p.award > img a > div.messageBox > p.award > img

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
Images header#header > div.contents > div.quick-links > a
Memes header#header > div.contents > div.quick-links > a
Editorial Content header#header > div.contents > div.quick-links > a
Meme review a.card > div.content > div > button.stamp
Guides a.card > div.content > div > button.stamp
Meme a.wide-card > div.content > div > button.stamp
Meme a.wide-card > div.content > div > button.stamp
Meme a.wide-card > div.content > div > button.stamp
Meme a.wide-card > div.content > div > button.stamp
Meme a.wide-card > div.content > div > button.stamp
Meme a.wide-card > div.content > div > button.stamp
Meme a.wide-card > div.content > div > button.stamp
Collections a.wide-card > div.content > div > button.stamp
Collections a.wide-card > div.content > div > button.stamp
Meme a.wide-card > div.content > div > button.stamp
Collections a.wide-card > div.content > div > button.stamp

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
Remember a.wide-card > div.content > div.badges > button.badge
Collection a.wide-card > div.content > div.badges > button.badge
Collection a.wide-card > div.content > div.badges > button.badge
Remember a.wide-card > div.content > div.badges > button.badge
Collection a.wide-card > div.content > div.badges > button.badge
○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
●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
●`[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
●`<frame>` or `<iframe>` elements have a title
●`<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
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Image elements do not have `[alt]` attributes that are redundant text.
●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
○`<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
○`<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
○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