Skip to content
https://coub.com

Accessibility

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

F
Alt Text Quality
Action
24 of 44 images have issues
FIX
24 of 44 images have issues
Critical::
24 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
14 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
20 image(s) with good alt text
44 images 20 good alt text 24 missing
IssueCount
missing24 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

F
Form Accessibility
Action
22 of 22 controls have issues
FIX
22 of 22 controls have issues
Critical::
20 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input>; <input>; <input>; <input>; <input>; <input>; <input>; <input>; <input>; <input> (+10 more)
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="q" id="q">; <input type="text" name="q" id="q">
22 controls
0 labeled
2 placeholder only
20 unlabeled
ControlTypeLabelMethod
#qtext(Search Coub)placeholder only
#qtext(Search Coub)placeholder only
inputinput(none)none
inputinput(none)none
inputinput(none)none
inputinput(none)none
inputinput(none)none
inputinput(none)none
inputinput(none)none
inputinput(none)none
inputinput(none)none
inputinput(none)none
inputinput(none)none
inputinput(none)none
inputinput(none)none
inputinput(none)none
inputinput(none)none
inputinput(none)none
inputinput(none)none
inputinput(none)none
inputinput(none)none
inputinput(none)none

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

<input>; <input>; <input>; <input>; <input>; <input>; <input>; <input>; <input>; <input> (+10 more)

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="text" name="q" id="q">; <input type="text" name="q" id="q">

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
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::
3 navigation landmark(s) detected
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 3 <nav> element(s)
Back to Top
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.
F
Lighthouse Accessibility Audits
Action
Score 35/100 — 8 failing, 5 passed
FIX
35

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.coub-description__about__inner > div.dropdown > div.dropdown__handler > button.sb div.coub-description__about__inner > div.dropdown > div.dropdown__handler > button.sb
div.coub-description__about__inner > div.dropdown > div.dropdown__handler > button.sb div.coub-description__about__inner > div.dropdown > div.dropdown__handler > button.sb
div.coub-description__about__inner > div.dropdown > div.dropdown__handler > button.sb div.coub-description__about__inner > div.dropdown > div.dropdown__handler > button.sb
div.coub-description__about__inner > div.dropdown > div.dropdown__handler > button.sb div.coub-description__about__inner > div.dropdown > div.dropdown__handler > button.sb
div.coub-description__about__inner > div.dropdown > div.dropdown__handler > button.sb div.coub-description__about__inner > div.dropdown > div.dropdown__handler > button.sb
div.coub-description__about__inner > div.dropdown > div.dropdown__handler > button.sb div.coub-description__about__inner > div.dropdown > div.dropdown__handler > button.sb
div.coub-description__about__inner > div.dropdown > div.dropdown__handler > button.sb div.coub-description__about__inner > div.dropdown > div.dropdown__handler > button.sb
div.coub-description__about__inner > div.dropdown > div.dropdown__handler > button.sb div.coub-description__about__inner > div.dropdown > div.dropdown__handler > button.sb
div.coub-description__about__inner > div.dropdown > div.dropdown__handler > button.sb div.coub-description__about__inner > div.dropdown > div.dropdown__handler > button.sb
div.coub-description__about__inner > div.dropdown > div.dropdown__handler > button.sb div.coub-description__about__inner > div.dropdown > div.dropdown__handler > button.sb
div.coub-description__about__inner > div.dropdown > div.dropdown__handler > button.sb div.coub-description__about__inner > div.dropdown > div.dropdown__handler > button.sb
div.coub-description__about__inner > div.dropdown > div.dropdown__handler > button.sb div.coub-description__about__inner > div.dropdown > div.dropdown__handler > button.sb
div.coub-description__about__inner > div.dropdown > div.dropdown__handler > button.sb div.coub-description__about__inner > div.dropdown > div.dropdown__handler > button.sb
div.coub-description__about__inner > div.dropdown > div.dropdown__handler > button.sb div.coub-description__about__inner > div.dropdown > div.dropdown__handler > button.sb
div.coub-description__about__inner > div.dropdown > div.dropdown__handler > button.sb div.coub-description__about__inner > div.dropdown > div.dropdown__handler > button.sb
div.coub-description__about__inner > div.dropdown > div.dropdown__handler > button.sb div.coub-description__about__inner > div.dropdown > div.dropdown__handler > button.sb
div.coub-description__about__inner > div.dropdown > div.dropdown__handler > button.sb div.coub-description__about__inner > div.dropdown > div.dropdown__handler > button.sb
div.coub-description__about__inner > div.dropdown > div.dropdown__handler > button.sb div.coub-description__about__inner > div.dropdown > div.dropdown__handler > button.sb
div.coub-description__about__inner > div.dropdown > div.dropdown__handler > button.sb div.coub-description__about__inner > div.dropdown > div.dropdown__handler > button.sb
div.coub-description__about__inner > div.dropdown > div.dropdown__handler > button.sb div.coub-description__about__inner > div.dropdown > div.dropdown__handler > button.sb

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.coub-description__about__inner > div.coub-description__avatar > a > img.image div.coub-description__about__inner > div.coub-description__avatar > a > img.image
div.fullscreen-changer__animation_container > div.viewer > div.contents > img.viewer__img div.fullscreen-changer__animation_container > div.viewer > div.contents > img.viewer__img
div.coub-description__about__inner > div.coub-description__avatar > a > img.image div.coub-description__about__inner > div.coub-description__avatar > a > img.image
div.fullscreen-changer__animation_container > div.viewer > div.contents > img.viewer__img div.fullscreen-changer__animation_container > div.viewer > div.contents > img.viewer__img
div.coub-description__about__inner > div.coub-description__avatar > a > img.image div.coub-description__about__inner > div.coub-description__avatar > a > img.image
div.fullscreen-changer__animation_container > div.viewer > div.contents > img.viewer__img div.fullscreen-changer__animation_container > div.viewer > div.contents > img.viewer__img
div.coub-description__about__inner > div.coub-description__avatar > a > img.image div.coub-description__about__inner > div.coub-description__avatar > a > img.image
div.fullscreen-changer__animation_container > div.viewer > div.contents > img.viewer__img div.fullscreen-changer__animation_container > div.viewer > div.contents > img.viewer__img
div.coub-description__about__inner > div.coub-description__avatar > a > img.image div.coub-description__about__inner > div.coub-description__avatar > a > img.image
div.fullscreen-changer__animation_container > div.viewer > div.contents > img.viewer__img div.fullscreen-changer__animation_container > div.viewer > div.contents > img.viewer__img
div.coub-description__about__inner > div.coub-description__avatar > a > img.image div.coub-description__about__inner > div.coub-description__avatar > a > img.image
div.fullscreen-changer__animation_container > div.viewer > div.contents > img.viewer__img div.fullscreen-changer__animation_container > div.viewer > div.contents > img.viewer__img
div.coub-description__about__inner > div.coub-description__avatar > a > img.image div.coub-description__about__inner > div.coub-description__avatar > a > img.image
div.fullscreen-changer__animation_container > div.viewer > div.contents > img.viewer__img div.fullscreen-changer__animation_container > div.viewer > div.contents > img.viewer__img
div.coub-description__about__inner > div.coub-description__avatar > a > img.image div.coub-description__about__inner > div.coub-description__avatar > a > img.image
div.fullscreen-changer__animation_container > div.viewer > div.contents > img.viewer__img div.fullscreen-changer__animation_container > div.viewer > div.contents > img.viewer__img
div.coub-description__about__inner > div.coub-description__avatar > a > img.image div.coub-description__about__inner > div.coub-description__avatar > a > img.image
div.fullscreen-changer__animation_container > div.viewer > div.contents > img.viewer__img div.fullscreen-changer__animation_container > div.viewer > div.contents > img.viewer__img
div.coub-description__about__inner > div.coub-description__avatar > a > img.image div.coub-description__about__inner > div.coub-description__avatar > a > img.image
div.fullscreen-changer__animation_container > div.viewer > div.contents > img.viewer__img div.fullscreen-changer__animation_container > div.viewer > div.contents > img.viewer__img

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.page-menu > div.page-menu__inner > div.page-menu__item > a.-fill div.page-menu > div.page-menu__inner > div.page-menu__item > a.-fill
div.page-menu > div.page-menu__inner > div.page-menu__item > a.-fill div.page-menu > div.page-menu__inner > div.page-menu__item > a.-fill
div.page-menu > div.page-menu__inner > div.page-menu__item > a.-fill div.page-menu > div.page-menu__inner > div.page-menu__item > a.-fill
div.coub-description__about > div.coub-description__about__inner > div.coub-description__avatar > a div.coub-description__about > div.coub-description__about__inner > div.coub-description__avatar > a
div.coub-description__about > div.coub-description__about__inner > div.coub-description__avatar > a div.coub-description__about > div.coub-description__about__inner > div.coub-description__avatar > a
div.coub-description__about > div.coub-description__about__inner > div.coub-description__avatar > a div.coub-description__about > div.coub-description__about__inner > div.coub-description__avatar > a
div.coub-description__about > div.coub-description__about__inner > div.coub-description__avatar > a div.coub-description__about > div.coub-description__about__inner > div.coub-description__avatar > a
div.coub-description__about > div.coub-description__about__inner > div.coub-description__avatar > a div.coub-description__about > div.coub-description__about__inner > div.coub-description__avatar > a
div.coub-description__about > div.coub-description__about__inner > div.coub-description__avatar > a div.coub-description__about > div.coub-description__about__inner > div.coub-description__avatar > a
div.coub-description__about > div.coub-description__about__inner > div.coub-description__avatar > a div.coub-description__about > div.coub-description__about__inner > div.coub-description__avatar > a
div.coub-description__about > div.coub-description__about__inner > div.coub-description__avatar > a div.coub-description__about > div.coub-description__about__inner > div.coub-description__avatar > a
div.coub-description__about > div.coub-description__about__inner > div.coub-description__avatar > a div.coub-description__about > div.coub-description__about__inner > div.coub-description__avatar > a
div.coub-description__about > div.coub-description__about__inner > div.coub-description__avatar > a div.coub-description__about > div.coub-description__about__inner > div.coub-description__avatar > 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.

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
94 div.coub-description__views-count > div.counter > div.dropdown__handler > div
1.3K div.coub-description__views-count > div.counter > div.dropdown__handler > div
1.3K div.coub-description__views-count > div.counter > div.dropdown__handler > div
1.4K div.coub-description__views-count > div.counter > div.dropdown__handler > div
# 14 div.coub-description__badges > div.dropdown > div.dropdown__handler > button.sb
964 div.coub-description__views-count > div.counter > div.dropdown__handler > div
1.1K div.coub-description__views-count > div.counter > div.dropdown__handler > div
824 div.coub-description__views-count > div.counter > div.dropdown__handler > div
1.5K div.coub-description__views-count > div.counter > div.dropdown__handler > div
1K div.coub-description__views-count > div.counter > div.dropdown__handler > div
1.3K div.coub-description__views-count > div.counter > div.dropdown__handler > div

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
muzloRAIii div.coub__vd > div.coub__description > div.coub-description__title > h5.description__title

These are opportunities to improve keyboard navigation in your application.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.webkit html.webkit

These are opportunities to improve the interpretation of your content by users in different locales.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.webkit html.webkit

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-hidden="true"]` is not present on the document `<body>`
Document has a `<title>` element
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
`<video>` elements contain a `<track>` element with `[kind="captions"]`
`[accesskey]` values are unique
`[aria-*]` attributes match their roles
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
Deprecated ARIA roles were not used
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements use only permitted ARIA attributes
`[role]`s have all required `[aria-*]` attributes
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
`[role]` values are valid
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
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
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 a valid value for its `[lang]` attribute
`<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.
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
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.
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.
B
Heading Hierarchy
22 headings, 2 skip(s)
REVIEW
22 headings, 2 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Newest and featured coubs to discover.
  • H3 Top creators skipped
  • H5 𓆩𝕸𝔯𝕲𝔥𝖔𝔰ⱦ⚜︎꧂ skipped
  • H5 ◤𝓐𝔩𝔬𝔫𝔨✟𝔥𝔞𝔱𝔢 ◢
  • H5 Arthouse
  • H5 CrazyCatLady
  • H5 muzloRAIii
  • H5 muzloRAIii
  • H5 invasion
  • H5 Distance under the cover of the Starry Sky
  • H5 Supra MK4
  • H5 Supra MK4
  • H5 Once Again About Zombies
  • H5 gluer
  • H5 pegadora
  • H5 Rest in peace 😭🙌😇 Tung Tung Tung Sahur
  • H5 rest in peace 😭🙌😇 tung tung tung Sahur
  • H5 Apollo 11: A Hurtful Mistrust
  • H5 Аполлон-11: обидное недоверие
  • H5 Fire in My Heart~
  • H5 MovieTrailers CoD
  • H5 MovieTrailers CoD

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

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

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 Coub. Page not found 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
Web Manifest
Action
Valid manifest
REVIEW
Valid manifest
Info::
Name present: Coub Push Notification
Warning::
No 192x192 icon
A 192px icon is required for PWA installation.
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name Coub Push Notification 192×192 icon 512×512 icon Start URL / Display Mode standalone
Name Coub Push Notification Display Mode standalone
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 Newest and featured …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Top creators21.00:13.0:1
#000000
#FFFFFF
Pass
title Top сreators - vide…21.00:14.5:1
#000000
#FFFFFF
Pass
a Home21.00:14.5:1
#000000
#FFFFFF
Pass
a Popular21.00:14.5:1
#000000
#FFFFFF
Pass
a Featured21.00:14.5:1
#000000
#FFFFFF
Pass
a Best coubs21.00:14.5:1
#000000
#FFFFFF
Pass
a Stories21.00:14.5:1
#000000
#FFFFFF
Pass
a Who to follow21.00:14.5:1
#000000
#FFFFFF
Pass
a My likes21.00:14.5:1
#000000
#FFFFFF
Pass
a Bookmarks21.00:14.5:1
#000000
#FFFFFF
Pass
li Communities21.00:14.5:1
#000000
#FFFFFF
Pass
div Animals & Pets21.00:14.5:1
#000000
#FFFFFF
Pass
div Art & Design21.00:14.5:1
#000000
#FFFFFF
Pass
div Auto & Technique21.00:14.5:1
#000000
#FFFFFF
Pass
div Blogging21.00:14.5:1
#000000
#FFFFFF
Pass
div Cartoons21.00:14.5:1
#000000
#FFFFFF
Pass
div Celebrity21.00:14.5:1
#000000
#FFFFFF
Pass
div Dance21.00:14.5:1
#000000
#FFFFFF
Pass
div Fashion & Beauty21.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